From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] lvm: add note about requirements of snapshot-as-volume-chains
Date: Fri, 25 Jul 2025 11:52:08 +0200 [thread overview]
Message-ID: <20250725095208.249266-1-f.gruenbichler@proxmox.com> (raw)
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
Notes:
not sure whether we want to also add a note suggesting to (heavily)
overprovision the LUN/backing device on the storage side, so that there is
enough "space" for creating snapshots?
pve-storage-lvm.adoc | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc
index 6928330..c508fe1 100644
--- a/pve-storage-lvm.adoc
+++ b/pve-storage-lvm.adoc
@@ -57,8 +57,7 @@ snapshot's name and starts a new volume backed by the snapshot.
+
A volume based on a snapshot references its parent snapshot volume as its
backing volume and records only the differences to that backing volume.
-Snapshot volumes are currently thick-provisioned LVM logical volumes, but the
-underlying block storage may provide thin provisioning.
+Snapshot volumes are currently thick-provisioned LVM logical volumes.
+
This design avoids issues with native LVM snapshots, such as significant
input/output (I/O) penalties and unexpected, dangerous behavior when running out
@@ -74,6 +73,11 @@ functionality.
The snapshot functionality is managed by the PVE storage system.
+
Enabling or disabling this flag only affects newly created virtual disk volumes.
++
+For efficient support of `snapshot-as-volume-chain`, the backing storage must
+support thin-provisioning and discard. Each snapshot will appear to use the
+full volume size on the PVE side, but the actual space usage on the underlying
+storage will be smaller if those requirements are met.
.Configuration Example (`/etc/pve/storage.cfg`)
----
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-25 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 9:52 Fabian Grünbichler [this message]
2025-07-27 12:03 ` DERUMIER, Alexandre via pve-devel
2025-07-28 8:27 ` 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=20250725095208.249266-1-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.