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): kexec-tools-1.101-88.1 How reproducible: Always. Steps to Reproduce: 1. add 'ext3 LABEL=/1' to /etc/kdump.conf 2. execute kdump 3. Actual results: kdump fails to save vmcore to the dump partition. Expected results: kdump succeeds to save vmcore to the dump partition which is specified in /etc/kdump.conf. Additional info: Appended patch fixes the problem.
Created attachment 138155 [details] mkdumprd.diff
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 /proc/vmcore to # /mnt/var/crash/%DATE/
added in -90.el5
kexec-tools-1.101-164.el5 included in 20070208.0.