Help regarding renaming of vmcore-incomplete to vmcore

[Atsushi Kumagai]

>I can't find this file in my system? Can you help me with it?

In the first place, I don't know how you got core dump and what
kind of environment you tested with, so it's difficult to give
pointed advice.

If you explain what you did in order from first in detail,
I could be of your help.

Thanks,
Atsushi Kumagai

>On 8 May 2017 at 07:11, Atsushi Kumagai <ats-kumagai at wm.jp.nec.com> wrote:
>> Hello,
>>
>>>Hi I am a university student, and have made some changes to
>>>makedumpfile to produce a gzipped output of core dump. The issue I'm
>>>facing is that the output i get from makedumpfile (after it completes
>>>successfully) is vmcore-incomplete.gzip.
>>>
>>>But this file is not being renamed to vmcore.gzip (even thought the
>>>dump the complete as I verified it by loading into CRASH utility). Can
>>>someone please point out to me the changes I should make to solve this
>>>bug (or  can point to the code where this renaming is done).
>>
>> makedumpfile doesn't have such renaming mechanism, it just name the dump
>> as user specify. I guess "vmcore-incomplete" you said is came from kexec-tools.
>> For example, kexec-tools of RHEL7 generate the code below for dump-capture kernel:
>>
>>    110     echo "kdump: saving vmcore"
>>    111     $CORE_COLLECTOR /proc/vmcore $_mp/$KDUMP_PATH/$HOST_IP-$DATEDIR/vmcore-incomplete || return 1
>>    112     mv $_mp/$KDUMP_PATH/$HOST_IP-$DATEDIR/vmcore-incomplete $_mp/$KDUMP_PATH/$HOST_IP-$DATEDIR/vmcore
>>    113     sync
>>
>> $CORE_COLLECTOR is makedumpfile, so the code generate "vmcore-incomplete"
>> by makedumpfile and rename it to vmcore by mv.
>> If you want "vmcore.gzip", you should just specify vmcore.gzip for
>> makedumpfile.
>>
>>
>> Thanks,
>> Atsushi Kumagai
>>
>
>_______________________________________________
>kexec mailing list
>kexec at lists.infradead.org
>http://lists.infradead.org/mailman/listinfo/kexec