wangbin wrote:
You said it had 2.5GB of memory, but according to this output
you only have 1GB of memory.

I think the number of dirty pages is high. But except from
that I don't see any symptoms of problems here. You shouldn't
be getting ENOMEM before also the swap space is exhausted.
Does the system ever run low on swap?

Your description sounds like memory leak, but the meminfo
output show no symptoms of a leak. When did you get this
meminfo output? Does it look like this when you in fact have
got ENOMEM?

I have a few hints here:
http://www.daimi.au.dk/~kasperd/comp...q.html#memleak
But I'm not sure how much it will help in your case.

If you want to know about the memory usage of a particular
process take a look in /proc/%d/maps, it will tell you
which part of the address space is anonymous memory
allocations and which are memory mapped files.

Removed mlist.linux.kernel, I don't think it is apropriate.

--
Kasper Dupont -- der bruger for meget tid paa usenet.
For sending spam use mailto:aaarep@daimi.au.dk
/* Would you like fries with that? */

Hi

I'm really sorry. I try to check every box to understand what's the
meaning of the output. So what I post is from another box. The real
one is
total: used: free: shared: buffers: cached:
Mem: 2636136448 2629435392 6701056 1217822720 204898304 877502464
Swap: 4301758464 360468480 3941289984
MemTotal: 2574352 kB
MemFree: 6544 kB
MemShared: 1189280 kB
Buffers: 200096 kB
Cached: 598496 kB
SwapCached: 258440 kB
Active: 1442604 kB
Inact_dirty: 261412 kB
Inact_clean: 542296 kB
Inact_target: 643544 kB
HighTotal: 1703856 kB
HighFree: 2036 kB
LowTotal: 870496 kB
LowFree: 4508 kB
SwapTotal: 4200936 kB
SwapFree: 3848916 kB
BigPagesFree: 0 kB

From database point of view, the performance is ok. From the output of
vmstat, there is no swap.And the swap file is only used by 10%.
r b w swpd free buff cache si so bi bo in cs
us sy id
0 1 0 352000 7004 200604 600944 0 0 1 2 0 0
2 0 2
1 0 0 352000 7004 200608 600944 0 0 116 95 1155 2724
4 1 95
1 0 0 352000 6996 200612 600944 0 0 120 141 1806 4114
6 2 92
0 0 0 352000 7004 200616 600944 0 0 124 129 1454 3358
4 1 94

In http://www.redhat.com/advice/tips/meminfo.html,
"LowFree: The amount of free memory of the low memory region. This is
the memory the kernel can address directly. All kernel datastructures
need to go into low memory."
In http://www.oreilly.com/catalog/spt2/chapter/ch04.html
"Occasionally, however, a system will experience a kernel memory
allocation error. While there is a limit on the size of kernel
memory,[7] the problem is caused by the kernel trying to get memory
when the free list is completely exhausted. Since the kernel cannot
always wait for memory to become available, this can cause operations
to fail rather than be delayed."

So is it possible that the ocfs driver needs more memory, but fail
because of very low in LowFree? However,
http://linuxcompressed.sourceforge.net/vm24/ shows that pages in
inactive_clean can be reused, and the box has a lot in Inact_clean.
"inactive_clean list
* contains clean, old pages
* can be reused by __alloc_pages, like free pages
* pages are not mapped in any process "

I also don't know how would /proc/sys/vm/freepages affect it, because
/proc/sys/vm/freepages affects swap behavior while there is
no swap happening on the box, only paging.

Thanks,
Bin