sd.conf entries
2007-12-25 6:58:00
Just a quick question. I recall in years past that if sd.conf was
pre-populated with entries that a boot time delay penalty would occur
which was supposed to be something like 3 seconds per lun for luns
that really weren't available.
My question is does solaris and the sd driver still behave this way?
With a modern SAN array this behaviour wouldn't make a lot of sense
because with the HBA logged in to the array port and bound to say scsi
target 80 the scsi layer on solaris could simply issue a report luns
command rather than probing for luns just because they were listed in
sd.conf.
Can anyone please clear this up for me.
Regards,
Vic
Comments
Got something to say?
You must be logged in to post a comment.
