Anaconda in previous Fedora releases lacked the ability to correctly identify and set up multipath devices for use as installation targets. This feature represents the addition of that ability.
- Name: Peter Jones
- Email: email@example.com
- Targeted release: Fedora 13
- Last updated: 9-Feb-2010
- Percentage of completion: 95%
This feature adds support for installing to a multipath device and booting from such a device.
Benefit to Fedora
This is a hardware enabling feature. It allows Fedora to be installed on machines which were previously problematic.
This has repercussions in several packages:
- identification/setup before install
- configure dracut to build a hostonly initrd
- build initrd at the end of the installation rather than as soon as the kernel is installed
- assemble mpath devices during boot in order to correctly find the root filesystem
How To Test
- install to a machine with multipath storage.
- Ideally, test devices should include active/active and active/passive configurations.
- see if it boots correctly afterwards
- boot, and then run "dmsetup ls" and "dmsetup table" as root, making sure that the output indicates that / is indeed using a multipath device.
During installation, multipath devices should show up on the "multipath" tab under "Specialized Storage Devices", and the constituent devices should not be present.
This depends on changes to:
- anaconda (80% done (kickstart support is TODO))
- dracut (100% done)
- device-mapper-multipath (100% done)
- lvm (100% done, I think)
- kernel (100% done)
- grubby (100% done)
- None necessary - hardware that doesn't install correctly still won't install correctly.
- No separate docs at this time; we will add some for kickstart support. There's also some documentation of the UI as part of the storage design page.
- anaconda now supports installation to multipath devices.