Description of problem:
In rc.sysinit, MD device activation happens before multipath meaning that if a
user configures an MD array consisting of device-mapper-multipath devices, MD
will bind the devices first and multipath is unable to start correctly.
Working around this requires the user to deactivate MD, run multipath and then
manually reactivate the MD array with the correct (multipathed) member devices.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure multiple paths to storage using device-mapper-multipath
2. Create an MD software RAID array using the multipath devices (e.g.
Resulting MD array after reboot contains individual paths as members. No
multipath maps are created.
Multipath maps created. MD array contains mpath devices as members.
We do not support arbitrary-level stacking of DM and MD - the alternative would
be to keep execing both mdadm and lvm until there's nothing left to do, and I
don't think that's right.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Yes, at this point we don't do MD on multipath. LVM on multipath should be
supported, if needed.
*** Bug 704890 has been marked as a duplicate of this bug. ***