From: Karl-Philipp Richter <krichter722@aol.de>
To: linux-btrfs@vger.kernel.org
Subject: Assertion `!(exist->nmirrors >= 2)' failed
Date: Tue, 24 Jun 2014 15:43:56 +0200 [thread overview]
Message-ID: <53A9809C.30705@aol.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Hi together,
I wondered whether
$ sudo btrfs rescue chunk-recover -y /dev/loop2p1
btrfs: chunk-recover.c:124: process_extent_buffer: Assertion
`!(exist->nmirrors >= 2)' failed.
$ echo $?
134
is an error in btrfs or an error message of (the correctly working)
btrfs. Any ideas what this could mean? I'm having this trouble with a
system which is so messed up that I even can't restore
$ sudo btrfs restore /dev/loop2p1 /mnt/data_extension/restore
parent transid verify failed on 1068982272 wanted 47618 found 47575
parent transid verify failed on 1068982272 wanted 47618 found 47575
parent transid verify failed on 1068982272 wanted 47618 found 47575
parent transid verify failed on 1068982272 wanted 47618 found 47575
Ignoring transid failure
leaf parent key incorrect 1068982272
Couldn't setup extent tree
parent transid verify failed on 1068982272 wanted 47618 found 47575
Ignoring transid failure
leaf parent key incorrect 1068982272
Couldn't read fs root: -1
I'm issueing the command because it seems to be the last thing I can do
to rescue any data of that partition.
This occurs with v3.12 (output of `btrfs --version`) as well as the
latest commit 24cf4d8c3ee924b474f68514e0167cc2e602a48d of btrfs-progs.
Best regards,
Kalle Richter
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]
next reply other threads:[~2014-06-24 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 13:43 Karl-Philipp Richter [this message]
2014-06-25 1:20 ` Assertion `!(exist->nmirrors >= 2)' failed Gui Hecheng
2014-07-18 9:29 ` Karl-Philipp Richter
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=53A9809C.30705@aol.de \
--to=krichter722@aol.de \
--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).