linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Schitter <ms@mur.at>
To: cwillu <cwillu@cwillu.com>
Cc: "Fajar A. Nugraha" <list@fajar.net>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs csum failed
Date: Wed, 04 May 2011 14:27:57 +0200	[thread overview]
Message-ID: <4DC1464D.4060204@mur.at> (raw)
In-Reply-To: <BANLkTiniD_mztDPriodDWybTzt7Dqtherg@mail.gmail.com>

Am 2011-05-04 13:51, schrieb cwillu:
>> 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.

well -- i am doing a backup of all images every night. this process 
should work like a simple "scrub" because all data (and its checksumes) 
will be read. that's the way i stumbled over this problem!

>> 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.

would it make some sense to remount the volume with checksumming enabled 
and run additional tests to find similar suspect blocks to prevent this 
kind of suddenly broken files?

martin

  reply	other threads:[~2011-05-04 12:27 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
2011-05-04 12:27           ` Martin Schitter [this message]
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=4DC1464D.4060204@mur.at \
    --to=ms@mur.at \
    --cc=cwillu@cwillu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list@fajar.net \
    /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).