On Fri, 17 Mar 2017 10:27:11 +0100 Lionel Bouton <lionel-subscript...@bouton.name> wrote:
> Hi, > > Le 17/03/2017 à 09:43, Hans van Kranenburg a écrit : > > btrfs-debug-tree -b 3415463870464 > > Here is what it gives me back : > > btrfs-debug-tree -b 3415463870464 /dev/sdb > btrfs-progs v4.6.1 > checksum verify failed on 3415463870464 found A85405B7 wanted 01010101 > checksum verify failed on 3415463870464 found A85405B7 wanted 01010101 > bytenr mismatch, want=3415463870464, have=72340172838076673 > ERROR: failed to read 3415463870464 > > Is there a way to remove part of the tree and keep the rest ? It could > help minimize the time needed to restore data. If you are able to experiment with writable snapshots, you could try using "btrfs-corrupt-block" to kill the bad block, and see what btrfsck makes out of the rest. In a similar case I got little to no damage to the overall FS. http://www.spinics.net/lists/linux-btrfs/msg53061.html -- With respect, Roman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
