Bug 41913 - raid-bootup improvement
raid-bootup improvement
Product: Red Hat Raw Hide
Classification: Retired
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-05-22 17:22 EDT by Helge Deller
Modified: 2014-03-16 22:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-05-22 17:32:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch against rc.sysinit (874 bytes, patch)
2001-05-22 17:32 EDT, Helge Deller
no flags Details | Diff

  None (edit)
Description Helge Deller 2001-05-22 17:22:55 EDT
Description of Problem:

at boot-up /etc/rc.d/rc.sysinit starts up the raiddevices from 
/etc/raidtab (if this file exists) and falls back to a raid-repair-shell 
if it can't find/load the devices. This is behaviour is correct and 
should be like that, but I use personally sometimes a raid-array on a 
external scsi-storage, which I don't want to use every time. So if I  
leave my /etc/raidtab the boot-up stops everytime with a repair-shell if 
I haven't enabled the external storage and I need to remove or rename 
/etc/raidtab and reboot the machine.

Instead rc.sysinit should verify in /etc/fstab if this raid-device should 
really be loaded at bootup (via the "noauto" flag in /etc/fstab) and 
_only_ if "noauto" is _not_ given on the fstab-line start the 
raid-services on this device.

The attached patch does this and skips initialization of raid-devices, 
which have the "noauto" flag set in /etc/fstab.

Please apply.
Comment 1 Helge Deller 2001-05-22 17:32:11 EDT
Created attachment 19350 [details]
patch against rc.sysinit
Comment 2 Bill Nottingham 2001-05-23 18:01:11 EDT
Will be in 5.88-1 - thanks.

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