Re: Sparse LUN scanning - 2.4.x

[Jim Zajkowski <jamesez@umich.edu>]

On 2005-01-11 19:07:53 -0500, Michael Clark <michael@metaparadigm.com> said:

>> The problem is this: since LUN 0 does not show up -- specifically, it 
>> can't read the vendor or model informaton -- the kernel SCSI scan does 
>> not match with the table to tell the kernel to do sparse LUN 
>> scanning... so the RAID does not appear.

> Add the Xserve with the BLIST_SPARSELUN flag into the blacklist/quirks 
> table in drivers/scsi/scsi_scan.c

It already is in the quirks list.

The problem is that LUN 0 does not show up on this machine, so the 
quirks table doesn't work.  Looking at /proc/scsi/scsi shows the device 
but only sorta:

> Host: scsi1 Channel: 00 Id: 00 Lun: 00
>   Vendor:          Model:                  Rev:
>   Type:   Processor                        ANSI SCSI revision: ffffffff

whereas the LUN that is mapped shows up like this:

> Host: scsi1 Channel: 00 Id: 00 Lun: 01
>   Vendor: APPLE    Model: Xserve RAID      Rev: 1.20
>   Type:   Direct-Access                    ANSI SCSI revision: 02

So since the information doesn't show up, the quirks table magic 
doesn't work since it doesn't know that it needs to do a sparse lun 
scan.

--Jim

-- 
Jim Zajkowski          OpenPGP 0x21135C3    http://www.jimz.net/pgp.asc
System Administrator  8A9E 1DDF 944D 83C3 AEAB  8F74 8697 A823 2113 5C53
UM Life Sciences Institute