On 31.05.2017 19:10, Richard W.M. Jones wrote:
On Wed, May 31, 2017 at 06:54:33PM +0300, Pavel Butsykin wrote:
It is assumed that the user has already made a preparatory with the
image:
1. freeing space at the end of the image
2. reducing the last partition on the disk
3. rebuilding fs
Only after these steps, the user can reduce the image by qemu-img.
It's tricky with GPT, as GPT puts a second copy of the header in the
last few sectors of the disk. I always advise people to use trim (or
virt-sparsify) instead of trying to adjust virtual disk size.
virt-sparsify is a very useful utility, I use it too :) I agree that the
trim is much better if the goal is only to free up space on the host
disk. But there's another goal is to limit further growth of the image.
Nevertheless I don't think we should prevent shrinking qcow2 virtual
size. It's likely useful to someone.
Rich.
