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: Fri, 8 Oct 2010 13:16:35 -0400 [thread overview]
Message-ID: <20101008171635.GS4804@think> (raw)
In-Reply-To: <loom.20101007T155351-932@post.gmane.org>
On Thu, Oct 07, 2010 at 02:12:33PM +0000, Gerhard Kulzer wrote:
> I have a weird problem concerning 5 btrfs partitions on 3 different disks:
> My system became slow and started to hang and go, so I shut it down and it
> hang totally whilst shutting down. With the sysrq shortcut I could kill it
> and restart.
>
> Booting didn't work any more throwing me into a shell at initramfs.
Ok, I'd like to go through each of these btrfs partitions one at a time.
> Here is a dmesg trace during booting from the CD, it not the crash yet.
>
> [ 7.782823] Btrfs loaded
> [ 7.786081] xor: automatically using best checksumming function: pIII_sse
> [ 7.804000] pIII_sse : 11626.000 MB/sec
> [ 7.804001] xor: using function: pIII_sse (11626.000 MB/sec)
> [ 7.805746] device-mapper: dm-raid45: initialized v0.2594b
> [ 7.851186] device fsid 3a4b4bc6c07de70b-2b32b3df70d2459f devid 1 transid
> 407064 /dev/sda2
> [ 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
next prev parent reply other threads:[~2010-10-08 17:16 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 [this message]
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
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=20101008171635.GS4804@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.