From owner-freebsd-stable Sat Aug 8 11:54:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12563 for freebsd-stable-outgoing; Sat, 8 Aug 1998 11:54:55 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mh2.cts.com (mh2.cts.com [209.68.192.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12556 for ; Sat, 8 Aug 1998 11:54:54 -0700 (PDT) (envelope-from mdavis@io.cts.com) Received: from io.cts.com (io.cts.com [198.68.174.34]) by mh2.cts.com (8.8.7/8.8.5) with ESMTP id LAA03603 for ; Sat, 8 Aug 1998 11:54:32 -0700 (PDT) Received: (from mdavis@localhost) by io.cts.com (8.8.8/8.8.8) id LAA03637 for stable@freebsd.org; Sat, 8 Aug 1998 11:54:32 -0700 (PDT) (envelope-from mdavis) From: Morgan Davis Message-Id: <199808081854.LAA03637@io.cts.com> Subject: tuning nfs To: stable@FreeBSD.ORG Date: Sat, 8 Aug 1998 11:54:31 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where might I find information on tuning NFS for FreeBSD 2.2.7 (other than the man pages)? And what is the news on NFS 3 performance and reliability? I recently read a message here that said NFS 3 is very broken in 2.2.7. True? We have a server that is causing these messages to appear on clients: nfs server nsfserv-i2:/data: not responding nfs server nsfserv-i2:/data: is alive again nfs server nsfserv-i2:/data: not responding nfs server nsfserv-i2:/data: is alive again nfs server nsfserv-i2:/data: not responding nfs server nsfserv-i2:/data: is alive again nfs server nsfserv-i2:/data: not responding nfs server nsfserv-i2:/data: is alive again nfs server nsfserv-i2:/data: not responding nfs server nsfserv-i2:/data: is alive again The pairs ("not responding" and "is alive again") seem to occur in the same second, according to timestamps in /var/log/messages. Is this from having some timeout threshhold set too low, not enough nfsds on the server, not enough nfsiods on the client, a network problem, or what? Is it a real problem or just an annoying diagnostic? Thanks for whatever assistance you can offer. --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message