From: Neil Brown <neilb@suse.de>
To: Willy Tarreau <w@1wt.eu>
Date: Fri, 11 Aug 2006 10:33:32 +1000
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17627.53340.43470.60811@cse.unsw.edu.au>
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?
In-Reply-To: message from Willy Tarreau on Thursday August 10
References: <4ae3c140608081524u4666fb7x741734908c35cfe6@mail.gmail.com>
	<20060810045711.GI8776@1wt.eu>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 871
Lines: 21

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. 
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.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/