I have a Dell 6650 running RedHat AS 2.1 kernel 2.4.9-e49 enterprise with dual QLogic 2314 cards attached in failover mode. I recently had our storage guy add a new LUN.

I had hoped to add this lun by executing this:
But sadly, while QLogic SANSurfer can now see the LUN, I cannot run fdisk against it, or make a file system on it.

Is there a way to make this LUN visible to the OS without rebooting or unmounting all my other SAN partitions?

Thanks much.

Nevermind I figured this out by googling.

I had to run this command first for each QLogic adapter if anyone is interested:

What is the ADAPTER_ID ??? where to get it ?

Thanks in advance

The adapter ID is automagically assigned by the kernel. In the directory /proc/scsi/qla2300, there will be 1 or more files named "0", "1", "2" and so on. Each one corresponds to detailed kernel information about your QLogic cards. There is 1 file for each card installed on your system. If you cat the file, you can see detailed information about the cards including firmware and driver version.

Hi again,

mmmmm I am trying to figure out how this works.
The case is that I have Emulex 9200 cards in my proliant servers.... and only have the directory /proc/scsi/lpfc/ ... and in there files 0 and 1.
A cat of the 0 file looks like:
-----
servername:/proc/scsi/lpfc# cat 0
Emulex LightPulse FC SCSI 7.0.3
Emulex LightPulse LP9002 2 Gigabit PCI Fibre Channel Adapter on PCI bus 06 device 08 irq 5
SerialNum: MS34076343
Firmware Version: 3.92A2 (C2D3.92A2)
Hdw: 2002606d
VendorId: 0xf90010df
Portname: 10:00:00:00:c9:38:1c:2d Nodename: 20:00:00:00:c9:38:1c:2d

Link Up - Ready:
PortID 0x160f00
Fabric
Current speed 2G
lpfc0t00 DID 1b0b00 WWPN 50:00:60:e8:02:c5:91:00 WWNN 50:00:60:e8:02:c5:91:00
lpfc0t01 DID 111d00 WWPN 50:00:60:e8:02:c5:51:04 WWNN 50:00:60:e8:02:c5:51:04
---------

So... what should I echo into this file in order to have my HBA recongnize the disks online ???!!!

Thanks in advance

The Emulex cards are not the same as the QLogic cards so echoing qlogic commands won't work. I would google for Linux emulex documentation such as this: http://www.emulex.com/ts/docfc/linux...f/trouble.pdf.