Bug 460080

Summary:	fstyp's hardcoded into mkdumprd
Product:	[Fedora] Fedora	Reporter:	Richard P <rp8034l>
Component:	kexec-tools	Assignee:	Neil Horman <nhorman>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	medium
Version:	9
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:	2008-08-26 10:45:44 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 Richard P 2008-08-26 03:27:47 UTC

Description of problem:

kdump kernel fails to boot if root fstyp not ext2, ext3 or minix.
Root cause is mkdumprd; it hardcodes ext2, ext3 & minix into the 
generated initrd.

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

Fedora 9 - kexec-tools-1.102pre-8.fc9.x86_64

How reproducible:

I my case, fstyp of root file system was reiserfs.

Steps to Reproduce
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Perhaps the mkdumprd script could be enhanced to extract fstyp from fstab ?

Comment 1 Neil Horman 2008-08-26 10:45:44 UTC

kdump only supports root filesystems that are ext2/3 or minix.  If you have a root filesystem that is not one of those types, then you need to select an alternate dump target (see kdump.conf)