Re: one PG is stuck on single OSD and does not sync back

Eugen Block <eblock@xxxxxx> · Mon, 08 Feb 2021 13:21:45 +0000

Hi,

one option would be to decrease (or set to 0) the primary-affinity of  
osd.14 and see if that brings the pg back.

Regards,
Eugen

Zitat von Boris Behrens <bb@xxxxxxxxx>:

Good day together,

I've got an issue after rebooting an osd node. It looks like there is one
PG that does not sync back to the other UP osds.
I've tried to restart the ceph processes for all three OSDs and when I
stopped the one on OSD.14 the PG went down.

Any ideas what I can do?

# ceph pg ls degraded
PG    OBJECTS DEGRADED MISPLACED UNFOUND BYTES OMAP_BYTES* OMAP_KEYS* LOG
 STATE                                           SINCE VERSION
REPORTED          UP            ACTING  SCRUB_STAMP
 DEEP_SCRUB_STAMP
10.1a    2078      766         0       0     0  9071695544   28506523 3031
active+undersized+degraded+remapped+backfilling    2m 301810'52824786
301818:1346392477 [18,14,54]p18 [14]p14 2021-01-02 06:28:01.124161
2021-01-02 06:28:01.124161

PG_AVAILABILITY Reduced data availability: 1 pg inactive, 1 pg down
    pg 10.1a is down, acting [18,54]

Cheers
 Boris
--
Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im
groÃƒ¼en Saal.
_______________________________________________
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