r 200GB data) and a very small
non-production CephFS volume (1GB).
~Jay
-----Original Message-
From: Jay Sullivan
Sent: Wednesday, January 19, 2022 12:36 PM
To: 'Igor Fedotov' ; ceph-users@ceph.io
Subject: RE: [ceph-users] Re: Scope of Pacific 16.2.6 OMAP Keys Bug?
~Jay
-Original Message-
From: Igor Fedotov
Sent: Wednesday, January 19, 2022 8:24 AM
To: Jay Sullivan ; ceph-users@ceph.io
Subject: [ceph-users] Re: Scope of Pacific 16.2.6 OMAP Keys Bug?
Hey Jay,
first of all I'd like to mention that there were two OMAP naming scheme
modificat
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.sulli
lse
Am I missing a step in how to fully apply this setting?
Thanks!
~Jay
-Original Message-
From: Igor Fedotov
Sent: Tuesday, June 22, 2021 7:46 AM
To: Jay Sullivan ; ceph-users@ceph.io
Subject: Re: [ceph-users] Spurious Read Errors: 0x6706be76
Hi Jay,
this alert was introduced in
In the week since upgrading one of our clusters from Nautilus 14.2.21 to
Pacific 16.2.4 I've seen four spurious read errors that always have the same
bad checksum of 0x6706be76. I've never seen this in any of our clusters before.
Here's an example of what I'm seeing in the logs:
ceph-osd.132.lo
