Re: Enterprise patch needed - please help

[Andrew Patterson <andrew@fc.hp.com>]

On Thu, 2002-05-30 at 06:43, Michael Clark wrote:
> 
> On 05/30/02 20:38, Alan Cox wrote:
> 
> >On Thu, 2002-05-30 at 05:46, Michael Clark wrote:
> >  
> >
> >>Also, some devices need a BLIST_SPARSELUN added in scsi_scan.c - even if 
> >>the device
> >>reports SCSI-3, the scanning code by defaults stops when it finds a lun 
> >>that doesn't
> >>respond. It is quite common with enterpise storage to have sparse 
> >>between luns.
> >>    
> >>

The following entries in the device_list array of scsi_scan.c should do
the trick for HP arrays.

   {"HP", "A6188A", "*", BLIST_SPARSELUN},      // HP Va7100 Array
   {"HP", "A6189A", "*", BLIST_SPARSELUN},      // HP Va7400 Array
   {"HP", "A6189B", "*", BLIST_SPARSELUN},      // HP Va7410 Array
   {"HP", "OPEN-", "*", BLIST_SPARSELUN},       // HP XP Arrays

Note that you must have a LUN at LUN number 0, to detect sparse LUN's
above LUN number 7.  

Andrew Patterson

    

> >
> >If we use report luns should we even be checking BLIST_SPARSELUN I
> >wonder
> >
> >  
> >
> Oh, is this new or maybe my device doesn't report luns as I've needed
> the sparse lun hint even though device was correctly detected as SCSI-3.
> This is with 2.4.18
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>