From: "Miguel Negrão" <miguel.negrao-lists@friendlyvirus.org>
To: "list, btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs check : extent-tree.c:283: find_search_start: Assertion `!(1)' failed
Date: Thu, 22 Aug 2013 11:28:56 +0100 [thread overview]
Message-ID: <5215E7E8.8030208@friendlyvirus.org> (raw)
In-Reply-To: <5213A46C.20701@friendlyvirus.org>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Hi,
Forgot to ask the important question, is it still possible to recover
this filesystem or is it doomed ?
best,
Miguel
Em 20-08-2013 18:16, Miguel Negrão escreveu:
> Hi,
>
> I have a btrfs partition on a usb external hard drive which doesn't
> mount anymore. I tried doing a btrfs check on it, but it fails with the
> error on the subject. The btrfs progs were compiled from git today. I
> have a backup of this partition elsewhere, so I can restore from there
> if all else fails.
>
> The output of
>
> sudo btrfs check --repair /dev/sdc1 > ~/log/btfs-repair-1.log 2>&1
>
> was
>
> parent transid verify failed on 7624175616 wanted 1431 found 1428
> parent transid verify failed on 7624175616 wanted 1431 found 1428
> Ignoring transid failure
> leaf parent key incorrect 7624175616
> checking extents
> parent transid verify failed on 7624175616 wanted 1431 found 1428
> Ignoring transid failure
>
> ...
>
>
> leaf parent key incorrect 7717249024
> Unable to find block group for 0
> btrfs: extent-tree.c:283: find_search_start: Assertion `!(1)' failed.
> enabling repair mode
> Checking filesystem on /dev/sdc1
> UUID: 42688de3-f4ed-4592-bb34-02c9d5014e51
>
>
>
> best,
>
--
Miguel Negrão
http://www.friendlyvirus.org/miguelnegrao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
prev parent reply other threads:[~2013-08-22 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 17:16 btrfs check : extent-tree.c:283: find_search_start: Assertion `!(1)' failed Miguel Negrão
2013-08-22 10:28 ` Miguel Negrão [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=5215E7E8.8030208@friendlyvirus.org \
--to=miguel.negrao-lists@friendlyvirus.org \
--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.