On Wed, May 3, 2023 at 4:33 AM Janek Bevendorff <janek.bevendorff@uni-weimar.de> wrote:
Hi Patrick,
I'll try that tomorrow and let you know, thanks!
I was unable to reproduce the crash today. Even with mds_abort_on_newly_corrupt_dentry set to true, all MDS booted up correctly (though they took forever to rejoin with logs set to 20).
To me it looks like the issue has resolved itself overnight. I had run a recursive scrub on the file system and another snapshot was taken, in case any of those might have had an effect on this. It could also be the case that the (supposedly) corrupt journal entry has simply been committed now and hence doesn't trigger the assertion any more. Is there any way I can verify this?
You can run: https://github.com/ceph/ceph/blob/main/src/tools/cephfs/first-damage.py Just do: python3 first-damage.py --memo run.1 <meta pool> No need to do any of the other steps if you just want a read-only check. -- Patrick Donnelly, Ph.D. He / Him / His Red Hat Partner Engineer IBM, Inc. GPG: 19F28A586F808C2402351B93C3301A3E258DD79D