From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Is my btrfs filesystem definitely dead?
Date: Sun, 12 May 2013 18:02:30 +0200 [thread overview]
Message-ID: <h1r46a-vsn.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: loom.20130512T115912-723@post.gmane.org
Ross <Ross.Richardson.aus@gmail.com> schrieb:
> Sébastien Luttringer <seblu <at> seblu.net> writes:
>
>>
>> Hello, after a crash with linux 3.8.0, I'm unable to
> mount my btrfs root
>> filesystem. I tried with a archlinux rescue cd with a
> linux 3.7.5, but I
>> got the following errors:
>>
>> First trying to fix the fs:
>>
>> # btrfsck
>> usage: btrfsck dev
>> Btrfs v0.20-rc1
>> # btrfsck /dev/sdd2
>> checking extents
>> checking fs roots
>> checking root refs
>> [1] 1051 segmentation fault (core dumped) btrfsck
> /dev/sdd2
>> # dmesg|grep 1051
>> [ 956.804097] btrfsck[1051]: segfault at 7f563c319410
> ip
>> 00007f56307c4c25 sp 00007ffffa7fbdf0 error 4 in
>> libc-2.17.so[7f563074a000+1a4000]
>>
>> Trying to mount the FS i got a OOPS.
>> # mount /dev/sdd2 /new_root
>> [ 60.602232] device label bitumefs devid 1 transid
> 40042 /dev/sdd2
>> [ 60.603629] btrfs: disk space caching is enabled
>> [ 60.615642] Btrfs detected SSD devices, enabling
> SSD mode
>> [ 60.769651] ------------[ cut here ]------------
>> [ 60.769709] kernel BUG at fs/btrfs/free-space-
> cache.c:1553!
[snip]
Tried to clear the space cache during mounting? There's a mount option for
it but currently do not remember it.
HTH,
Kai
prev parent reply other threads:[~2013-05-12 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 22:48 Is my btrfs filesystem definitely dead? Sébastien Luttringer
2013-02-24 0:30 ` Sébastien Luttringer
2013-02-24 0:32 ` Jan Steffens
2013-05-12 10:00 ` Ross
2013-05-12 16:02 ` Kai Krakow [this message]
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=h1r46a-vsn.ln1@hurikhan.ath.cx \
--to=hurikhan77+btrfs@gmail.com \
--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).