Bug 56002 - noauto+RAID broken
noauto+RAID broken
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
7.2
noarch Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-11-10 00:28 EST by Mike Bird
Modified: 2014-03-16 22:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-05 15:55:23 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 Mike Bird 2001-11-10 00:28:08 EST
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 15:55:23 EDT
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.

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