https://tracker.ceph.com/issues/53062 Can someone help me understand the scope of the OMAP key bug linked above? I’ve been using 16.2.6 for three months and I don’t _think_ I’ve seen any related problems. I upgraded my Nautilus (then 14.2.21) clusters to Pacific (16.2.4) in mid-June. One of my clusters was born in Jewel and has made all of the even-numbered releases to Pacific. I skipped over 16.2.5 and upgraded to 16.2.6 in mid-October. It looks like the aforementioned OMAP bug was discovered shortly after, on/around October 20th. My clusters had bluestore_fsck_quick_fix_on_mount set to true until about 10 minutes ago. I _think_ all of my OSDs did the OMAP conversion when I upgraded from Nautilus to Pacific back in June (I remember it taking several minutes per spinning OSD). Questions for my sanity: * Do I need to upgrade to 16.2.7 ASAP? Or can I wait until my next regular maintenance window? * What is the risk of staying on 16.2.6 if I have bluestore_fsck_quick_fix_on_mount set to false? * If I don’t have OSDs crashing, how would I know if I was impacted by the bug? Thanks! ❤ ~Jay -- Jay Sullivan Rochester Institute of Technology jay.sullivan@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |