Alexei,
Thanks for the your input.
In fact, I agree with you about download drivers (I follow the same rule, as you, avoid downloading drivers or packages from the Internet if the system has one). We just tried it because, after apply the SP3, we can't see the LUN0 (/dev/sdb) anymore and, before apply SP3, we see the LUN0 as /dev/sdb but we got lots of I/O errors.
Fdisk was used just to create a single partition to test the LUN. There is no specific reason. We tried to use Yast but we just see both cards (the internal MegaRaid and Emulex LP8000), but there is no aditional information about the disks. This information is available in the HBAnyware (wich depends from LP8000 downloaded driver to work).
The Emulex show the LUNS in HBAnyware utility, but Linux can't access then. Bellow is piece of dmesg. The only diference between SP3 driver and Emulex download driver is jsut one line (marked bellow):
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
SCSI subsystem initialized
megaraid cmm: 2.20.2.6 (Release Date: Mon Mar 7 00:01:03 EST 2005)
megaraid: 2.20.4.6 (Release Date: Mon Mar 07 12:27:22 EST 2005)
megaraid: probe new device 0x1028:0x0013:0x1028:0x016e: bus 2:slot 14:func 0
ACPI: PCI interrupt 0000:02:0e.0[A] -> GSI 46 (level, low) -> IRQ 20
megaraid: fw version:[521S] bios version:[H430]
scsi0 : LSI Logic MegaRAID driver
scsi[0]: scanning scsi channel 0 [Phy 0] for non-raid devices
Vendor: PE/PV Model: 1x2 SCSI BP Rev: 1.0
Type: Processor ANSI SCSI revision: 02
scsi[0]: scanning scsi channel 1 [Phy 1] for non-raid devices
Vendor: PE/PV Model: 1x8 SCSI BP Rev: 1.0
Type: Processor ANSI SCSI revision: 02
scsi[0]: scanning scsi channel 2 [virtual] for logical drives
Vendor: MegaRAID Model: LD 0 RAID0 69G Rev: 521S
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 143114240 512-byte hdwr sectors (73274 MB)
sda: asking for cache data failed
sda: assuming drive cache: write through
sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 2, id 0, lun 0
lpfc: module not supported by Novell, setting U taint flag. (THIS LINE DON'T APPEARS WITH SP3 DRIVER, REMAINING IS THE SAME)
Emulex LightPulse Fibre Channel SCSI driver 8.0.16.17
Copyright(c) 2003-2005 Emulex. All rights reserved.
ACPI: PCI interrupt 0000:03:0b.0[A] -> GSI 37 (level, low) -> IRQ 21
lpfc 0000:03:0b.0: 0:1303 Link Up Event x1 received Data: x1 x2 x0 x0
scsi1 : Emulex LightPulse LP8000 1 Gigabit PCI Fibre Channel Adapter on PCI bus 03 device 58 irq 21
scsi: unknown device type 12
Vendor: COMPAQ Model: ARRAY CONTROLLER Rev: 2.40
Type: RAID ANSI SCSI revision: 00
kjournald starting. Commit interval 5 seconds
-----Mensagem original-----
De: Alexei_Roudnev [mailto:Alexei_Roudnev@(protected)]
Enviada em: segunda-feira, 13 de março de 2006 17:11
Para: Anderson Carlos Trindade; suse-oracle@(protected)
Assunto: Re: [suse-oracle] Oracle9i RAC using Dell PowerEdge 2800,
Emulex LP8000 and StorageWorks RA4100
It is all pretty sprange:
(1) You SHOULD NOT download drivber from Emulex - SLES9 SP3 have driver
which works well and is wel tested with ALL systems (and if you download
driver, you always risk to have uncompatible driver and system).
(2) Why use fdisk - SuSe have yast -> disk which should be used (I am just
curious). For hardware, SuSe have yast -> hardware -> (click on teh card) -
it shows everything. + you can run 'lsscsi' command.
(3) If it was LP9xxx card, you should upgrade firmware. But I believe it is
not necessary for LP8000 (which is pretty stable and solid HBA).
In reality, SuSe changed Emulex driver in SP2 (Emulex drivers in SP1 and Sp2
are absolutely different), and new driver do not understand some old (and
wrongly implemented) Compaq storage system (old driver had numerous hacks
which helped to use them). May be , it is a case? Did you try to get support
from Emulex (they helped me when I invesrigated simular problem).
But anyway, I created one rule for myself - if Linux have embedded driver,
it is better to use it, donot compile driver manually. It works for VGA
cards and it works for HBA cards.
As I remember, EMC adviced to add some information into the SCSI table.
Problem with the new LP driver was that it have not old hacks (implemented
in old driver) which rewrite information so that (broken) COmpaq storage
pretended to behave normally, so new drivers could not work with some Compaq
storage systems (which definitely violated SCSI standard). I am not sure
about your case, so better consuilt with Emulex (and better try both,
original driver and downloaded one).
----- Original Message -----
From: "Anderson Carlos Trindade" <anderson@(protected)>
To: <suse-oracle@(protected)>
Sent: Monday, March 13, 2006 11:48 AM
Subject: [suse-oracle] Oracle9i RAC using Dell PowerEdge 2800, Emulex LP8000
and StorageWorks RA4100
Hi List,
We're trying to set up a RAC environment, using:
Oracle 9.2.0.6 64-bit
SLES 9 SP3 64-bit
2 x Dell PowerEdge 2800
2 x HBA Emulex LP8000
1 x HP StorageWorks RA4100
Connection to storage throught FC switch
The used procedure:
1) - We installed the SusE Linux on the first machine. At the installation,
Yast shows two disks, the internal disk (/dev/sda) and the LUN created by
our vendor before we get the storage (/dev/sdb). We installed the system
into /dev/sda, leaving the /dev/sdb for use with RAC
2) - After system installation, we made tests into the storage. First, fdisk
/dev/sdb to create a single partition. At this moment, we can see lots of
I/O errors over the storage (but no erros reported by fdisk). We created a
huge tar file into the storage and, again, lots of I/O errors in the system
console, but no erros reported by tar utility.
3) - After that, we installed SP3. At the boot, we can see the new Emulex
driver is loaded but /dev/sdb is not present anymore. Trying to fdisk
/dev/sdb, we got "unable to open device /dev/sdb).
4) - Then, we download the latest Emulex driver from
<http://www.emulex.com/> www.emulex.com, and the HBAnyware utility. The
problem is the same: we can see messages from driver in the boot phase
(there is no error messages), but the /dev/sdb device is not available.
5) - We used HBAnyware utility (from Emulex) to get some more information
about the HBA. Throught this utility, we can see all the hardware components
in a way similar to this:
<Host Name>
+ - Emulex LP 8000
+ <one WWN address, from Storage RA4100 I think>
+ LUN0
We can conclude, from the information above, the hardware connections are
OK. The question is: why can't we see the LUNS into Linux box after applying
the SP3? Ins't Linux compatible with StorageWorks RA4100? Is it necessary to
install any aditional packages?
Every input is welcome.
Lookinf for your help.
Thanks,
Anderson
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting
