Hi guys, I have some questions about btrfs' handling of invalid csums. For the sake of argument I'm assuming no raid or anything like that (so only one copy exists of every file). When I try to access a file whose csum does not match, btrfs logs an error and refuses access to the file. I have two questions about this: 1) What happens to the file. Will btrfs just leave it alone, or will it be deleted from disk (I seem to remember reading this somewhere, just want to confirm)? 2) How may I tell btrfs to ignore all csums and just assume they are all correct? The reason for wanting this is in case the csum is garbled and the file is intact, or the csum is correct and the file is only partially garbled, but may still contain useful data. Any help would be greatly appreciated. Cheers, Tom -- 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
