This may be by design since the driver is handling the errors. When the drive is mounted with -o recovery, and then a scrub is performed, scrub will show no errors. fatdrive ~ # dmesg | tail [35348.694291] repair_io_failure: 4 callbacks suppressed [35348.694297] BTRFS: read error corrected: ino 1 off 93863407616 (dev /dev/sds sector 183326968) [35351.029568] BTRFS (device sdt): parent transid verify failed on 8392192475136 wanted 148989 found 147789 [35351.048101] BTRFS: read error corrected: ino 1 off 8392192475136 (dev /dev/sds sector 2314785632) [35470.018881] BTRFS (device sdt): parent transid verify failed on 94051291136 wanted 150686 found 150687 [35470.150372] BTRFS (device sdt): parent transid verify failed on 94051291136 wanted 150686 found 150687 [35948.602971] BTRFS (device sdt): parent transid verify failed on 94238015488 wanted 150690 found 150691 [35948.608723] BTRFS (device sdt): parent transid verify failed on 94238015488 wanted 150690 found 150691 [36114.453009] BTRFS (device sdt): parent transid verify failed on 94238015488 wanted 150690 found 150691 [36114.472586] BTRFS (device sdt): parent transid verify failed on 94238015488 wanted 150690 found 150691 fatdrive ~ # btrfs scrub status /mnt/data scrub status for f591ac13-1a69-476d-bd30-346f87a491da scrub started at Mon Apr 27 06:48:44 2015 and was aborted after 2651 seconds total bytes scrubbed: 2.39TiB with 0 errors I have reported this as issue 97351. https://bugzilla.kernel.org/show_bug.cgi?id=97351-- 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
