On 2018年06月30日 06:11, marble wrote: > Hey, > Thanks for the quick reply :-) > >> Is there anything like unexpected power loss happens? > Power loss may have happened. >> And would you provide the following data for debugging? >> >> # btrfs ins dump-super -fFa /dev/mapper/black > I attached it.
Looks pretty good. Then we could go through normal salvage routine. Please try the following commands and especially keep an eye on the stderr output: (The follow option is added in recent btrfs-progs releases, so please ensure your btrfs-progs is up to date) # btrfs ins dump-tree -b 1084653568 --follow /dev/mapper/black # btrfs ins dump-tree -b 1083604992 --follow /dev/mapper/black # btrfs ins dump-tree -b 1083981824 --follow /dev/mapper/black # btrfs ins dump-tree -b 1084325888 --follow /dev/mapper/black Or just use old roots and let btrfs check to judge: # btrfs check --tree-root 1084751872 /dev/mapper/black # btrfs check --tree-root 1083801600 /dev/mapper/black # btrfs check --tree-root 1084145664 /dev/mapper/black # btrfs check --tree-root 1084473344 /dev/mapper/black >> And further more, what's the device mapper setup for /dev/mapper/black? >> Is there anything like RAID here? > I think this is the result of luks. "black" is the name I passed to > cryptsetup open. Maybe some powerloss screwed up encryption? I'm not pretty sure how things will happen when power loss happens. Anyway, let's see how above btrfs check and dump-tree ends. Thanks, Qu >> Thanks, >> Qu > Cheers, > marble >
signature.asc
Description: OpenPGP digital signature
