From: Neil Horman <nhorman@redhat.com>
To: Gareth Glaccum <verycoldpenguin@hotmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS using too much memory on diskless system
Date: Thu, 24 Feb 2005 08:38:12 -0500 [thread overview]
Message-ID: <421DD8C4.6080702@redhat.com> (raw)
In-Reply-To: <BAY101-F38CA29432DA94D86024AD3BD640@phx.gbl>
Gareth Glaccum wrote:
> Hi,
> I have a diskless system built and am having weird issues with the way
> NFS client is working. I am using SLES 9.0 with the stock kernel
> (2.6.5-7.111-30 I think from memory).
> I have mounted an NFS partition from another machine without any issues.
> However, when I use anything to write to the partition (for example, see
> later) the system uses memory to cache the files as I am mounted over GbE.
> However, the machine is not limiting the memory used at all. In fact, it
> is using so much it is crashing the machine or causing other programs to
> be OOM'd.
>
> To recreate the problem, the following command took the machine out in
> less than 3 seconds dd if=/dev/zero of=/mnt/NFSMOUNT bs=1024k count=4000
> The machine has 4GB of memory and is using around 300Mb for its OS all
> told.
> Is there some way of limiting the NFS cache size like there used to be
> in the 2.4 kernel? (see section B7 of the nfs FAQ I believe)
>
> Any ideas gratefully received,
> Gareth
>
It sounds to me your kernel has some sort of vm bug, but if you want to
shrink page cache usage, you may want to play with the dirty_vm_*
settings in /proc/sys/vm. I'm still getting used to the 2.6 sysctls,
but I believe that those settings allow you to specify when your kernel
decides its under sufficient memory pressure to start moving data back
to disk.
HTH
Neil
> _________________________________________________________________
> It's fast, it's easy and it's free. Get MSN Messenger today!
> http://www.msn.co.uk/messenger
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman@redhat.com
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-02-24 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 12:19 NFS using too much memory on diskless system Gareth Glaccum
2005-02-24 13:17 ` Bill Rugolsky Jr.
2005-02-24 14:07 ` Gareth Glaccum
2005-02-24 13:38 ` Neil Horman [this message]
2005-02-24 14:14 ` Gareth Glaccum
2005-02-24 14:56 ` Neil Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=421DD8C4.6080702@redhat.com \
--to=nhorman@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=verycoldpenguin@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.