@@ -22,17 +22,22 @@ placement groups will help you identify the problem.
2222Monitoring OSDs
2323===============
2424
25- An OSD's status is as follows: it is either in the cluster (``in ``) or out of the cluster
26- (``out ``); likewise , it is either up and running (``up ``) or down and not
27- running (``down ``). If an OSD is ``up ``, it can be either ``in `` the cluster
28- (if so, you can read and write data) or ``out `` of the cluster. If the OSD was previously
29- ``in `` the cluster but was recently moved ``out `` of the cluster, Ceph will migrate its
30- PGs to other OSDs. If an OSD is ``out `` of the cluster, CRUSH will
31- not assign any PGs to that OSD. If an OSD is ``down ``, it should also be
25+ An OSD's status is either in the cluster (``in ``) or out of the cluster
26+ (``out ``); and , it is either up and running (``up ``), or it is down and not
27+ running (``down ``). If an OSD is ``up ``, it may be either ``in `` the cluster
28+ (you can read and write data) or it is ``out `` of the cluster. If it was
29+ ``in `` the cluster and recently moved ``out `` of the cluster, Ceph will migrate
30+ placement groups to other OSDs. If an OSD is ``out `` of the cluster, CRUSH will
31+ not assign placement groups to the OSD. If an OSD is ``down ``, it should also be
3232``out ``.
3333
34- .. note :: If an OSD is ``down`` and ``in``, then there is a problem and the cluster
35- is not in a healthy state.
34+ .. note :: If an OSD is ``down`` and ``in``, there is a problem and the cluster
35+ will not be in a healthy state.
36+
37+ The problem here seems to be with the word "should" above, and then with the
38+ information in the note that there is a problem when an OSD is "down" and "in".
39+ We need to replace "should" with something less modal and tentative. Does the
40+ sentence mean to say "When an OSD is 'down', it is therefore a fortiori 'out'."?
3641
3742.. ditaa ::
3843
0 commit comments