Actual disk usage and vzdump size is way different

Bivas Mandal

Active Member
Jun 12, 2018
1
0
41
35
Hello,

Not sure if this is correct behavior.

VM 101
Assigned disk
Code:
$ sudo qm config 101 | grep ^scsi0
scsi0: data:101/vm-101-disk-1.qcow2,size=53452M

Actual disk usage
Code:
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        51G   20G   32G  38% /

vzdump size
Code:
28G    vzdump-qemu-101-2018_09_26-13_30_02.vma.lzo

+++++++++++++++++++++++++++++++++++++++++++++++

VM 105
Assigned disk
Code:
$ sudo qm config 105 | grep ^scsi0
scsi0: data:105/vm-105-disk-1.qcow2,size=27852M

Actual disk usage
Code:
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        27G   19G  7.5G  72% /

vzdump size
Code:
9.3G    vzdump-qemu-105-2018_09_26-13_45_13.vma.lzo


If you notice closely, the vzdump size is less then actual disk usage for VM 105, which is not the case with VM 101

Both VM is pretty much identical in term of configuration
Ubuntu Cloud image 16.04
pve-manager 5.2-1

Any input would be greatly appreciated.
 
this depends greatly on the data, since both backups are compressed (note the '.lzo' ending) with LZO
so if your data is easy to compress, the image will be smaller

on the other hand, if your vm writes many/big files and deletes them afterwards (and does not trigger an fstrim) the blocks on the disk still look like they are used, so they will be backed up
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!