From: Willy Tarreau <w@1wt.eu>
To: Neil Brown <neilb@suse.de>
Cc: Xin Zhao <uszhaoxin@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: What's the NFS OOM problem?
Date: Fri, 11 Aug 2006 05:57:56 +0200 [thread overview]
Message-ID: <20060811035756.GB1261@1wt.eu> (raw)
In-Reply-To: <17627.53340.43470.60811@cse.unsw.edu.au>
On Fri, Aug 11, 2006 at 10:33:32AM +1000, Neil Brown wrote:
> On Thursday August 10, w@1wt.eu wrote:
> >
> > > Can someone help me and give me a brief description on OOM issue?
> >
> > I don't know about any OOM issue related to NFS. At most it might happen
> > on the client (eg: stating firefox from an NFS root) which might not have
> > enough memory for new network buffers, but I don't even know if it's
> > possible at all.
>
> We've had reports of OOM problems with NFS at SuSE.
> The common factors seem to be lots of memory (6G+) and very large
> files.
Just out of curiosity, does it happen on 32bit or 64bit machines (or both) ?
> Tuning down /proc/sys/vm/dirty_*ratio seems to avoid the problem,
> but I'm not very close to understanding what the real problem is.
The most important is to be aware of it ;-)
> NeilBrown
Thanks for the info,
Willy
next prev parent reply other threads:[~2006-08-11 4:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 22:24 What's the NFS OOM problem? Xin Zhao
2006-08-09 2:33 ` H. Peter Anvin
2006-08-10 4:57 ` Willy Tarreau
2006-08-10 21:53 ` Grant Coady
2006-08-11 0:33 ` Neil Brown
2006-08-11 3:57 ` Willy Tarreau [this message]
2006-08-11 4:24 ` Neil Brown
2006-08-11 8:48 ` Peter Zijlstra
2006-08-14 2:03 ` Neil Brown
2006-08-15 18:24 ` Roger Heflin
2006-08-17 5:04 ` Neil Brown
2006-08-17 13:29 ` Roger Heflin
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=20060811035756.GB1261@1wt.eu \
--to=w@1wt.eu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=uszhaoxin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).