[ceph-users] Re: [IMPORTANT NOTICE] Potential data corruption in Pacific

2021-10-29 Thread Igor Fedotov
Hi Tobias, thanks a lot for your input, certain improvment on the critical issue notification process is needed indeed. We have an active discussion in the dev community (CLT group specifically) on how to better arrange such notifications. Perhaps it would be good to have a wider audience fo

[ceph-users] Re: [IMPORTANT NOTICE] Potential data corruption in Pacific

2021-10-29 Thread Radoslav Milanov
Not everyone is subscribed to low traffic MLs. Something like should be posted on all lists I think. On 29.10.2021 г. 05:43 ч., Daniel Poelzleithner wrote: On 29/10/2021 11:23, Tobias Fischer wrote: I would propose to either create a separate Mailing list for these kind of Information from t

[ceph-users] Re: [IMPORTANT NOTICE] Potential data corruption in Pacific

2021-10-29 Thread Daniel Poelzleithner
On 29/10/2021 11:23, Tobias Fischer wrote: > I would propose to either create a separate Mailing list for these kind > of Information from the Ceph Dev Community or use a Mailing list where > not that much is happening, e.g. ceph-announce> > What do you think? I like that, low traffic ML are e

[ceph-users] Re: [IMPORTANT NOTICE] Potential data corruption in Pacific

2021-10-28 Thread Igor Fedotov
On 10/28/2021 7:13 PM, Eneko Lacunza wrote: Hi all, For those looking for the exact commands, I think they are: * Check value for bluestore_fsck_quick_fix_on_mount: ceph config get osd bluestore_fsck_quick_fix_on_mount * Set bluestore_fsck_quick_fix_on_mount to false: ceph config set osd b