Bug 126202 - (IT_51360) mdadm -As not being set on boot.
mdadm -As not being set on boot.
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: initscripts (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-06-17 10:23 EDT by Brett Simpson
Modified: 2014-03-16 22:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-08 11:33:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brett Simpson 2004-06-17 10:23:34 EDT
Description of problem:
On bootup the raid portion of the /etc/rc.d/rc.sysinit doesn't
initialize any mdadm created arrays from /etc/mdadm.conf.
Although raidtools can do this, via a raidtab entry, I am unable to
get it to automatically failback when using multipath. I need to have
the auto failback functionality without having to manually failback
the paths.
For now I have added the following in my /etc/rc.d/rc.sysinit to make
mdadm work on boot.

update_boot_stage RCraid

if [ -f /etc/mdadm.conf ]
then
/sbin/mdadm -As
fi

if [ -f /etc/raidtab ]; then

Any chance on adding something similar to the initscripts package?

Thanks
Brett
Comment 1 Bastien Nocera 2004-10-08 11:33:11 EDT
There is no proper mdadm support in RHEL3. There are plans to have
mdadm support implemented in the next release.

Note You need to log in before you can comment on or make changes to this bug.