No description
a3a9a2ab19
Without the 'discard-no-unref', a qcow2 file can grow beyond what 'qemu-img measure' reports, because of fragmentation. This can lead to IO errors with qcow2 on top of LVM storages, where the containing LV is allocated with that size. Guard enabling the option with having 'snapshot-as-volume-chain' in the storage configuration for now. Enabling it always should be evaluated a bit more and tested on different storages. It is a runtime-only option just affecting how referencing clusters is handled during discard in qcow2 and nothing else, so it is also fine for existing images and migration streams. While 'snapshot-as-volume-chain' is not the perfect proxy, as that's not only for LVM, it's an experimental feature that covers the LVM case and it seems like a nice fit to try out the new option on file-based storages too. Suggested-by: Alexandre Derumier <alexandre.derumier@groupe-cyllene.com> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com> |
||
|---|---|---|
| debian | ||
| src | ||
| .gitignore | ||
| Makefile | ||