On Wed, Apr 19, 2006 at 09:26:15PM +0300, Jussi Silvennoinen wrote:
> Hello,
>
> how does one do persistent binding from qla2xxx/2300 on RHEL4
> (2.6.9-34.ELsmp.i686)?
I'd recommend lvm. You won't have to care about luns, uuids and the
like. The mapping is on-disk and works even when you wipe the host.
> scli doesn't work because /dev/qla2xxx is not there, neither does
> sansurfer. This is because of the drivermutilation I presume.
>
> Both utilities work fine with the driver available from qlogic's site.
>
> This sort of mutilation which prevents hardware configuration utilities
> from being used is most annoying and frankly ADOLESCENT behavior.
>
> I suppose my only course of action is to open up a support request and
> spend three days serving their "further information" inquiries and end up
> having my hat handed to me with "no it doesn't work" answer.
>
> I suppose I could rig up a shellscript which is run during bootup which
> checks is the driver the mutilated one or proper one from qlogic and
> compiles&replaces it if needed but I'd rather not go in to that with
> hardware which is supposed to be supported. I already have similar things
> done for the unsupported hardware in our datacenter (Areca, SSD).
If you need the qlogic "full" driver you can use the packages at
http://atrpms.net/dist/el4/qla2xxx/
Make sure to recreate the initrd, e.g. something like the kernel rpm's
%postin scriplet, for example for smp:
/sbin/new-kernel-pkg --package kernel-smp --mkinitrd --depmod --install 2.6.9-34.ELsmp
--
Axel.Thimm at ATrpms.net
Attachment:
pgpzSyifljebL.pgp
Description: PGP signature