Report this

What is the reason for this report?

Mounted Volume reports a different total size than DO and lsblk

Posted on April 18, 2023

Some weeks ago I resize a volume from 200G to 400G, however, after mounting the volume df -h reports a different size compared to the output of lsblk:

root@nextcloud-ubuntu-22-10:~# mount -o discard,defaults,noatime /dev/disk/by-id/scsi-0DO_Volume_volume-nyc1-01 /mnt/volume_nyc1_01
root@nextcloud-ubuntu-22-10:~# lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0     7:0    0  44.5M  1 loop /snap/certbot/2913
loop1     7:1    0 116.8M  1 loop /snap/core/14946
loop2     7:2    0  63.2M  1 loop /snap/core20/1623
loop4     7:4    0  53.2M  1 loop /snap/snapd/18933
loop5     7:5    0  49.8M  1 loop /snap/snapd/18596
loop6     7:6    0    73M  1 loop /snap/core22/607
loop7     7:7    0  63.3M  1 loop /snap/core20/1852
loop8     7:8    0   163M  1 loop /snap/lxd/24643
loop9     7:9    0 164.3M  1 loop /snap/lxd/24758
sda       8:0    0   400G  0 disk /mnt/volume_nyc1_01
vda     252:0    0    60G  0 disk 
├─vda1  252:1    0  59.9G  0 part /
├─vda14 252:14   0     4M  0 part 
└─vda15 252:15   0   106M  0 part /boot/efi
vdb     252:16   0   474K  1 disk 
root@nextcloud-ubuntu-22-10:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           795M  1.6M  794M   1% /run
/dev/vda1        58G  9.5G   49G  17% /
tmpfs           3.9G     0  3.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/vda15      105M  6.1M   99M   6% /boot/efi
overlay          58G  9.5G   49G  17% /var/lib/docker/overlay2/1f39e60670311eb27761adb1e9e58082a3e22e3ad5c13f0fd720506efd9db8a5/merged
overlay          58G  9.5G   49G  17% /var/lib/docker/overlay2/5a81b10e3777a7388b0ce12dba4b404c3de4a44a6caf4f657a1cdf9a9bf04977/merged
overlay          58G  9.5G   49G  17% /var/lib/docker/overlay2/fb855e28ecb6c25b1975eeab2010dfb562912f3cf69af4b412b8080eb9844654/merged
overlay          58G  9.5G   49G  17% /var/lib/docker/overlay2/1fdf016c1a5552b946f3a02e624617b5a415ad587d9782c372ad5d66c35b040f/merged
overlay          58G  9.5G   49G  17% /var/lib/docker/overlay2/d17a4792dc72c43153bb8bc90c97fb15cae6b54a11e6e5e9085d1559fbaa06cc/merged
overlay          58G  9.5G   49G  17% /var/lib/docker/overlay2/a423edd6beaf2679c8ce19139121fa9f6f76f7884a34f3ce5b3edf312825a64c/merged
tmpfs           795M  4.0K  795M   1% /run/user/0
/dev/sda        149G   86G   56G  61% /mnt/volume_nyc1_01

Sadly, my Nextcloud instance reports lack of free space, which is not true since the volume has enough room. How can I fix this?



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
0

Accepted Answer

Hi there,

Once you resize your block storage volume, you would also need to expand the filesystem in order to be able to use the new space.

You can do that by following the steps here:

https://docs.digitalocean.com/products/volumes/how-to/increase-size/

Hope that this helps!

Best,

Bobby

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.