From: Chris Mason <chris.mason@fusionio.com>
To: Russell Coker <russell@coker.com.au>
Cc: Chris Mason <clmason@fusionio.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Debian 3.7.1 BTRFS crash
Date: Thu, 14 Mar 2013 09:04:23 -0400 [thread overview]
Message-ID: <20130314130423.GJ15014@shiny.masoncoding.com> (raw)
In-Reply-To: <201303141736.09724.russell@coker.com.au>
On Thu, Mar 14, 2013 at 12:36:09AM -0600, Russell Coker wrote:
> On Thu, 14 Mar 2013, Chris Mason <chris.mason@fusionio.com> wrote:
> > Bad key ordering is pretty rare, and it usually means memory
> > corruptions. Are you reproducing this on the same machine or a
> > different one?
>
> I've attached a kernel message log of mounting it on another system (which
> incidentally has ECC RAM) running the Debian package of kernel 3.8.2. The end
> result of this was a system on which the sync command blocked in D state
> indefinitely and which couldn't be rebooted in any way other than a hardware
> reset.
Just to make sure I've got the sequence right, this is mounting the same
corrupted image on a second system?
The end result of that should be some messages about the bad blocks we
found and then the FS forced readonly. If not, you're right there is
definitely a bug there.
-chris
next prev parent reply other threads:[~2013-03-14 13:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 1:38 Debian 3.7.1 BTRFS crash Russell Coker
2013-03-13 1:56 ` Harald Glatt
2013-03-13 2:03 ` Eric Sandeen
2013-03-13 5:07 ` Jérôme Poulin
2013-03-13 10:56 ` Bart Noordervliet
2013-03-13 11:31 ` Swâmi Petaramesh
2013-03-14 19:04 ` Norbert Scheibner
2013-03-14 23:17 ` Martin Steigerwald
2013-03-13 13:47 ` Eric Sandeen
2013-03-13 14:03 ` Russell Coker
2013-03-13 19:19 ` Chris Mason
2013-03-14 6:36 ` Russell Coker
2013-03-14 13:04 ` Chris Mason [this message]
2013-03-14 9:48 ` Martin Steigerwald
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=20130314130423.GJ15014@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
/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).