Re: But why is the RAM gone?! [message #26812 is a reply to message #26664] |
Fri, 01 February 2008 10:27 |
xemul
Messages: 248 Registered: November 2005
|
Senior Member |
|
|
Cached pages are included in the "busy" memory reported in /proc/meminfo, thus the "free" value is most often very low. However, beancounters do not account for such pages. The do not account for kernel memory allocated by drivers, disk request and some more as well, so if there's a leak in a driver we cannot definitely detect this.
The easiest way to find (ok - guess) which process consumes too much memory is to launch top and set the sorting by RSS value.
I'd pay more attention to 107 VE, since it shows to consume too many kmemsize and physpages, but if you launch top in ve0 it would be more than enough.
BTW, it would be nice if you also provide the kmemsize and physpapges graphs, not just privvmpages.
However, there can be some memory leak in your scsi (raid) driver. The best we can do now to check this is to run these VEs on different hardware...
Thanks,
Pavel
|
|
|