Linux Device Mapper development
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Mike Christie <mchristi@redhat.com>,
	device-mapper development <dm-devel@redhat.com>,
	Hannes Reinecke <hare@suse.de>,
	Benjamin Marzinski <bmarzins@redhat.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>
Subject: Re: [Question] udev ID_UID attribute ???
Date: Fri, 8 Jul 2016 22:45:11 +0200	[thread overview]
Message-ID: <c6ca404f-4e0e-d7c9-de1f-60e0697df789@gmail.com> (raw)
In-Reply-To: <5c9472d8-ef1a-bfd7-a916-d4120d881fc1@redhat.com>

On 07/08/2016 05:52 PM, Mike Christie wrote:

> On 07/07/2016 04:21 PM, Xose Vazquez Perez wrote:
>> Is "ID_UID" really valid?
>>
>> libmultipath/hwtable.c:         .uid_attribute = "ID_UID",
>>
> 
> I was wondering the same thing. For ceph rbd, we do not have the normal
> scsi serial/wwn values, so I am modifying our udev rule to export ID_UID.
> 
> I made the ID_UID, the values we use for the udev (/dev/rbd) name which
> is the pool name (basically just a grouping of storage) plus the image
> name (basically name of a disk created in a pool).

ID_UID isn't "standard". It wasn't found in kernel, multipath-tools or systemd(udev)
sources.

It's variable returned by dasdinfo from 390-tools package, it contains the "DASD uid"
of a dasd device. And it's used by udev rules to make symlinks for dasd devices under
/dev/disk/by-id/

This is hercules, but in a LPAR shows a similar output:
sles11-s390x:~ # dasdinfo -e -a -d /dev/dasda
ID_BUS=ccw
ID_TYPE=disk
ID_UID=HRC.ZZ000000000001.0120.22
ID_XUID=HRC.ZZ000000000001.0120.22
ID_SERIAL=0X0122

sles11-s390x:~ # grep ID_UID  /etc/udev/rules.d/59-dasd.rules
KERNEL=="dasd*[!0-9]", ENV{ID_UID}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_UID}"
KERNEL=="dasd*[0-9]", ENV{ID_UID}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_UID}-part%n"


It was used for dasd devices in multipath-tools because they haven't a WWN.

So, invent another undocumented variable name :-) , "ID_CEPH" or "ID_CEPH-RBD" ...

  reply	other threads:[~2016-07-08 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 21:21 [Question] udev ID_UID attribute ??? Xose Vazquez Perez
2016-07-08 15:52 ` Mike Christie
2016-07-08 20:45   ` Xose Vazquez Perez [this message]
2016-07-11  6:40     ` Hannes Reinecke

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=c6ca404f-4e0e-d7c9-de1f-60e0697df789@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    --cc=mchristi@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