From b082fd68b651d732297f87fc4b2f25bef5ef2262 Mon Sep 17 00:00:00 2001 From: John Wilkins Date: Wed, 14 May 2014 00:13:41 -0700 Subject: [PATCH] doc: Minor edit. Signed-off-by: John Wilkins --- doc/rados/operations/add-or-rm-osds.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/rados/operations/add-or-rm-osds.rst b/doc/rados/operations/add-or-rm-osds.rst index a125854f8e2c..e17e961eba14 100644 --- a/doc/rados/operations/add-or-rm-osds.rst +++ b/doc/rados/operations/add-or-rm-osds.rst @@ -104,10 +104,10 @@ weight). ceph auth add osd.{osd-num} osd 'allow *' mon 'allow rwx' -i /var/lib/ceph/osd/ceph-{osd-num}/keyring -#. Add the OSD to the CRUSH map so that it can begin receiving data. The +#. Add the OSD to the CRUSH map so that the OSD can begin receiving data. The ``ceph osd crush add`` command allows you to add OSDs to the CRUSH hierarchy wherever you wish. If you specify at least one bucket, the command - will place the OSD in the most specific bucket you specify, *and* it will + will place the OSD into the most specific bucket you specify, *and* it will move that bucket underneath any other buckets you specify. **Important:** If you specify only the root bucket, the command will attach the OSD directly to the root, but CRUSH rules expect OSDs to be inside of hosts. -- 2.47.3