Bug 57978

Summary:	initscripts-5.84.1-1 tries to raidstart undefined devices
Product:	[Retired] Red Hat Linux	Reporter:	Chris Watt <cnww>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED WONTFIX	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-02-22 20:42:18 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 Chris Watt 2002-01-04 07:41:00 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (Win98; U)

Description of problem:
A direct result of the fix to bug 51231 "Bug in GREP causes raid 
initialization to fail" appears to be that rc.sysinit now attempts to 
raidstart devices which are not actually defined in /etc/raidtab

Version-Release number of selected component (if applicable): 5.84.1-1


How reproducible:
Always

Steps to Reproduce:
1.Edit /etc/raidtab and insert a comment like, for example:
# sample raiddev configuration file
2. Reboot
	

Actual Results:  rc.sysinit will try to raidstart device "sample".

Expected Results:  rc.sysinit should ignore the comment line.

Additional info:
While I found this when looking for the source of a startup error message 
on a server running RHL 7.1, I believe that this bug occurrs in RHL 7.2 as 
well (it seems to use the same regular expression).

I would humbly suggest that you replace the line:
for i in `grep "^[^*]*raiddev" /etc/raidtab | awk '{print $2}'`
with the line:

for i in `grep "^[[:space:]]*raiddev" /etc/raidtab | awk '{print $2}'`
Which should, AFAICT, fix this without re-breaking 51231

Comment 1 Bill Nottingham 2005-02-22 20:42:18 UTC

Closing out bugs on older, no longer supported releases. Apologies for any lack
of response. Please reopen if it persists on current releases.