First computer/file system: (from the photo):
[ 136.259984] BTRFS critical (device nvme0n1p8): corrupt leaf: root=257 block=31259951104 slot=9 ino=3244515, name hash mismatch with key, have 0x00000000F22F547D expect 0x0000000092294C62 This is not obviously a bit flip. I'm not sure what's going on here. Second computer/file system: [30177.298027] BTRFS critical (device nvme0n1p8): corrupt leaf: root=791 block=57084067840 slot=64 ino=1537855, name hash mismatch with key, have 0x00000000a461adfd expect 0x00000000a461adf5 This is clearly a bit flip. It's likely some kind of hardware related problem, despite the memory checking already done, it just is rare enough to evade detection with a typical memory tester like memtest86(+). You could try 'memtester' or '7z b 100' and see if you can trigger it. It's a catch-22 with such a straightforward problem like a bit flip, that it's risky to attempt a repair which can end up causing worse corruption. What about the mount options for both file systems? (cat /proc/mounts or /etc/fstab) -- Chris Murphy
