BTRFS critical: corrupt leaf: name hash mismatch with key â options?

Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
I have lots of these messages in my journal:
kernel: BTRFS critical (device dm-5): corrupt leaf: root=5 block=879480373248 slot=55 ino=820922, name hash mismatch with key, have 0x00000000e1726375 expect 0x0000000030b05af8
Occasionally, the file system will, apparently spontaneously (but probably in connection to these messages), switch into read-only mode, which is fairly annoying because I only start noticing it once I already have something IâÂÂd like to save, and a reboot seems to be the only solution. Apart from that, though, the file system appears to function normally, so IâÂÂm not convinced those messages are quite as critical as they sound.
A btrfs scrub doesnâÂÂt help (âÂÂtotal bytes scrubbed: 894.66GiB with 0 errorsâÂÂ).
What options do I have to address this? The file system in question is the root file system, and IâÂÂd prefer to not have to reinstall my system, mainly because I currently donâÂÂt have enough free space on external disks.
The message is always identical, so the problem only seems to affect the one block mentioned. If IâÂÂm guessing correctly that ino= refers to an inode number, then the affected path seems to be one I donâÂÂt really care about (command courtesy of this answer):
$ sudo btrfs inspect-internal inode-resolve 820922 /
//home/[user name]/.cache/mozilla/firefox/[profile name]/cache2/entries
Trying to list entries of that directory will cause ls to spew out a bunch of EIO errors while trying to stat some of the files in the directory. Switching to long output format makes it clearer that most files in the directory are not affected â itâÂÂs just a few files where permissions, owner and timestamp are a bunch of question marks, between a lot more files where the metadata is intact and readable.
I could try to delete those entries that seem to be unstatable, or even the entire directory, since itâÂÂs just a cache anyways, apparently. But before I try it and potentially wreak more havoc on an already damaged portion of the file system â does anyone know if thatâÂÂs a good idea or not? Or other ideas for investigating this situation?
filesystems btrfs root-filesystem
add a comment |Â
up vote
-1
down vote
favorite
I have lots of these messages in my journal:
kernel: BTRFS critical (device dm-5): corrupt leaf: root=5 block=879480373248 slot=55 ino=820922, name hash mismatch with key, have 0x00000000e1726375 expect 0x0000000030b05af8
Occasionally, the file system will, apparently spontaneously (but probably in connection to these messages), switch into read-only mode, which is fairly annoying because I only start noticing it once I already have something IâÂÂd like to save, and a reboot seems to be the only solution. Apart from that, though, the file system appears to function normally, so IâÂÂm not convinced those messages are quite as critical as they sound.
A btrfs scrub doesnâÂÂt help (âÂÂtotal bytes scrubbed: 894.66GiB with 0 errorsâÂÂ).
What options do I have to address this? The file system in question is the root file system, and IâÂÂd prefer to not have to reinstall my system, mainly because I currently donâÂÂt have enough free space on external disks.
The message is always identical, so the problem only seems to affect the one block mentioned. If IâÂÂm guessing correctly that ino= refers to an inode number, then the affected path seems to be one I donâÂÂt really care about (command courtesy of this answer):
$ sudo btrfs inspect-internal inode-resolve 820922 /
//home/[user name]/.cache/mozilla/firefox/[profile name]/cache2/entries
Trying to list entries of that directory will cause ls to spew out a bunch of EIO errors while trying to stat some of the files in the directory. Switching to long output format makes it clearer that most files in the directory are not affected â itâÂÂs just a few files where permissions, owner and timestamp are a bunch of question marks, between a lot more files where the metadata is intact and readable.
I could try to delete those entries that seem to be unstatable, or even the entire directory, since itâÂÂs just a cache anyways, apparently. But before I try it and potentially wreak more havoc on an already damaged portion of the file system â does anyone know if thatâÂÂs a good idea or not? Or other ideas for investigating this situation?
filesystems btrfs root-filesystem
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I have lots of these messages in my journal:
kernel: BTRFS critical (device dm-5): corrupt leaf: root=5 block=879480373248 slot=55 ino=820922, name hash mismatch with key, have 0x00000000e1726375 expect 0x0000000030b05af8
Occasionally, the file system will, apparently spontaneously (but probably in connection to these messages), switch into read-only mode, which is fairly annoying because I only start noticing it once I already have something IâÂÂd like to save, and a reboot seems to be the only solution. Apart from that, though, the file system appears to function normally, so IâÂÂm not convinced those messages are quite as critical as they sound.
A btrfs scrub doesnâÂÂt help (âÂÂtotal bytes scrubbed: 894.66GiB with 0 errorsâÂÂ).
What options do I have to address this? The file system in question is the root file system, and IâÂÂd prefer to not have to reinstall my system, mainly because I currently donâÂÂt have enough free space on external disks.
The message is always identical, so the problem only seems to affect the one block mentioned. If IâÂÂm guessing correctly that ino= refers to an inode number, then the affected path seems to be one I donâÂÂt really care about (command courtesy of this answer):
$ sudo btrfs inspect-internal inode-resolve 820922 /
//home/[user name]/.cache/mozilla/firefox/[profile name]/cache2/entries
Trying to list entries of that directory will cause ls to spew out a bunch of EIO errors while trying to stat some of the files in the directory. Switching to long output format makes it clearer that most files in the directory are not affected â itâÂÂs just a few files where permissions, owner and timestamp are a bunch of question marks, between a lot more files where the metadata is intact and readable.
I could try to delete those entries that seem to be unstatable, or even the entire directory, since itâÂÂs just a cache anyways, apparently. But before I try it and potentially wreak more havoc on an already damaged portion of the file system â does anyone know if thatâÂÂs a good idea or not? Or other ideas for investigating this situation?
filesystems btrfs root-filesystem
I have lots of these messages in my journal:
kernel: BTRFS critical (device dm-5): corrupt leaf: root=5 block=879480373248 slot=55 ino=820922, name hash mismatch with key, have 0x00000000e1726375 expect 0x0000000030b05af8
Occasionally, the file system will, apparently spontaneously (but probably in connection to these messages), switch into read-only mode, which is fairly annoying because I only start noticing it once I already have something IâÂÂd like to save, and a reboot seems to be the only solution. Apart from that, though, the file system appears to function normally, so IâÂÂm not convinced those messages are quite as critical as they sound.
A btrfs scrub doesnâÂÂt help (âÂÂtotal bytes scrubbed: 894.66GiB with 0 errorsâÂÂ).
What options do I have to address this? The file system in question is the root file system, and IâÂÂd prefer to not have to reinstall my system, mainly because I currently donâÂÂt have enough free space on external disks.
The message is always identical, so the problem only seems to affect the one block mentioned. If IâÂÂm guessing correctly that ino= refers to an inode number, then the affected path seems to be one I donâÂÂt really care about (command courtesy of this answer):
$ sudo btrfs inspect-internal inode-resolve 820922 /
//home/[user name]/.cache/mozilla/firefox/[profile name]/cache2/entries
Trying to list entries of that directory will cause ls to spew out a bunch of EIO errors while trying to stat some of the files in the directory. Switching to long output format makes it clearer that most files in the directory are not affected â itâÂÂs just a few files where permissions, owner and timestamp are a bunch of question marks, between a lot more files where the metadata is intact and readable.
I could try to delete those entries that seem to be unstatable, or even the entire directory, since itâÂÂs just a cache anyways, apparently. But before I try it and potentially wreak more havoc on an already damaged portion of the file system â does anyone know if thatâÂÂs a good idea or not? Or other ideas for investigating this situation?
filesystems btrfs root-filesystem
filesystems btrfs root-filesystem
asked 6 mins ago
Lucas Werkmeister
34616
34616
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f478717%2fbtrfs-critical-corrupt-leaf-name-hash-mismatch-with-key-options%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password