Red Hat Bugzilla – Bug 245731
diskdump documentation confusing for shared swap/dump devices
Last modified: 2013-08-05 23:49:32 EDT
Description of problem:
The diskdumputils README has a lengthy section on formatting the device for
diskdump use, including the following paragraph:
When you see the above message but want to format them as dump-dedicated
devices, follow the instructions below.
First, disable the swap partition with swappoff, or unmount the partition
with umount. Then, run the command below.
# diskdumpfmt -f <device>
Although this mentions using dump-dedicated devices, it leaves it unclear as to
whether devices that are used for both swapping and dumping should also be
formatted in this way (they shouldn't).
This causes confusion & gives the impression that shared swap/dump devices don't
work when in fact they are fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Read /usr/share/doc/diskdumputils-1.3.25/README
No exact steps for configuring shared devices are present, nor is there a clear
comment that the diskdumpfmt step is not needed in this case.
Clear instructions for either case.
Created attachment 157883 [details]
patch clarifying swap usage & fixing typo (swappoff)
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
Thanks for your patch. I reviewed it and it looks good. I'll include this patch
into new diskdumputils package.
MODIFIED: CVS Tag: diskdumputils-1_4_1-5
Packages can be found here:
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 therefore 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.