OSD crash with "no available blob id" / Zombie blobs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello !

On our Octopus (v15.2.15) cluster, mainly used for OpenStack,
We had several OSD crash.
Some would not restart with "no available blob id" assertion.

We found several related bugs :
https://tracker.ceph.com/issues/48216
https://tracker.ceph.com/issues/38272

The workaround that works is to fsck / repair the stopped OSD :
ceph-bluestore-tool --path /var/lib/ceph/osd/ceph-<osd_id> --command repair

But it's not a long term solution.

I have seen a PR merged in 2019 here :
https://github.com/ceph/ceph/pull/28229

But don't find if it made to Octopus, and if it resolves completely the problem.

I also wonder if someone had that problem with Pacific, which could motivate us to upgrade from Octopus.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux