This is a followup to a message I posted a few days ago. I'm in a boot
from SAN configuration onto an IBM DS4400. The initial install using
the "mpath" boot parameter went great. I did have to uncomment the
blacklist line from /etc/multipath.conf, but after that, multipath -l
looks as I would expect it to for two paths, configured active/passive:
[EMAIL PROTECTED] ~]# multipath -l
mpath0 () dm-0 IBM,1742
[size=8.0G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][enabled]
\_ 0:0:0:0 sda 8:0 [active][undef]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:0 sdb 8:16 [active][undef]
When I then attempt to upgrade to the latest RHEL kernel package, the
RPM upgrade seems to case the paths to fail, and the / partition gets
flagged as read-only. The kernel upgrade seems to complete though.
When I reboot into the new kernel, a number of things happen.
- For starters, the ip6tables service stalls for about 30 seconds. I'm
not using ip6 (yet), but this didn't happen after the initial install.
- The following error messages pop up during boot:
Cannot open bindings file [/var/lib/multipath/bindings] : Read-only file
system
/dev/sda2: open failed: No such device or address
Found duplicate PV using /dev/dm-7 not /dev/mapper/mpath0p2
When I get booted into the system, the multipath command shows a
less-reassuring bit of output:
[EMAIL PROTECTED] ~]# multipath -l
mpath0 () dm-0 IBM,1742
[size=8.0G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 0:0:0:0 sda 8:0 [active][undef]
\_ 1:0:0:0 sdb 8:16 [active][undef]
3600a0b80000f82ce0000006241e539ccdm-5 IBM,1742
[size=8.0G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 0:0:0:0 sda 8:0 [active][undef]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:0 sdb 8:16 [active][undef]
I can get something that's a bit more sane, by running multipath -F, but
the configuration isn't right (I can't round-robin the active/passive
paths without causing some issues):
[EMAIL PROTECTED] ~]# multipath -F
mpath0: map in use
[EMAIL PROTECTED] ~]# multipath -l
mpath0 () dm-0 IBM,1742
[size=8.0G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 0:0:0:0 sda 8:0 [active][undef]
\_ 1:0:0:0 sdb 8:16 [active][undef]
[EMAIL PROTECTED] ~]#
Any ideas what may be going on here? I'm assuming the kernel upgrade
scripts aren't maintaining something about the boot process that the
mpath command to anaconda does. I'm just not sure what. Booting into
the old kernel doesn't give me the original results anymore either.
Thanks
DC
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
