https://bugzilla.novell.com/show_bug.cgi?id=335486 User michael.d.taylor@exgate.tek.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335486#c93 --- Comment #93 from Michael Taylor <michael.d.taylor@exgate.tek.com> 2009-01-09 10:56:20 MST --- Hi Marius, Thank you for your work on this issue, and finding the tmpfs root cause. Since creating this bug, I have moved my Oracle machines to use HugePages, which are incompatible with the tmpfs construct, so you can close the bug. Here is the Oracle note. I have removed the parameter that made use of /tmpfs and my network interfaces are now working. Thanks, -Michael Subject: MEMORY_TARGET/MEMORY_MAX_TARGET And Linux Hugepages Doc ID: 473165.1 Type: HOWTO Modified Date : 26-MAY-2008 Status: MODERATED In this Document Goal Solution This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review. Applies to: Oracle Server - Enterprise Edition - Version: 11.1.0.6 Linux x86 Goal Using MEMORY_TARGET/MEMORY_MAX_TARGET for managing memory in an 11g database on Linux. When trying to check if Hugpages are being used by running the command (grep Huge /proc/meminfo), can see that Hugepages are not being used. But, When using SGA_MAX_SIZE to manage the memory in the same database, can see by using the same command (grep Huge /proc/meminfo) that Hugepages are being used. Does MEMORY_TARGET/MEMORY_MAX_TARGET make use of Linux Hugepages? Solution Automatic Memory Management (MEMORY_TARGET/MEMORY_MAX_TARGET) cannot be used in conjunction with Hugepages on Linux. This is because its memory segments are memory mapped files in /dev/shm. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.