Forgot your password?
New user?
Document Actions
Rebuild of initrd needed after changes to multipath configuration
After any changes to the multipath configuration of a cluster node, a new initrd must be created.
Background
The device mapper multipath maps block devices with the same unique id to eachother and ensures that their names stay the same after reboot.
Because the multipath configuration is also part of the generic initrd used by the Open-Sharedroot Project, the initrd must reflect the latest changes to the multipath configuration.
What happens if the configuration is not updated in the initrd?
The danger is that a device will be used differently in the stages of the initrd. This might confuse the multipath representation on the cluster nodes so that a cluster may require a reboot to revert to a common clusterwide multipath configuration.
So don't forget to build a new initrd after each multipath configuration change. Also make sure that the initrd has been successfully written to the storage. This is even more important on virtualized configurations where Xen or KVM may use buffered writes to the storage.
Follow @OpenSharedroot on twitter