From be97b7d5b89d7021f71695b4c1b78830bad4dab6 Mon Sep 17 00:00:00 2001 From: Loic Dachary Date: Fri, 19 Sep 2014 10:28:55 +0200 Subject: [PATCH] documentation: fix bugous osd stop/start example Signed-off-by: Loic Dachary --- doc/rados/troubleshooting/troubleshooting-osd.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/rados/troubleshooting/troubleshooting-osd.rst b/doc/rados/troubleshooting/troubleshooting-osd.rst index e67038c68755..18460067f9af 100644 --- a/doc/rados/troubleshooting/troubleshooting-osd.rst +++ b/doc/rados/troubleshooting/troubleshooting-osd.rst @@ -6,7 +6,8 @@ Before troubleshooting your OSDs, check your monitors and network first. If you execute ``ceph health`` or ``ceph -s`` on the command line and Ceph returns a health status, the return of a status means that the monitors have a quorum. If you don't have a monitor quorum or if there are errors with the monitor -status, address the monitor issues first. Check your networks to ensure they +status, `address the monitor issues first <../troubleshooting-mon>`_. +Check your networks to ensure they are running properly, because networks may have a significant impact on OSD operation and performance. @@ -96,14 +97,14 @@ maintenance, set the cluster to ``noout`` first:: Once the cluster is set to ``noout``, you can begin stopping the OSDs within the failure domain that requires maintenance work. :: - ceph osd stop osd.{num} + stop ceph-osd id={num} .. note:: Placement groups within the OSDs you stop will become ``degraded`` while you are addressing issues with within the failure domain. Once you have completed your maintenance, restart the OSDs. :: - ceph osd start osd.{num} + start ceph-osd id={num} Finally, you must unset the cluster from ``noout``. :: -- 2.47.3