Hi all, The restore from a backup is not working properly when dealing with sparse volumes.
VM created with 4G disk sparse Before backup: Size 1.09G Backup: Size 527M Restore: Size 4.03G This indicates that the resulting image is padded with 'NULLs' up to configured disk size. The same observation goes for cloning and moving images (storage migrate). The size for the destination image always reflects the size from configuration loosing sparse feature. Cloning and storage migration could perhaps benefit from the option -S to qemu-img (-S means create a sparse image during conversion). -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael <at> rasmussen <dot> cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir <at> datanom <dot> net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir <at> miras <dot> org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- /usr/games/fortune -es says: There is more simplicity in the man who eats caviar on impulse than in the man who eats Grape-Nuts on principle. -- G. K. Chesterton
signature.asc
Description: PGP signature
_______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
