On 27/04/11 21:56, Kevin Wolf wrote:
When you don't have a backing file, leaving an cluster unallocated means
that it's zero. When you have a backing file, it could be anything. So
if qemu-img convert wanted to save this space, it would have to read
from the backing file and leave the cluster unallocated if it reads as zero.
This is something that qemu-img doesn't do today.
... which would explain the behaviour I'm seeing then. Great, time to
dust off my Kernighan & Ritchie I guess.
Thanks for the explanation.
Regards,
Brad
