>From: Ed Wilts [mailto:[EMAIL PROTECTED]]
>
>On Thu, Jul 11, 2002 at 11:00:53AM +0000, Pierre Hardy wrote:
>> Is there support for Fiber Channel with Red Hat?  If there is, where can 
>> get material on it and read up? 
>
>Yes, there is support.  EMC even has Linux on their officially supported
>list.  Other vendors also support Linux.
>
>A quick Google search for "Linux fiber channel" will give you lots of
>hits to start your research.

I'll warn you right now its not as easy as that. I've been struggling to get

some NFS boxes attached to an IBM ESS Shark and the amount of useful info
has
been sparse. (PS: Love the Shark. Love being able to configure it myself
instead
of having to get approval for my changes from some EMC chowderhead)

What I've learned:

        1) RedHat 7.3 has made some changes to the initrd that causes the
SAN drives o be detected BEFORE the local SCSI drives. While you could in
theory boot from these, I'm not a big fan of the idea, esp. since in my
experience their detect order can change (observed under Windows, at least).
It worked "properly" under RH 7.2.

I'm tweaking the process, but basically you need to rebuild your initrd
using mkinitrd.

For now, what I did causes the 

        2) The default kernel DOES NOT scan all LUNs, even if you pass the
"max_scsi_luns=256" flag. The result is that you only see the first SAN
disk. To the best of my knowledge, this was also a problem in 7.2.

So go into the kernel sources and build yourself a new kernel, being sure to
enable the "probe all SCSI LUNs" option. Not such a bad idea anyway, but I'd
have preferred to keep the QA-ed official kernel. Might as well build the
drivers for the local kernel in, this should ensure they're detected first.

Oh, the qla2200/qla2300 drivers are NOT in the SCSI driver section, but in a
config choice further down. Don't panic :^)

Hopefully that's what you need. 





_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to