From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager 2/2] ceph: osd: stop running pveremove during cleanup
Date: Tue, 17 Mar 2026 13:33:40 +0100 [thread overview]
Message-ID: <20260317123343.299525-3-m.sandoval@proxmox.com> (raw)
In-Reply-To: <20260317123343.299525-1-m.sandoval@proxmox.com>
Since [7f007e7fc] ceph will call pvremove while zapping the OSD. Thus we
remove our pvremove call in order to avoid failing to remove an already
removed PV.
The aforementioned commit is included in all versions since Reef which
is the oldest supported version in Proxmox VE 9.
[7f007e7fc] https://github.com/ceph/ceph/commit/7f007e7fc75b4d6e7465c684f7e5b2458883dcc5
Suggested-by: Fiona Ebner <f.ebner@proxmox.com>
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
PVE/API2/Ceph/OSD.pm | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/PVE/API2/Ceph/OSD.pm b/PVE/API2/Ceph/OSD.pm
index a0768dc0..28f631ca 100644
--- a/PVE/API2/Ceph/OSD.pm
+++ b/PVE/API2/Ceph/OSD.pm
@@ -1048,20 +1048,6 @@ __PACKAGE__->register_method({
eval { PVE::Ceph::Tools::ceph_volume_zap($osdid, $cleanup) };
warn $@ if $@;
-
- if ($cleanup) {
- # try to remove pvs, but do not fail if it does not work
- for my $osd_part (@{ $osd_list->{$osdid} }) {
- for my $dev (@{ $osd_part->{devices} }) {
- ($dev) = ($dev =~ m|^(/dev/[-_.a-zA-Z0-9\/]+)$|); #untaint
-
- eval {
- run_command(['/sbin/pvremove', $dev], errfunc => sub { });
- };
- warn $@ if $@;
- }
- }
- }
} else {
my $partitions_to_remove = [];
if ($cleanup) {
--
2.47.3
prev parent reply other threads:[~2026-03-17 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 12:33 [PATCH manager 0/2] " Maximiliano Sandoval
2026-03-17 12:33 ` [PATCH manager 1/2] ceph: osd: stop triggering udev Maximiliano Sandoval
2026-03-17 12:33 ` Maximiliano Sandoval [this message]
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=20260317123343.299525-3-m.sandoval@proxmox.com \
--to=m.sandoval@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.