Red Hat Bugzilla – Bug 175207
[RHEL4 U3] A whole device cannot be 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:
Whole device (i.e. a disk device that is not partitioned) cannot be registered as a diskdump-dedicated device.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Edit /etc/sysconfig/diskdump to register whole device (e.g. /dev/sda or /dev/sdb) as a dump device.
2. Run "service diskdump restart"
3. Run "service diskdump status"
Actual Results: A message "diskdump not enabled" is shown.
diskdump service is not ready to dump memory.
Expected Results: A message "diskdump enabled" is shown.
diskdump service is ready to dump memory.
*** Bug 175192 has been marked as a duplicate of this bug. ***
This is not a regression but just a bug. So I change the summary.
A whole device cannot be configured for diksdump on the earliest
kernel-2.6.9-x. However, there is a workaround for this problem.
A partitioned disk device can be used as well as a whole device.
diskdump's users only partition a disk device with fdisk and
the like even if they need to use a whole device as a dump device.
I plan to include this fix in the next release because
this problem has an impact upon other little, and also
requires a lot of testing. However, I need to update
the README file that is included in diskdumputils so that
users can know that a whole device cannot be configured
for diskdump on RHEL4.
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.
Product Management has reviewed and declined this request. You may appeal this
decision by reopening this request.