All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Evan LeCompte <evanlec@gmail.com>
Subject: Re: FS won't mount, open_ctree failed, Assertion !(path->slots[0] == 0) failed
Date: Tue, 27 Dec 2011 12:18:43 +0100	[thread overview]
Message-ID: <201112271218.43396.Martin@lichtvoll.de> (raw)
In-Reply-To: <4EF8C5C4.7090301@gmail.com>

Am Montag, 26. Dezember 2011 schrieb Evan LeCompte:
> On 12/23/2011 06:15 PM, Chris Mason wrote:
> > On Fri, Dec 23, 2011 at 09:37:28AM +0000, Evan LeCompte wrote:
> >> I'm having the very same issue as you. I've tried all the latest
> >> btrfs tools, btrfsck, btrfs-zero-log, restore, find-root etc etc.
> >>=20
> >> All to no avail. only err output is always
[=E2=80=A6]
> >> Is there ANY way to even recover ANY files at all from these btrfs
> >> filesystems that lose transid sync? mine occurred simply from a
> >> loose sata cable falling out of one of my drives while the system
> >> was running.
[=E2=80=A6]
> >> Please help us, anyone!
> >=20
> > Which kernel are you running?  If you're on a 3.2 kernel or you hav=
e
> > a recent pull of my git tree, you can try mount -o recovery.
[=E2=80=A6]
> Chris,
> Can you help me work through the copy out recovery tools that you
> mentioned?

If all else fails depending of the file formats of the files you want t=
o=20
recover you can also try some of the forensic tools like photorec from=20
testdisk or foremost. I believe there is a third one. This should get y=
ou=20
the files, although the filenames and directory structure will likely b=
e=20
lost. And it takes quite long on higher capacity or slow drives.

With photorec I managed to recover 100 images from a smartmedia card th=
at=20
appeared empty on Linux - while the digital camera still saw the images=
=2E

--=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-12-27 11:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07  2:39 FS won't mount, open_ctree failed, Assertion !(path->slots[0] == 0) failed dsmith
2011-12-23  9:37 ` Evan LeCompte
2011-12-23 18:15   ` Chris Mason
2011-12-25 18:56     ` Evan LeCompte
2011-12-25 19:00     ` Evan LeCompte
2011-12-26 19:06     ` Evan LeCompte
2011-12-27 11:14       ` Martin Steigerwald
2011-12-27 11:18       ` Martin Steigerwald [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=201112271218.43396.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=evanlec@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 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.