Corrupt leaf, name hash mismatch with key

[Michał Węgrzynek]

Hi!






It correlated  with a backing device error:



so it seems this the reason for corruption.




total 0








Regards,

Michał

I'm running btrfs on a bcache device, for now, it performed flawlessly. Yesterday, however, during backup, I found the following errors in the journal: BTRFS critical (device bcache0): corrupt leaf: root=1 block=367591424 slot=1 ino=10085264, name hash mismatch with key, have 0x00000000fffffffe expect 0x0000000099a9205a maj 02 16:47:58 miner kernel: print_req_error: I/O error, dev sdb, sector 8950560 maj 02 16:48:41 miner kernel: sd 2:0:0:0: [sdb] tag#29 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE maj 02 16:48:41 miner kernel: sd 2:0:0:0: [sdb] tag#29 Sense Key : Medium Error [current] maj 02 16:48:41 miner kernel: sd 2:0:0:0: [sdb] tag#29 Add. Sense: Unrecovered read error - auto reallocate failed maj 02 16:48:41 miner kernel: sd 2:0:0:0: [sdb] tag#29 CDB: Read(16) 88 00 00 00 00 00 00 88 92 f0 00 00 01 00 00 00 The inode in question corresponds to /home/mwegrzynek/.cache/google-chrome/Default/Cache/ so it's making a lot of noise during Chrome usage ;). I'm not able to delete it, nor its parent [mwegrzynek@miner ~]$ LC_ALL=C rm -rf /home/mwegrzynek/.cache/google-chrome/Default/Cache/ rm: cannot remove '/home/mwegrzynek/.cache/google-chrome/Default/Cache/': Directory not empty [mwegrzynek@miner ~]$ LC_ALL=C ls -l /home/mwegrzynek/.cache/google-chrome/Default/Cache/ ls: reading directory '/home/mwegrzynek/.cache/google-chrome/Default/Cache/': Input/output error [mwegrzynek@miner ~]$ LC_ALL=C rm -rf /home/mwegrzynek/.cache/google-chrome/Default/ rm: cannot remove '/home/mwegrzynek/.cache/google-chrome/Default/Cache': Directory not empty I tried to run btrfs check --repair on this filesystem, but it just looped on this inode for a half an hour not fixing anything (sorry, no logs available, but I may try to reproduce them if needed). I was able to rename the folder, so no problems for now for me, I also ordered a replacement drive. Can you tell me, how to fix these kinds of errors? Would they be corrected when running a mirror? How to deal with these things in production setup?

smime.p7s
Description: Kryptograficzna sygnatura S/MIME