From 1def3d023937770c85f0ea037e98ec9fe685086c Mon Sep 17 00:00:00 2001 From: Satoru Takeuchi Date: Thu, 7 Jan 2021 21:56:56 +0900 Subject: [PATCH] docs: describe how to remove healthy Ceph OSDs Current document of OSD removal only describe the case of broken OSDs. Signed-off-by: Satoru Takeuchi --- Documentation/ceph-osd-mgmt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ceph-osd-mgmt.md b/Documentation/ceph-osd-mgmt.md index c81fef9ed..c920d72a5 100644 --- a/Documentation/ceph-osd-mgmt.md +++ b/Documentation/ceph-osd-mgmt.md @@ -66,7 +66,7 @@ and it is safe to proceed. If an OSD is failing, the PGs will not be perfectly c ### From the Toolbox 1. Determine the OSD ID for the OSD to be removed. The osd pod may be in an error state such as `CrashLoopBackoff` or the `ceph` commands -in the toolbox may show which OSD is `down`. +in the toolbox may show which OSD is `down`. If you want to remove a healthy OSD, you should run `kubectl -n rook-ceph scale deployment rook-ceph-osd- --replicas=0` beforehand. 2. Mark the OSD as `out` if not already marked as such by Ceph. This signals Ceph to start moving (backfilling) the data that was on that OSD to another OSD. - `ceph osd out osd.` (for example if the OSD ID is 23 this would be `ceph osd out osd.23`) 3. Wait for the data to finish backfilling to other OSDs.