On Tue, Aug 15, 2017 at 05:16:06PM +0800, Eryu Guan wrote: >On Mon, Aug 14, 2017 at 03:03:13PM +0800, Lu Fengqi wrote: >> I catch this following error from dmesg when this testcase fails. >> >> [17446.661127] Buffer I/O error on dev sdb1, logical block 64, async page read >> >> We expect to inject disk IO errors on the device when xfs_io reads the >> specific file, but other processes may trigger IO error earlier. So, we >> can use task-filter to solve this problem. >> >> Signed-off-by: Lu Fengqi <lufq.fnst@xxxxxxxxxxxxxx> > >This looks OK to me. Does btrfs/143 need a similar fix? > >Thanks, >Eryu > > Although btrfs/143 has a similar problem, this method doesn't work for it. Unlike btrfs/142, the second IO error needs to be triggered by another process, not by xfs_io. So we can't simply set task-filter to solve this problem. I'm still investigating a way to solve the problem. Do you have any ideas? Any help will be greatly appreciated. -- Thanks, Lu -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
