From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: James Harvey <jmsharvey771@gmail.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs@vger.kernel.org
Subject: Re: csum failed, bad tree, block, IO failures. Is my drive dead or has my BTRFS broke itself?
Date: Mon, 18 Oct 2021 12:08:46 +0200 [thread overview]
Message-ID: <20211018100846.GF30611@twin.jikos.cz> (raw)
In-Reply-To: <32b91541-1b30-eb26-36d0-7a642172b547@suse.com>
On Sun, Oct 17, 2021 at 08:00:59AM +0800, Qu Wenruo wrote:
> On 2021/10/17 04:45, James Harvey wrote:
> > Check hasn't done yet, but it's spit out about 1700 messages (tmux
> > won't let me scroll up futher) that all look like this:
>
> Yeah, this means quite a lot of metadata are filled with garbage.
>
> I'm not sure why, but it doesn't like to be caused by btrfs itself.
Agreed, this amount of garbage would be detected by other means
(mismatching csums while the system is still in use or by
pre-write/post-read tree checker). It's not bitflips, there are too many
changes eg. in the bogus block offsets.
Analyzing the actual data left on disk for some known pattern could at
least give some hint what it was, eg. strings, file headers or raw
pointers. Besides that a manual system check could prevent that in the
future, so check cables, possible overheating, up to date
kernel/firmware (in case it would be cause by other subsystems).
next prev parent reply other threads:[~2021-10-18 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 0:14 csum failed, bad tree, block, IO failures. Is my drive dead or has my BTRFS broke itself? James Harvey
2021-10-16 1:52 ` Qu Wenruo
2021-10-16 3:18 ` James Harvey
2021-10-16 3:30 ` Qu Wenruo
2021-10-16 20:45 ` James Harvey
2021-10-17 0:00 ` Qu Wenruo
2021-10-18 10:08 ` David Sterba [this message]
2021-10-18 10:37 ` James Harvey
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=20211018100846.GF30611@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=jmsharvey771@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.