From: Chris Mason <chris.mason@oracle.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: csum errors
Date: Thu, 15 Jul 2010 15:03:09 -0400 [thread overview]
Message-ID: <20100715190309.GI8623@think> (raw)
In-Reply-To: <201007152030.18431.johannes.hirte@fem.tu-ilmenau.de>
On Thu, Jul 15, 2010 at 08:30:17PM +0200, Johannes Hirte wrote:
> Am Dienstag 13 Juli 2010, 14:23:58 schrieb Johannes Hirte:
> > ino 1959333 off 898342912 csum 4271223884 private 4271223883
>
> I think, this is a different error. I've only seen them on filesystems from my
> Opteron system. It seems that the recorded csums are wrong and it looks to me
> like rounding errors. The data itself should be correct, as I've tested one
> affected file via md5sum against the original on another filesystem.
> Any ideas what is going wrong here?
Are you doing data mirroring?
We can map that block and do a raw read off the device to see what the
data blocks actually contain.
-chris
next prev parent reply other threads:[~2010-07-15 19:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 14:27 kernel BUG at fs/btrfs/extent-tree.c:1353 Johannes Hirte
2010-07-08 14:31 ` Chris Mason
2010-07-08 15:40 ` Johannes Hirte
2010-07-14 15:25 ` Johannes Hirte
2010-07-15 0:11 ` Dave Chinner
2010-07-15 18:14 ` Johannes Hirte
2010-07-16 14:59 ` Johannes Hirte
2010-07-19 8:01 ` Miao Xie
2010-07-22 18:07 ` Johannes Hirte
2010-07-23 11:02 ` Daniel J Blueman
2010-07-23 11:14 ` Bob Copeland
2010-07-29 17:09 ` Johannes Hirte
2010-07-29 18:54 ` Jens Axboe
2010-08-13 12:19 ` David Woodhouse
2010-07-11 12:28 ` Johannes Hirte
2010-07-13 12:23 ` Johannes Hirte
2010-07-15 18:30 ` csum errors Johannes Hirte
2010-07-15 19:03 ` Chris Mason [this message]
2010-07-15 19:32 ` Johannes Hirte
2010-07-15 19:35 ` Chris Mason
2010-07-15 20:00 ` Johannes Hirte
2010-07-17 4:55 ` Brian Rogers
2010-08-10 21:06 ` Sebastian 'gonX' Jensen
2010-08-14 7:05 ` Brian Rogers
2010-08-14 11:10 ` Sebastian 'gonX' Jensen
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=20100715190309.GI8623@think \
--to=chris.mason@oracle.com \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).