Bug 593132

Summary:	Not all hugepages are released on database shutdown
Product:	Red Hat Enterprise Linux 5	Reporter:	Bill Braswell <bbraswel>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.4	CC:	bturner, csieh, dmair, lwoodman, tao
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-12-03 16:47:40 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:

Description Bill Braswell 2010-05-17 21:48:11 UTC

Several customers are experiencing a similar problem.  When shutting down a database engine, not all of shared memory is released when hugepages are in use.  This is occurring on systems running Oracle and Sybase as well as on RHEL 5.3 and 5.4.

The amount lost varies from system to system.  But the loss is consistent on each system.  In other words, if the loss is 1 gigabyte, it will always be 1 gigabyte on that system.  Each time the database is started and later stopped, more memory is leaked until there is not enough available to start the database.

The ipcs command shows the shared memory segment as having been released after the database shutdown is complete, but the HugePages_Free field in /proc/meminfo does not show all the memory having been released.

Attempting to manually force the pages to be released by echoing 0 into /proc/sys/vm/nr_hugepages does not seem to have any effect on this issue.

This is the same problem as bz593131 but on 5.4.

Comment 8 Larry Woodman 2010-12-03 16:47:40 UTC


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