From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] storage: note that qcow2 internal snapshots are inefficient
Date: Fri, 28 Nov 2025 16:56:09 +0100 [thread overview]
Message-ID: <20251128155628.223336-1-f.ebner@proxmox.com> (raw)
It's a commonly reported issue, most recently again in the enterprise
support, that taking or removing snapshots of large qcow2 files on
file-based network storages can take a very long time. Add a note
about this limitation.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
pvesm.adoc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/pvesm.adoc b/pvesm.adoc
index d36baf8..165b446 100644
--- a/pvesm.adoc
+++ b/pvesm.adoc
@@ -88,6 +88,11 @@ block device functionality.
^2^: On file based storages, snapshots are possible with the 'qcow2' format,
either using the internal snapshot function, or snapshots as volume chains^4^.
+Creating and deleting internal 'qcow2' snapshots will block a running VM and
+is not an efficient operation. The performance is particularly bad with network
+storages like NFS. On some setups and for large disks (multiple hundred GiB or
+TiB sized), these operations may take several minutes, or in extreme cases, even
+hours.
^3^: It is possible to use LVM on top of an iSCSI or FC-based storage.
That way you get a `shared` LVM storage
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-11-28 15:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251128155628.223336-1-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.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