From: Patrick Mansfield <patmans@us.ibm.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Martin Peschke3 <MPESCHKE@de.ibm.com>,
"Robert J. Adams (jason)" <radams@siscom.net>,
EXT / DEVOTEAM VAROQUI Christophe <ext.devoteam.varoqui@sncf.fr>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: Mount by WWN (FC, using qlogic 2200)
Date: Wed, 4 Feb 2004 12:15:15 -0800 [thread overview]
Message-ID: <20040204121514.A9609@beaverton.ibm.com> (raw)
In-Reply-To: <1075925194.2029.102.camel@mulgrave>; from James.Bottomley@steeleye.com on Wed, Feb 04, 2004 at 03:06:33PM -0500
On Wed, Feb 04, 2004 at 03:06:33PM -0500, James Bottomley wrote:
> On Wed, 2004-02-04 at 14:58, Martin Peschke3 wrote:
> > As there might be several paths to a device identified by a WWPN
> > in the form of 2 or more host bus adapters connecting to that WWPN,
> > don't you want to mount an FCP device by
> > <adapter identifier> + <WWPN> + <FCP_LUN> ?
>
> Actually, I think the question was about WWN, i.e. the EVPD page 0x83
> World Wide Name, which uniquely identifies the device independent of
> transport.
>
> The answer is that someone needs to think about doing it using udev.
[added hotplug list to the cc]
scsi_id is included with the udev source now, and can be used to solve
most of the problem.
We still need something that tells udev what to do with multiple matches -
for multi-pathed sd's showing up multiple times, we don't want to drop the
other sd's, and that is what will happen right now with udev.
-- Patrick Mansfield
next prev parent reply other threads:[~2004-02-04 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 19:58 Mount by WWN (FC, using qlogic 2200) Martin Peschke3
2004-02-04 20:06 ` James Bottomley
2004-02-04 20:15 ` Patrick Mansfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 9:52 EXT / DEVOTEAM VAROQUI Christophe
[not found] <OFB4AE9EAB.C15E2C56-ON87256E30.007E8F0D-88256E30.007F5E0C@us.ibm.com>
2004-02-04 23:23 ` James Bottomley
2004-02-05 0:33 ` Bryan Henderson
2004-02-05 13:56 ` Tom Coughlan
2004-02-05 15:10 ` James Bottomley
2004-02-05 16:38 ` Patrick Mansfield
2004-02-04 10:19 EXT / DEVOTEAM VAROQUI Christophe
2004-02-04 18:39 ` Robert J. Adams (jason)
2004-02-04 1:27 NH Support
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=20040204121514.A9609@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=MPESCHKE@de.ibm.com \
--cc=ext.devoteam.varoqui@sncf.fr \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=radams@siscom.net \
/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