Re: [PATCH blktests v2 3/3] Add tests for the SRP initiator and target drivers

[Omar Sandoval <osandov@osandov.com>]

On Tue, Jul 03, 2018 at 12:50:10PM -0700, Omar Sandoval wrote:
> On Tue, Jul 03, 2018 at 12:49:13PM -0700, Omar Sandoval wrote:
> > On Fri, Jun 29, 2018 at 09:13:53AM -0700, Bart Van Assche wrote:
> > > On 06/28/18 16:43, Omar Sandoval wrote:
> > > > On Wed, Jun 27, 2018 at 02:49:08PM -0700, Bart Van Assche wrote:
> > > > [ ... ]
> > > > srp/002 (File I/O on top of multipath concurrently with logout and login (mq)) [failed]
> > > > runtime  6.680s  ...  6.640s
> > > >      --- tests/srp/002.out       2018-06-28 15:18:36.537169282 -0700
> > > >      +++ results/nodev/srp/002.out.bad   2018-06-28 16:21:59.930603931 -0700
> > > >      @@ -3,5 +3,4 @@
> > > >       Unloaded the rdma_rxe kernel module
> > > >       Configured SRP target driver
> > > >       Unloaded the ib_srp kernel module
> > > >      -Unloaded the ib_srpt kernel module
> > > >      -Unloaded the rdma_rxe kernel module
> > > >      +/dev/disk/by-id/dm-uuid-mpath-3600140572616d6469736b31000000000: not found
> > > > 
> > > > And everything else fails like srp/002.
> > > 
> > > I think that indicates a problem with the multipathing software on your
> > > setup. Was multipathd running? Had the proper multipath configuration
> > > (/etc/multipath.conf) been provided? Was multipathing enabled in the kernel
> > > config?
> > 
> > Ah, the README says /etc/multipathd.conf. Fixing it to multipath.conf
> > didn't work, either, though.
> 
> Hit send too early. multipathd is running, but I did find this in my
> dmesg:
> 
> [ 1844.347561] multipath[6558]: segfault at 100 ip 00007fbb7cda51e6 sp 00007fffe9241798 error 4 in libc-2.27.so[7fbb7cd0e000+1b3000]
> 
> I'll look into that.

Alright, I installed multipath-tools from source and the segfaults are
gone, but I still don't get these symlinks. Instead, they show up as

/dev/disk/by-id/scsi-3600140572616d6469736b32000000000

Any ideas?