Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks"
Date: Tue, 13 Mar 2018 12:58:51 -0400	[thread overview]
Message-ID: <20180313165851.GC2785@redhat.com> (raw)
In-Reply-To: <1520959569.2638.19.camel@wdc.com>

On Tue, Mar 13 2018 at 12:46pm -0400,
Bart Van Assche <Bart.VanAssche@wdc.com> wrote:

> On Tue, 2018-03-13 at 12:31 -0400, Mike Snitzer wrote:
> > But now I cannot get the test to run:
> > 
> > # srp-test/run_tests -c -d -r 10 -t 02-mq
> > Unloaded the ib_srpt kernel module
> > Unloaded the rdma_rxe kernel module
> > SoftRoCE network interfaces: rxe0 rxe1 rxe2 rxe3
> > Zero-initializing /dev/ram0 ... done
> > Zero-initializing /dev/ram1 ... done
> > Configured SRP target driver
> > Running test srp-test/tests/02-mq ...
> > Test file I/O on top of multipath concurrently with logout and login (0 min; mq)
> > Unloaded the ib_srp kernel module
> > /dev/disk/by-id/dm-uuid-mpath-3600140572616d6469736b31000000000: not found
> > Test srp-test/tests/02-mq failed
> > 
> > [  379.634518] ib_srp: QP creation failed for dev rxe1: -22
> > [  379.639849] srpt/10.16.43.122: Unsupported SCSI Opcode 0xa3, sending CHECK_CONDITION.
> > [  379.665891] sd 7:0:0:1: [sdk] Attached SCSI disk
> > [  379.673312] ib_srp: QP creation failed for dev rxe2: -22
> > [  379.688331] ib_srp: QP creation failed for dev rxe3: -22
> > [  379.708324] ib_srp: bad dest parameter '[2620:52:0:102f:219:99ff:feb7:2648'
> > [  379.724538] ib_srp: target creation request is missing one or more parameters
> > [  379.740253] ib_srp: bad dest parameter '[2620:52:0:102f:219:99ff:feb7:2648'
> > [  379.756531] ib_srp: target creation request is missing one or more parameters
> > [  379.773242] ib_srp: bad dest parameter '[2620:52:0:102f:219:99ff:feb7:2648'
> > [  379.789532] ib_srp: target creation request is missing one or more parameters
> > [  379.805255] ib_srp: bad dest parameter '[2620:52:0:102f:219:99ff:feb7:2648'
> > [  379.822532] ib_srp: target creation request is missing one or more parameters
> 
> That's weird. I will see whether I can reproduce this with linux-next, since I have
> not yet tried to run srp-test against linux-next myself.

OK, I appreciate it (you'll need to revert thos commits I shared in the
other linux-next thread).

  reply	other threads:[~2018-03-13 16:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 20:28 [PATCH] Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks" Bart Van Assche
2018-03-12 21:23 ` Mike Snitzer
2018-03-12 21:32   ` Bart Van Assche
2018-03-13  1:23     ` Mike Snitzer
2018-03-13 16:43       ` Bart Van Assche
2018-03-13 17:02         ` Mike Snitzer
2018-03-13 17:07           ` Mike Snitzer
2018-03-13 17:10             ` Bart Van Assche
2018-03-13 21:41               ` Mike Snitzer
2018-03-14 16:34                 ` Bart Van Assche
2018-03-13 15:25     ` Mike Snitzer
2018-03-13 16:31       ` Mike Snitzer
2018-03-13 16:46         ` Bart Van Assche
2018-03-13 16:58           ` Mike Snitzer [this message]
2018-03-30 17:04         ` Bart Van Assche
2018-03-13 16:38       ` Bart Van Assche

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=20180313165851.GC2785@redhat.com \
    --to=snitzer@redhat.com \
    --cc=Bart.VanAssche@wdc.com \
    --cc=dm-devel@redhat.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