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 663303

Summary:	Scp copy huge vmcore of netdump
Product:	Red Hat Enterprise Linux 4	Reporter:	Chao Ye <cye>
Component:	netdump	Assignee:	Neil Horman <nhorman>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
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:
Clones:	663305 663310 (view as bug list)		Environment:
Last Closed:	2010-12-15 11:56:56 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:
Bug Blocks:	663305, 663310

Description Chao Ye 2010-12-15 10:39:47 UTC

Description of problem:
When I tried to copy vmcore from netdump-server to netdump-client, I encountered a weird problem:
[root@pogolinux-2 ~]# ls -lsh /var/crash/10.16.65.30-2010-12-14-22\:09/
total 29G
76K -rw-------  1 netdump netdump  67K Dec 14 22:55 log
16G -rw-------  1 netdump netdump 260G Dec 14 22:55 vmcore
The vmcore takes 16G, but scp tried to copy 260G. In our network condition, it'll take more than 30hours!!!

Version-Release number of selected component (if applicable):
kernel-2.6.9-92.EL
netdump-0.7.16-15
netdump-server-0.7.16-15

How reproducible:
100%

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


Expected results:


Additional info:

Comment 1 Neil Horman 2010-12-15 11:52:39 UTC

*** Bug 663305 has been marked as a duplicate of this bug. ***

Comment 2 Neil Horman 2010-12-15 11:56:56 UTC

What makes you think this has anything to do with netdump?  netdump creates sparse files on disk, as you would hope since not many systems can store lots of 260G files.  16G is the on disk allocation, but 260G is the actual file size if all the zero pages were allocated.  At most scp likely has a problem moving sparse files around.