Bug 56002

Summary: noauto+RAID broken
Product: [Retired] Red Hat Linux Reporter: Mike Bird <mgb>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED CURRENTRELEASE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: noarch   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-05 19:55:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike Bird 2001-11-10 05:28:08 UTC
Description of Problem: Change in rc.sysinit in RH7.2 skips starting
/dev/mdN devices marked noauto in fstab, but fsck still checks them
... and bombs
Version-Release number of selected component (if applicable): initscriipts-6.40-1


How Reproducible:


Steps to Reproduce:
1. Create a RAID (happens to be RAID-5 here but I don't think it matteers)
2. mke2fs the RAID, add it to /etc/fstab and mark it noauto
3. reboot

Actual Results: rc.sysinit skips starting that /dev/mdN because it is
noauto, but fsck tries it anyway and bombs

Expected Results: Previous to RH7.2, the RAID start was not skipped
and the server rebooted and I didn't have to drive to the next county
to fix it  :-O
Additional Information:

Comment 1 Bill Nottingham 2005-04-05 19:55:23 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

With mdadm, this isn't as much of an issue in this case; previously, the RAID
startup code did change post-7.2, so the issue may have been fixed in the meantime.