From: Fiona Ebner <f.ebner@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Michael Köppl" <m.koeppl@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v6 2/3] print warning for PVE::Storage::path errors instead of failing
Date: Wed, 21 May 2025 13:02:33 +0200 [thread overview]
Message-ID: <16761db2-de14-453d-acba-5a226cd1b29c@proxmox.com> (raw)
In-Reply-To: <20250520090818.44881-7-m.koeppl@proxmox.com>
I'd prefer a commit title like "fix #3711: make removal of VM possible
if storage doesn't exit anymore" and add a brief rationale to the commit
message. The current title does not convey any information about the "why".
Am 20.05.25 um 11:08 schrieb Michael Köppl:
> Co-authored-by: Stefan Hrdlicka
As already, mentioned, needs to be adapted.
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
With the comments addressed
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> PVE/QemuServer.pm | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index e02bf7d4..68bbf4ce 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -2132,7 +2132,8 @@ sub destroy_vm {
> return if !$volid || $volid =~ m|^/|;
> return if $volids->{$volid};
>
> - my ($path, $owner) = PVE::Storage::path($storecfg, $volid);
> + my ($path, $owner) = eval { PVE::Storage::path($storecfg, $volid) };
> + log_warn("failed to get path and owner of volume '$volid': $@\n") if $@;
No need for the trailing "\n". In fact, it will be duplicate if $@
already contains it. Semi-related note: log_warn() will add a trailing
newline if the passed-in message doesn't contain it.
> return if !$path || !$owner || ($owner != $vmid);
>
> $volids->{$volid} = 1;
There are two warnings further below in the function when vdisk_free()
fails, please adapt those to use log_warn() too for consistency and
better visibility for users. Should be its own patch.
_______________________________________________
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-05-21 11:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 9:08 [pve-devel] [PATCH container/qemu-server v6 0/7] fix #3711 and adapt drive detach/remove behavior Michael Köppl
2025-05-20 9:08 ` [pve-devel] [PATCH container v6 1/4] fix #3711: lxc: print warning if storage for mounted volume does not exist anymore Michael Köppl
2025-05-20 13:33 ` Fiona Ebner
2025-05-22 6:08 ` Thomas Lamprecht
2025-05-27 7:37 ` Michael Köppl
2025-05-22 6:17 ` Thomas Lamprecht
2025-05-27 7:29 ` Michael Köppl via pve-devel
2025-05-20 9:08 ` [pve-devel] [PATCH container v6 2/4] config: apply_pending: get unused volid through parse_volume() Michael Köppl
2025-05-20 13:45 ` Fiona Ebner
2025-05-20 13:49 ` Fiona Ebner
2025-05-20 9:08 ` [pve-devel] [PATCH container v6 3/4] fix #3711: lxc: allow removing unused mp if storage no longer exists Michael Köppl
2025-05-20 14:03 ` Fiona Ebner
2025-05-27 9:34 ` Michael Köppl
2025-05-27 10:03 ` Fiona Ebner
2025-05-20 9:08 ` [pve-devel] [PATCH container v6 4/4] add linked clone check when destroying container Michael Köppl
2025-05-20 14:13 ` Fiona Ebner
2025-05-20 9:08 ` [pve-devel] [PATCH qemu-server v6 1/3] adapt linked clone check to not die if an error occurs during check Michael Köppl
2025-05-21 10:49 ` Fiona Ebner
2025-05-20 9:08 ` [pve-devel] [PATCH qemu-server v6 2/3] print warning for PVE::Storage::path errors instead of failing Michael Köppl
2025-05-21 11:02 ` Fiona Ebner [this message]
2025-05-20 9:08 ` [pve-devel] [PATCH qemu-server v6 3/3] mark volumes pending detach as unused if storage was removed Michael Köppl
2025-05-21 11:16 ` Fiona Ebner
2025-05-26 12:24 ` Michael Köppl
2025-05-27 16:05 ` [pve-devel] superseded: [PATCH container/qemu-server v6 0/7] fix #3711 and adapt drive detach/remove behavior Michael Köppl
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=16761db2-de14-453d-acba-5a226cd1b29c@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=m.koeppl@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal