From: Eryu Guan <eguan@redhat.com>
To: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
bo.li.liu@oracle.com
Subject: Re: [PATCH] fstests: btrfs: enhance regression test for nocsum dio read's repair
Date: Tue, 15 Aug 2017 17:16:06 +0800 [thread overview]
Message-ID: <20170815091606.GG14807@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170814070313.20092-1-lufq.fnst@cn.fujitsu.com>
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@cn.fujitsu.com>
This looks OK to me. Does btrfs/143 need a similar fix?
Thanks,
Eryu
next prev parent reply other threads:[~2017-08-15 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 7:03 [PATCH] fstests: btrfs: enhance regression test for nocsum dio read's repair Lu Fengqi
2017-08-15 9:16 ` Eryu Guan [this message]
2017-08-15 9:54 ` Lu Fengqi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170815091606.GG14807@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=bo.li.liu@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).