Date: Thu, 29 May 2003 16:05:04 -0500 From: Marc Wiz <marc@wiz.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Improving FreeBSD NFS performance (esp. directory updates) Message-ID: <20030529210504.GB19899@freshaire.wiz.com> In-Reply-To: <AC6FAEF0-9217-11D7-AA52-000A956888C8@lumeta.com> References: <AC6FAEF0-9217-11D7-AA52-000A956888C8@lumeta.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030529210504.GB19899>