Bug 460080 - fstyp's hardcoded into mkdumprd
Summary: fstyp's hardcoded into mkdumprd
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kexec-tools
Version: 9
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Neil Horman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-26 03:27 UTC by Richard P
Modified: 2008-08-26 10:45 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-08-26 10:45:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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)


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