linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Gerhard Kulzer <gerhard@kulzer.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: system crash at mounting of btrfs
Date: Tue, 12 Oct 2010 20:49:15 -0400	[thread overview]
Message-ID: <20101013004915.GM22691@think> (raw)
In-Reply-To: <loom.20101012T083638-169@post.gmane.org>

On Tue, Oct 12, 2010 at 06:44:13AM +0000, Gerhard Kulzer wrote:
> Chris Mason <chris.mason <at> oracle.com> writes:
> 
> 
> > 
> > Ok, so tell me more about the SSD with the btrfs-of-death.  Is it a
> > multi-device SSD?
> > 
> > -chris
> > 
> Its a single device Intel X25-M G2 Postville 80GB

Ok, if you can confirm this is the very first oops you see:

[    7.923556] kernel BUG at /build/buildd/linux-2.6.35/fs/btrfs/tree-log.c:813!

I've got a utility that will wipe the log and get you mountable again.
The intel drive should definitely support barriers, are you doing
anything with LVM or raid or dm-crypt on top of it?

-chris

  reply	other threads:[~2010-10-13  0:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 14:12 system crash at mounting of btrfs Gerhard Kulzer
2010-10-08  6:32 ` Gerhard Kulzer
2010-10-08 17:16 ` Chris Mason
2010-10-09  5:37   ` Gerhard Kulzer
2010-10-09 13:08     ` Gerhard Kulzer
2010-10-11 23:55       ` Chris Mason
2010-10-12  6:44         ` Gerhard Kulzer
2010-10-13  0:49           ` Chris Mason [this message]
2010-10-13  6:00             ` Francis Galiegue
2010-10-13  6:42             ` Gerhard Kulzer
2010-10-13 12:33             ` Erik Hoppe
  -- strict thread matches above, loose matches on Subject: below --
2010-10-08  6:43 Tomasz Chmielewski
2010-10-08 16:49 ` Gerhard Kulzer
2010-10-08 16:53   ` Chris Mason
2010-10-08 17:04     ` Gerhard Kulzer
2010-10-27 14:39 [PATCH] Btrfs: fix dentry->d_parent abuses Josef Bacik
2010-10-27 14:53 ` system crash at mounting of btrfs Erik Hoppe

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=20101013004915.GM22691@think \
    --to=chris.mason@oracle.com \
    --cc=gerhard@kulzer.net \
    --cc=linux-btrfs@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).