Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 663310

Summary:	Diskdump generated huge vmcore
Product:	Red Hat Enterprise Linux 4	Reporter:	Chao Ye <cye>
Component:	diskdumputils	Assignee:	Linda Wang <lwang>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.9
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	663303	Environment:
Last Closed:	2012-06-20 13:32:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	663303
Bug Blocks:	663305

Description Chao Ye 2010-12-15 10:44:38 UTC

+++ This bug was initially created as a clone of Bug #663303 +++

Description of problem:
I found that same problem exist on diskdump, I checked the vmcore generated by diskdump:
[root@bootp-66-87-235 analyse-crash]# ls -lsh /var/crash/127.0.0.1-2010-12-15-09\:38/
total 134M
134M -rw-------  1 root root 2.0G Dec 15 10:35 vmcore
It takes a long time to save the vmcore.

Version-Release number of selected component (if applicable):
kernel-2.6.9-92.EL
diskdumputils-1.4.1-7

How reproducible:
100%

Steps to Reproduce:
1.Dump vmcore
2.
3.
  
Actual results:

Expected results:

Additional info:

Comment 1 Jiri Pallich 2012-06-20 13:32:35 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.