For sanitizing the debug tree I tried this backwards method: # btrfs-image -c5 -t4 -s /dev/mapper/brick1 > btrfsimage_30f4724a.bin # lvcreate -V 603440807936b -T vg/thintastic -n btr1 # btrfs-image -r btrfsimage_30f4724a.bin /dev/vg/btr1 # btrfs inspect-internal dump-tree /dev/vg/btr1 > btrfsdebugtree_30f4724a.log But I see by default, -r makes modifications to the chunk tree, so maybe it's not a useful debug tree? Anyway, the two btrfs checks (original and lowmem) and the debug tree are here: 30f4724a-first.logs.tar 254MiB https://drive.google.com/open?id=0B_2Asp8DGjJ9QmZOV3pNS212Yk0 There are 4 more file systems, 2 are single device, 2 are two device (raid1) fs's. I'm not sure how to use this indirect btrfs-image approach with raid1. 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
