Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 153957 - diskdump partition got re-initilized during machine boot up if /var/crash does not have enough space to store vmcore
diskdump partition got re-initilized during machine boot up if /var/crash doe...
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: diskdumputils (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Akira Imamura
Depends On:
  Show dependency treegraph
Reported: 2005-04-05 22:01 EDT by Shu-Chih Lin
Modified: 2007-11-30 17:07 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-06 20:10:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Shu-Chih Lin 2005-04-05 22:01:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
diskdump partition got re-initilized during machine boot up if /var/crash does not have enough space to store vmcore. As a result, the most recent kernel coredump stored in the diskdump partition is lost.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Symbolic link /var/crash to a file system with less than 100MB free space
2. Cause the kernel to panic (e.g. insmod ./crash.o as illustrated in
3. After the incore image has been dumped to pre-defined diskdump partition, 
   restart the machine.   

Actual Results:  During bootup, error message would indicate not enough
space has been detected in /var/crash and yet the diskdump partition still got re-initialized right afterwards

Expected Results:  If /var/crash does not have enough space, it should report error and skip the re-initialization step. This way, system administrator can clean up /var/crash and use "savecore" to save vmcore into /var/crash afterwards. Or else, the core from the most recent kernel panic is lost forever.

Additional info:
Comment 1 Akira Imamura 2005-04-06 15:03:22 EDT
This is not a bug. This is a deliberate action that device is reformatted even 
if savecore fails. This means that diskdump is always available because 
diskdump formats a device when diskdump starts. Please use a script file 
called diskdump-nospace in order to avoid the problem mentioned above.
A description of diskdump-nospace is here:
The script file itself is here:
The usage is shown in the above script file. diskdump-nospace can clean 
up "/var/crash" by customizing.


Note You need to log in before you can comment on or make changes to this bug.