Red Hat Bugzilla – Bug 795804
[RFE] Add NFSv4 support to kdump
Last modified: 2013-09-29 22:30:21 EDT
Description of problem:
When using kdump, the network destinations can only be NFSv3 or SSH with shell access.
The NFSv3 only destination requires extra network configuration to enable portmapping, compared to NFSv4. Adding this option would ease configuration and maintenance.
The SSH option launches remote commands, like mktemp, to perform the dump. The destination service cannot be restricted to SFTP or SCP only (and sometimes cannot be a different unix-like system, as happened with HP/UX).
Version-Release number of selected component (if applicable):
Enable a remote system with NFSv4 only or SFTP only. Configure a local system to use that destination for kdump. Force a panic in the local system to make it try to dump in the remote system.
Steps to Reproduce:
1.Enable a remote system with NFSv4 only or SFTP only.
2.Configure a local system to use that destination for kdump.
3.Force a panic in the local system to make it try to dump in the remote system.
No dump is stored in the remote system.
Dump is stored in the remote system.
I'd suggest keeping "net" option in the kdump.conf file for backwards compatibility, and adding "nfs3", "nfs4", "ssh" and "sftp". In my dreams I even would include "rsync" (without ssh, pure rsync) :-D
Created attachment 566220 [details]
Created attachment 566238 [details]
Rename "nfs3" to "nfs", to sync with the names in "mount".
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.