From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 09:35:46 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1BC737B401 for ; Wed, 30 Apr 2003 09:35:46 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC54343F3F for ; Wed, 30 Apr 2003 09:35:45 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h3UGZgJ6072810; Wed, 30 Apr 2003 11:35:42 -0500 (CDT) (envelope-from dan) Date: Wed, 30 Apr 2003 11:35:42 -0500 From: Dan Nelson To: "Sparrevohn, Thomas" Message-ID: <20030430163542.GB90046@dan.emsphone.com> References: <2946E9F05C8DD511A7DC0002A5608CE4BEC3A5@GBCHM201> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2946E9F05C8DD511A7DC0002A5608CE4BEC3A5@GBCHM201> X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: "'freebsd-hackers@freebsd.org'" cc: "'omestre@freeshell.org'" Subject: Re: rpc.lockd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 16:35:47 -0000 In the last episode (Apr 30), Sparrevohn, Thomas said: > After changing my FS to UFS2 yesterday I saw strange behaviour from > rpc.statd and rpc.lockd - The statd process grew to 256MB in size. > There are memory leaks some where in the 5.0-Release with UFS2 that I > did not see with UFS1 - It seems that inactive pages are never > reclaimed and on a 1GB system during a make world I ended up with 8MB > free. rpc.statd is always that size; you probably never noticed it before. It mmaps a 256MB window, but only uses a couple KB of it. http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/admin.html#STATD-MEM-LEAK -- Dan Nelson dnelson@allantgroup.com