From: Fiona Ebner <f.ebner@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [PATCH storage 4/5] lvm plugin: use relative path for qcow2 rebase command
Date: Tue, 29 Jul 2025 11:04:19 +0200 [thread overview]
Message-ID: <107d54af-a2d7-4a17-98b3-7e3cfb05db80@proxmox.com> (raw)
In-Reply-To: <20250729073844.185466-5-f.gruenbichler@proxmox.com>
Am 29.07.25 um 9:39 AM schrieb Fabian Grünbichler:
> otherwise the resulting qcow2 file will contain an absolute path, which makes
> renaming the backing VG of the storage impossible.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
with a nit below:
> ---
> src/PVE/Storage/LVMPlugin.pm | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/src/PVE/Storage/LVMPlugin.pm b/src/PVE/Storage/LVMPlugin.pm
> index db1be98..9a04db6 100644
> --- a/src/PVE/Storage/LVMPlugin.pm
> +++ b/src/PVE/Storage/LVMPlugin.pm
> @@ -1120,12 +1120,13 @@ sub volume_snapshot_delete {
> my $parentpath = $snapshots->{$parentsnap}->{file};
This variable is unused now and could be removed like in the previous patch.
> print
> "$volname: deleting snapshot '$snap' by rebasing '$childsnap' on top of '$parentsnap'\n";
> - print "running 'qemu-img rebase -b $parentpath -F qcow2 -f qcow2 $childpath'\n";
> + my $rel_parent_path = get_snap_name($class, $volname, $parentsnap);
> + print "running 'qemu-img rebase -b $rel_parent_path -F qcow2 -f qcow2 $childpath'\n";
> $cmd = [
> '/usr/bin/qemu-img',
> 'rebase',
> '-b',
> - $parentpath,
> + $rel_parent_path,
> '-F',
> 'qcow2',
> '-f',
_______________________________________________
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-29 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 7:38 [pve-devel] [PATCH storage/qemu-server 0/5] avoid absolute qcow2 references Fabian Grünbichler
2025-07-29 7:38 ` [pve-devel] [PATCH storage 1/5] plugin: fix typo in rebase log message Fabian Grünbichler
2025-07-29 8:09 ` Fiona Ebner
2025-07-29 7:38 ` [pve-devel] [PATCH storage 2/5] lvm " Fabian Grünbichler
2025-07-29 8:09 ` Fiona Ebner
2025-07-29 7:38 ` [pve-devel] [PATCH storage 3/5] plugin: use relative path for qcow2 rebase command Fabian Grünbichler
2025-07-29 9:01 ` Fiona Ebner
2025-07-29 7:38 ` [pve-devel] [PATCH storage 4/5] lvm " Fabian Grünbichler
2025-07-29 9:04 ` Fiona Ebner [this message]
2025-07-29 7:38 ` [pve-devel] [PATCH qemu-server 5/5] blockdev-stream/-commit: make backing file relative Fabian Grünbichler
2025-07-29 9:17 ` Fiona Ebner
2025-07-29 12:02 ` [pve-devel] superseded: [PATCH storage/qemu-server 0/5] avoid absolute qcow2 references 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=107d54af-a2d7-4a17-98b3-7e3cfb05db80@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox