From: 李丙洋 10208981 Date: Tue, 4 Sep 2018 06:01:46 +0000 (+0800) Subject: doc: Fix Spelling Error of Rados Operations X-Git-Tag: v14.0.1~424^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=refs%2Fpull%2F23903%2Fhead;p=ceph.git doc: Fix Spelling Error of Rados Operations Signed-off-by: Li Bingyang --- diff --git a/doc/rados/operations/add-or-rm-osds.rst b/doc/rados/operations/add-or-rm-osds.rst index 89d16f9f5a11..9e6682f4570b 100644 --- a/doc/rados/operations/add-or-rm-osds.rst +++ b/doc/rados/operations/add-or-rm-osds.rst @@ -135,7 +135,7 @@ weight). Replacing an OSD ---------------- -When disks fail, or if an admnistrator wants to reprovision OSDs with a new +When disks fail, or if an administrator wants to reprovision OSDs with a new backend, for instance, for switching from FileStore to BlueStore, OSDs need to be replaced. Unlike `Removing the OSD`_, replaced OSD's id and CRUSH map entry need to be keep intact after the OSD is destroyed for replacement. diff --git a/doc/rados/operations/bluestore-migration.rst b/doc/rados/operations/bluestore-migration.rst index 56ecce196ebd..91a64c9314e7 100644 --- a/doc/rados/operations/bluestore-migration.rst +++ b/doc/rados/operations/bluestore-migration.rst @@ -32,7 +32,7 @@ Mark out and replace -------------------- The simplest approach is to mark out each device in turn, wait for the -data to rereplicate across the cluster, reprovision the OSD, and mark +data to replicate across the cluster, reprovision the OSD, and mark it back in again. It is simple and easy to automate. However, it requires more data migration than should be necessary, so it is not optimal.