Thread (6 messages) 6 messages, 2 authors, 2021-11-23

Re: read time tree block corruption detected

From: Nikolay Borisov <hidden>
Date: 2021-11-22 10:36:44


On 22.11.21 г. 12:07, x8062 wrote:
At 2021-11-22 15:24:38, "Nikolay Borisov" [off-list ref] wrote:
quoted

On 22.11.21 г. 7:26, x8062 wrote:
quoted
Hello,
 I got periodic warns in my linux console. in dmesg it is the following pasted text.
At https://btrfs.wiki.kernel.org/index.php/Tree-checker I learned it may be a error, so i send the message. Hopefully it could help, Thanks in advance!

[  513.900852] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465

You have faulty ram, since 393 has the 17th bit set to 0 whilst has it
set to 1. So your ram is clearly corrupting bits. I advise you run a
memtest tool and look for possibly changing the faulty ram module.
Thank you, can't believe the ram is not so stable.  I'll run a memtest later.
Actually according to the output this is a read-time corruption. THis
means the corrupted data has already been written to disk, likely by an
older kernel that didn't have the tree cherk code. So running a memcheck
is still useful to prevent future corruption.

As far as the corrupted files goes - well its data is corrupted. It can
technically be fixed, but you'd have to do it yourself. Or alternatively
go back on an older kernel i.e pre- 5.11 and try to copy that particular
file (inode 2394634).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help