[20] in linux-scsi channel archive
Re: Default, no probing of luns > 0
daemon@ATHENA.MIT.EDU (Rik Faith)
Tue Jan 24 11:46:40 1995
Date: Tue, 24 Jan 1995 10:31:09 -0500
From: Rik Faith <faith@cs.unc.edu>
To: Drew Eckhardt <drew@boulder.openware.com>
In-Reply-To: [Drew Eckhardt <drew@boulder.openware.com>] Mon 23 Jan 1995 11:17:06 MST
CC: linux-scsi@vger.rutgers.edu, linux-activists@niksula.hut.fi
On Mon 23 Jan 1995 11:17:06 MST,
Drew Eckhardt <drew@boulder.openware.com> wrote:
> There are still large numbers of broken SCSI devices out there which
> are extremely unhappy (ie, lock the SCSI bus up, do an unexpected
> disconnect, etc) when you attempt to talk to them at a LUN other
> than 0.
>
> Since very few devices use multiple LUNs (SCSI bridge boards,
> fan out adapters, jukeboxes, and CD changers are the only
> ones to come to mind), I think that it might be reasonable
> to make the default maximum LUN searched 0 instead of 7.
>
> We could scan for the additional LUNS only when
> - The user used the max_scsi_luns= command line
> option.
> - Certain vendor & model combinations were returned
> in result for the IDENTIFY command sent to
> LUN 0 of a given target.
> Comments?
I think this is an excellent idea and will alleviate many of the buf
reports and problems that LUN scanning causes.
Note that I have CC'd the linux-scsi list at vger -- can we please continue
this discussion on the vger list?
