From owner-freebsd-questions@FreeBSD.ORG Thu May 29 14:05:05 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF9BB37B401 for ; Thu, 29 May 2003 14:05:05 -0700 (PDT) Received: from freshaire.wiz.com (freshaire.wiz.com [66.143.183.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B21D43F75 for ; Thu, 29 May 2003 14:05:05 -0700 (PDT) (envelope-from marc@wiz.com) Received: from freshaire.wiz.com (localhost [127.0.0.1]) by freshaire.wiz.com (8.12.6/8.12.6) with ESMTP id h4TL543Z021391 for ; Thu, 29 May 2003 16:05:04 -0500 (CDT) (envelope-from marc@freshaire.wiz.com) Received: (from marc@localhost) by freshaire.wiz.com (8.12.6/8.12.6/Submit) id h4TL54eD021390 for freebsd-questions@freebsd.org; Thu, 29 May 2003 16:05:04 -0500 (CDT) Date: Thu, 29 May 2003 16:05:04 -0500 From: Marc Wiz To: FreeBSD Questions Message-ID: <20030529210504.GB19899@freshaire.wiz.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Subject: Re: Improving FreeBSD NFS performance (esp. directory updates) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2003 21:05:06 -0000 On Thu, May 29, 2003 at 04:54:00PM -0400, Tom Limoncelli wrote: > I have a NFS server with (so far) a single NFS client. Things work > fine, however if (on the client) I do an "rm -rf foo" on a large (deep > and wide) directory tree the tty receives "NFS server not > responding"/"NFS server ok" messages. > > I don't think the network is at fault, nor is the server really going > away. I think the client is just impatient. Is there a way to speed > up a large "rm -rf"? I have soft-writes enabled but alas.... Tom, please reproduce the problem but before doing it run the following commands and save the output: On the client: nfsstat -c netstat -m netstat -s On the server: nfsstat -s netstat -m netstat -s Run the rm -rf /foo Rerun the above commands on both the client and server and of course save the output again :-) RTFM-ing for nfsstat I am disappointed that nfsstat does not have -z option for zeroing out the counters. Time to look at the source :-) Marc (who in a former life and now current life is doing NFS support) -- Marc Wiz marc@wiz.com Yes, that really is my last name.