public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
	"mark@tuxis.nl" <mark@tuxis.nl>
Cc: "DERUMIER, Alexandre" <aderumier@odiso.com>
Subject: Re: [PVE-User] Volume chain snapshotting
Date: Tue, 25 Nov 2025 10:34:18 +0100	[thread overview]
Message-ID: <ee1fd2b9-2c21-4f20-a7b3-696fbfc187ac@proxmox.com> (raw)
In-Reply-To: <mailman.40.1763998299.399.pve-user@lists.proxmox.com>

Am 24.11.25 um 4:31 PM schrieb DERUMIER, Alexandre via pve-user:
> 
> Hi Mark !
> 
>>> 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?
> 
> It should be possible to use move disk to do it. (Define same storage
> twice, without volume-chain  and another with with-volume chain, and
> move to qcow2).

Please don't! This can break shared LVM storages because it fails to
honor locking guarantees! LVM metadata corruption is possible with
concurrent operations and Proxmox VE won't be aware of it actually being
the same storage under the hood.

> Alternatively, I think it could be possible to simply enable it on your
> current storage (in storage.cfg directory), and do the move disk to
> qcow2 format.
> (but be carefull to not have existing internal snapshots, as it's not
> supported to have both kind of snapshots at the same time)

You can also just enable the flag for an existing LVM storage via the
web UI/API/CLI, no need for manual editing. You will not be able to
disable the flag anymore as long as qcow2 formatted images exist
however. Moving disks to the same storage while changing formats is a
possibility, yes.


_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user


  reply	other threads:[~2025-11-25  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2025-11-24 14:42 Mark Schouten via pve-user
2025-11-24 15:49 ` g.husson_proxmox-pve-user--- via pve-user
2025-11-25  9:41   ` 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=ee1fd2b9-2c21-4f20-a7b3-696fbfc187ac@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=aderumier@odiso.com \
    --cc=mark@tuxis.nl \
    --cc=pve-user@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 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