From: Chris Mason <chris.mason@oracle.com>
To: Leszek Ciesielski <skolima@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs no csum found for inode X start 0
Date: Thu, 25 Feb 2010 19:45:30 -0500 [thread overview]
Message-ID: <20100226004530.GD29451@think> (raw)
In-Reply-To: <23a15591002250134m753cd437jb14e320d2e8b39b3@mail.gmail.com>
On Thu, Feb 25, 2010 at 10:34:22AM +0100, Leszek Ciesielski wrote:
> (My previous post seems to have been discarded because of the
> attachment size, I'm resending it without the dmesg output - which can
> be found @ http://pastebin.com/T0J3z59j )
>
> Hi,
>
> yesterday I updated my kernel (clean clone from
> mason/btrfs-unstable.gi), pulling in the single latest change I have
> been missing ( http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=commit;h=3f6fae9559225741c91f1320090b285da1413290
> ) and adding my patch from http://patchwork.kernel.org/patch/81547/ .
> Previous kernel version (without my patch - could this be my fault?)
> has been running fine for 14 days, but after recompiling and
> rebooting, my dmesg output is full of "btrfs no csum found for inode
> 386 start 0" and "btrfs csum failed ino 386 extent 65191274496 csum
> 1851253866 wanted 0 mirror 1" and "btrfs csum failed ino 82619 off
> 8749056 csum 2686054019 private 0",
I don't think your patch alone could have caused this. Has anything
else strange been happening on this machine?
The fact that all your files are wrong is especially strange. Have you
ever mounted this FS with mount -o nodatasum?
-chris
next prev parent reply other threads:[~2010-02-26 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23a15591002242352r665ffddax479d4cbfd8c88cdb@mail.gmail.com>
2010-02-25 9:34 ` btrfs no csum found for inode X start 0 Leszek Ciesielski
2010-02-25 20:52 ` Leszek Ciesielski
2010-02-25 23:21 ` Mike Fedyk
2010-02-26 0:45 ` Chris Mason [this message]
2010-02-26 10:51 ` Leszek Ciesielski
2010-02-26 16:19 ` Chris Mason
2010-02-26 20:53 ` Leszek Ciesielski
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=20100226004530.GD29451@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=skolima@gmail.com \
/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