On Fri, Jan 04, 2013 at 08:01:44AM -0500, Chris Mason wrote: > > I'm not quite sure if the messages match the test (best guess, neighbouring > > tests were fine): > > > > [102885.667444] btrfs csum failed ino 638 off 425984 csum 1842675109 private 2279232751 > > [102885.676804] btrfs csum failed ino 638 off 430080 csum 1842675109 private 1192041375 > > [102885.686094] btrfs csum failed ino 638 off 434176 csum 2297282744 private 1619428542 > > [102885.686103] btrfs csum failed ino 638 off 438272 csum 3709984297 private 2868627320 > > [102885.686112] btrfs csum failed ino 638 off 442368 csum 1504116677 private 1239355148 > > [102885.686121] btrfs csum failed ino 638 off 446464 csum 1957839041 private 3848200057 > > [102885.686129] btrfs csum failed ino 638 off 450560 csum 3836729483 private 2867416946 > > I think fsx leaves the bad file, you can test the inode number? # btrfs inspect ino 638 /mnt/a1 /mnt/a1/junk # md5sum /mnt/a1/junk md5sum: /mnt/a1/junk: Input/output error dmesg says: [165711.839959] btrfs csum failed ino 638 off 262144 csum 3105135418 private 2393479556 [165711.899328] btrfs csum failed ino 638 off 262144 csum 2566472073 private 2393479556 -- 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
