Red Hat Bugzilla – Bug 156010
[RHEL4-U2] Diskdump - swap partition support
Last modified: 2013-07-03 09:25:18 EDT
1. Feature Name: Diskdump - swap partition support as dump device
Architectures (mark all that apply)
x 32-bit x86
x 64-bit Itanium2
x 64-bit AMD64/Intel EM64T
x 64-bit IBM POWER
31-bit IBM S/390
64-bit IBM zSeries
External links: Diskdump
Priority (H,M,L): Medium
Target Releases: RHEL4-U2 Beta
Target Release Date:
Drivers or hardware dependency: None
Target Kernel: RHEL4-U2 Beta Kernel
PM ACK for U2.
eng mgt ack for inclusion on canfix list for u2, not the mustfix list.
also I agree w/ QA that there is also the expectation that Fujitsu has an
accompanying testplan and intend to perform that testing. Note the above status
indicates this is questionable whether it will be completed in U2 or whether it
will realistically have to wait till U3 for delivery.
Also note, that this level of change must be completed by June 20th. Reason
being we can't take in large features late in the cycle.
How complete is the prototype?
The kernel part is almost complete and works with no problem.
The userland part has just made and has rouge edges It needs more
internal test and review.
(2005-06-17) The patch is posted to rhkernel-list.
I tested the U2 kernel on our machined and confirmed this feature works without
I see problems.
Did you actually have data written out in your swap partition before causing the
crash? In my testing, this will fail - the crash won't happen because the
diskdump signature gets overwritten when data is swapped out.
Apparently the problem was that I followed the instructions in the README,
rather than just adding my swap device to the /etc/sysconfig/diskdump file and
starting the diskdump service. Looks to be working fine now.
I will update the README and it will be in the next update of diskdumputils
package. Thank you for the feedback.
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.