Bug 1020134

Summary:	Device names on Mdadm are forced to be changed into ones quite different from initial OS installation's
Product:	[Fedora] Fedora	Reporter:	Ta-chang <ta.chang1972>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-17 11:37:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ta-chang 2013-10-17 06:03:54 UTC

Description of problem:
Device names on Mdadm are forced to be changed into ones quite different from initial OS installation's (please see the following URL because it describes almost the same content of issue as mine, although its main topic is for another distribution: http://board.issociate.de/thread/508621/Question-on-md126--md127-issues.html)

Version-Release number of selected component (if applicable):
kernel: 3.10.14-100.fc18.x86_64 x86_64
mdadm: mdadm-3.2.6-21.fc18.x86_64

How reproducible:
After several manual system reboots since initial OS installation, device names of Mdadm are forced to be changed into quite different ones from then (i.e. /dev/md127, /dev/md126...).

Steps to Reproduce:
1.Normal Mdadm setup during initial OS installation and update kernel to the lateset version

Actual results:
Filesystem corruptions, especially super-block faults

Expected results:
Future unexpected corruptions of filesystem on Mdadm shown in syslog outputs

Additional info:

Comment 1 Josh Boyer 2013-10-17 11:37:05 UTC

I believe this is a duplicate of 1018272

*** This bug has been marked as a duplicate of bug 1018272 ***