From: "DERUMIER, Alexandre via pve-devel" <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
Subject: Re: [pve-devel] [PATCH qemu-server 6/6] fix #6543: use qcow2 'discard-no-unref' option when using snapshot-as-volume-chain
Date: Thu, 24 Jul 2025 18:01:36 +0000 [thread overview]
Message-ID: <mailman.101.1753380109.367.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <20250724135956.112138-7-f.ebner@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 12988 bytes --]
From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server 6/6] fix #6543: use qcow2 'discard-no-unref' option when using snapshot-as-volume-chain
Date: Thu, 24 Jul 2025 18:01:36 +0000
Message-ID: <5bba0756ec4cf006f5a5d26afb0340bcf7fd3d68.camel@groupe-cyllene.com>
Thanks Fiona !
>>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.
I'll try to do test with qcow2 files on nfs after my holiday. It should
help with qcow2 fragmentation indeed.
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-24 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 13:59 [pve-devel] [PATCH-SERIES qemu-server 0/6] blockdev and snapshot-as-volume-chain on LVM fixes Fiona Ebner
2025-07-24 13:59 ` [pve-devel] [PATCH qemu-server 1/6] blockdev: helper to add common options Fiona Ebner
2025-07-24 13:59 ` [pve-devel] [PATCH qemu-server 2/6] blockdev: fix discard Fiona Ebner
2025-07-24 13:59 ` [pve-devel] [PATCH qemu-server 3/6] tests: image convert: avoid hard-coded VM ID in result Fiona Ebner
2025-07-24 13:59 ` [pve-devel] [PATCH qemu-server 4/6] tests: image convert: properly set snapshot-as-volume-chain option Fiona Ebner
2025-07-24 13:59 ` [pve-devel] [PATCH qemu-server 5/6] tests: image convert: add tests where storages with 'snapshot-as-volume-chain' are the target Fiona Ebner
2025-07-24 13:59 ` [pve-devel] [PATCH qemu-server 6/6] fix #6543: use qcow2 'discard-no-unref' option when using snapshot-as-volume-chain Fiona Ebner
2025-07-24 18:01 ` DERUMIER, Alexandre via pve-devel [this message]
2025-07-25 7:38 ` Fabian Grünbichler
2025-07-25 8:24 ` Fiona Ebner
2025-07-25 7:40 ` [pve-devel] [PATCH-SERIES qemu-server 0/6] blockdev and snapshot-as-volume-chain on LVM fixes Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.101.1753380109.367.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox