From: Gerhard Kulzer <gerhard@kulzer.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: system crash at mounting of btrfs
Date: Sat, 9 Oct 2010 13:08:40 +0000 (UTC) [thread overview]
Message-ID: <loom.20101009T150327-437@post.gmane.org> (raw)
In-Reply-To: loom.20101009T073143-310@post.gmane.org
Gerhard Kulzer <gerhard <at> kulzer.net> writes:
>
> Chris Mason <chris.mason <at> oracle.com> writes:
>
> > > [ 7.881078] Btrfs detected SSD devices, enabling SSD mode
> > > [ 7.923553] ------------[ cut here ]------------
> > > [ 7.923556] kernel BUG at /build/buildd/linux-2.6.35/fs/btrfs
> /tree-log.c:813!
> > > [ 7.923558] invalid opcode: 0000 [#1] SMP
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > Once you see kernel BUG() that's the crash ;)
> >
> > This isn't from the btrfs scan, this is from mounting the FS. Could you
> > please mount the filesystems one at a time and see if they all fail or
> > of it is just this one.
> >
> > -chris
> > --
> Ahh big surprise, I can mount my other btrfs partitions (4 on 2 HDD) all of a
> sudden.
> I wonder why, because I tried before and I got a crash with all of them.
> The only difference now is that I took the SSD with the 5th partition out.
> I have a boot partition as ext4 on that same SSD drive which I can mount
> w/o problems. So I think it's not the SSD itself that is buggy.
>
Ok, I understand a bit more now.
a) when I boot my system from CD and the faulty SSD btrfs is physically present,
then there's a little hick-up during boot resulting in my first trace and the
system crashes if I subsequently mount ANY other btrfs partition.
b) If I boot w/o the SSD, then there is no hick-up and I can mount all remaining
btrfs partitions w/o crash and the data is there.
Gerhard
next prev parent reply other threads:[~2010-10-09 13:08 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 [this message]
2010-10-11 23:55 ` Chris Mason
2010-10-12 6:44 ` Gerhard Kulzer
2010-10-13 0:49 ` Chris Mason
2010-10-13 6:00 ` Francis Galiegue
2010-10-13 6:42 ` Gerhard Kulzer
2010-10-13 12:33 ` Erik Hoppe
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=loom.20101009T150327-437@post.gmane.org \
--to=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).