From: Ihno Krumreich <ihno@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Persistent naming for iSCSI devices
Date: Fri, 14 Nov 2003 14:20:56 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106881970418725@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106880228800918@msgid-missing>
hi,
How does the name reflect the source where the disks
come from. Target, Lun and what does B stand for?
Ihno
On Fri, Nov 14, 2003 at 04:05:04PM +0530, Surekha.PC wrote:
>
> Hi,
>
> Just a slight correction for my earlier mail.
>
> The example should have been
>
> NUMBER, BUS="scsi", ID=C:B:T:L, NAME="cCbBtTlL"
>
> And with the new field to be used for iSCSI devices,
>
> NUMBER, BUS="scsi", id=C:B:T:L, device_type="iscsi", NAME="iscsi-bBtTlL"
>
> Thanks,
> surekha
>
> -----Original Message-----
> From: linux-hotplug-devel-admin@lists.sourceforge.net
> [mailto:linux-hotplug-devel-admin@lists.sourceforge.net] On Behalf Of
> Surekha.PC
> Sent: Friday, November 14, 2003 3:00 PM
> To: linux-hotplug-devel@lists.sourceforge.net
> Subject: Persistent naming for iSCSI devices
>
>
>
> Hi,
>
> The persistent naming for iscsi disks cannot not achieved with the
> following rule in udev.config.
>
> NUMBER, BUS="scsi", ID=C:B:T:L, NAME="c0b0t6l0"
>
> The controller number is not unique for a particular HBA. Hence
> persistency is not retained. To overcome this problem for iSCSI devices,
> I would like to introduce another field in the following rule for udev.
>
> NUMBER, BUS="scsi", id=C:B:T:L, device_type="iscsi", NAME="iscsi-b0t6l0"
>
> With this approach the naming for iSCSI devices will be persistent
> regardless of controller id.
>
--
Best regards/Mit freundlichen Grüßen
Ihno Krumreich
"Never trust a computer you can lift."
--
Ihno Krumreich ihno@suse.de
SuSE Linux AG Projectmanager S390 & zSeries
Deutschherrnstr. 15-19 +49-911-74053-439
90429 Nürnberg http://www.suse.de
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-11-14 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 9:42 Persistent naming for iSCSI devices Surekha.PC
2003-11-14 10:47 ` Surekha.PC
2003-11-14 14:20 ` Ihno Krumreich [this message]
2003-11-14 14:43 ` Surekha.PC
2003-11-19 13:49 ` Surekha.PC
2003-11-20 0:02 ` Greg KH
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=marc-linux-hotplug-106881970418725@msgid-missing \
--to=ihno@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).