Dump is saved in /var/crash even if a different location is specified in the environment booted from FC-SAN device
Issue
- In the environment booted from FC-SAN device, even if the location where dump is saved to FC-SAN disk is specified in
/etc/kdump.conf, dump is saved in/var/crash. - This problem seems to occur because the order that recognizes the device of FC-SAN is different on usual kernel and kernel for kdump.
- In a case of a customer, all devices including FC-SAN are detected on normal kernel as follows:
/dev/sda - FC-SAN logical disk
/dev/sdb - FC-SAN logical disk
/dev/sdc - Onboard disk - Those are also detected on kdump kernel in different order:
/dev/sda - Onboard disk
/dev/sdb - FC-SAN logical disk
/dev/sdc - FC-SAN logical disk
Environment
- Red Hat Enterprise Linux 5.3
- kernel-2.6.18-128.el5
- kexec-tools-1.102pre-56.el5 or later version
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
