From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH-SERIES storage 0/3] fix #6587: lvm plugin: snapshot info: fix parsing snapshot name
Date: Wed, 30 Jul 2025 19:29:19 +0200 [thread overview]
Message-ID: <DBPKFW9K7DYP.22KSRN5JIDF1H@proxmox.com> (raw)
In-Reply-To: <20250730162117.160498-1-f.ebner@proxmox.com>
On Wed Jul 30, 2025 at 6:20 PM CEST, Fiona Ebner wrote:
> Volume names are allowed to contain underscores, so it is impossible
> to determine the snapshot name from just the volume name, e.g:
> snap_vm-100-disk_with_underscore_here_s_some_more.qcow2
>
> Therefore, we need to also rely on the volume name itself to properly
> parse the snapshot name.
Did some testing and tried to break things.
Works as advertised and even fixes previously broken snapshots--that is,
if one tried to delete a snapshot on LVM before this patch, the snapshot
would become stuck in the "deleted" state. Once this patch was applied,
I was able to delete the stuck snapshot as well (after `qm unlock`,
naturally).
The changes also seem fine to me; gave patch 02 most of my attention
since that's where the fix is. Couldn't spot anything wrong with any of
the changes here.
So, LGTM -- consider:
Tested-by: Max R. Carrara <m.carrara@proxmox.com>
Reviewed-by: Max R. Carrara <m.carrara@proxmox.com>
>
> Fiona Ebner (3):
> lvm plugin: snapshot info: avoid superfluous argument for closure
> fix #6587: lvm plugin: snapshot info: fix parsing snapshot name
> lvm plugin: volume snapshot: actually print error when renaming
>
> src/PVE/Storage/LVMPlugin.pm | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
_______________________________________________
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-07-30 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 16:20 Fiona Ebner
2025-07-30 16:20 ` [pve-devel] [PATCH storage 1/3] lvm plugin: snapshot info: avoid superfluous argument for closure Fiona Ebner
2025-07-30 16:20 ` [pve-devel] [PATCH storage 2/3] fix #6587: lvm plugin: snapshot info: fix parsing snapshot name Fiona Ebner
2025-07-30 16:20 ` [pve-devel] [PATCH storage 3/3] lvm plugin: volume snapshot: actually print error when renaming Fiona Ebner
2025-07-30 17:29 ` Max R. Carrara [this message]
2025-07-30 17:36 ` [pve-devel] applied: [PATCH-SERIES storage 0/3] fix #6587: lvm plugin: snapshot info: fix parsing snapshot name Thomas Lamprecht
2025-07-31 8:34 ` Fiona Ebner
2025-07-31 8:50 ` Thomas Lamprecht
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=DBPKFW9K7DYP.22KSRN5JIDF1H@proxmox.com \
--to=m.carrara@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.