Re: IBM ESS (Shark) connectivity on a RedHat AS 2.1

From: F. Michael Orr (morr_at_utility.vccs.edu)
Date: 02/10/04


Date: Tue, 10 Feb 2004 10:32:40 -0500

On Mon, 09 Feb 2004 18:15:49 -0800, Mike O'Reilly wrote:

> Ilya Usvyatsky wrote:
>> Hi folks,
>> I am trying to connect a Shark (IBM ESS) array to a Linux box that is
>> running RH AS 2.1 (errata 27). I am using 2 Qlogic 2300 HBA's. I've
>> configured array and zoned the switch so that 8 LUNs should be visible
>> to the host. Yet, the host
>> for some strange reason sees only one LUN - on both adaptors. I am
>> using the 'latest and greatest' Qlogic driver (not the one that comes
>> from RH). And I am able to see my other array (HPXP) on the very same
>> box with no problem.
>> Your help will be greatly appreciated.
>> Puzzled,
>> Ilya.
>
> Can you see all the LUNS in the BIOS. Go into the QLA2x00 BIOS,
> Fast!UTIL by hitting ctrl-Q when you see our BIOS banner. Run the Fibre
> Disk Utility to determine the ID(s) of the target, hit enter on the
> target to see its LUNS. It is important that you have LUN 0 present and
> that all the LUNS be contiguous (do not skip LUNS).

You also have to set up support for multiple LUNs per target; this is not
on by default. Add the following line to /etc/modules.conf:

options scsi_mod max_scsi_luns=128

Then, recreate the initrd image from which you boot via 'mkinitrd'. You
also _may_ have to add the line "max_scsi_luns=128" as a command line
parameter to the kernel; I have had situations where sometimes that was
required and other times it was not.

After you can see the LUNs, if you run SDD, then you _MUST_ use ext2;
ext3 will panic your kernel. Also, if you're like our shop and use a
"cookie-cutter" LUN size, then you can't use LVM on the LUNs; you have to
use Software RAID-0. An unfortunate side effect of the way the Linux
kernel allocates device descriptors is that a Linux system will only be
able to see 40 LUNs if it boots off of a SCSI device, even with the above
configuration. Other than all of the above caveats, you should be able to
access the Shark quite well; we have several production RHAS systems doing
just that.

Have you gotten a copy of SC26-7446? That is very specific about the
needed changes, kernel levels, etc, and can be downloaded from IBM's Shark
Web site (http://www.storage.ibm.com/hardsoft/products/ess/index.html?)



Relevant Pages

  • SUMMARY: 1TB External RAID shows up as 512GB
    ... that multi-LUN SCSI-based devices fail to show LUNS beyond the first one. ... The raid controller is Compaq smart array controller 5300 ... The driver for the raid controller is cpqary3. ...
    (SunManagers)
  • Re: RAID A1000: Cant see the module
    ... I applied the glm patch also. ... You should see the luns listed... ... so it seems the system is quite confused with the array. ... backout patch and rm6, clean the references to it and power-cycle system ...
    (comp.unix.solaris)
  • Re: Please help - adaptec 2820sa not ... RESOLVED
    ... Sysinstall does _not_ see my 2.7TB raid6 array. ... You should make two LUNs, and concat them or stripe them with GEOM. ... You shouldn't waste either disk space or money. ... If I make one array, I lose 25% to raid overhead. ...
    (freebsd-questions)
  • Re: VMS SAN Primer
    ... didn't support VMS and anything on the same storage array. ... If storage arrays present SCSI disks to VMS, why would one an array need ... "Mapping" is done to associate LUNs with FAs. ...
    (comp.os.vms)
  • Re: IBM ESS (Shark) connectivity on a RedHat AS 2.1
    ... Ilya Usvyatsky wrote: ... > configured array and zoned the switch so that 8 LUNs should be visible ... Can you see all the LUNS in the BIOS. ...
    (linux.redhat)