Are you on a x86-64 machine? (I'm on Centos 4.1, though updated)
If I run anything above 1.38.0, my jobs will eventually run the system out of
RAM, and the system won't be able to start more processes:
31-Mar 11:30 duct-dir: bedlam.cse.2006-03-31_04.05.46 Error: open mail pipe
/export/bacula/s
On Tue, 11 Apr 2006, Eric Warnke wrote:
What you are seeing appears to be normal block device caching under
the linux kernel and nothing to worry about.
To explain:
buffers = i/o (disk) write buffers
cache = i/o (disk) read cache
These are dynamic. Linux works on the principle that if the m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've noticed when running 2.6, the machine appears to want to use all of
the RAM. However, running more processes will not make it swap until it
would have otherwise begun swapping. Seems to handle the memory usage
pretty well, IMO.
_ _ _ _ __
What you are seeing appears to be normal block device caching under
the linux kernel and nothing to worry about.
Cheers,
Eric
On 4/11/06, Aaron Zschau <[EMAIL PROTECTED]> wrote:
> I'm noticing extremely heavy memory loads when running a large bacula
> job. The system running the fd and director
I'm noticing extremely heavy memory loads when running a large bacula
job. The system running the fd and director processes spikes to
using all but about 18mb of the 5gb of memory installed. If I sort
by memory usage in Top, no processes are using anywhere near the
missing memory, howeve
