From: mail@ikherbers.com
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs write time tree block corruption
Date: Fri, 15 Apr 2022 16:15:36 +0200 [thread overview]
Message-ID: <Yll+CD/h6YmNX5TR@localhost> (raw)
In-Reply-To: <4daec659-c1d1-b100-89f7-8a2a2e3e1fc5@suse.com>
On 2022-04-15T10:04:01+0300, Nikolay Borisov wrote:
>
>
> On 15.04.22 г. 3:59 ч., Maik wrote:
> > Hello,
> >
> > I just received a corrupt leaf error on my root filesystem:
> > [29854.502499] BTRFS critical (device dm-0): corrupt leaf: root=2 block=579036020736 slot=86, unexpected item end, have 16789244 expect 12028
>
> This suggests a memory bitflip
>
> 16789244 = 1000000000010111011111100
> 12028 = ^ 10111011111100
>
> The good thing is the tree checker caught this before this corruption went
> on disk. I advise you do run memtest.
Thanks for the pointer.
Indeed my RAM was faulty :(, but the filesystem is alright.
Thank you all for this amazing bitflip detector :)!
Maik
prev parent reply other threads:[~2022-04-15 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 0:59 btrfs write time tree block corruption Maik
2022-04-15 7:04 ` Nikolay Borisov
2022-04-15 14:15 ` mail [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yll+CD/h6YmNX5TR@localhost \
--to=mail@ikherbers.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox