Storage not showing true size

[jpodner]

Hello,

My Ubuntu server has over 500 GBs and Cloudron seems to be only using 100gbs and I was wondering how I can change that

I’ve looked at resizing options on your website and it does not seem to help much.

I maybe doing something dumb here which is 100% possible. italicised text

[girish]

@jpodner Can you post your df -h output? The size displayed there is all that is available to Cloudron . Also, I assume you are getting the 100G number from the system graphs?

[jpodner]

@girish Here is my output with that command. To answer your question about where I am getting this. Yes I'm getting in from the graph inside the web GUI. The size of the hard drive I gave my VM was 525Gb

Last login: Tue Jan 31 12:32:11 2023 from 192.168.5.157
marquette@cloudron:~$ df -h
Filesystem                         Size  Used Avail Use% Mounted on
tmpfs                              1.6G  2.0M  1.6G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   98G   19G   75G  21% /
tmpfs                              7.9G     0  7.9G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
/dev/sda2                          2.0G  245M  1.6G  14% /boot
tmpfs                              1.6G  4.0K  1.6G   1% /run/user/1000
192.168.5.81:/export/cloudron       48G  1.8G   46G   4% /mnt/cloudronbackup

[girish]

@jpodner said in Storage not showing true size:

/dev/mapper/ubuntu--vg-ubuntu--lv 98G 19G 75G 21% /

The above is where the 100G comes from. I suspect you have not resized the filesystem to take up the full disk size.

You have to use something like resize2fs - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/storage_administration_guide/ext4grow . So, I think resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv

[jpodner]

@girish I've tried that and it outputs the following command

marquette@cloudron:~$ sudo resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv
resize2fs 1.46.5 (30-Dec-2021)
The filesystem is already 26214400 (4k) blocks long.  Nothing to do!

[girish]

@jpodner Can you also provide lsblk output ?

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recognize-expanded-volume-linux.html also has a good write up. May I ask where you have this hard disk ? Is this a home server or some VPS provider?

[jpodner]

@girish This is hosted on-prem in a Vmware environment

lsblk output

marquette@cloudron:~$ sudo lsblk
[sudo] password for marquette:
NAME                      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0                       7:0    0  79.9M  1 loop /snap/lxd/22923
loop2                       7:2    0  61.9M  1 loop /snap/core20/1405
loop3                       7:3    0  49.8M  1 loop /snap/snapd/17950
loop4                       7:4    0  63.3M  1 loop /snap/core20/1778
loop5                       7:5    0 111.9M  1 loop /snap/lxd/24322
sda                         8:0    0   525G  0 disk
├─sda1                      8:1    0     1M  0 part
├─sda2                      8:2    0     2G  0 part /boot
└─sda3                      8:3    0   523G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0   100G  0 lvm  /
sr0                        11:0    1  1024M  0 rom

[girish]

@jpodner thanks. Unfortunately, I don't really know much about LVM. From the output it's apparent that the lvm (/) needs to be resized to the actual partition size. On the internet, there's lots of articles of lvresize/pvresize etc. I think you have to investigate more in that direction. Maybe vmware has tools as well to help out here.

(But to address the original issue, Cloudron is only reporting what linux is reporting and what has been made available. We don't have disk/lvm utilities, this is outside Cloudron's control).