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. By default mon_warn_not_deep_scrubbed = 0 OPTION(mon_warn_not_deep_scrubbed, OPT_INT, 0) By default osd_deep_scrub_interval = 1 week OPTION(osd_deep_scrub_interval, OPT_FLOAT, 60*60*24*7) // once a week So by default if a pg has not been deep scrubbed in more than a week you will get this warning. I believe the value reported, 86400, is incorrect in the case of a deep scrub as it should be 604800 and this looks like a copy and paste error. I'll submit a patch to rectify that. The calculations for scrub (as opposed to deep scrub) are very similar except the value involved is 86400, or one day (mon_scrub_interval). I'll leave it as an exercise for you to do the math in your cases using the values you have set locally. HTH. On Thu, Jul 20, 2017 at 5:10 AM, Gencer W. Genç <gencer@xxxxxxxxxxxxx> wrote: > 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.5e scrub ok > > 2017-07-19 15:05:10.123522 [INF] 3.5e scrub starts > > 2017-07-19 15:05:14.613124 [WRN] Health check update: 914 pgs not scrubbed > for 86400 (PG_NOT_SCRUBBED) > > 2017-07-19 15:05:07.433748 [INF] 1.c4 scrub ok > > ... > > > > Should this be scared us? > > > > Gencer. > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- Cheers, Brad _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |