On 2016-05-12 20:29, Austin S. Hemmelgarn wrote: >> I wonder if there is a way to correct or detect that situation. > The closest we could get is to provide an option to handle this in > scrub, preferably with a big scary warning on it as this same > situation can be easily cause by someone modifying the disks > themselves (we can't reasonably protect against that, but we > shouldn't make it trivial for people to inject arbitrary data that > way either). "btrfs check" has the option "--init-csum-tree"... Anyway, it should be exist an option to recalculate the checksum for a single file. BTRFS is good to highlight that a file is corrupted, but it should have the possibility to read it anyway: in some case is better to have a corrupted file (knowing that it is corrupted) that loosing all the file. BR G.Baroncelli -- gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5 -- 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
