On Sun, 2002-10-06 at 07:26, Michael Clark wrote:
> >>I see. ATM I'm using 2.4.19, but would like to get to 2.4.20, because of
> >>the TG3 fixes.
> >
> >
> > You were probably thinking of CONFIG_SCSI_MULTI_LUN above, then. That causes the kernel to probe all LUNs instead of just LUN 0, which is the default due to a lot of broken devices to respond to all LUNs instead of just LUN 0. The sparse LUN option is in addition to that in 2.5.x.
> >
> > If this is for a live server, it might be easiest to hard code the LUNs you need it to probe in to 2.4.x for now, and wait until 2.6.x for proper support.
>
> 2.4 supports sparse lun scanning, although it is not enabled
> dynamically and requires add a BLIST_SPARSELUN flag for your device
> in the device_list array in drivers/scsi/scsi_scan.c
I worked with Andrea to get the PV660F doing this, because it was not
working correctly, so I know of what you speak. I'll get that info from
/proc/scsi/scsi and then fix it up and see if that does it.
> You just need to get the Vendor and Model info from /proc/scsi/scsi
>
> I am using qlogic 2300s with sparse luns working fine on 2.4.18.
using the LB static bindings and *failover* still works?
> ~mc
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:55 EST