[26] in linux-scsi channel archive
Re: Probing luns > 0 (fwd)
daemon@ATHENA.MIT.EDU (Andrew Walker)
Wed Jan 25 07:40:30 1995
From: andy@eng.kvaerner.no (Andrew Walker)
To: eowmob@exp-math.uni-essen.de (Michael Weller)
Date: Wed, 25 Jan 1995 12:41:53 +0100 (MET)
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.3.89.9501251119.G88478-0100000@werner.exp-math.uni-essen.de> from "Michael Weller" at Jan 25, 95 11:57:37 am
Hi,
Michael Weller wrote:
> > It just dawned on me that another option is a command line parameter which
> > just indicates which SCSI id's to probe for multiple LUNs:
> >
> > scsi_multi_luns=35
> >
> > i.e. probe id's 3 and 5 for multiple LUNs.
> >
> > -Andy
>
> Keep in mind for all those solutions that there may be more than one
> SCSI-BUS in the system. (at least for different host adapter types, I think
> multiple 1542 are still not supported. Some adapters even have more than
> one SCSI bus themself. This the SCSI id alone does not identify a SCSI device
> completely.
>
> Michael.
You're right, of course. I should have thought of that - after all, I do have
two SCSI adapters in my PC - one BT-545S and a AHA-1510 (on an SB16/SCSI-2).
This makes life worse. You could represent the adapter numbers in the command
line some way, but this is effectively hard-coding the order in which they
get detected :-( Anybody see a way around this without building a list of devices
to be probed for multiple LUNs?
-Andy
--
Andy Walker Kvaerner Engineering a.s.
Andrew.Walker@eng.kvaerner.no P.O. Box 222, N-1324 Lysaker, Norway
......if the answer isn't violence, neither is it silence......
