From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container v8 2/4] destroy_lxc, delete_mp_volume: rename $volume to $volid
Date: Thu, 26 Jun 2025 18:06:20 +0200 [thread overview]
Message-ID: <20250626160626.311407-5-m.koeppl@proxmox.com> (raw)
In-Reply-To: <20250626160626.311407-1-m.koeppl@proxmox.com>
$volid states more clearly that it's a volume ID, avoiding confusion
about the values these variables hold.
No functional change intended.
Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
---
src/PVE/LXC.pm | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
index dacd6cf0..2bb75dd8 100644
--- a/src/PVE/LXC.pm
+++ b/src/PVE/LXC.pm
@@ -945,16 +945,16 @@ sub get_primary_ips {
}
sub delete_mountpoint_volume {
- my ($storage_cfg, $vmid, $volume) = @_;
+ my ($storage_cfg, $vmid, $volid) = @_;
- return if PVE::LXC::Config->classify_mountpoint($volume) ne 'volume';
+ return if PVE::LXC::Config->classify_mountpoint($volid) ne 'volume';
- my ($vtype, $name, $owner) = PVE::Storage::parse_volname($storage_cfg, $volume);
+ my ($vtype, $name, $owner) = PVE::Storage::parse_volname($storage_cfg, $volid);
if ($vmid == $owner) {
- PVE::Storage::vdisk_free($storage_cfg, $volume);
+ PVE::Storage::vdisk_free($storage_cfg, $volid);
} else {
- warn "ignore deletion of '$volume', CT $vmid isn't the owner!\n";
+ warn "ignore deletion of '$volid', CT $vmid isn't the owner!\n";
}
}
@@ -965,13 +965,13 @@ sub destroy_lxc_container {
my $remove_volume = sub {
my ($ms, $mountpoint) = @_;
- my $volume = $mountpoint->{volume};
+ my $volid = $mountpoint->{volume};
- return if $volids->{$volume};
- $volids->{$volume} = 1;
+ return if $volids->{$volid};
+ $volids->{$volid} = 1;
- eval { delete_mountpoint_volume($storage_cfg, $vmid, $volume); };
- PVE::RESTEnvironment::log_warn("failed to delete mountpoint volume $volume: $@") if $@;
+ eval { delete_mountpoint_volume($storage_cfg, $vmid, $volid); };
+ PVE::RESTEnvironment::log_warn("failed to delete mountpoint volume $volid: $@") if $@;
};
PVE::LXC::Config->foreach_volume_full($conf, { include_unused => 1 }, $remove_volume);
--
2.39.5
_______________________________________________
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-06-26 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 16:06 [pve-devel] [PATCH container/qemu-server/storage v8 00/10] fix #3711 and adapt drive detach/remove behavior Michael Köppl
2025-06-26 16:06 ` [pve-devel] [PATCH storage v8 1/2] vdisk_free: print warning if underlying storage does not exist Michael Köppl
2025-06-26 16:06 ` [pve-devel] [PATCH storage v8 2/2] parse_volname: print warning if storage does not exists Michael Köppl
2025-06-26 16:06 ` [pve-devel] [PATCH container v8 1/4] fix #3711: warn about storage errors during mountpoint delete Michael Köppl
2025-06-26 16:06 ` Michael Köppl [this message]
2025-06-26 16:06 ` [pve-devel] [PATCH container v8 3/4] config: ensure valid volid through parse_volume() Michael Köppl
2025-06-26 16:06 ` [pve-devel] [PATCH container v8 4/4] add linked clone check when destroying container template Michael Köppl
2025-06-26 16:06 ` [pve-devel] [PATCH qemu-server v8 1/4] adapt linked clone check to not die if an error occurs during check Michael Köppl
2025-06-26 16:06 ` [pve-devel] [PATCH qemu-server v8 2/4] fix #3711: make removal of VM possible if store does not exist anymore Michael Köppl
2025-06-26 16:06 ` [pve-devel] [PATCH qemu-server v8 3/4] destroy_vm: use log_warn for vdisk_free errors for consistency Michael Köppl
2025-06-26 16:06 ` [pve-devel] [PATCH qemu-server v8 4/4] display warnings for storage errors or if storage no longer exists Michael Köppl
2025-07-08 11:09 ` [pve-devel] [PATCH container/qemu-server/storage v8 00/10] fix #3711 and adapt drive detach/remove behavior Lukas Wagner
2025-07-15 16:29 ` 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=20250626160626.311407-5-m.koeppl@proxmox.com \
--to=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