linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Matthew Booth <matthew@heisenbug.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Unable to boot btrfs filesystem, and btrfsck aborts
Date: Mon, 11 Mar 2013 19:49:52 -0400	[thread overview]
Message-ID: <20130311234952.GF3058@localhost.localdomain> (raw)
In-Reply-To: <CAF8C-HiwkgnuMOgq_4AGYoK9pOKZoL-WGYVFc497BuU+_z2GbQ@mail.gmail.com>

On Mon, Mar 11, 2013 at 04:44:58PM -0600, Matthew Booth wrote:
> My laptop crashed hard earlier today. It reset immediately to a black
> screen followed by the BIOS. I have no idea why.
> 
> However, it now fails to boot. I took a picture of the kernel panic
> that results from trying to mount the root filesystem:
> https://plus.google.com/107763699965053810188/posts/QZZt7GYzBZi
> 
> To make things worse, btrfsck aborts with a double free, without
> fixing it. I took a picture of that, too:
> https://plus.google.com/107763699965053810188/posts/gKYqGgFhWyT
> 
> As the kernel panic mentions btrfs_remove_free_space, I also tried
> mounting with clear_cache. Unfortunately it didn't dislodge anything.
> 
> This is on a fully updated Fedora 18 system. I would really like to
> get this data back. If anybody could offer a suggestion I'd be very
> grateful.
>

This is fixed in 3.9, I'll send those patches back to -stable, sorry I should
have done that before now.  If you can't get a 3.9 kernel to boot then just use
btrfs-zero-log and you'll be good to go.  Thanks,

Josef 

      parent reply	other threads:[~2013-03-11 23:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 22:44 Unable to boot btrfs filesystem, and btrfsck aborts Matthew Booth
2013-03-11 22:49 ` Harald Glatt
2013-03-11 22:53   ` Jan Steffens
2013-03-11 22:57     ` Harald Glatt
2013-03-11 23:49 ` Josef Bacik [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=20130311234952.GF3058@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=matthew@heisenbug.com \
    /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).