Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After configure nfs kdump server on rhevh, it created /var/crash/var/crash/ directory on kdump server and saved vmcore file to this directory.
It's better to use /var/crash/ and saved vmcore file to /var/crash/.
Version-Release number of selected component (if applicable):
rhev-hypervisor-6.1-20110506
How reproducible:
Always.
Steps to Reproduce:
1. configure nfs kdump server on rhevh
2. reboot
3. kdump service is starting, echo c> /proc/sysrq-trigger
Actual results:
vmcore file is saved to /var/crash/var/crash/
Expected results:
vmcore file is saved to /var/crash/
this is more a feature of kdump we can't necessarily change, it will put the vmcore under <mountpoint>:/var/crash. To get it just under /var/crash we would need to set kdump to just /. If / isn't exported on the nfs server it will fail. Exporting / over nfs isn't gonna be common if not a security issue, may just need to put a release note in and file a bug to put a hardcoded directory into kdump options.
ok, this is even documented in man kdump.conf:
net <nfs mount>
Will mount fs and copy /proc/vmcore to
<mnt>/var/crash/%HOST-%DATE/, supports DNS. Note that a fqdn
should be used as the server name in the mount point