From: cwillu <cwillu@cwillu.com>
To: Martin Schitter <ms@mur.at>
Cc: "Fajar A. Nugraha" <list@fajar.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs csum failed
Date: Wed, 4 May 2011 05:51:03 -0600 [thread overview]
Message-ID: <BANLkTiniD_mztDPriodDWybTzt7Dqtherg@mail.gmail.com> (raw)
In-Reply-To: <4DC13B02.9030604@mur.at>
On Wed, May 4, 2011 at 5:39 AM, Martin Schitter <ms@mur.at> wrote:
> Am 2011-05-04 04:18, schrieb Fajar A. Nugraha:
>>>
>>> could you give me some advice how to debug/report this specific
>>> problem more
>>>>
>>>> precise?
>>
>> If it's not reproducible then I'd suspect it'd be hard to do.
>
> the last working snapshot is from 2011-05-02-17:13. i can reproduce this
> file system corruption on one specific file in any hourly snapshot later.
That's not surprising, any later snapshots will be sharing the same
corrupted block.
> that looks very unplausible to me. there is an RAID1 layer beneath btrfs in
> our setup and i don't see any errors there.
That doesn't rule out the possibility of corruption when it was
written in the first place, or some similar problem that the raid1
faithfully reproduced on both mirrors. That's not to say that it's
impossible that the problem is in btrfs, just that it's not the only
plausible possibility.
> and the 'nodatasum' option should also ignore csum issues.-- isn't it?
No, it only affects writing new checksums; any existing checksums are
still checked.
next prev parent reply other threads:[~2011-05-04 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 21:56 btrfs csum failed Martin Schitter
2011-05-04 0:28 ` Josef Bacik
2011-05-04 0:44 ` Martin Schitter
2011-05-04 2:18 ` Fajar A. Nugraha
2011-05-04 11:39 ` Martin Schitter
2011-05-04 11:47 ` Hugo Mills
2011-05-04 11:51 ` cwillu [this message]
2011-05-04 12:27 ` Martin Schitter
2011-05-04 13:23 ` Edward Ned Harvey
2011-05-04 14:42 ` Martin Schitter
2011-05-04 18:10 ` Chris Mason
2011-05-04 14:09 ` Jan Schmidt
2011-05-04 12:31 ` Kaspar Schleiser
2011-05-04 13:25 ` Martin Schitter
2011-05-04 14:39 ` Josef Bacik
2011-05-04 12:39 ` Chris Mason
2011-05-04 14:06 ` Martin Schitter
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=BANLkTiniD_mztDPriodDWybTzt7Dqtherg@mail.gmail.com \
--to=cwillu@cwillu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
--cc=ms@mur.at \
/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;
as well as URLs for NNTP newsgroup(s).