From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>,
linux-kernel@vger.kernel.org, io-uring@vger.kernel.org
Subject: Re: [Bug] fio hang when running multiple job io_uring/hipri over nvme
Date: Thu, 17 Jun 2021 10:56:53 -0600 [thread overview]
Message-ID: <1b56a4f7-ce56-ee32-67d5-0fcd5dc6c0cb@kernel.dk> (raw)
In-Reply-To: <6691cf72-3a26-a1bb-228d-ddec8391620f@kernel.dk>
On 6/17/21 10:48 AM, Jens Axboe wrote:
> On 6/17/21 5:17 AM, Ming Lei wrote:
>> Hello,
>>
>> fio hangs when running the test[1], and doesn't observe this issue
>> when running a
>> such single job test.
>>
>> v5.12 is good, both v5.13-rc3 and the latest v5.13-rc6 are bad.
>>
>>
>> [1] fio test script and log
>> + fio --bs=4k --ioengine=io_uring --fixedbufs --registerfiles --hipri
>> --iodepth=64 --iodepth_batch_submit=16
>> --iodepth_batch_complete_min=16 --filename=/dev/nvme0n1 --direct=1
>> --runtime=20 --numjobs=4 --rw=randread
>> --name=test --group_reporting
>>
>> test: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T)
>> 4096B-4096B, ioengine=io_uring, iodepth=64
>> ...
>> fio-3.25
>> Starting 4 processes
>> fio: filehash.c:64: __lookup_file_hash: Assertion `f->fd != -1' failed.
>> fio: pid=1122, got signal=6
>> ^Cbs: 3 (f=0): [f(1),r(1),K(1),r(1)][63.6%][eta 00m:20s]
>
> Funky, would it be possible to bisect this? I'll see if I can reproduce.
Actually, this looks like a fio bug, that assert is a bit too trigger
happy. Current -git should work, please test and see if things work.
I believe it's just kernel timing that causes this, not a kernel issue.
--
Jens Axboe
next prev parent reply other threads:[~2021-06-17 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 11:17 [Bug] fio hang when running multiple job io_uring/hipri over nvme Ming Lei
2021-06-17 16:48 ` Jens Axboe
2021-06-17 16:56 ` Jens Axboe [this message]
2021-06-17 22:39 ` Ming Lei
2021-06-18 14:56 ` Jens Axboe
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=1b56a4f7-ce56-ee32-67d5-0fcd5dc6c0cb@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.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 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.