public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
* [PATCH v2 docs] storage: note that qcow2 internal snapshots are inefficient
@ 2026-03-23 11:06 Fiona Ebner
  2026-03-23 11:59 ` Maximiliano Sandoval
  0 siblings, 1 reply; 2+ messages in thread
From: Fiona Ebner @ 2026-03-23 11:06 UTC (permalink / raw)
  To: pve-devel

It's a commonly reported issue, often also 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>
---

Changes in v2:
* add recommendation about doing the operations offline

 pvesm.adoc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/pvesm.adoc b/pvesm.adoc
index c634f6b..97feca0 100644
--- a/pvesm.adoc
+++ b/pvesm.adoc
@@ -88,6 +88,12 @@ 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. If your setup is affected, create and remove snapshots while the VM is
+shut down, expecting a long task duration.
 
 ^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





^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH v2 docs] storage: note that qcow2 internal snapshots are inefficient
  2026-03-23 11:06 [PATCH v2 docs] storage: note that qcow2 internal snapshots are inefficient Fiona Ebner
@ 2026-03-23 11:59 ` Maximiliano Sandoval
  0 siblings, 0 replies; 2+ messages in thread
From: Maximiliano Sandoval @ 2026-03-23 11:59 UTC (permalink / raw)
  To: Fiona Ebner; +Cc: pve-devel

Fiona Ebner <f.ebner@proxmox.com> writes:

> It's a commonly reported issue, often also 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>
> ---
>
> Changes in v2:
> * add recommendation about doing the operations offline
>
>  pvesm.adoc | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/pvesm.adoc b/pvesm.adoc
> index c634f6b..97feca0 100644
> --- a/pvesm.adoc
> +++ b/pvesm.adoc
> @@ -88,6 +88,12 @@ 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. If your setup is affected, create and remove snapshots while the VM is
> +shut down, expecting a long task duration.
>  
>  ^3^: It is possible to use LVM on top of an iSCSI or FC-based storage.
>  That way you get a `shared` LVM storage

Looks good to me.

Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>

-- 
Maximiliano




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-03-23 12:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-03-23 11:06 [PATCH v2 docs] storage: note that qcow2 internal snapshots are inefficient Fiona Ebner
2026-03-23 11:59 ` Maximiliano Sandoval

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal