N Notaria New Member Sep 1, 2026 1 0 1 Saturday at 18:18 #1 cuando copio una VM (vm-100-disk-0.qcow2) en proxmox de pesar 900GB pasa a pesar 4.5TB
C cyruspy Renowned Member Jul 2, 2013 207 32 93 Saturday at 21:50 #2 Notaria said: cuando copio una VM (vm-100-disk-0.qcow2) en proxmox de pesar 900GB pasa a pesar 4.5TB Click to expand... Might be a sparse file thing?
Notaria said: cuando copio una VM (vm-100-disk-0.qcow2) en proxmox de pesar 900GB pasa a pesar 4.5TB Click to expand... Might be a sparse file thing?
K kawano-y New Member Jul 15, 2025 22 3 3 Yesterday at 11:43 #3 Yes, it could be related to sparse files. You can compare the apparent size and the actual disk usage with: ls -lh vm-100-disk-0.qcow2 du -h vm-100-disk-0.qcow2
Yes, it could be related to sparse files. You can compare the apparent size and the actual disk usage with: ls -lh vm-100-disk-0.qcow2 du -h vm-100-disk-0.qcow2
C cyruspy Renowned Member Jul 2, 2013 207 32 93 Yesterday at 12:42 #4 kawano-y said: Yes, it could be related to sparse files. You can compare the apparent size and the actual disk usage with: ls -lh vm-100-disk-0.qcow2 du -h vm-100-disk-0.qcow2 Click to expand... That being said, and doing some guesswork @Notaria, FAT32 doesn't support sparse files. Check which filesystem are you using in the destination disk. Reactions: kawano-y
kawano-y said: Yes, it could be related to sparse files. You can compare the apparent size and the actual disk usage with: ls -lh vm-100-disk-0.qcow2 du -h vm-100-disk-0.qcow2 Click to expand... That being said, and doing some guesswork @Notaria, FAT32 doesn't support sparse files. Check which filesystem are you using in the destination disk.
