Description of problem:
The kdump seems to complete properly but the vmcore created by kdump
is incomplete (the file name is vmcore-incomplete). I think the cause of
this problem is that file caches won't be written to the disk before kdump
reboots system. The kdump can create the vmcore completely by running
"umount" before running "reboot".
Version-Release number of selected component (if applicable):
This problem occurs easier in the case that the reserved
memory for 2nd kernel is larger.
Steps to Reproduce:
1. Run "service kdump start".
2. Make system panic.
3. See a created vmcore file after rebooting.
-r-------- 1 root root 15943680000 Nov 13 20:51 vmcore-incomplete
-r-------- 1 root 0 16341865252 Nov 13 20:51 vmcore
Created attachment 141162 [details]
This patch is based on -131.el5 and can fix this problem.
you're patch is wrong, you still need that unmount in case something goes wrong
during the copy. you don't want to leave a filesystem mounted if you switchroot
to the rootfs to run init.
I'll fix this and the nfs case shortly.
fixed in -132.el5. thanks