[PVE-User] Image resize/missing space

[Shain Miley]

Hello,

I just noticed that there appears to be some missing space (at least as reported using df from inside our guests).  The amount missing seems to increase, the more you increase the .raw image size.

I was hoping someone on the list might be able to comment as to whether or not this is expected behavior (and why).


1)start off with a 24GB raw image:

root at proxmox1:/# qemu-img info vm-212-disk-1.raw 
image: vm-212-disk-1.raw
file format: raw
virtual size: 24G (25769803776 bytes)
disk size: 900M


root at template:~# df -h
Filesystem            Size   Used   Avail  Use%   Mounted on
/dev/vda1              23G  732M   21G   4% /



2)resize the container to 200GB

root at proxmox1:/# qm stop 212

root at proxmox1:/# qemu-img resize vm-212-disk-1.raw +176GB
Image resized.

root at proxmox1:/# qemu-img info vm-212-disk-1.raw 
image: vm-212-disk-1.raw
file format: raw
virtual size: 200G (214748364800 bytes)
disk size: 900M


3)resize the partition

root at proxmox1:/# cfdisk vm-212-disk-1.raw

root at template:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/vda1              23G  733M   21G   4% /



4)do an online resize of vda

root at template:~# resize2fs /dev/vda1
resize2fs 1.41.12 (17-May-2010)
Filesystem at /dev/vda1 is mounted on /; on-line resizing required
old desc_blocks = 2, new_desc_blocks = 13
Performing an on-line resize of /dev/vda1 to 52428208 (4k) blocks.
The filesystem on /dev/vda1 is now 52428208 blocks long.

5)recheck disk space and there appears to be 9GB of missing space :-(

root at template:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/vda1             197G  749M  187G   1% /

Thanks in advance,

Shain





Shain Miley | Manager of Systems and Infrastructure, Digital Media | smiley at npr.org | 202.513.3649