From owner-freebsd-questions@FreeBSD.ORG Thu May 29 13:54:03 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 13F6F37B404 for ; Thu, 29 May 2003 13:54:03 -0700 (PDT) Received: from exgw2.lumeta.com (exgw2.lumeta.com [65.198.68.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E71943F85 for ; Thu, 29 May 2003 13:54:02 -0700 (PDT) (envelope-from tal@lumeta.com) Received: from lucy.corp.lumeta.com (h65-246-245-10.lumeta.com [65.246.245.10]) by exgw2.lumeta.com (Postfix) with ESMTP id 83492373850 for ; Thu, 29 May 2003 16:54:01 -0400 (EDT) Received: from localhost (localhost.corp.lumeta.com [127.0.0.1]) by lucy.corp.lumeta.com (Postfix) with ESMTP id 6619BA896A for ; Thu, 29 May 2003 16:54:01 -0400 (EDT) Received: from lucy.corp.lumeta.com ([127.0.0.1]) by localhost (lucy.corp.lumeta.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89931-09 for ; Thu, 29 May 2003 16:54:01 -0400 (EDT) Received: from lumeta.com (talmacmm.corp.lumeta.com [65.246.246.66]) by lucy.corp.lumeta.com (Postfix) with ESMTP id 0B1C6A8968 for ; Thu, 29 May 2003 16:54:01 -0400 (EDT) Date: Thu, 29 May 2003 16:54:00 -0400 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Tom Limoncelli To: freebsd-questions@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.552) X-Virus-Scanned: by amavisd-new at lumeta.com Subject: 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 20:54:03 -0000 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.... Details: The server is an Intel Xeon CPU 2.20GHz running FreeBSD 4.8 (updated to the latest RELENG_4_8 release yesterday). It has a 1000TX interface to a Cisco switch. The partition is part of a SCSI RAID unit (160MB/s transfer rate, Tagged Queueing enabled). The partition that is exported to the client is: # mount | egrep e2 /dev/da0s1f on /e2 (ufs, NFS exported, local, soft-updates) /etc/rc.conf lists: nfs_server_flags="-u -t -n 16" The client is a (accoriding to dmesg) "Pentium III/Pentium III Xeon/Celeron (934.99-MHz 686-class CPU)" running FreeBSD 4.7-RELEASE. amd is configured to mount the partion with "opts:=rw:nfs_proto=udp;nfs_vers=3". /etc/rc.conf lists: nfs_client_flags="-n 4" Any tuning suggestions? --tal