From: Omar Sandoval <osandov@osandov.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "osandov@fb.com" <osandov@fb.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests v2 3/3] Add tests for the SRP initiator and target drivers
Date: Fri, 6 Jul 2018 16:10:57 -0700 [thread overview]
Message-ID: <20180706231057.GH25954@vader> (raw)
In-Reply-To: <e62c7749ff73f1cb7ab91fccffb5f353dd8d7c58.camel@wdc.com>
On Fri, Jul 06, 2018 at 11:07:06PM +0000, Bart Van Assche wrote:
> On Fri, 2018-07-06 at 16:03 -0700, Omar Sandoval wrote:
> > Alright, I'm not getting the udev events at all (even after enabling
> > CONFIG_DM_UEVENT in addition to everything mentioned in the README). I
> > have no idea where to go from here.
> >
> > After, e.g., srp/002 fails, this is the state of my system:
> >
> > $ sudo multipath -l
> > $ ls /sys/class/block
> > nvme0n1 ram0 ram1 ram2 sda sdb sdc sdd vda vda1 vdb vdc vdd
> > $ lsblk
> > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> > sda 8:0 0 32M 0 disk
> > sdb 8:16 0 32M 0 disk
> > sdc 8:32 0 32M 0 disk
> > sdd 8:48 0 32M 0 disk
> > vda 254:0 0 16G 0 disk
> > └─vda1 254:1 0 16G 0 part /
> > vdb 254:16 0 8G 0 disk
> > vdc 254:32 0 8G 0 disk
> > vdd 254:48 0 8G 0 disk
> > nvme0n1 259:0 0 8G 0 disk
> > $ lsscsi
> > [0:0:0:0] disk Linux scsi_debug 0188 /dev/sda
> > [1:0:0:0] disk LIO-ORG IBLOCK 4.0 /dev/sdb
> > [1:0:0:1] disk LIO-ORG IBLOCK 4.0 /dev/sdd
> > [1:0:0:2] disk LIO-ORG IBLOCK 4.0 /dev/sdc
>
> That's weird. If you want I can install Arch Linux myself and debug this
> further.
At this point, that might be easier.
> Something that would also help is if you could run the following
> commands as root and provide their output:
>
> echo reconfigure | multipathd -k
> multipath -ll
# cat /etc/multipath.conf
defaults {
user_friendly_names yes
queue_without_daemon no
}
devices {
device {
vendor "LIO-ORG|SCST_BIO|FUSIONIO"
product ".*"
features "1 queue_if_no_path"
path_checker tur
}
}
blacklist {
device {
vendor "ATA"
}
device {
vendor "QEMU"
}
device {
vendor "Linux"
product "scsi_debug"
}
devnode "^nullb.*"
}
blacklist_exceptions {
property ".*"
devnode "^nvme"
}
# echo reconfigure | multipathd -k
multipathd> reconfigure
ok
multipathd>
# multipath -ll
So, no output.
next prev parent reply other threads:[~2018-07-06 23:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 21:49 [PATCH blktests v2 0/3] Add SRP initiator driver tests Bart Van Assche
2018-06-27 21:49 ` [PATCH blktests v2 1/3] src/Makefile: Rename $(TARGETS) into $(C_TARGETS) Bart Van Assche
2018-06-28 6:41 ` Johannes Thumshirn
2018-06-27 21:49 ` [PATCH blktests v2 2/3] Add the discontiguous-io test program Bart Van Assche
2018-06-28 6:42 ` Johannes Thumshirn
2018-06-27 21:49 ` [PATCH blktests v2 3/3] Add tests for the SRP initiator and target drivers Bart Van Assche
2018-06-28 23:43 ` Omar Sandoval
2018-06-29 16:13 ` Bart Van Assche
2018-07-03 19:49 ` Omar Sandoval
2018-07-03 19:50 ` Omar Sandoval
2018-07-03 21:39 ` Omar Sandoval
2018-07-04 5:59 ` Hannes Reinecke
2018-07-04 16:24 ` Bart Van Assche
2018-07-06 21:21 ` Omar Sandoval
2018-07-06 23:03 ` Omar Sandoval
2018-07-06 23:07 ` Bart Van Assche
2018-07-06 23:10 ` Omar Sandoval [this message]
2018-07-06 23:15 ` Omar Sandoval
2018-07-09 6:06 ` Hannes Reinecke
2018-07-09 22:57 ` 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=20180706231057.GH25954@vader \
--to=osandov@osandov.com \
--cc=Bart.VanAssche@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.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