Bug 656047

Summary:	fix memory usage calculation in kdump init script
Product:	Red Hat Enterprise Linux 6	Reporter:	Dave Maley <dmaley>
Component:	kexec-tools	Assignee:	Neil Horman <nhorman>
Status:	CLOSED DUPLICATE	QA Contact:	Kernel Dump QE <kernel-dump-qe>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1	CC:	amwang, phan
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-23 11:50:55 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:	608683
Bug Blocks:

Description Dave Maley 2010-11-22 22:34:52 UTC

Description of problem:
the current method to determine KMEMINUSE (slab value from /proc/meminfo) is not accurate and leads to unnecessary warnings during service startup.

The kdump firstboot module uses this same method.  As noted in:
https://bugzilla.redhat.com/show_bug.cgi?id=608683#c10
https://bugzilla.redhat.com/show_bug.cgi?id=608683#c11

..work is already being done to improve the calculation in firstboot.  I'm opening this bug to ensure this same fix is also included in the init script.

note: feel free to close as a duplicate to bug 608683 if deemed appropriate.


Version-Release number of selected component (if applicable):
kexec-tools-2.0.0-145.el6.src.rpm

Comment 2 Neil Horman 2010-11-23 11:50:55 UTC

That measurement is the best we can do at the moment.  its better to estimate conservatively here.  We're planning on improving this for 6.1 with bz 608683

*** This bug has been marked as a duplicate of bug 608683 ***