| Re: But why is the RAM gone?! [message #26982 is a reply to message #26664] |
Wed, 06 February 2008 13:25   |
xemul
Messages: 248
Registered: November 2005
|
Senior Member |
|
|
OK, I can imagine two more points of memory leaks.
The 1st is direct page allocations - they can be examined via /proc/buddyinfo file.
The 2nd one is vmalloc - get by cat /proc/meminfo | grep -i vmalloc command.
These are both kernel memory objects, but that would be strange if some driver uses them  .
As the last attempt to understand what is going on is to wait till the free is close to zero, make the echo m > /proc/sysrq-trigger and then get the dmesg messages starting from 'SysRq: Show Memory' line up to the end - this will show us the overall memory state by the time of out-of-memory condition.
Upd: Can you please show us the config you compiled the kernel with.
Upd2:
| Quote: |
Would it be wise to test a precompiled enterprise-kernel (linux-image-2.6.18-ovz-028stab051.1-enterprise debian package) on a 32bit xeon machine (4GB)?
|
For 4Gb of ram regular kernel (smp/up) is more than enough.
| Quote: |
How stable is the 2.6.22-branch? Is it save enough for everyday use?
|
2.6.22 was our development branch. It is no longer supported.
[Updated on: Wed, 06 February 2008 13:31] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
