From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Jesse Taube <jtaubepe@redhat.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
John Meneghini <jmeneghi@redhat.com>,
Daniel Wagner <dwagner@suse.de>
Subject: Re: [PATCH blktests 0/2] Test multipath and marginal ports
Date: Mon, 17 Aug 2026 16:38:43 +0900 [thread overview]
Message-ID: <aoK5sfNpxIUz7C02@shinhome> (raw)
In-Reply-To: <CADRr4beUeZo9ZA9TZVmWQ9Vegm2LvTXkW0wGNxYA6_7z_njMEA@mail.gmail.com>
On Aug 14, 2026 / 10:18, Jesse Taube wrote:
...
> > I applied the series on top of v7.2-rc7 kernel. Then I ran the test case added
> > by this blktests series and observed the failurea below:
> >
> > nvme/070 (tr=fc) (test nvme-fc marginal path handling) [failed]
> > runtime 33.581s ... 33.028s
> > --- tests/nvme/070.out 2026-08-14 12:03:21.338000000 +0900
> > +++ /home/shin/Blktests/blktests/results/nodev_tr_fc/nvme/070.out.bad 2026-08-14 20:17:04.731000000 +0900
> > @@ -2,7 +2,8 @@
> > Starting background I/O
> > Testing iopolicy: numa
> > Changing FC links to online
> > -Set all online: pass
> > +No FC ports are being used, expected atleast one in use when all are online in numa mode.
> > +Set all online: fail
> > One host marginal: pass
> > ...
> > (Run 'diff -u tests/nvme/070.out /home/shin/Blktests/blktests/results/nodev_tr_fc/nvme/070.out.bad' to see the entire diff)
> >
> > Is this failure expected?
>
> No. I can't reproduce the issue either.
> Does this happen consistently?
Yes, it happnes always I run the test case. After I rebased to v7.2 kernel, it
shows a bit different message:
nvme/070 (tr=fc) (test nvme-fc marginal path handling) [failed]
runtime 37.200s ... 38.926s
--- tests/nvme/070.out 2026-08-17 11:13:53.073000000 +0900
+++ /home/shin/Blktests/blktests/results/nodev_tr_fc/nvme/070.out.bad 2026-08-17 16:34:17.997000000 +0900
@@ -3,10 +3,14 @@
Testing iopolicy: numa
Changing FC links to online
Set all online: pass
-One host marginal: pass
+FC port on (/sys/class/nvme-subsystem/nvme-subsys6/nvme6) is being used, expected no use.
+One host marginal: fail
All marginal: pass
...
(Run 'diff -u tests/nvme/070.out /home/shin/Blktests/blktests/results/nodev_tr_fc/nvme/070.out.bad' to see the entire diff)
> Maybe the links are still connecting?
Should I try to add some sleeps in the test script? If so, could you suggest
where to put the sleeps?
If it helps, I will share the kernel config I use. If you want it, please let
me know.
prev parent reply other threads:[~2026-08-17 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 17:45 [PATCH blktests 0/2] Test multipath and marginal ports Jesse Taube
2026-08-12 17:45 ` [PATCH blktests 1/2] nvme: Add _setup_nvmet_port_marginal Jesse Taube
2026-08-12 19:03 ` John Meneghini
2026-08-14 11:28 ` Shin'ichiro Kawasaki
2026-08-12 17:45 ` [PATCH blktests 2/2] nvme/070: Test multipath and marginal ports Jesse Taube
2026-08-12 19:03 ` John Meneghini
2026-08-14 11:47 ` Shin'ichiro Kawasaki
2026-08-14 15:10 ` John Meneghini
2026-08-14 11:24 ` [PATCH blktests 0/2] " Shin'ichiro Kawasaki
2026-08-14 14:18 ` Jesse Taube
2026-08-17 7:38 ` Shin'ichiro Kawasaki [this message]
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=aoK5sfNpxIUz7C02@shinhome \
--to=shinichiro.kawasaki@wdc.com \
--cc=dwagner@suse.de \
--cc=jmeneghi@redhat.com \
--cc=jtaubepe@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox