From: Karl-Philipp Richter <krichter722@aol.de>
To: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Assertion `!(exist->nmirrors >= 2)' failed
Date: Fri, 18 Jul 2014 11:29:36 +0200 [thread overview]
Message-ID: <53C8E900.7070302@aol.de> (raw)
In-Reply-To: <1403659201.22912.2.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]
Hi Gui,
I'm getting back at this a bit late, but I could now run `btrfsck
--repair` with btrfs-progs 24cf4d8c3ee924b474f68514e0167cc2e602a48d on
Linux 3.16-rc5 in an Oracle VirtualBox VM with Ubuntu 14.04. It doesn't
suceed yet, but at least I'm not getting immediate errors.
Best regards,
Karl
Am 25.06.2014 03:20, schrieb Gui Hecheng:
> On Tue, 2014-06-24 at 15:43 +0200, Karl-Philipp Richter wrote:
>> 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
>
> Hi, Karl
> For the Assertion above, this one below may do a help.
> https://patchwork.kernel.org/patch/4339091/
>
> -Gui
>
>> 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 --]
prev parent reply other threads:[~2014-07-18 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 13:43 Assertion `!(exist->nmirrors >= 2)' failed Karl-Philipp Richter
2014-06-25 1:20 ` Gui Hecheng
2014-07-18 9:29 ` Karl-Philipp Richter [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=53C8E900.7070302@aol.de \
--to=krichter722@aol.de \
--cc=guihc.fnst@cn.fujitsu.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 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).