x27; | while read i; do
> ceph pg deep-scrub ${i}; done
>
>
>
> --
>
> Petr Malkov
>
>
>
> -
>
> Message: 57
>
> Date: Wed, 19 Jul 2017 16:38:20 +
>
> From: Roger Brown
>
> To: ceph-users
>
> Subject: [ceph-users] pgs not deep-scrubb
ceph-users
Subject: [ceph-users] pgs not deep-scrubbed for 86400
Message-ID:
Content-Type: text/plain; charset="utf-8"
I just upgraded from Luminous 12.1.0 to 12.1.1 and was greeted with this
new "pgs not deep-scrubbed for" warning. Should this resolve itse
This code shows how that all works (part of some new health reporting code).
https://github.com/ceph/ceph/blob/master/src/mon/PGMap.cc#L3188-L3203
So the last_deep_scrub_stamp of the pg is compared to deep_cutoff which is the
time now minus mon_warn_not_deep_scrubbed + osd_deep_scrub_interval.
B
Exactly have this issue (or not?) at the moment. Mine says "906 pgs not
scrubbed for 86400". But it is decrementing slowly (very slowly).
I cannot find any documentation for exact "pgs not srubbed for" phrase on
the web but only this.
Log like this:
2017-07-19 15:05:10.125041 [INF] 3.5
I just upgraded from Luminous 12.1.0 to 12.1.1 and was greeted with this
new "pgs not deep-scrubbed for" warning. Should this resolve itself, or
should I get scrubbing?
$ ceph health detail
HEALTH_WARN 4 pgs not deep-scrubbed for 86400; 15 pgs not scrubbed for 86400
PG_NOT_DEEP_SCRUBBED 4 pgs not
