From: Anthony D'Atri Date: Fri, 21 Mar 2025 21:59:02 +0000 (-0400) Subject: doc/cephadm/services: Add mention of --zap for OSD removal X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=9e462aa692378b66b03392d7719579deb466e815;p=ceph.git doc/cephadm/services: Add mention of --zap for OSD removal Signed-off-by: Anthony D'Atri (cherry picked from commit 20b621fceb865403e19e1d7876f81e670829ff59) --- diff --git a/doc/cephadm/services/osd.rst b/doc/cephadm/services/osd.rst index 6b1ab7bfc3a46..f21f1f317d7a6 100644 --- a/doc/cephadm/services/osd.rst +++ b/doc/cephadm/services/osd.rst @@ -273,26 +273,29 @@ Remove an OSD Removing an OSD from a cluster involves two steps: -#. evacuating all placement groups (PGs) from the OSD -#. removing the PG-free OSD from the cluster +#. Evacuating all placement groups (PGs) from the OSD +#. Removing the PG-free OSD from the cluster The following command performs these two steps: .. prompt:: bash # - ceph orch osd rm [--replace] [--force] + ceph orch osd rm [--replace] [--force] [--zap] Example: .. prompt:: bash # ceph orch osd rm 0 + ceph orch osd rm 1138 --zap Expected output:: Scheduled OSD(s) for removal -OSDs that are not safe to destroy will be rejected. +OSDs that are not safe to destroy will be rejected. Adding the ``--zap`` flag +directs the orchestrator to remove all LVM and partition information from the +OSD's drives, leaving it a blank slate for redeployment or other reuse. .. note:: After removing OSDs, if the drives the OSDs were deployed on once again