On 11/9/21 07:35, Ansgar Jazdzewski wrote:
Hi fellow ceph users, I did an upgrade from 14.2.23 to 16.2.6 not knowing that the current minor version had this nasty bug! [1] [2]
I'm sorry you hit this bug. We tried to warn users through documentation. Apparently this is not enough and other ways of informing operators about such (rare) incidents might be worthwile. I have put this topic on the agenda for the upcoming user + dev monthly meeting [1].
we were able to resolve some of the omap issues in the rgw.index pool but still have 17pg's to fix in the rgw.meta and rgw.log pool! I have a couple of questions: - did someone have done a script to fix that pg's we were only able to fix the index with our approach [3]
Not as far as I know of.
- why is the 16.2.6 version still in the public mirror (should it not be moved)
This issue can happen when you upgrade from an older version to Pacific. So no matter if you would have used any other minor version, you would still have the same problem.
- do you have any other workarounds to resolve this?
16.2.7 should have the fix. If this fix is also able to repair clusters bitten by the bug is not yet clear to me.
Gr. Stefan _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
