Hi,
After recreating some related OSDs (3, 71 and 237), now the acting set is
normal but the PG is incomplete now and there are slow ops on primary OSD
(3). I have tried to make it normal
with osd_find_best_info_ignore_history_les way but the PG is still
incomplete. On this condition the I/O from clients sometimes is freezing, I
suspect that the blocks inside this PG cause I/O freeze. How can I resolve
this incomplete PG or at least to make the client I/O not freeze for
recovering the rest of the normal block like recovering the drive with bad
sectors?
Best regards,
On Wed, May 5, 2021 at 12:29 AM Lazuardi Nasution <mrxlazuardin@xxxxxxxxx>
wrote:
> Hi,
>
> Suddenly we have a recovery_unfound situation. I find that PG acting set
> is missing some OSDs which are up. Why can't OSD 3 and 71 on following PG
> query result be members of PG acting set? Currently, we use v15.2.8. How to
> recover from this situation?
>
> {
> "snap_trimq": "[]",
> "snap_trimq_len": 0,
> "state":
> "active+forced_recovery+recovery_unfound+undersized+degraded+remapped",
> "epoch": 237505,
> "up": [
> 3,
> 237,
> 71,
> 132,
> 115,
> 56
> ],
> "acting": [
> 2147483647,
> 237,
> 2147483647,
> 132,
> 115,
> 56
> ],
> "backfill_targets": [
> "3(0)",
> "71(2)"
> ],
> "acting_recovery_backfill": [
> "3(0)",
> "56(5)",
> "71(2)",
> "115(4)",
> "132(3)",
> "237(1)"
> ],
>
> Best regards.
>
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
