linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Not Zippy <notzippy@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs: open_ctree failed
Date: Mon, 26 Mar 2012 22:57:40 +0100	[thread overview]
Message-ID: <20120326215740.GA2597@carfax.org.uk> (raw)
In-Reply-To: <CANDob0+cBXnNH1dZ5socF7vaNoAB8wHACA4cN-w_1Z4T=VKUbA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]

On Mon, Mar 26, 2012 at 02:40:24PM -0700, Not Zippy wrote:
> Was working this morning and my kernel crashed. Unfortunately one of
> my two btrfs partitions would not mount after rebooting, this is the
> error log:
> [ 1518.147030] device label MediaNew devid 1 transid 28844 /dev/sdc3
> [ 1518.147364] btrfs: enabling auto defrag
> [ 1518.147372] btrfs: use lzo compression
> [ 1518.632469] parent transid verify failed on 498530500608 wanted
> 26696 found 27535
> [ 1518.632707] parent transid verify failed on 498530500608 wanted
> 26696 found 27535
> [ 1518.640263] parent transid verify failed on 498530500608 wanted
> 26696 found 27535
> [ 1518.640279] parent transid verify failed on 498530500608 wanted
> 26696 found 27535
> [ 1518.660243] btrfs: open_ctree failed
> 
> Tried btrfsck after a lot of messages got:
> ...
> leaf parent key incorrect 563096514560
> Unable to find block group for 0
> btrfsck: extent-tree.c:284: find_search_start: Assertion `!(1)' failed.

   btrfsck doesn't fix anything. It just checks the FS and tells you
that there's something wrong (which it just did). If you're feeling
very very brave, there's the "dangerdonteveruse" branch of the
btrfs-progs tools in cmason's git, which might fix things.
Alternatively, it might fuck up your filesystem so badly there's no
way you can retrieve any remaining data from it. Your choice.

> My kernel 3.0.0-16-generic, any hope for this ? Or is he dead jim ? I
            ^^^^^ Old, old, old. It's a bit late now, but you should
                  really keep up with the latest kernels. That should help
				  minimise this kind of event.

> don't have any snapshots of the partition.

   btrfs snapshots wouldn't help here. LVM snapshots would, of course.

   There's a restore tool that may allow you to copy off any data
that's not backed up (you *do* have backups, right? for an
experimental filesystem?). See the wiki at [1].

   Hugo.

[1] http://btrfs.ipv5.de/index.php?title=Restore

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
    --- "I will not be pushed,  filed, stamped, indexed, briefed, ---    
               debriefed or numbered.  My life is my own."               

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2012-03-26 21:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANDob0+rwkLGeJg4kP+TpPpN8VOdrOV684F5YiLC6+BkzYehHA@mail.gmail.com>
2012-03-26 21:40 ` btrfs: open_ctree failed Not Zippy
2012-03-26 21:57   ` Hugo Mills [this message]
2012-03-26 22:36     ` Not Zippy
2012-03-26 22:47       ` Hugo Mills
2012-03-27  0:20         ` Chris Samuel
2012-03-27 12:58         ` Not Zippy
2012-03-27 13:02           ` Hugo Mills
2012-03-27 15:21             ` Not Zippy
2012-03-27 17:37               ` Not Zippy
     [not found] <4EE6C49A.5070600@genome.wustl.edu>
2011-12-14 22:43 ` Samuel Just
     [not found] <CAPXeO6QbDxyoqYRhXxMGvc9JYQ6TZrTF7MwCNg-xdU-MgCQU3w@mail.gmail.com>
2011-07-07  9:20 ` Yulin, Denis

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=20120326215740.GA2597@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=notzippy@gmail.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).