This is the output of free. It IS using it, its not cached.
fudd:/home# free -m
total used free shared buffers cached
Mem: 374 371 3 0 0 28
-/+ buffers/cache: 342 32
Swap: 384 4 380
This is my partition layout aswell:
fudd:/home# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/ide/host2/bus0/target0/lun0/part5
1.4G 157M 1.2G 12% /
/dev/ide/host2/bus0/target0/lun0/part1
15M 7.7M 7.7M 50% /boot
/dev/ide/host2/bus0/target0/lun0/part6
2.4G 1.3G 1.1G 52% /usr
/dev/ide/host2/bus0/target0/lun0/part7
1.9G 98M 1.8G 6% /var
/dev/ide/host2/bus0/target0/lun0/part9
27G 21G 6.2G 78% /home
All but / are xfs partitions.
Dana
On Tue, 15 May 2001, Joshua Baker-LePain wrote:
> On Tue, 15 May 2001 at 1:47pm, Dana Soward wrote
>
> > Is anyone else having memory problems with the CVS kernel? Ive got a
> > server here with 384MB, and its using 325 of it right now. It should be
> > using about 30, tops. It *might* be something to do with debian woody,
> > but i wanna make sure no one else is having XFS issues. Also, i cant seem
>
> Are you sure that all that memory is being used? The 2.4 kernel is very
> aggressive when it comes to cacheing (which is a good thing). What does
> the output of 'free' say?
>
> In general, you *want* all your memory used up. You just don't want
> running processes to be the ones using it all.
>
> --
> Joshua Baker-LePain
> Department of Biomedical Engineering
> Duke University
>
|