Hello, I have a number of VM images in sparse NOCOW files, with:
# du -B M -sc * ... 46030M total and: # du -B M -sc --apparent-size * ... 96257M total But despite there being nothing else on the filesystem and no snapshots, # df -B M . ... 1M-blocks Used Available Use% ... ... 710192M 69024M 640102M 10% ... The filesystem itself is: Data, RAID0: total=70.00GiB, used=67.38GiB System, RAID0: total=64.00MiB, used=16.00KiB Metadata, RAID0: total=1.00GiB, used=7.03MiB GlobalReserve, single: total=16.00MiB, used=0.00B So there's about 23 GB of overhead to store only 46 GB of data. I vaguely remember the reason is something along the lines of the need to keep around old extents, which are split in the middle when CoWed, but the entire old extent must be also kept in place, until overwritten fully. These NOCOW files are being snapshotted for backup purposes, and the snapshot is getting removed usually within 30 minutes (while the VMs are active and writing to their files), so it was not pure NOCOW 100% of the time. Main question is, can we have this recorded/explained in the wiki in precise terms (perhaps in Gotchas), or is there maybe already a description of this issue on it somewhere? I looked through briefly just now, and couldn't find anything similar. Only remember this being explained once on the mailing list a few years ago. (Anyone has a link?) Also, any way to mitigate this and regain space? Short of shutting down the VMs, copying their images into new files and deleting old ones. Balance, defragment or "fallocate -d" (for the non-running ones) do not seem to help. What's unfortunate is that "fstrim -v" only reports ~640 GB as having been trimmed, which means the overhead part will be not freed by TRIM if this was on top of thin-provisioned storage either. -- With respect, Roman
