How effective would it be to directly write to the underlying device and then running tests to see if the corruption is properly detected? I just ran a fuzz test by syncing, and then manually corrupting a file with the help of a surgical sed (yes, the before and after patterns had fixed equal lengths). First I got an I/O error (expected), then I ran scrub and got more problems (not ok), the system froze (not good), a reboot failed to mount the system again (worse), and then the fsck program dumped core. -- 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
