Red Hat Bugzilla – Bug 239406
savecore will not use reserved space
Last modified: 2010-10-22 10:49:50 EDT
Description of problem:
In calculating the amount of disk space for a dump, savecore uses the f_bavail
field from statfs. Since this does not include reserved blocks a savecore can
fail despite there being sufficient space in the dump file system.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure a /var/crash filesystem that is just large enough to contain system RAM
2. Perform a crash, e.g. sysrq-c
3. Wait for reboot to save core
"no space for dump image."
Dump copies succesfuly
Created attachment 154321 [details]
patch to make diskdumputils use f_bfree when checking space
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
I've already fixed the bug. The fix is included in diskdumputils-1.3.49. However
it is different from the proposed patch on comment #1.
MODIFIED -- CVS Tag: diskdumputils-1_4_0-1
The diskdumputils package has been re-spun -- CVS Tag: diskdumputils-1_4_1-1
Please post QA results here. I will transfer the test results
to the errata's QA report, and then set this bugzilla to VERIFIED
via the errata interface.
I've done testing. There's no regression and unfixed bug as for
this BZ. So could you please file the errata for me?
This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time. This request will be
reviewed for a future Red Hat Enterprise Linux release.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.