From: Christoph Hellwig <hch@infradead.org>
To: "Surekha.PC" <surekhap@cisco.com>
Cc: 'SCSI Mailing List' <linux-scsi@vger.kernel.org>
Subject: Re: iSCSI device naming issues
Date: Sun, 4 Jul 2004 21:11:11 +0100 [thread overview]
Message-ID: <20040704201111.GA8038@infradead.org> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAANoIxZIFzbEaqwjJgytz2AeKAAAAQAAAAXdSfMOoTnU6X86O4sbqWzAEAAAAA@cisco.com>
On Thu, Jul 01, 2004 at 07:28:03PM +0530, Surekha.PC wrote:
>
> Whenever an iSCSI device is configured in the system, a hotplug
> event is generated which invokes udev for device node creation.
> iSCSI driver has a CALLOUT rule for udev to generate a unique
> name for iSCSI devices.
>
> The iSCSI callout program receives a sysfs device path like
> /sys/block/sdc whenever a block device is added. From the device
> symlink under /sys/block/sdc, it obtains the corresponding device
> path under /sys/devices/.. . It extracts the device quadruple
> (c,b,t,l) and identifies iSCSI device by parsing the path
> /sys/class/scsi_host/iscsi/c:b:t:l. For c:b:t:l as 0:0:0:0,
> iSCSI device name will be /udev/iscsib0t0l0.
> P.S: <hostX> is replaced by "iscsi" above to lookup for iSCSI devices.
Please just use the standard naming scheme instead of inventing
your own names.
prev parent reply other threads:[~2004-07-04 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 13:58 iSCSI device naming issues Surekha.PC
2004-07-01 15:57 ` Mike Anderson
2004-07-01 17:29 ` udev naming of st devices [was Re: iSCSI device naming issues] Patrick Mansfield
2004-07-04 19:57 ` iSCSI device naming issues Arjan van de Ven
2004-07-07 9:05 ` Surekha.PC
2004-07-04 20:11 ` Christoph Hellwig [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=20040704201111.GA8038@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=surekhap@cisco.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