Re: LSI Profibre DF4000R LUN register problem on RH4.2

Jin Zhao <[email protected]>
Newsgroups gmane.linux.redhat.release.taroon.general
Organization Qcorps Residential, Inc.
Message-ID <[email protected]>
On Mon, 2006-09-18 at 13:58 -0500, Jin Zhao wrote:
After some diggings and hacking, I eventually got a solution to the problem. 

Adding these lines into /etc/rc.sysinit would fix the LUN register problem.
=========================================================================
#
# /etc/rc.sysinit
#############################################################
# mylex DAC-FFx2 controller device info:
#   LSI,ProFibre 4000R,*,BLIST_FORCELUN|BLIST_SPARSELUN|BLIST_LARGELUN
# insert the following line before the start_udev line
#
[ -f /proc/scsi/device_info ] && echo "LSI:ProFibre
4000R:0x242">/proc/scsi/device_info
=========================================================================
The above is a work-around for RHAS4.2. For RHAS4.3 and above, using the
scsi_mod parameters in /etc/modprobe.conf plus an initrd rebuild should
produce the same result.

=======================================================================
#
# /etc/modprobe.conf (RHAS4.3 and above)
############################################################
scsi_mod max_luns=256 dev_flags=LSI:ProFibre 4000R:0x240
=======================================================================

References:
1. kernel-2.6.x-src/include/scsi/scsi_devinfo.h
2. kernel-2.6.x-src/drivers/scsi/scsi_devinfo.c
3. Redhat Enterpise Linux 4 update 3 Release Notes. 

Jin

> > Date: Fri, 15 Sep 2006 11:20:28 -0500
> > From: Jin Zhao <[email protected]>
> > Subject: LSI Profibre DF4000R LUN register problem on RH4.2
> > To: [email protected]
> > Message-ID: <1158337228.4372.42.camel-5dPkI+PXL+Qr1oCt4N1a01aTQe2KTcn/@public.gmane.org>
> > Content-Type: text/plain
> > 
> > This problem seemed really odd to me. 
> > 
> > We have an old LSI Profibre DF4000R (with Mylex DC-FFx2 controller)
> > fibre channel storage system. It worked with a RHEL3 upgrade5 server
> > with a QLA2342 FC HBA card. Recently we tried to test the server with
> > RHEL4 update2, but found out that not all LUNs can be automatically
> > registered to the OS. 
> > 
> > The following is the content of /proc/scsi/scsi
> > /proc/scsi/scsi
> > ===================================================================
> > Attached devices:
> > Host: scsi2 Channel: 00 Id: 00 Lun: 00
> >   Vendor: ADAPTEC  Model: Adaptec Mirror   Rev: V1.0
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > Host: scsi2 Channel: 00 Id: 01 Lun: 00
> >   Vendor: ADAPTEC  Model: Adaptec Mirror   Rev: V1.0
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > Host: scsi9 Channel: 00 Id: 00 Lun: 00
> >   Vendor: LSI      Model: ProFibre 4000R   Rev: 5902
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > ===================================================================
> > We can only see one Profibre 4000R device.
> > 
> > This is /proc/scsi/qla2xxx/9 content with SCSI LUN information.
> > ===================================================================
> > SCSI LUN Information:
> > (Id:Lun)  * - indicates lun is not registered with the OS.
> > ( 0: 0): Total reqs 25, Pending reqs 0, flags 0x2, 0:0:01 00
> > ( 0: 1): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 2): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 3): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 4): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 5): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 6): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 7): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 8): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ===================================================================
> > We can see there are 9 LUNs but only the LUN 0 get registered. 
> > 
> > If I run 'echo "scsi add single device 9 0 0 1" >/proc/scsi/scsi', the
> > second device will be registered and used a /dev/sdd.
> > 
> > /proc/scsi/scsi after manually adding device
> > ===================================================================
> > Attached devices:
> > Host: scsi2 Channel: 00 Id: 00 Lun: 00
> >   Vendor: ADAPTEC  Model: Adaptec Mirror   Rev: V1.0
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > Host: scsi2 Channel: 00 Id: 01 Lun: 00
> >   Vendor: ADAPTEC  Model: Adaptec Mirror   Rev: V1.0
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > Host: scsi9 Channel: 00 Id: 00 Lun: 00
> >   Vendor: LSI      Model: ProFibre 4000R   Rev: 5902
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > Host: scsi9 Channel: 00 Id: 00 Lun: 01
> >   Vendor: LSI      Model: ProFibre 4000R   Rev: 5902
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > ===================================================================
> > 
> > /proc/scsi/qla2xxx/9 content with SCSI LUNs after manually adding
> > device.
> > ===================================================================
> > SCSI LUN Information:
> > (Id:Lun)  * - indicates lun is not registered with the OS.
> > ( 0: 0): Total reqs 49, Pending reqs 0, flags 0x2, 0:0:01 00
> > ( 0: 1): Total reqs 37, Pending reqs 0, flags 0x2, 0:0:01 00
> > ( 0: 2): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 3): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 4): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 5): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 6): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 7): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ( 0: 8): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:01 00
> > ===================================================================
> > 
> > What I can guess is that the problem might be from either mid-layer scsi
> > scan or RHEL4 hot-plugging system. (RHEL4 uses udev for devfs and
> > hotplug. which is still relatively new to me. )
> > 
> > Anybody else has better idea about the problem?
> > 
> > Thanks
> > 
> > Jin 
> > 
> > 
> > 
> > ------------------------------
> > 
> > --
> > Taroon-list mailing list
> > [email protected]
> > https://www.redhat.com/mailman/listinfo/taroon-list
> > 
> > End of Taroon-list Digest, Vol 31, Issue 9
> > ******************************************

--
Taroon-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/taroon-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.