From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] lvm storage: state snapshot-as-volume-chain is a technology preview
Date: Thu, 4 Sep 2025 14:52:01 +0200 [thread overview]
Message-ID: <0708d5d2-a59e-4958-b409-4d8bdc01502e@proxmox.com> (raw)
In-Reply-To: <20250829122442.390127-1-m.sandoval@proxmox.com>
Am 29.08.25 um 14:24 schrieb Maximiliano Sandoval:
> This matches the description in the Changelog for Proxmox VE 9 [1].
>
> [1] https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.0
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> pve-storage-lvm.adoc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc
> index 6928330..fc2a8ef 100644
> --- a/pve-storage-lvm.adoc
> +++ b/pve-storage-lvm.adoc
> @@ -75,6 +75,8 @@ The snapshot functionality is managed by the PVE storage system.
> +
> Enabling or disabling this flag only affects newly created virtual disk volumes.
>
> +WARNING: Snapshots as volume chains are currently a **technology preview** in {pve}.
can we make this a note? It's not like tech. preview's are experimental
and totally unsupported after all.
Tangentially related: would be nice to get a short section describing the
implications of what "technology preview" means and link to that here.
> +
> .Configuration Example (`/etc/pve/storage.cfg`)
> ----
> lvm: myspace
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-04 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 12:24 Maximiliano Sandoval
2025-09-03 8:46 ` Friedrich Weber
2025-09-03 8:48 ` Shannon Sterz
2025-09-04 12:52 ` Thomas Lamprecht [this message]
2025-09-04 13:29 ` Maximiliano Sandoval
2025-09-04 13:33 ` Maximiliano Sandoval
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=0708d5d2-a59e-4958-b409-4d8bdc01502e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.sandoval@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.