I'm using a boot-from-SAN bladecenter (equivalent of two FC controllers
per blade) and an IBM DS4400 SAN. When I install RHEL5 using the
"mpath" command line, the install pretty much goes OK, despite being
incredibly at each step in setting up partitions. Upon boot, I comment
the blacklist entry in the multipath.conf file, start the multipathd,
and things seem to behave about as I would expect them to.
When I then attempt to upgrade to the first errata kernel, paths start
failing and filesystems get marked read-only. The upgrade apparently
completes, but upon reboot into the new kernel, lvm find duplicate paths
and multipath -l spits out multiple paths as well.
My only guess is that something that the mpath argument tells anaconda
to carefully set up isn't being maintained by the kernel upgrade
process. Any ideas? A document from IBM suggests that the filter and
types lines in lvm.conf might have to be edited. Is that still true,
and could that be causing the trouble?
Also, this is more hardware specific, but a few documents suggest that
the DS4000 series is going to need a specific path checker to work
"best." My understanding is that such a beast would allow dm-mpath to
figure out which path is preferred. Until that program is written
though, is there any reason to be concerned about running RHEL5 with the
current level of support?
Thanks
DC
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
