* [pve-devel] [PATCH docs] storage: note that qcow2 internal snapshots are inefficient
@ 2025-11-28 15:56 Fiona Ebner
0 siblings, 0 replies; only message in thread
From: Fiona Ebner @ 2025-11-28 15:56 UTC (permalink / raw)
To: pve-devel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-11-28 15:56 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-11-28 15:56 [pve-devel] [PATCH docs] storage: note that qcow2 internal snapshots are inefficient Fiona Ebner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox