From: Liu Yiding <liuyd.fnst@cn.fujitsu.com>
To: lkp@lists.01.org
Subject: Re: 07173c3ec2: stderr.fio:pid=#, err=#/file:filesetup.c:#, func=fsync, error=Input/output_error
Date: Wed, 26 Jun 2019 09:18:36 +0800 [thread overview]
Message-ID: <7812195c-d6e9-8edc-a31c-23db3d9dc4b2@cn.fujitsu.com> (raw)
In-Reply-To: <20190625104713.GA20120@ming.t460p>
[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]
Hi, Ming Lei.
在 2019/6/25 下午6:47, Ming Lei 写道:
> Hi rong.a.chen,
>
> Thanks for your report!
>
> On Tue, Jun 25, 2019 at 04:32:48PM +0800, kernel test robot wrote:
>> FYI, we noticed the following commit (built with gcc-7):
>>
>> commit: 07173c3ec276cbb18dc0e0687d37d310e98a1480 ("block: enable multipage bvecs")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>
>> in testcase: fio-basic
>> on test machine: 72 threads Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz with 256G memory
>> with following parameters:
>>
>> runtime: 300s
>> nr_task: 8t
>> disk: 1SSD
>> fs: xfs
>> rw: randread
>> bs: 2M
>> ioengine: sync
>> test_size: 512g
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>> fio: pid=0, err=5/file:filesetup.c:190, func=fsync, error=Input/output error
>> fio: pid=0, err=5/file:filesetup.c:190, func=fsync, error=Input/output error
> I just tried the fio(randread, bs:2M, sync, nvme, xfs and block device) test on
> 5.2-rc6 kernel, looks it can't be reproduced.
>
> For multi-page bvec change, I'd suggest to run test on 5.1 at least,
> since there are several follow-up fixes.
>
> Also the dmesg log seems not intact, looks it only shows booting.
>
> Please let us know if the issue can be triggered on 5.1 or 5.2.
This issue can be triggered on v5.1 and v5,2-rc* (include v5.2-rc6)
on v5.2-rc6 run 20 times, 10 times trigger out this issue.
>
> Thanks,
> Ming
> _______________________________________________
> LKP mailing list
> LKP(a)lists.01.org
> https://lists.01.org/mailman/listinfo/lkp
>
>
next prev parent reply other threads:[~2019-06-26 1:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 8:32 07173c3ec2: stderr.fio:pid=#, err=#/file:filesetup.c:#, func=fsync, error=Input/output_error kernel test robot
2019-06-25 10:47 ` Ming Lei
2019-06-26 1:18 ` Liu Yiding [this message]
2019-06-26 2:05 ` Ming Lei
2019-06-26 2:21 ` Liu Yiding
2019-06-26 2:28 ` Liu Yiding
2019-06-26 2:42 ` Liu Yiding
2019-06-26 3:32 ` Ming Lei
2019-06-27 0:59 ` Liu Yiding
2019-06-27 3:41 ` Ming Lei
2019-07-01 0:59 ` Liu Yiding
2019-07-01 2:47 ` Ming Lei
2019-07-01 4:49 ` Liu Yiding
2019-07-01 6:29 ` Ming Lei
2019-07-01 6:44 ` Ming Lei
2019-07-01 6:54 ` Liu Yiding
2019-07-01 7:14 ` Ming Lei
2019-07-01 7:18 ` Liu Yiding
2019-07-01 7:29 ` Ming Lei
2019-07-02 4:46 ` Liu Yiding
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=7812195c-d6e9-8edc-a31c-23db3d9dc4b2@cn.fujitsu.com \
--to=liuyd.fnst@cn.fujitsu.com \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.