From: Martin Schitter <ms@mur.at>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs csum failed
Date: Wed, 04 May 2011 13:39:46 +0200 [thread overview]
Message-ID: <4DC13B02.9030604@mur.at> (raw)
In-Reply-To: <BANLkTin1quUuSq4oKdt1SowTPv4dhGEM5g@mail.gmail.com>
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.
whenever i make a simple:
cat snapshot-2011-05-02-18:13/sata-images/image_xy.raw > /dev/null
i get an "Input/output error" and the quoted debug messages in dmesg and
kernel-log
could this be seen as an useful starting point for further investigations?
> Usually checksum errors is early sign of hardware failure (most
> common are disk or power supply).
that looks very unplausible to me. there is an RAID1 layer beneath btrfs
in our setup and i don't see any errors there.
and the 'nodatasum' option should also ignore csum issues.-- isn't it?
martin
next prev parent reply other threads:[~2011-05-04 11:39 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 [this message]
2011-05-04 11:47 ` Hugo Mills
2011-05-04 11:51 ` cwillu
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=4DC13B02.9030604@mur.at \
--to=ms@mur.at \
--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).