Red Hat Bugzilla – Bug 813354
kdump.conf does not accept 'auto' as a filesystem type
Last modified: 2015-02-08 16:38:01 EST
+++ This bug was initially created as a clone of Bug #813345 +++
Description of problem:
the kdump.conf manpage states thus:
<fs type> <partition>
Will mount -t <fs type> <partition> /mnt and copy /proc/vmcore to /mnt/var/crash/%DATE/. NOTE: <partition> can be a device node, label or uuid.
However, mount -t auto works (it also works in fstab) and it does not work in kdump.conf with an error regarding fsck.auto which does not exist.
This becomes an issue when you have a mixed deployment of rhel5.7 and 5.8 where the default filesystem changed from ext3 to ext4 and the customer's standard kdump.conf stopped working...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. In kdump.conf specify your filesystem type as 'auto'
2. service kdump restart
Stopping kdump: [ OK ]
Detected change(s) the following file(s):
/etc/kdump.conf: Unsupported type auto: fsck.auto not found
Failed to run mkdumprd
Starting kdump: [FAILED]
The kdump service should restart normally and automagically identify between ext3/4 with the 'auto' fs option as mount does.
This can also be seen as a simpler documentation bug where the man page should specify that the filesystem type must exist and cannot be 'auto.' It should also explain what happens with that line and that a corresponding fsck.* executable must exist...
--- Additional comment from firstname.lastname@example.org on 2012-04-17 10:47:16 EDT ---
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Created attachment 601168 [details]
document the supported fs types
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.