A disk on Linode Web could not be resized
I am trying to resize a disk on my Linode ('Web') so that I can create an image of it. The Linode is a 1 CPU Core / 25 GB Storage / 1 GB RAM.
When running df -h, I get the following:
Filesystem Size Used Avail Use% Mounted on
udev 448M 0 448M 0% /dev
tmpfs 99M 980K 98M 1% /run
/dev/sda 24G 4.4G 20G 19% /
tmpfs 491M 0 491M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 491M 0 491M 0% /sys/fs/cgroup
/dev/loop0 70M 70M 0 100% /snap/lxd/17124
/dev/loop1 56M 56M 0 100% /snap/core18/1248
/dev/loop2 56M 56M 0 100% /snap/core18/1845
/dev/loop3 71M 71M 0 100% /snap/lxd/19462
/dev/loop4 33M 33M 0 100% /snap/snapd/12561
/dev/loop5 33M 33M 0 100% /snap/snapd/10425
tmpfs 99M 0 99M 0% /run/user/1001
However, after shutting down my server, when I try to resize to 6000 MB, I get the following error:
A disk on Linode Web could not be resized by birchlake. (Failed after 9 seconds)
7 Replies
6000 Mb = 600 Gb which is greater than your plan allows. If you need 600 Gb, you can buy it extra for as long as you need it & then release it. The extra charge will be small for a short amount of time.
-- sw
6000 Mb = 600 Gb which is greater than your plan allows
Sorry @stevewi, 6000 MB = 6GB.
https://www.google.co.uk/search?q=6000+mb
Looking at the disk usage output, there is a bit over 4.4GB being used (by my calculations I’d say 4825 MB) so I’m not sure why this is failing.
Have you tried support?
Having same error. After upgrading plan from 1GB RAM Nanode to 2GB RAM Linode, I encountered failure in resizing the the disk from 25600MB to 51200MB. Tried power off the linode then do resizing but still failed.
Thanks, all. I contacted support and they told me the usage is being reported as 7411MB which is why the resize is failing. I'm waiting to hear back on why there's a discrepancy in size reported.
I contacted support and they told me the usage is being reported as 7411MB
Wow, that’s getting on for a 100% discrepancy.
I’d be intrigued to know the outcome of this.
mpeters
Linode Staff
When an image is created, it is sized based on the total number of inodes needed to create the image. Individual files smaller than the size of a single inode will still occupy the space needed, and can create the discrepancy you're seeing between your DF output and the image size.
You can compare the difference by running both df -h and df -ih on your Linode.
Some additional information on this can be found within the following Community Questions: