From: Mark Schouten via pve-user <pve-user@lists.proxmox.com>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Cc: Mark Schouten <mark@tuxis.nl>, Alexandre de Rumier <aderumier@odiso.com>
Subject: [PVE-User] Volume chain snapshotting
Date: Mon, 24 Nov 2025 14:42:16 +0000 [thread overview]
Message-ID: <mailman.39.1763997186.399.pve-user@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4794 bytes --]
From: "Mark Schouten" <mark@tuxis.nl>
To: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Cc: "Alexandre de Rumier" <aderumier@odiso.com>
Subject: Volume chain snapshotting
Date: Mon, 24 Nov 2025 14:42:16 +0000
Message-ID: <em9f436164-dd83-4d7d-95aa-383aa205d080@4f26fb63.com>
Hi all,
Since PVE9, we have Volume Chain Snapshotting. The documentation states:
'Enabling or disabling this flag only affects newly created virtual disk
volumes.’
Two questions:
1: Are there plans to make it possible to convert existing LVM Backed
storages with images that already exist? Or is there an idea how we can
convert existing images?
2: Why is this in status ’Technology Preview’? What are the risks that
are in the back of the heads of the developers? Or is it mainly ’there
might be bugs, but we expect dataconsistency to be OK’?
Thanks,
—
Mark Schouten
CTO, Tuxis B.V.
+31 318 200208 / mark@tuxis.nl
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next reply other threads:[~2025-11-24 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 14:42 Mark Schouten via pve-user [this message]
2025-11-24 15:49 ` g.husson_proxmox-pve-user--- via pve-user
2025-11-25 9:41 ` Fiona Ebner
[not found] <em9f436164-dd83-4d7d-95aa-383aa205d080@4f26fb63.com>
2025-11-24 15:31 ` DERUMIER, Alexandre via pve-user
2025-11-25 9:34 ` Fiona Ebner
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.39.1763997186.399.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=aderumier@odiso.com \
--cc=mark@tuxis.nl \
/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