From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: What's the NFS OOM problem? Date: Fri, 11 Aug 2006 10:33:32 +1000 Message-ID: <17627.53340.43470.60811@cse.unsw.edu.au> References: <4ae3c140608081524u4666fb7x741734908c35cfe6@mail.gmail.com> <20060810045711.GI8776@1wt.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Xin Zhao , linux-kernel , linux-fsdevel@vger.kernel.org Return-path: Received: from mx1.suse.de ([195.135.220.2]:52682 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S932336AbWHKAdi (ORCPT ); Thu, 10 Aug 2006 20:33:38 -0400 To: Willy Tarreau In-Reply-To: message from Willy Tarreau on Thursday August 10 Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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