incorrect disk size

[Jakub_Mitura]

Hello I had run out of memory in my additional disk attached to VM, I increased the space available from 528Gb to 610 Gb but from ssh terminal I see that system did not seen the diffrence and still show old size

below disk as dev/sdb

```

root@vm-nvidia-gpu-v100-vm2-vm:/mnt# df -H
Filesystem Size Used Avail Use% Mounted on
/dev/root 323G 41G 282G 13% /
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 3.2G 1.4M 3.2G 1% /run
tmpfs 5.3M 0 5.3M 0% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/loop0 59M 59M 0 100% /snap/core18/2409
/dev/loop1 59M 59M 0 100% /snap/core18/2538
/dev/loop2 66M 66M 0 100% /snap/core20/1593
/dev/loop3 66M 66M 0 100% /snap/core20/1611
/dev/loop5 319M 319M 0 100% /snap/google-cloud-sdk/268
/dev/loop6 71M 71M 0 100% /snap/lxd/21835
/dev/loop7 72M 72M 0 100% /snap/lxd/22753
/dev/sda15 110M 5.5M 104M 5% /boot/efi
/dev/loop8 50M 50M 0 100% /snap/snapd/16010
/dev/loop9 50M 50M 0 100% /snap/snapd/16292
/dev/sdb 528G 528G 0 100% /mnt/disks/sdb
tmpfs 3.2G 8.2k 3.2G 1% /run/user/1003
tmpfs 3.2G 8.2k 3.2G 1% /run/user/1002
overlay 323G 41G 282G 13% /var/lib/docker/overlay2/c5765e2d3e095c9be3fc91a5b3ff81be091f62fe655f2a00766eab3ff29a829a/merged
/dev/loop10 310M 310M 0 100% /snap/google-cloud-sdk/270

```

I tried to reset instance, I waited 24 h for changes to apply... but still it do not help.

Thanks for help !

[emelgoza · Accepted solution]

Hello, Jakub,

Thanks for contacting us.

Regarding the issue that you are facing about resizing the storage of one of your VMs, I would like to mention that this probably happened because it's necessary to resize the OS capacity. There are multiple options, and some of them are: 

1. You could include commands at the startup script, but that would depend on your configuration.
2. You can check the link to directly resize the OS VM. 
3. If the previous option does not work, you could detach the disk from the instance, then attach it to an instance that is working properly, resize the partition and/or check any possible conflict in the tmp folders and reattach the disk to the instance (this option should be considered a last resort, I strongly recommend following the 2nd one).

By the way, I recommend performing a snapshot before proceeding. After the snapshot, please reboot the instance, and the disk should be expanded automatically. Let me know your results.

Best regards,

Erick