This bug was initially created as a copy of Bug #2175307 I am copying this bug because: 5.3z2 clone of 6.1 bz Description of problem: This RFE is for a functionality in the MDS to detect specific damage to the metadata "dentries". The damage is associated with a long-standing bug (#38452). This change will catch the damage before it's persisted. If **new** damage is detected to be written to persistent storage (i.e. RADOS), the MDS will abort to avoid persisting damage. This will hopefully have the benefit of providing logs in the same time period that the damage was created for analysis. https://tracker.ceph.com/issues/38452 https://tracker.ceph.com/issues/58482 Documentation for support when customers encounter the abort will be forthcoming and available before 6.1 is released.
Hi Patrick, we are analyzing the issue. Can you please help with reproduction steps for the same. Regards, Amarnath
As initial backport tests did not pass and we are on a tight deadline, I am moving this to 5.3z3 for now. :( We may issue an async (or even grab it back) if we figure out and resolve the test issues fast enough.
(In reply to Amarnath from comment #2) > Hi Patrick, > > we are analyzing the issue. > Can you please help with reproduction steps for the same. You would run these tests: https://gitlab.cee.redhat.com/ceph/ceph/-/merge_requests/278/diffs#7b2dc3f617cfcca3e13c38ef537cd6355175ac6b_565_567
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat Ceph Storage 5.3 Bug Fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:3259