Red Hat Bugzilla – Bug 887909
PRD33 - auto shrink qcow volumes on merge of block volumes
Last modified: 2016-02-10 15:26:37 EST
Description of problem:
On merge of qcow volumes on block the new volume after merge has the size that is the sum of all merged volumes.
This size is unnecessarily big, since the volumes are in qcow2 format.
The fix should optimize the size of the new volume to be the minimal size used by the data on disk.
steps to reproduce:
1. create a vm with a thin provisioned disk.
2. create a snapshot
3. delete the snapshot
Fede, please add dependency on qemu-img bug as the above patch cannot be merged until qemu fully supports the required functionality.
*** Bug 974124 has been marked as a duplicate of this bug. ***
5374bce1-906a-4389-bfdb-06d1cc00d442::DEBUG::2013-08-13 17:57:52,955::blockVolume::331::Storage.Volume::(shrinkToOptimalSize) Shrink qcow volume: d7700983-b3ca-42a3-88b6-5d20e4e51f35 to : 1073741824.0 bytes
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.