Red Hat Bugzilla – Bug 165877
LVM volumes built on top of mdadm.conf-declared RAID arrays do not get activated
Last modified: 2014-03-16 22:55:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Description of problem:
If you setup an LVM volume on top of a RAID array declared in /etc/mdadm.conf, instead of raidtab, it does not get activated at boot.
LVM volumes are initially searched for before RAID arrays are activated.
rc.sysinit makes two more tries to search for LVM volumes, but only if RAID arrays are declared through /etc/raidtab.
Since raidtools and, by extension, /etc/raidtab are not installed/used by default in RHEL4 anymore, LVM volumes can get overlooked.
It seems like the second shot at LVM initialization that currently only happens if raidtab exists should probably occur if any RAID arrays have been activated, not only if raidtab exists (see line 620 in rc.sysinit).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Declare RAID array in /etc/mdadm.conf. Make sure no /etc/raidtab exists.
2. Create LVM volume
3. Reboot. It will not be activated.
*** This bug has been marked as a duplicate of 149514 ***