From: Alexander Beregalov <a.beregalov@gmail.com>
To: Chris Mason <chris.mason@oracle.com>,
Alexander Beregalov <a.beregalov@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfsck: checksum verify failed
Date: Thu, 12 Nov 2009 17:16:34 +0300 [thread overview]
Message-ID: <a4423d670911120616k2538809erc006c26fe86eb14d@mail.gmail.com> (raw)
In-Reply-To: <20091112140233.GB5211@think>
2009/11/12 Chris Mason <chris.mason@oracle.com>:
> On Thu, Nov 12, 2009 at 05:08:53AM +0300, Alexander Beregalov wrote:
>> # for i in `seq 1 20`; do btrfsck /dev/sde|grep "checksum verify
>> failed";echo; done
>> checksum verify failed on 31945617408 wanted 6607632D found 9CC3ED0
>> checksum verify failed on 31945617408 wanted 6607632D found AFBBF41
>
> Was your filesystem mounted at the time? =C2=A0It's strange that the =
checksum
> keeps changing, that points to the data in the block changing.
It was not.
Any tips how I can try to find a root cause?
It is raid0 of two disks.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-12 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 2:08 btrfsck: checksum verify failed Alexander Beregalov
2009-11-12 14:02 ` Chris Mason
2009-11-12 14:16 ` Alexander Beregalov [this message]
2009-11-12 14:50 ` Chris Mason
2009-11-12 15:43 ` Alexander Beregalov
2009-11-12 17:25 ` Chris Mason
2009-11-12 17:41 ` Alexander Beregalov
2009-11-12 20:03 ` Chris Mason
2009-11-12 21:44 ` Alexander Beregalov
2009-11-13 21:17 ` Chris Mason
[not found] <AANLkTikncVbqe7BJp+PAT3eCzLVgEWo-OzbmADHyARvB@mail.gmail.com>
2010-08-09 3:32 ` Evert Vorster
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=a4423d670911120616k2538809erc006c26fe86eb14d@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=chris.mason@oracle.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