Bug 787864

Summary:	dracut ordering problems causes potential total RAID loss
Product:	[Fedora] Fedora	Reporter:	H. Peter Anvin <hpa>
Component:	dracut	Assignee:	dracut-maint
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dracut-maint, harald, jonathan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-14 01:11:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description H. Peter Anvin 2012-02-06 22:52:39 UTC

Description of problem:
Dracut starts a RAID before it has enough devices to operate, and then cannot add the remaining drives back in.

This is probably due to the "fix" for bug 751667.

Version-Release number of selected component (if applicable):
dracut-013-20.fc16.noarch.rpm
mdadm-3.2.3-3.fc16.x86_64.rpm

How reproducible:
No idea, this system doesn't boot very often.

Actual results:
On boot, a RAID-6 with 6 disks has only 3 disks enabled, the array is inactive, and the boot failed.  Attempts at assembling the RAID manually fails due to divergent serial numbers; mdadm --assemble --force seems to have worked.


Expected results:
Boot.


Additional info:
See bug 751667.

Comment 1 Harald Hoyer 2012-07-03 07:51:40 UTC

Is this still happening for you?

Comment 2 Fedora End Of Life 2013-01-16 22:38:21 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-14 01:11:13 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.