From: Arnd Bergmann <arnd@arndb.de>
To: dsterba@suse.cz
Cc: Chris Mason <chris.mason@fusionio.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Oops when mounting btrfs partition
Date: Mon, 11 Feb 2013 17:06:10 +0000 [thread overview]
Message-ID: <201302111706.10332.arnd@arndb.de> (raw)
In-Reply-To: <20130208161035.GI12339@twin.jikos.cz>
On Friday 08 February 2013, David Sterba wrote:
> On Mon, Feb 04, 2013 at 09:55:50PM +0000, Arnd Bergmann wrote:
> > On Saturday 02 February 2013, Chris Mason wrote:
> >
> > I've done a full backup of all data now, without any further Ooops messages, but
> > I did get these:
> >
> > [66155.429029] btrfs no csum found for inode 1212139 start 23707648
>
> The missing csums were caused by a bug introcuded in 3.8-rc1 and fixed
> in rc5.
>
Ok, thanks for the information.
Arnd
prev parent reply other threads:[~2013-02-11 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 14:51 Oops when mounting btrfs partition Arnd Bergmann
2013-02-02 15:20 ` Chris Mason
2013-02-02 17:58 ` Arnd Bergmann
2013-02-04 21:55 ` Arnd Bergmann
2013-02-08 16:10 ` David Sterba
2013-02-11 17:06 ` Arnd Bergmann [this message]
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=201302111706.10332.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--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).