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
signature.asc
Description: OpenPGP digital signature
