I'm unable to reproduce this with kernel and progs built from integration branch (I think, anyway); this is what I built: git clone git://repo.or.cz/btrfs-progs-unstable/devel.git cd devel git checkout integration-20140729 git clone git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git cd linux-btrfs git checkout integration After corrupting a file, the only difference from 3.16.0 is when reading the corrupt file is I get __readpage_endio_check in dmesg. If I understand correctly, corruption is detected, data is correctly rebuilt from parity and sent up to sha1sum but the corrected data is not written back to disk (expected). A balance also causes corruption to be detected but this time the fix is written to disk, the corruption isn't detected after this. [ 82.798368] BTRFS info (device sdd): disk space caching is enabled [ 82.875705] SELinux: initialized (dev sdd, type btrfs), uses xattr [ 92.699491] BTRFS info (device sdd): csum failed ino 257 off 0 csum 2566472073 expected csum 2759032090 [ 92.791565] BTRFS info (device sdd): csum failed ino 257 off 4096 csum 3231022384 expected csum 2759032090 [ 92.791862] BTRFS info (device sdd): csum failed ino 257 off 0 csum 2566472073 expected csum 2759032090 [ 92.850708] BTRFS info (device sdd): csum failed ino 257 off 8192 csum 3303363542 expected csum 2759032090 [ 92.873660] BTRFS info (device sdd): csum failed ino 257 off 12288 csum 2295875483 expected csum 2759032090 [ 92.921120] BTRFS info (device sdd): csum failed ino 257 off 16384 csum 1837874343 expected csum 2759032090 [ 93.022287] BTRFS info (device sdd): csum failed ino 257 off 20480 csum 4011747594 expected csum 2759032090 [ 93.303243] BTRFS info (device sdd): csum failed ino 257 off 24576 csum 199417701 expected csum 2759032090 [ 93.475170] BTRFS info (device sdd): csum failed ino 257 off 28672 csum 802473067 expected csum 2759032090 [ 93.559571] BTRFS info (device sdd): csum failed ino 257 off 32768 csum 2190845313 expected csum 2759032090 [ 282.402413] BTRFS info (device sdd): disk space caching is enabled [ 282.487717] SELinux: initialized (dev sdd, type btrfs), uses xattr [ 286.119979] __readpage_endio_check: 7 callbacks suppressed [ 286.121279] BTRFS info (device sdd): csum failed ino 257 off 0 csum 2566472073 expected csum 2759032090 [ 286.284266] BTRFS info (device sdd): csum failed ino 257 off 4096 csum 3231022384 expected csum 2759032090 [ 286.383582] BTRFS info (device sdd): csum failed ino 257 off 8192 csum 3303363542 expected csum 2759032090 [ 286.383592] BTRFS info (device sdd): csum failed ino 257 off 0 csum 2566472073 expected csum 2759032090 [ 286.693884] BTRFS info (device sdd): csum failed ino 257 off 12288 csum 2295875483 expected csum 2759032090 [ 286.983491] BTRFS info (device sdd): csum failed ino 257 off 16384 csum 1837874343 expected csum 2759032090 [ 287.233004] BTRFS info (device sdd): csum failed ino 257 off 20480 csum 4011747594 expected csum 2759032090 [ 287.279199] BTRFS info (device sdd): csum failed ino 257 off 24576 csum 199417701 expected csum 2759032090 [ 287.505774] BTRFS info (device sdd): csum failed ino 257 off 28672 csum 802473067 expected csum 2759032090 [ 287.601100] BTRFS info (device sdd): csum failed ino 257 off 32768 csum 2190845313 expected csum 2759032090 Chris Murphy-- 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
