On 01/17/2017 09:21 PM, David Turner wrote:
Looking through the additional osd config options for scrubbing show a
couple options that can prevent a PG from scrubbing immediately.
osd_scrub_during_recovery - default true - If false, no new scrub can
be scheduled while their is active recover
..@mosibi.nl]
Sent: Tuesday, January 17, 2017 1:07 PM
To: ceph-users@lists.ceph.com
Subject: Re: [ceph-users] Manual deep scrub
On 01/17/2017 05:15 PM, David Turner wrote:
David,
All OSDs with a copy of the PG need to not be involved in any scrub for the
scrub to start immediately. It is
On 01/17/2017 05:15 PM, David Turner wrote:
David,
All OSDs with a copy of the PG need to not be involved in any scrub
for the scrub to start immediately. It is not just the primary OSD
but all secondary OSDs as well for a scrub to be able to run on a PG.
I thought of that and checked if th
h-users-boun...@lists.ceph.com] on behalf of Richard
Arends [cephmailingl...@mosibi.nl]
Sent: Tuesday, January 17, 2017 8:27 AM
To: ceph-users@lists.ceph.com
Subject: Re: [ceph-users] Manual deep scrub
On 01/17/2017 04:09 PM, David Turner wrote:
Hi,
You want to look into the settings osd_max_scrubs which i
On 01/17/2017 04:09 PM, David Turner wrote:
Hi,
You want to look into the settings osd_max_scrubs which indicates how
many different scrub operations an OSD can be involved in at once
That's still the default, thus 1. A pg that i wanted to deep-scrub this
afternoon, should be done by an OSD
You want to look into the settings osd_max_scrubs which indicates how many
different scrub operations an OSD can be involved in at once (the well chosen
default is 1), as well as osd_scrub_max_interval and osd_deep_scrub_interval.
One of the differences in your cluster from before to now is tim
