On Sat, Sep 01, 2012 at 06:03:32PM -0700, Shentino wrote: > This whole subject was also about using sed to corrupt-o-magic a > file's data on disk. > > Is this an acceptable method for testing? Starting with kernels 3.4 the error handling has been improved, namely for the EIO, so it shouldn't take your box down when you hit one. Newer kernels got fixes to the 'transaction abort' cleanup, so it should be possible to umount and mount the filesystem without problems. The filesystem should survive shooting at blocks, the checksums catch any change (with respect to it's strength, ie. generating a hash collision will lead to crash/abort later). Expected result for reading blocks after random writes is: * EIO for the corrupted block (both data or metadata) provided that there's no other copy * transparent and automatic repair from other copies I've tested this on an 2 disk data/raid1, metadata/raid1 with a running dd over one of the devices continually and using the filesystem. It was slower. david -- 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
