From: Yi Zhang <yi.zhang@redhat.com>
To: "open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>
Cc: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
Ming Lei <ming.lei@redhat.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Sagi Grimberg <sagi@grimberg.me>
Subject: [bug report] blktests nvme/tcp nvme/014 failed due to Read/Flush timeout
Date: Mon, 22 Apr 2024 12:55:33 +0800 [thread overview]
Message-ID: <CAHj4cs_9XT6Ky4=LTy4SZ5AVfhAUec2k52b81-OKqzsDubobmw@mail.gmail.com> (raw)
Hello
I found nvme/014 failed[1] on one of my servers, seems it was due to
Read/Flush timeout during the test[2], I tried to add sync operation
after the dd operation[3] and the failure can be fixed now and no
timeout from dmesg, could anyone help check if it's one test issue or
nvme/tcp stack issue, thanks.
[1]
# uname -r
6.9.0-rc4+
# nvme_trtype=tcp ./check nvme/014
nvme/014 (flush a NVMeOF block device-backed ns) [failed]
runtime 33.432s ... 41.334s
--- tests/nvme/014.out 2024-04-19 00:02:03.596691663 -0400
+++ /root/blktests/results/nodev/nvme/014.out.bad 2024-04-22
00:10:10.042478026 -0400
@@ -1,4 +1,4 @@
Running nvme/014
-NVMe Flush: success
+NVMe status: Command Aborted By Host: The command was aborted as
a result of host action(0x371)
disconnected 1 controller(s)
Test complete
[2]
# dmesg
[ 724.690961] run blktests nvme/014 at 2024-04-22 00:09:28
[ 724.706957] loop0: detected capacity change from 0 to 2097152
[ 724.715174] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
[ 724.724103] nvmet_tcp: enabling port 0 (127.0.0.1:4420)
[ 724.735368] nvmet: creating nvm controller 1 for subsystem
blktests-subsystem-1 for NQN
nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349.
[ 724.749633] nvme nvme1: creating 96 I/O queues.
[ 724.757813] nvme nvme1: mapped 96/0/0 default/read/poll queues.
[ 724.789035] nvme nvme1: new ctrl: NQN "blktests-subsystem-1", addr
127.0.0.1:4420, hostnqn:
nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
[ 758.518247] nvme nvme1: I/O tag 1 (0001) type 4 opcode 0x2 (I/O
Cmd) QID 86 timeout
[ 758.525908] nvme nvme1: starting error recovery
[ 758.530447] nvme nvme1: I/O tag 81 (0051) type 4 opcode 0x0 (I/O
Cmd) QID 87 timeout
[ 758.538914] nvme1n1: I/O Cmd(0x2) @ LBA 2097024, 8 blocks, I/O
Error (sct 0x3 / sc 0x71)
[ 758.547101] I/O error, dev nvme1n1, sector 2097024 op 0x0:(READ)
flags 0x80700 phys_seg 1 prio class 0
[ 758.562940] nvme nvme1: Reconnecting in 10 seconds...
[ 758.568093] nvme nvme1: Removing ctrl: NQN "blktests-subsystem-1"
[ 758.572165] nvme1n1: I/O Cmd(0x0) @ LBA 2097024, 8 blocks, I/O
Error (sct 0x3 / sc 0x70)
[ 758.582367] Buffer I/O error on dev nvme1n1, logical block 262128,
async page read
[ 758.618831] nvme nvme1: Property Set error: 880, offset 0x14
[3]
diff --git a/tests/nvme/014 b/tests/nvme/014
index 839b91f..3f6a68f 100755
--- a/tests/nvme/014
+++ b/tests/nvme/014
@@ -37,7 +37,7 @@ test() {
dd if=/dev/urandom of="/dev/${ns}" \
count="${count}" bs="${bs}" status=none
-
+ sync
nvme flush "/dev/${ns}"
_nvme_disconnect_subsys
--
Best Regards,
Yi Zhang
next reply other threads:[~2024-04-22 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 4:55 Yi Zhang [this message]
2024-04-22 8:27 ` [bug report] blktests nvme/tcp nvme/014 failed due to Read/Flush timeout Daniel Wagner
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='CAHj4cs_9XT6Ky4=LTy4SZ5AVfhAUec2k52b81-OKqzsDubobmw@mail.gmail.com' \
--to=yi.zhang@redhat.com \
--cc=chaitanya.kulkarni@wdc.com \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.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).