Skip to content

Commit 20b621f

Browse files
committed
doc/cephadm/services: Add mention of --zap for OSD removal
Signed-off-by: Anthony D'Atri <[email protected]>
1 parent 60a56d0 commit 20b621f

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

doc/cephadm/services/osd.rst

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -288,26 +288,29 @@ Remove an OSD
288288

289289
Removing an OSD from a cluster involves two steps:
290290

291-
#. evacuating all placement groups (PGs) from the OSD
292-
#. removing the PG-free OSD from the cluster
291+
#. Evacuating all placement groups (PGs) from the OSD
292+
#. Removing the PG-free OSD from the cluster
293293

294294
The following command performs these two steps:
295295

296296
.. prompt:: bash #
297297

298-
ceph orch osd rm <osd_id(s)> [--replace] [--force]
298+
ceph orch osd rm <osd_id(s)> [--replace] [--force] [--zap]
299299

300300
Example:
301301

302302
.. prompt:: bash #
303303

304304
ceph orch osd rm 0
305+
ceph orch osd rm 1138 --zap
305306

306307
Expected output::
307308

308309
Scheduled OSD(s) for removal
309310

310-
OSDs that are not safe to destroy will be rejected.
311+
OSDs that are not safe to destroy will be rejected. Adding the ``--zap`` flag
312+
directs the orchestrator to remove all LVM and partition information from the
313+
OSD's drives, leaving it a blank slate for redeployment or other reuse.
311314

312315
.. note::
313316
After removing OSDs, if the OSDs' drives

0 commit comments

Comments
 (0)