On 12/16/2010 01:24 AM, Or Gerlitz wrote:
can it explain the delay in exposing the luns to the initiator scsi stack?
Not sure what you mean exactly.
The initiator will do iscsi login then scan for devices by doing echo -
- - > /sys/class/scsi_host/hostX/scan. The scsi layer handles this by
doing inquirys and report luns commands. If it finds devices it creates
the scsi_device kernel structs for the logical unit. So the kernel
initaitor stack knows about the LUs right away and we should see them in
sysfs.
When the kernel creates the scsi_device struct and does a add on the
kobject in the device struct in them, udev would see a hoplug event and
handle this by making the /dev nodes. So a udev issue could slow down
the creation of the /dev nodes.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
