From: Bob Pearson <rpearsonhpe@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>,
"Pearson, Robert B" <robert.pearson2@hpe.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Daisuke Matsuda (Fujitsu)" <matsuda-daisuke@fujitsu.com>,
'Rain River' <rain.1986.08.12@gmail.com>,
Zhu Yanjun <yanjun.zhu@linux.dev>,
"leon@kernel.org" <leon@kernel.org>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [bug report] blktests srp/002 hang
Date: Fri, 20 Oct 2023 12:12:57 -0500 [thread overview]
Message-ID: <0d8cfab5-f956-4758-858c-2cc16082e64b@gmail.com> (raw)
In-Reply-To: <5f8a5236-2a31-44b4-ae54-b723b229a7ed@acm.org>
On 10/19/23 14:17, Bart Van Assche wrote:
> On 10/18/23 14:52, Bob Pearson wrote:
>> results are slightly ambiguous but I ran the command here:
>>
>> rpearson:blktests$ sudo use_siw=1 ./check srp/002
>> srp/002 (File I/O on top of multipath concurrently with logout and login (mq)) [failed]time 245.018s ...
>> runtime 245.018s ... 128.110s
>> --- tests/srp/002.out 2023-02-15 12:07:40.675530344 -0600
>> +++ /home/rpearson/src/blktests/results/nodev/srp/002.out.bad 2023-10-18 16:36:14.723323257 -0500
>> @@ -1,2 +1 @@
>> Configured SRP target driver
>> -Passed
>> rpearson:blktests$
>>
>> And while it was hung I ran the following:
>>
>> root@rpearson-X570-AORUS-PRO-WIFI: dmsetup ls | while read a b; do dmsetup message $a 0 fail_if_no_path; done
>> device-mapper: message ioctl on mpatha-part1 failed: Invalid argument
>> Command failed.
>> device-mapper: message ioctl on mpatha-part2 failed: Invalid argument
>> Command failed.
>> device-mapper: message ioctl on mpathb-part1 failed: Invalid argument
>> Command failed.
>>
>> mpath[ab]-part[12] are multipath devices (dm-1,2,3) holding the Ubuntu system images and not the devices created
>> by blktests. When this command finished the srp/002 run came back life but did not succeed (see above)
>>
>> The dmesg log is attached
>
> Hi Bob,
>
> Thank you for having shared these results. The 'dmsetup message' command
> should only be applied to multipath devices created by the srp/002
> script and not to the multipath devices created by Ubuntu but I'm not
> sure how to do that.
>
> If the above 'dmsetup message' command resolved the hang, that indicates
> that the root cause of the hang is probably in user space and not in the
> kernel. Did you use the Ubuntu version of multipathd or a self-built
> version of multipathd? I remember that last time I ran the SRP tests on
> an Ubuntu system that I had to replace Ubuntu's multipathd with a self-built binary to make the tests pass.
>
> Thanks for having shared the dmesg output. I don't think it is possible to derive the root cause from that output, which is unfortunate.
>
> Thanks,
>
> Bart.
>
Bart,
The results from yesterday are from Ubuntu 23.04 which has multipath-tools at version 0.8.8.
Ubuntu 23.10 has version 0.9.4. Github has head of tree at 0.9.6. Do you recall which version
made it work when you were looking at this? It may be less risky for me to upgrade to
Ubuntu 23.10 than try and build multipath-tools from source.
Bob
next prev parent reply other threads:[~2023-10-20 17:13 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 6:46 [bug report] blktests srp/002 hang Shinichiro Kawasaki
2023-08-22 1:46 ` Bob Pearson
2023-08-22 10:18 ` Shinichiro Kawasaki
2023-08-22 15:20 ` Bart Van Assche
2023-08-23 16:19 ` Bob Pearson
2023-08-23 19:46 ` Bart Van Assche
2023-08-24 16:24 ` Bob Pearson
2023-08-24 8:55 ` Bernard Metzler
2023-08-24 15:35 ` Bernard Metzler
2023-08-24 16:05 ` Bart Van Assche
2023-08-24 16:27 ` Bob Pearson
2023-08-25 1:11 ` Shinichiro Kawasaki
2023-08-25 1:36 ` Bob Pearson
2023-08-25 10:16 ` Shinichiro Kawasaki
2023-08-25 13:49 ` Bart Van Assche
2023-08-25 13:52 ` Bart Van Assche
2023-09-13 17:36 ` Bob Pearson
2023-09-13 23:38 ` Zhu Yanjun
2023-09-16 5:59 ` Zhu Yanjun
2023-09-19 4:14 ` Shinichiro Kawasaki
2023-09-19 8:07 ` Zhu Yanjun
2023-09-19 16:30 ` Pearson, Robert B
2023-09-19 18:11 ` Bob Pearson
2023-09-20 4:22 ` Zhu Yanjun
2023-09-20 16:24 ` Bob Pearson
2023-09-20 16:36 ` Bart Van Assche
2023-09-20 17:18 ` Bob Pearson
2023-09-20 17:22 ` Bart Van Assche
2023-09-20 17:29 ` Bob Pearson
2023-09-21 5:46 ` Zhu Yanjun
2023-09-21 10:06 ` Zhu Yanjun
2023-09-21 14:23 ` Rain River
2023-09-21 14:39 ` Bob Pearson
2023-09-21 15:08 ` Zhu Yanjun
2023-09-21 15:10 ` Zhu Yanjun
2023-09-22 18:14 ` Bob Pearson
2023-09-22 22:06 ` Bart Van Assche
2023-09-24 1:17 ` Rain River
2023-09-25 4:47 ` Daisuke Matsuda (Fujitsu)
2023-09-25 14:31 ` Zhu Yanjun
2023-09-26 1:09 ` Daisuke Matsuda (Fujitsu)
2023-09-26 6:09 ` Zhu Yanjun
2023-09-25 15:00 ` Bart Van Assche
2023-09-25 15:25 ` Bob Pearson
2023-09-25 15:52 ` Jason Gunthorpe
2023-09-25 15:54 ` Bob Pearson
2023-09-25 19:57 ` Bob Pearson
2023-09-25 20:33 ` Bart Van Assche
2023-09-25 20:40 ` Bob Pearson
2023-09-26 15:36 ` Rain River
2023-09-26 1:17 ` Daisuke Matsuda (Fujitsu)
2023-10-17 17:09 ` Bob Pearson
2023-10-17 17:13 ` Bart Van Assche
2023-10-17 17:15 ` Bob Pearson
2023-10-17 17:19 ` Bob Pearson
2023-10-17 17:34 ` Bart Van Assche
2023-10-17 17:58 ` Jason Gunthorpe
2023-10-17 18:44 ` Bob Pearson
2023-10-17 18:51 ` Jason Gunthorpe
2023-10-17 19:55 ` Bob Pearson
2023-10-17 20:06 ` Bart Van Assche
2023-10-17 20:13 ` Bob Pearson
2023-10-17 21:14 ` Bob Pearson
2023-10-17 21:18 ` Bart Van Assche
2023-10-17 21:23 ` Bob Pearson
2023-10-17 21:30 ` Bart Van Assche
2023-10-17 21:39 ` Bob Pearson
2023-10-17 22:42 ` Bart Van Assche
2023-10-18 18:29 ` Bob Pearson
2023-10-18 19:17 ` Jason Gunthorpe
2023-10-18 19:48 ` Bart Van Assche
2023-10-18 20:03 ` Bob Pearson
2023-10-18 20:04 ` Bob Pearson
2023-10-18 20:14 ` Bob Pearson
[not found] ` <fb5f6da5-5017-440d-9cb5-38796554366c@gmail.com>
2023-10-18 20:49 ` Bart Van Assche
2023-10-18 21:17 ` Pearson, Robert B
2023-10-18 21:27 ` Bart Van Assche
2023-10-18 21:52 ` Bob Pearson
2023-10-19 19:17 ` Bart Van Assche
2023-10-20 17:12 ` Bob Pearson [this message]
2023-10-20 17:41 ` Bart Van Assche
2023-10-18 19:38 ` Bart Van Assche
2023-10-17 19:18 ` Bart Van Assche
2023-10-18 8:16 ` Zhu Yanjun
2023-09-22 11:06 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-10-13 12:51 ` Linux regression tracking #update (Thorsten Leemhuis)
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=0d8cfab5-f956-4758-858c-2cc16082e64b@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.com \
--cc=rain.1986.08.12@gmail.com \
--cc=robert.pearson2@hpe.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yanjun.zhu@linux.dev \
/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).