Red Hat Bugzilla – Bug 162901
FEAT:[RHEL3-U7] diskdumputils - preservation of dump partition
Last modified: 2010-10-21 23:08:43 EDT
Escalated to Bugzilla from IssueTracker
The justification has been already described, but I show you that as below.
> Many customers hope that diskdump doesn't format a dump partition
> whenever savecore fails because they don't want to lose dump data.
FYI, this feature has been originally requested by Fujitsu as RHEL3-U6 feature.
But the target to be included in has been changed to U7 because I could not make
it before U6 deadline.
Since this feature would be implemented during the post-crash-reboot
"savecore" phase, I wouldn't think that it would require any
changes to the kernel portion of the diskump facility.
Shouldn't the component be set to "diskdumputils"?
(In reply to comment #14)
> Since this feature would be implemented during the post-crash-reboot
> "savecore" phase, I wouldn't think that it would require any
> changes to the kernel portion of the diskump facility.
> Shouldn't the component be set to "diskdumputils"?
Yes, this feature has no relation to the kernel.
Thank you. I fixed it.
All diskdump/diskdumputils bugzillas are assigned/owned by the in-house
Fujitsu team members -- but they cannot read "private" bugzilla entries,
even if they own the bugzilla.
(Don't get me started on how stupid that is...)
So, don't expect any answers to diskdump/diskdumputils bugzillas
if you privatize your comments.
Actually the half of diskdump feature requests for U7(BZ#162777, BZ#170829) are
not issued by Fujitsu. If they are considered to not appropriate for an update
release, we have no objection.
Can you read comment #17? Have they restored your ability to read
QE ACK. Fujitsu will be doing all the testing following the Errata process. Will
do other archs. as well.
Fixed applied in RHEL3 version diskdumputils-1.2.1-1.
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.