Red Hat Bugzilla – Bug 175854
[RHEL4-U3] Checking dump partition fails when a swap partition whose size is less than memory size is configured for diskdump.
Last modified: 2007-11-30 17:07:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.7.12) Gecko/20050919 Firefox/1.0.7
Description of problem:
Checking dump partition fails when a swap partition whose size is
less than memory size is configured for diskdump. A swap partition
as well as a normal dump partition should be configured for diskdump
even if the size of the partition is less than memory size only
when "dump_level" and/or "compress" that are module parameters are
specified as non-zero value. In other words, check_swap_partition()
in diskdump.c should not restrict the size of a swap partition
when partial dump or compressed dump is enabled.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a swap partition whose size is less than memory size.
2. Edit /etc/syscofig/diskdump so as to configure the swap partition as a dump device.
3. Run "service diskdump start" so as to start diskdump service.
4. Run "service diskdump status" so as to check that diskdump is enabled.
5. Panic the system.
Actual Results: Checking dump partition fails.
Expected Results: Checking dump partition succeeds. Then diskdump starts dumping memory.
I've just posted the patch to rhkernel-list.
committed in stream U4 build 34.14. A test kernel with this patch is available
This issue is on Red Hat Engineering's list of planned work items
for the upcoming Red Hat Enterprise Linux 4.4 release. Engineering
resources have been assigned and barring unforeseen circumstances, Red
Hat intends to include this item in the 4.4 release.
We have done testing of this BZ. There are no regressions
and unfixed bugs. So, I change the status to VERIFIED.
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.