public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
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 14:21:44 -0700	[thread overview]
Message-ID: <20180706212144.GF25954@vader> (raw)
In-Reply-To: <69e800ccba7644a5a0b26e6d83483310926a907b.camel@wdc.com>

On Wed, Jul 04, 2018 at 04:24:42PM +0000, Bart Van Assche wrote:
> On Tue, 2018-07-03 at 14:39 -0700, Omar Sandoval wrote:
> > 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?
> 
> Hello Omar,
> 
> The dm-uuid symlink is created by a udev rule. Apparently that udev rule is not
> in the same software package as multipathd. Can you run the following command to
> check whether that udev rule is available on your setup?
> 
> grep -r dm-uuid /lib/udev/rules.d/

$ grep -r dm-uuid /lib/udev/rules.d/
/lib/udev/rules.d/13-dm-disk.rules:ENV{DM_UUID}=="?*", SYMLINK+="disk/by-id/dm-uuid-$env{DM_UUID}"


> The name of the package that includes the dm-uuid rule depends on the distro,
> e.g. dmsetup or device-mapper. According to the git history of git repository
> https://sourceware.org/git/?p=lvm2.git the dm-uuid udev rule was added to that
> repository in August 2009, almost nine years ago.

Yup, it's in the device-mapper package for me on Arch Linux (and Arch
has very up-to-date versions of everything). I'll try some udev
debugging.

  reply	other threads:[~2018-07-06 21:21 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 [this message]
2018-07-06 23:03                 ` Omar Sandoval
2018-07-06 23:07                   ` Bart Van Assche
2018-07-06 23:10                     ` Omar Sandoval
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=20180706212144.GF25954@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