On Mon, Jul 11, 2016 at 11:17 AM, Tomáš Hrdina <thomas.rkh@xxxxxxxxx> wrote: > sudo btrfs-debug-tree /dev/sdc > It has 200000 lines. Don't know, what you use for bigger files. > > > sudo btrfs-debug-tree -b 6062434418688 /dev/sdc > http://sebsauvage.net/paste/?fc156dee1d1deb3b#YpG/TA0H3I313jMuC4pgsdj++TcuDaFwWIBeuuOXfCA= > > sudo btrfs-debug-tree -b 6062497202176 /dev/sdc > http://sebsauvage.net/paste/?86621abec9c239bd#kwTpZ7BZLcLw71yCfr3jHKZT08zsaXK3RgdFo7MFoFc= > > > sudo btrfs-debug-tree -b 6062470332416 /dev/sdc > http://sebsauvage.net/paste/?4ff40fa0b6b201c9#nFk7pT9MLj2w9egUJlgXdkmCkWyp1vSG0kADfq3J7eA= None of these have anything useful in them, there's no tree root there. > > It got some results, but I don't know, what to look for. > > > sudo btrfs-map-logical -l 7008899547136 /dev/sdc > parent transid verify failed on 7008807157760 wanted 70175 found 70133 > parent transid verify failed on 7008807157760 wanted 70175 found 70133 > checksum verify failed on 7008807157760 found F192848C wanted 1571393A > checksum verify failed on 7008807157760 found F192848C wanted 1571393A > bytenr mismatch, want=7008807157760, have=65536 > mirror 1 logical 7008899547136 physical 735226609664 device /dev/sdb > mirror 2 logical 7008899547136 physical 3166748524544 device /dev/sdc > > > Also I don't know, what to do with this. How to compute new csum. Right, that's pretty tricky to do manually. > > For me, it would be ok to give up and just start fresh. OK in that case do that. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
