From: Zac Dover Date: Wed, 23 Oct 2024 08:34:25 +0000 (+1000) Subject: doc/rados: standardize markup of "clean" X-Git-Tag: v18.2.5~319^2 X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=437e882835e95b6aab0c6374598827447ad56e1c;p=ceph.git doc/rados: standardize markup of "clean" Standardize the markup around the status "clean" in the documentation so that readers don't mistakenly get the idea that inconsistent presentation of the word "clean" implies a never-stated difference between one instance and the other. Signed-off-by: Zac Dover (cherry picked from commit c8b4155d2d27228917d4be1f11514504100c55c7) --- diff --git a/doc/rados/operations/health-checks.rst b/doc/rados/operations/health-checks.rst index 81dafdf03e987..1d5bb342d740d 100644 --- a/doc/rados/operations/health-checks.rst +++ b/doc/rados/operations/health-checks.rst @@ -1502,10 +1502,10 @@ This health check is raised if a certain percentage (determined by :confval:`mon_warn_pg_not_deep_scrubbed_ratio`) of the interval has elapsed after the time the scrub was scheduled and no scrub has been performed. -PGs will receive a deep scrub only if they are flagged as *clean* (which means -that they are to be cleaned, and not that they have been examined and found to -be clean). Misplaced or degraded PGs might not be flagged as ``clean`` (see -*PG_AVAILABILITY* and *PG_DEGRADED* above). +PGs will receive a deep scrub only if they are flagged as ``clean`` (which +means that they are to be cleaned, and not that they have been examined and +found to be clean). Misplaced or degraded PGs might not be flagged as ``clean`` +(see *PG_AVAILABILITY* and *PG_DEGRADED* above). This document offers two methods of setting the value of :confval:`osd_deep_scrub_interval`. The first method listed here changes the