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 container v6 2/4] config: apply_pending: get unused volid through parse_volume()
Date: Tue, 20 May 2025 15:49:19 +0200 [thread overview]
Message-ID: <922e34a1-836f-49d2-8e9b-dd1c14910d6e@proxmox.com> (raw)
In-Reply-To: <de3a2d79-e610-4c47-9439-b740401b7842@proxmox.com>
Am 20.05.25 um 15:45 schrieb Fiona Ebner:
> Am 20.05.25 um 11:08 schrieb Michael Köppl:
>> The volume ID returned by parse_volume() is used here as opposed to
>> $conf->{$opt} used for regular mount points because $conf->{$opt} is not
>> necessarily a valid volume ID in this case. This distinction is
>> important because is_volume_in_use does internally not consider
>> 'unused*' a valid volume key and does not check it. parse_volume knows
>> about 'unused*' and returns a valid volume ID.
>
> The key is not passed to is_volume_in_use(), just the value. The
> rationale is imprecise in that regard.
>
> Hmm, what can the value for 'unusedN' be other than a valid volume ID?
> Do you have an example? I'd rather avoid adding entries where it is not
> a volume ID to 'unusedN' in the first place.
Looking at the next patch, do you just mean it can be a volume ID whose
storage does not exist anymore?
_______________________________________________
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-20 13:49 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 [this message]
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
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=922e34a1-836f-49d2-8e9b-dd1c14910d6e@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