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 3/3] mark volumes pending detach as unused if storage was removed
Date: Wed, 21 May 2025 13:16:48 +0200 [thread overview]
Message-ID: <3b885c6a-5c82-496e-a818-17f0513bb1d2@proxmox.com> (raw)
In-Reply-To: <20250520090818.44881-8-m.koeppl@proxmox.com>
Am 20.05.25 um 11:08 schrieb Michael Köppl:
> If the storage backing the volume was removed, the volume will be marked
> as unused when pending actions are processed (e.g. volume was detached).
> Previously, the volume would simply disappear from the config.
Why? If the storage doesn't exist, the volume doesn't exist (from PVE's
perspective). What is the benefit of adding it as unused?
We could improve the current behavior by printing an informational
message for volumes that are not added as unused and a warning message
if the ownership couldn't be determined. I.e. warn if path() in
vm_is_volid_owner() fails, rather than quietly ignoring a failure there.
> Co-authored-by: Stefan Hrdlicka
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
> ---
> PVE/QemuServer.pm | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index 68bbf4ce..d47fa51c 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -1838,7 +1838,11 @@ sub vmconfig_register_unused_drive {
> delete $conf->{'special-sections'}->{cloudinit};
> } elsif (!drive_is_cdrom($drive)) {
> my $volid = $drive->{file};
> - if (vm_is_volid_owner($storecfg, $vmid, $volid)) {
> + my ($storeid, undef) = PVE::Storage::parse_volume_id($volid);
> + if (
> + !PVE::Storage::storage_config($storecfg, $storeid, 1)
> + || vm_is_volid_owner($storecfg, $vmid, $volid)
> + ) {
> PVE::QemuConfig->add_unused_volume($conf, $volid, $vmid);
> }
> }
_______________________________________________
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:17 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
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 [this message]
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=3b885c6a-5c82-496e-a818-17f0513bb1d2@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal