From: TAXI <taxi@a-city.de>
To: linux-btrfs@vger.kernel.org
Subject: FS Errors with 2.6.37
Date: Mon, 28 Feb 2011 08:30:38 +0100 [thread overview]
Message-ID: <20110228083038.18d56790@schlepptop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Hi,
I updated my kernel from 2.6.36 to 2.6.37 today but now I can't boot
anymore. The kernel sends BUG messages for BTRFS and couse of
that different services won't start correctly. Which services are
affected seems to chance from boot to boot and at the end the computer
hangs and my only change to reboot is using MagicSysRQ. I could save
the output of dmesg after one boot (which was hard couse the time I can
log me in and do things till the system hangs is short). Also when I'm
using magicSysRQ for syncing/unmounting partitions the BUG messages are
looping a few seconds.
Here is the relevant part of dmesg: http://pastebin.com/ideNvhBH
And (if needed) the full dmesg: http://pastebin.com/xDEct6TZ
The dmesg after booting with 2.6.36: http://pastebin.com/puT6Wx0v
The output of btrfsck: http://pastebin.com/9HbkVwLf
And a (bad quality) image of the (end of the) message when using
MagicSysRQ: http://img17.imageshack.us/img17/6895/dsc01892ja.jpg
I can still boot with the old 2.6.36 kernel.
Is there any way to access my data correctly with the 2.6.37 kernel?
P.S. Sorry for my bad english. :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
reply other threads:[~2011-02-28 7:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110228083038.18d56790@schlepptop \
--to=taxi@a-city.de \
--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).