Log-writes tool from Josef exposed btrfs data corruption. Although still digging, at least enhance --check-data-csum option so that log-replay --check can stop exactly at the point where btrfs data get corrupted, instead of manually checking the output.
Qu Wenruo (4): btrfs-progs: check: Check data csum for all copies btrfs-progs: check: Fix data csum check return value btrfs-progs: check: Continue check even csum error is found btrfs-progs: check: Distingusih csum checking output for --check-data-csum check/main.c | 93 ++++++++++++++++++++++++++++++++++++------------------------ 1 file changed, 56 insertions(+), 37 deletions(-) -- 2.16.2 -- 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