[ceph-users] Re: Erasure-coded PG stuck in the failed_repair state

2022-05-10 Thread Wesley Dillingham
In my experience: "No scrub information available for pg 11.2b5 error 2: (2) No such file or directory" is the output you get from the command when the up or acting osd set has changed since the last deep-scrub. Have you tried to run a deep scrub (ceph pg deep-scrub 11.2b5) on the pg and then try

[ceph-users] Re: Erasure-coded PG stuck in the failed_repair state

2022-05-11 Thread Robert Appleyard - STFC UKRI
Hi, Thanks for your reply, we have let it scrub and it’s still active+clean+inconsistent+failed_repair and we still get the same error: [root@ceph-adm1 ~]# rados list-inconsistent-obj 11.2b5 No scrub information available for pg 11.2b5 error 2: (2) No such file or directory My suspicion is that