From: David Sterba <dsterba@suse.cz>
To: Chris Murphy <lists@colorremedies.com>
Cc: "Niccolò Belli" <darkbasic@linuxsystems.it>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
"Qu Wenruo" <quwenruo.btrfs@gmx.com>,
"Josef Bacik" <josef@toxicpanda.com>
Subject: Re: Dead fs on 2 Fedora systems: block=57084067840 write time tree block corruption detected
Date: Fri, 16 Apr 2021 12:16:57 +0200 [thread overview]
Message-ID: <20210416101657.GX7604@twin.jikos.cz> (raw)
In-Reply-To: <CAJCQCtQ_B6b2vrntaXLO5bWdi_1X7p09F84S1pbpEVXX9_g_1w@mail.gmail.com>
On Thu, Apr 15, 2021 at 11:06:32AM -0600, Chris Murphy wrote:
> First computer/file system:
>
> (from the photo):
>
> [ 136.259984] BTRFS critical (device nvme0n1p8): corrupt leaf: root=257
> block=31259951104 slot=9 ino=3244515, name hash mismatch with key, have
> 0x00000000F22F547D expect 0x0000000092294C62
>
> This is not obviously a bit flip. I'm not sure what's going on here.
Not a bitflip in the hash itself, but it's produced by hashing a file
name, and if that had a bitflip then the hashes would differ. We've seen
a that already, there could be traces of the bogus filename in logs.
> Second computer/file system:
>
> [30177.298027] BTRFS critical (device nvme0n1p8): corrupt leaf: root=791
> block=57084067840 slot=64 ino=1537855, name hash mismatch with key, have
> 0x00000000a461adfd expect 0x00000000a461adf5
Yes that's a bitflip in the hash,
bin(0x00000000a461adfd^0x00000000a461adf5) = 0b1000
next prev parent reply other threads:[~2021-04-16 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 7:33 Dead fs on 2 Fedora systems: block=57084067840 write time tree block corruption detected Niccolò Belli
2021-04-15 17:06 ` Chris Murphy
2021-04-16 10:16 ` David Sterba [this message]
2021-04-15 17:27 ` Chris Murphy
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=20210416101657.GX7604@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=darkbasic@linuxsystems.it \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.com \
/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