Red Hat Bugzilla – Bug 857282
improve the warning message for dump target remain size checking
Last modified: 2015-02-08 16:38:33 EST
Description of problem:
Copying from email content:
> > Hi have the customer using the following methodogy for kdump. Is this a best practice method? and what about the error he is seeing. What is our best practice in collection of kdumps, and also helpful to GSS when a customer interacts with support?
> > "I have kdump enabled in the RHEL 6 Server build. I’ve added the following entry crashkernel=128M into the grub.conf file. I have the default entry core_collector makedumpfile -c --message-level 1 -d 31 in /etc/kdump.conf. I have /var/crash as the default target, with approximately 3.6 GB free. However, on the first reboot the kdump service says “There is not enough space to save a vmcore”. Yet, when I force a crash, the core dump is 45MB. Is it safe to ignore the 1-time message? "
In rhel7 we changed to warning to below:
"There might not be enough space to save a vmcore."
If user use core_collector such as 'cp' the original warning is right.
But for core_collector such as 'makedumpfile' which will compress and
exclude useless pages. This might be not right. We can not guarantee the
captured vmcore size is always small enough because this depends on the
1st kernel memory usage.
Change rhel6 warning to 'might not be' as what we do in rhel7 is better
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 616341 [details]
improve warning message for remain size checking
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.