[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sun-managers
Subject:    sd.conf entries
From:       SunAdmin <sunsysadmin () gmail ! com>
Date:       2007-03-29 15:25:21
Message-ID: 57248b5f0703290825i30301e6fx5c91e4c7d96ef134 () mail ! gmail ! com
[Download RAW message or body]

Hello List,

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
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
[prev in list] [next in list] [prev in thread] [next in thread]