From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 58A671FF150 for ; Mon, 06 Jul 2026 10:46:47 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 898A82143E; Mon, 06 Jul 2026 10:46:46 +0200 (CEST) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: Re: [PATCH manager 0/2] ceph: osd: stop running pveremove during cleanup In-Reply-To: <20260317123343.299525-1-m.sandoval@proxmox.com> (Maximiliano Sandoval's message of "Tue, 17 Mar 2026 13:33:38 +0100") References: <20260317123343.299525-1-m.sandoval@proxmox.com> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Mon, 06 Jul 2026 10:46:41 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1783327591303 X-SPAM-LEVEL: Spam detection results: 0 DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: CBWNZUMTUXSDNGBTFAWFAKEV567OAJ6G X-Message-ID-Hash: CBWNZUMTUXSDNGBTFAWFAKEV567OAJ6G X-MailFrom: m.sandoval@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Maximiliano Sandoval writes: > 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. Bump -- Maximiliano