That would have been my next question, did you verify that the
corrupted OSD was a primary? The default deep-scrub config scrubs all
PGs within a week, so yeah, it can take a week until it's detected. It
could have been detected sooner if those objects would have been in
use by clients and required to be updated (rewritten).
Zitat von Petr Bena <petr@bena.rocks>:
Hello,
No I don't have osd_scrub_auto_repair, interestingly after about a
week after forgetting about this, an error manifested:
[ERR] OSD_SCRUB_ERRORS: 1 scrub errors
[ERR] PG_DAMAGED: Possible data damage: 1 pg inconsistent
pg 4.1d is active+clean+inconsistent, acting [4,2]
which could be repaired as expected, since I damaged only 1 OSD.
It's interesting it took a whole week to find it. For some reason it
seems to be that running deep-scrub on entire OSD only runs it for
PGs where the OSD is considered "primary", so maybe that's why it
wasn't detected when I ran it manually?
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
