Jim Perrin wrote:
> Use the 'mpath' when you're installing, and that should pretty much
> take care of it. The one issue that we had is that the Centos/RHEL
> mpath option defaults to active/active pathing, so storage systems
> that use active/passive (like our DS4700) can get angry unless you
> change the configuration after install. Also, I've heard reports of
> some folks having delays with older HBAs like the qla23xx, needed a
> longer timeout than the 250 listed in /proc/scsi/scsi. I've not
> confirmed this, and it could simply be related to the way the san is
> cabled up or how the zones are defined.
Cool thanks! Our array is active-active so that's good to know.
I have a theory on why the system failed to boot in CentOS, the system
actually has a pair of internal disks connected to a SATA controller,
we turned the SATA controller off in the bios but the installer still
may of seen it and installed stuff to it. With VMWare it doesn't
support that SATA controller so it never touched the internal disks.
nate
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
