Sorry, I had lost access to my emails. Setting those affected OSDs out
would have been one of the next steps, great that it worked for you.
Zitat von Boris Behrens :
I've outed osd.18 and osd.54 and let it sync for some time and now the
problem is gone.
*shrugs
Thank you for the hints.
Am
I've outed osd.18 and osd.54 and let it sync for some time and now the
problem is gone.
*shrugs
Thank you for the hints.
Am Mo., 8. Feb. 2021 um 14:46 Uhr schrieb Boris Behrens :
> Hi,
> sure
>
> ID CLASS WEIGHTTYPE NAME STATUS REWEIGHT PRI-AFF
> -1 672.68457 root default
>
Hi,
sure
ID CLASS WEIGHTTYPE NAME STATUS REWEIGHT PRI-AFF
-1 672.68457 root default
-258.20561 host s3db1
23 hdd 14.55269 osd.23 up 1.0 1.0
69 hdd 14.55269 osd.69 up 1.0 1.0
73 hdd 14.55269 osd.73
Can you share 'ceph osd tree'? Are the weights of this OSD
appropriate? I've seen stuck PGs because of OSD weight imbalance. Is
the OSD in the correct subtree?
Zitat von Boris Behrens :
Hi Eugen,
I've set it to 0 but the "degraded objects" count does not go down.
Am Mo., 8. Feb. 2021 um
Hi Eugen,
I've set it to 0 but the "degraded objects" count does not go down.
Am Mo., 8. Feb. 2021 um 14:23 Uhr schrieb Eugen Block :
> 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
>
>
--
Die
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 :
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
