Bug #52901
closed
osd/scrub: setting then clearing noscrub may lock a PG in 'scrubbing' state
Added by Ronen Friedman over 2 years ago.
Updated about 2 years ago.
Description
Recent scrub scheduling code errs in (at one location) incorrectly considering noscrub as not
precluding deep-scrub.
- Subject changed from osd/scrub: setting then clearing noscrub may lock a PG in 'scrubbing' state "forever" to osd/scrub: setting then clearing noscrub may lock a PG in 'scrubbing' state
- Status changed from New to Fix Under Review
- Pull request ID set to 43521
Easy to reproduce: set noscrub, then request a deep-scrub. That will get the PG's Scrubber state-machine
stuck in such a way, that no further scrubs will be possible - even after the noscrub is released.
Happens in teuthology tests, too.
With the fix - cannot be reproduced by the sequence above.
- Status changed from Fix Under Review to Resolved
A test to detect this specific bug pushed as PR 43919
Will this be backported to a stable release?
Also available in: Atom
PDF