linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Missing SAS phy enumeration in newer versions of udev path_id
Date: Fri, 30 Mar 2012 08:23:46 +0000	[thread overview]
Message-ID: <4F756D92.1090206@suse.de> (raw)
In-Reply-To: <4F7567F1.2010201@ericsson.com>

On 03/30/2012 09:59 AM, Nils Carlson wrote:
> Hi,
> 
> We recently upgraded our version of udev and I saw that the symlinks
> under /dev/disk/by-path/ have changed since udev started using the
> path_id C code to no longer include phy enumeration for SAS disks.
> Was this change intentional? Would anyone mind if i re-create the
> behavior of the old bash script as we were using it?
> 
Not everybody at once ... I've just had several customer calls for
exactly the same issue.

Actually ... the company name seems to be vaguely familiar ...

To quote myself:

> Problem is that SAS has something called 'wide-ports', ie inherent
> port-bonding for SAS. When a system has wide ports, several PHYs
> are merged _physically_ together into a single connector.
> However, on the system side we're only seeing PHYs, so it'
> impossible to tell which of the phy has been used.
>
> So to handle this correctly we would need to generate symlinks for
> each phy in a wide port; however, currently the path_id program is
> only capable of printing out _one_ link per wide port.
>
> And actually, the original path_id script also printed out only
> one symlink, so even there it didn't handle wide ports correctly.
>

I've discussed this issue with Kay Sievers, and we agreed that we
should be fixing this.
It should be relatively easy to update the path_id program to print
out a link for each phy in a wide-port, and then we could do a
static enumeration via udev rules like

$env{ID_SAS_PHY0}="?*", SYMLINK+="/dev/disk/by-path/$ID_SAS_PHY0"
$env{ID_SAS_PHY1}="?*", SYMLINK+="/dev/disk/by-path/$ID_SAS_PHY1"

seeing that there is currently a max of 8 phys per wide port, we
only would need to specify 8 lines here. Which should be too bad.

You're welcome to lend a hand ...

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

      reply	other threads:[~2012-03-30  8:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  7:59 Missing SAS phy enumeration in newer versions of udev path_id Nils Carlson
2012-03-30  8:23 ` Hannes Reinecke [this message]

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=4F756D92.1090206@suse.de \
    --to=hare@suse.de \
    --cc=linux-hotplug@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).