From: Seth Forshee <sforshee@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Cc: linux-nvme@lists.infradead.org
Subject: nvme-tcp request timeouts
Date: Tue, 11 Oct 2022 10:31:41 -0500 [thread overview]
Message-ID: <Y0WMXSv8REysoqFy@do-x1extreme> (raw)
Hi,
I'm seeing timeouts like the following from nvme-tcp:
[ 6369.513269] nvme nvme5: queue 102: timeout request 0x73 type 4
[ 6369.513283] nvme nvme5: starting error recovery
[ 6369.514379] block nvme5n1: no usable path - requeuing I/O
[ 6369.514385] block nvme5n1: no usable path - requeuing I/O
[ 6369.514392] block nvme5n1: no usable path - requeuing I/O
[ 6369.514393] block nvme5n1: no usable path - requeuing I/O
[ 6369.514401] block nvme5n1: no usable path - requeuing I/O
[ 6369.514414] block nvme5n1: no usable path - requeuing I/O
[ 6369.514420] block nvme5n1: no usable path - requeuing I/O
[ 6369.514427] block nvme5n1: no usable path - requeuing I/O
[ 6369.514430] block nvme5n1: no usable path - requeuing I/O
[ 6369.514432] block nvme5n1: no usable path - requeuing I/O
[ 6369.514926] nvme nvme5: Reconnecting in 10 seconds...
[ 6379.761015] nvme nvme5: creating 128 I/O queues.
[ 6379.944389] nvme nvme5: mapped 128/0/0 default/read/poll queues.
[ 6379.947922] nvme nvme5: Successfully reconnected (1 attempt)
This is with 6.0, using nvmet-tcp on a different machine as the target.
I've seen this sporadically with several test cases. The fio fio-rand-RW
example test is a pretty good reproducer when numjobs in increased (I'm
setting it equal to the number of CPUs in the system).
Let me know what I can do to help debug this. I'm currently adding some
tracing to the driver to see if I can get an idea of the sequence of
events that leads to this problem.
Thanks,
Seth
next reply other threads:[~2022-10-11 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 15:31 Seth Forshee [this message]
2022-10-11 19:30 ` nvme-tcp request timeouts Chaitanya Kulkarni
2022-10-11 20:14 ` Seth Forshee
2022-10-11 20:19 ` Chaitanya Kulkarni
2022-10-11 20:37 ` Seth Forshee
2022-10-12 6:33 ` Sagi Grimberg
2022-10-12 16:55 ` Seth Forshee
2022-10-12 17:30 ` Sagi Grimberg
2022-10-13 4:57 ` Seth Forshee
2022-10-12 7:51 ` Sagi Grimberg
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=Y0WMXSv8REysoqFy@do-x1extreme \
--to=sforshee@kernel.org \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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