On Fri, Sep 22, 2017 at 12:39:24PM +0300, Pavel Butsykin wrote: > Now after shrinking the qcow2 image, at the end of the image file, there might > be a tail that probably will never be used. Although it will not bring any > tangible benefit, we can cut the tail if it is. Yes, it will not free up disk > space, but if the blocks were be allocated sequentially and the image is not > heavily fragmented then the virtual size of the image file will be > commensurate > with the real size. It also doesn't look like a great plus.. Well, at least we > can discuss it.
If the block backend has discard support enabled, can't we get the tail to be discarded rather than merely truncated ? Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
