sd.conf entries
- From: SunAdmin <sunsysadmin@xxxxxxxxx>
- Date: Thu, 29 Mar 2007 11:25:21 -0400
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@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
- Prev by Date: Default Password or password reset help on RSC 2.2.2 on Sun V490
- Next by Date: Solaris Volume Manager & soft partition striping
- Previous by thread: Default Password or password reset help on RSC 2.2.2 on Sun V490
- Next by thread: Solaris Volume Manager & soft partition striping
- Index(es):
Relevant Pages
|
|
