Red Hat Bugzilla – Bug 210174
kdump fails when the dump parition is specified as a label in /etc/kdump.conf
Last modified: 2007-11-30 17:07:35 EST
Description of problem:
/etc/kdump.conf does not allow to specify the dump partition as a label.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. add 'ext3 LABEL=/1' to /etc/kdump.conf
2. execute kdump
kdump fails to save vmcore to the dump partition.
kdump succeeds to save vmcore to the dump partition which is specified in
Appended patch fixes the problem.
Created attachment 138155 [details]
I'm going to add this feature, but for the record, the documentation in
kdump.conf clearly indicates that that a partition must be specified with the
local filesystem options. Opening requests for new features as bugs isn't going
to be acceptable after the beta 2 release.
Would you please elaborate on the local filesystem options? I think the
following is the documentation for saving a dump to a local filesystem, but it
seems not to say that the partition must be specified as the block device file only.
# <fs type> <partition> - will mount -t <fs type> <partition> /mnt and copy
added in -90.el5
kexec-tools-1.101-164.el5 included in 20070208.0.