Assertion `!(exist->nmirrors >= 2)' failed
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 $?
134is 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: -1I'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
Quoted 8 lines · Karl-Philipp Richter
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
Quoted 26 lines
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: -1I'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 commit24cf4d8c3ee924b474f68514e0167cc2e602a48dof btrfs-progs.Best regards,
Kalle Richter
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:
Quoted 44 lines · Karl-Philipp Richter
Quoted 8 lines
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 $? 134Hi, Karl
For the Assertion above, this one below may do a help.
https://patchwork.kernel.org/patch/4339091/-Gui
Quoted 26 lines
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: -1I'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 commit24cf4d8c3ee924b474f68514e0167cc2e602a48dof btrfs-progs.Best regards,
Kalle Richter