Re: Qlogic (isp driver) gone mad on 6.0

Matthew Jacob wrote:
> Okay, sorry- try this change:
> 
> 
> diff -u -r1.106 isp_freebsd.c
> --- isp_freebsd.c       31 Jul 2005 23:21:19 -0000      1.106
> +++ isp_freebsd.c       17 Aug 2005 21:55:55 -0000
> _at__at_ -2609,6 +2609,14 _at__at_
>                 cpi->hba_eng_cnt = 0;
>                 cpi->max_target = ISP_MAX_TARGETS(isp) - 1;
>                 cpi->max_lun = ISP_MAX_LUNS(isp) - 1;
> +#if    1
> +               /*
> +                * If we ever get around to using REPORT_LUNS, we can undo this.
> +
> +                */
> +               if (cpi->max_lun >= 256)
> +                       cpi->max_lun = 256;
> +#endif
>                 cpi->bus_id = cam_sim_bus(sim);
>                 if (IS_FC(isp)) {
>                         cpi->hba_misc = PIM_NOBUSRESET;
> 
> and see id this helps you.

Well, the system boots faster as it doesn't have to probe 16k devices, 
but there's still one problem - it sees the correct 3 luns per device, 
but then adds a 'fake' device at lun 256 which is essentially the same 
as the first lun.  Here's some more info:

# camcontrol devlist
<PE/PV 1x3 SCSI BP 1.1>            at scbus0 target 6 lun 0 (pass0,ses0)
<JetStor snappod1-vol1 R001>       at scbus2 target 0 lun 0 (pass1,da0)
<JetStor snappod1-vol2 R001>       at scbus2 target 0 lun 1 (pass2,da1)
<JetStor snappod1-vol3 R001>       at scbus2 target 0 lun 2 (pass3,da2)
<JetStor snappod1-vol1 R001>       at scbus2 target 0 lun 256 (pass4,da3)
<JetStor snappod2-vol1 R001>       at scbus2 target 2 lun 0 (pass5,da4)
<JetStor snappod2-vol2 R001>       at scbus2 target 2 lun 1 (pass6,da5)
<JetStor snappod2-vol3 R001>       at scbus2 target 2 lun 2 (pass7,da6)
<JetStor snappod2-vol1 R001>       at scbus2 target 2 lun 256 (pass8,da7)
<JetStor snappod3-vol1 R001>       at scbus2 target 3 lun 0 (pass9,da8)
<JetStor snappod3-vol2 R001>       at scbus2 target 3 lun 1 (pass10,da9)
<JetStor snappod3-vol3 R001>       at scbus2 target 3 lun 2 (pass11,da10)
<JetStor snappod3-vol1 R001>       at scbus2 target 3 lun 256 (pass12,da11)
<JetStor snappod1-vol1 R001>       at scbus3 target 0 lun 0 (pass13,da12)
<JetStor snappod1-vol2 R001>       at scbus3 target 0 lun 1 (pass14,da13)
<JetStor snappod1-vol3 R001>       at scbus3 target 0 lun 2 (pass15,da14)
<JetStor snappod1-vol1 R001>       at scbus3 target 0 lun 256 (pass16,da15)
<JetStor snappod2-vol1 R001>       at scbus3 target 1 lun 0 (pass17,da16)
<JetStor snappod2-vol2 R001>       at scbus3 target 1 lun 1 (pass18,da17)
<JetStor snappod2-vol3 R001>       at scbus3 target 1 lun 2 (pass19,da18)
<JetStor snappod2-vol1 R001>       at scbus3 target 1 lun 256 (pass20,da19)
<JetStor snappod3-vol1 R001>       at scbus3 target 3 lun 0 (pass21,da20)
<JetStor snappod3-vol2 R001>       at scbus3 target 3 lun 1 (pass22,da21)
<JetStor snappod3-vol3 R001>       at scbus3 target 3 lun 2 (pass23,da22)
<JetStor snappod3-vol1 R001>       at scbus3 target 3 lun 256 (pass24,da23)


You can see that the 'lun 256' marked devices are duplicates.

Eric




-- 
------------------------------------------------------------------------
Eric Anderson        Sr. Systems Administrator        Centaur Technology
Anything that works is better than anything that doesn't.
------------------------------------------------------------------------