05.04.19 22:32, Hugo Mills пише: >> Yet another corruption of my root BTRFS filesystem happened today. >> Didn't bother to run scrub, balance or check, just created disk image for future investigation and restored everything from backup. >> >> Here is what corruption looks like: >> [ 274.241339] BTRFS info (device dm-0): disk space caching is enabled >> [ 274.241344] BTRFS info (device dm-0): has skinny extents >> [ 274.283238] BTRFS info (device dm-0): enabling ssd optimizations >> [ 310.436672] BTRFS critical (device dm-0): corrupt leaf: root=268 block=42044719104 slot=123, bad key order, prev (1240717 108 41447424) current (1240717 76 41451520) > "Bad key order" is usually an indicator of faulty RAM -- a piece of > metadata gets loaded into RAM for modification, a bit gets flipped in > it (because the bit is stuck on one value), and then the csum is > computed for the page (including the faulty bit), and written out to > disk. In this case, it's not obvious, but I'd suggest that the second > field of the key has been flipped, as 108 is 0x6c, and 76 is 0x4c -- > one bit away from each other. > > I recommend you check your hardware thoroughly before attempting to > rebuild the FS. > > Hugo. Hm... this might indeed be related to RAM being overclocked a bit too much. It worked fine for a long time, but apparently not 100% stable. Rolled back overclock, thanks for suggestion! Sincerely, Nazar Mokrynskyi github.com/nazar-pc
