Now it's time to change the behavior of 'path'. If no target is specified
explicitly in /etc/kdump.conf, the 'path' will be chcked if any separate
file system is mounted on any tier of 'path'. If no mount, vmcore is written
into root file system. If yes, vmcore will be wirtten into the mounted
file system with the left path relative to mountpoint.
Signed-off-by: Baoquan He <bhe(a)redhat.com>
---
kexec-kdump-howto.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt
index 7ffeab9..dcaf7f2 100644
--- a/kexec-kdump-howto.txt
+++ b/kexec-kdump-howto.txt
@@ -377,6 +377,12 @@ example, 'path /data/coredumps' would lead to vmcore files
being written to
that the path option is ingnored if your kdump configuration results in the
core being saved from the initscripts in the root filesystem.
+Note: If a separate file system is mounted on any tier of specified path, and
+no explicit target is specified, kdump will find the mount and writes vmcore
+to the separate file system with the left path. For example, '/var/crash' is
+specified, and a separate disk is mounted on /var. Then vmcore will be written
+into ./crash/%HOST-%DATE of the disk.
+
Kdump Post-Capture Executable
It is possible to specify a custom script or binary you wish to run following
--
1.8.5.3