From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager 0/2] ceph: osd: stop running pveremove during cleanup
Date: Tue, 17 Mar 2026 13:33:38 +0100 [thread overview]
Message-ID: <20260317123343.299525-1-m.sandoval@proxmox.com> (raw)
See the individual commit descriptions.
Tested:
Ran the following commands in a 3-node ceph cluster:
- systemd reset-failed
- pveceph create osd $dev
- lsblk
- ceph osd out $id && ceph osd down $id && pveceph osd destroy $id --cleanup 1
- lsblk
a couple of times in a loop. And checked that each lsblk shows the right
state for $dev. Without the reset-failed the creation would fail after a
couple of iterations, but that seems unrelated.
Maximiliano Sandoval (2):
ceph: osd: stop triggering udev
ceph: osd: stop running pveremove during cleanup
PVE/API2/Ceph/OSD.pm | 43 -------------------------------------------
1 file changed, 43 deletions(-)
--
2.47.3
next 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 Maximiliano Sandoval [this message]
2026-03-17 12:33 ` [PATCH manager 1/2] ceph: osd: stop triggering udev Maximiliano Sandoval
2026-03-17 12:33 ` [PATCH manager 2/2] ceph: osd: stop running pveremove during cleanup Maximiliano Sandoval
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-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox