Re: [PATCH] btrfs-progs: Skip device tree when we failed to read it

[Qu Wenruo <quwenruo.btrfs@gmx.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1657 bytes --]



On 2019/12/7 上午11:47, Christian Wimmer wrote:
> Hi Qu,
> 
> 
>> Chunk tree is good, so is root tree and extent tree.
>>
>> You can go btrfs restore without problem. (Of course, need to use
>> patched version)
>>
>> Thanks,
>> Qu
> 
> 
> Unfortunately I can not restore the contents:
> 
> # ./btrfs restore /dev/sdb1 test/
> checksum verify failed on 5349895454720 found 000000A8 wanted 00000000
> checksum verify failed on 5349895454720 found 000000A8 wanted 00000000
> checksum verify failed on 5349895454720 found 000000A8 wanted 00000000
> bad tree block 5349895454720, bytenr mismatch, want=5349895454720, have=14275350892879035392
> WARNING: could not setup device tree, skipping it
> checksum verify failed on 3541835317248 found 00000044 wanted 00000000
> checksum verify failed on 3541835317248 found 00000061 wanted 0000001C
> checksum verify failed on 3541835317248 found 00000061 wanted 0000001C
> bad tree block 3541835317248, bytenr mismatch, want=3541835317248, have=18445340955138505899

This is another tree block corrupted, not the one in device tree.

And unfortunately, it's the fs tree (from your previews reply), and
that's not a good news.

This proved one bad news, there are more corruptions than we thought.

BTW, do you have any subvolumes/snapshots?
Since the corruption is in fs tree, we may have chances for other trees.

You can try "btrfs restore -l <dev>" grab the numbers and pass it to
"btrfs restore -r <number> <dev>" to try to recover other
subvolumes/snapshot.

Thanks,
Qu

> Error searching -5
> # 
> 
> What else can I try?
> 
> Thanks,
> 
> Chris
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]