From: Potnuri Bharat Teja <bharat@chelsio.com>
To: sagi@grimberg.me
Cc: hch@lst.de, linux-nvme@lists.infradead.org
Subject: Request timeout seen with NVMEoF TCP
Date: Wed, 9 Dec 2020 22:49:18 +0530 [thread overview]
Message-ID: <X9EHFnhujZo175Kw@chelsio.com> (raw)
Hi All,
I am seeing the following timeouts and reconnects on NVMF TCP initiator with latest v5.10-rc5
kernel.
I see the same behavior with nvme tree too (branch:nvme-5.11)
I last ran this with 5.8, where it was running fine.
Target configuration is, 1 target with 1gb ramdisk namespace. On intiator,
discover, connect and run fio or Iozone. Traces are seen within couple of minutes
after starting the test.
initiator dmesg:
--
[77206.339485] nvme nvme1: queue 11: timeout request 0x34 type 6
[77206.340070] nvme nvme1: starting error recovery
[77206.340360] nvme nvme1: queue 11: timeout request 0x36 type 6
[77206.340766] nvme nvme1: queue 11: timeout request 0x38 type 6
[77206.341128] nvme nvme1: queue 11: timeout request 0x39 type 6
[77206.341515] nvme nvme1: queue 11: timeout request 0x3a type 4
[77206.341871] block nvme1n1: no usable path - requeuing I/O
[77206.342103] nvme nvme1: Reconnecting in 10 seconds...
[77206.342170] block nvme1n1: no usable path - requeuing I/O
[77206.342871] block nvme1n1: no usable path - requeuing I/O
[77206.343183] block nvme1n1: no usable path - requeuing I/O
[77206.343498] block nvme1n1: no usable path - requeuing I/O
[77206.343810] block nvme1n1: no usable path - requeuing I/O
[77206.344103] block nvme1n1: no usable path - requeuing I/O
[77206.344387] block nvme1n1: no usable path - requeuing I/O
[77206.344705] block nvme1n1: no usable path - requeuing I/O
[77206.345027] block nvme1n1: no usable path - requeuing I/O
[77211.971543] nvme_ns_head_submit_bio: 449 callbacks suppressed
[77211.971547] block nvme1n1: no usable path - requeuing I/O
[77216.600034] block nvme1n1: no usable path - requeuing I/O
[77216.600386] block nvme1n1: no usable path - requeuing I/O
[77216.600752] block nvme1n1: no usable path - requeuing I/O
[77216.601150] block nvme1n1: no usable path - requeuing I/O
[77216.601531] block nvme1n1: no usable path - requeuing I/O
[77216.601915] block nvme1n1: no usable path - requeuing I/O
[77216.602176] block nvme1n1: no usable path - requeuing I/O
[77216.602467] block nvme1n1: no usable path - requeuing I/O
[77216.602830] block nvme1n1: no usable path - requeuing I/O
[77216.603597] nvme nvme1: creating 16 I/O queues.
[77216.642166] nvme nvme1: mapped 16/0/0 default/read/poll queues.
[77216.642516] debugfs: Directory 'hctx0' with parent '/' already present!
[77216.642899] debugfs: Directory 'hctx1' with parent '/' already present!
[77216.643177] debugfs: Directory 'hctx2' with parent '/' already present!
[77216.643475] debugfs: Directory 'hctx3' with parent '/' already present!
--
Please let me know if I could help with anything.
Thanks,
Bharat.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-12-09 17:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 17:19 Potnuri Bharat Teja [this message]
2020-12-09 18:02 ` Request timeout seen with NVMEoF TCP Sagi Grimberg
2020-12-10 17:06 ` Potnuri Bharat Teja
2020-12-10 21:47 ` Sagi Grimberg
2020-12-11 7:26 ` Potnuri Bharat Teja
2020-12-14 17:51 ` Sagi Grimberg
2020-12-14 18:05 ` Potnuri Bharat Teja
2020-12-14 19:27 ` Samuel Jones
2020-12-14 20:13 ` Sagi Grimberg
2020-12-15 1:53 ` Sagi Grimberg
2020-12-15 18:30 ` Wunderlich, Mark
2020-12-19 1:04 ` Sagi Grimberg
2020-12-16 5:51 ` Potnuri Bharat Teja
2020-12-19 1:35 ` Sagi Grimberg
2020-12-21 7:50 ` Potnuri Bharat Teja
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=X9EHFnhujZo175Kw@chelsio.com \
--to=bharat@chelsio.com \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).