From owner-freebsd-hackers Sat May 17 14:46:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14463 for hackers-outgoing; Sat, 17 May 1997 14:46:45 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14455 for ; Sat, 17 May 1997 14:46:43 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id RAA12022; Sat, 17 May 1997 17:46:13 -0400 (EDT) Date: Sat, 17 May 1997 17:46:12 -0400 (EDT) From: Brian Tao To: dk+@ua.net cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS service mysteriously stopping on 2.2-RELENG? In-Reply-To: <199705090814.BAA13828@dog.farm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 9 May 1997, Dmitry Kohmanyuk wrote: > > > May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.4 > > From looking at the source, it looks like an error while receiving RPC > from the server... specifically, in /sys/nfs/nfs_socket.c It seems like a lost packet or a timeout could cause this. In my particular case, I found the cause of the NFS server problems, and happily it isn't FreeBSD's fault. :) The nfsd's were restarted manually at some point, and there was a 10-minute CPU limit in effect. The nfsd's were silently dying off one by one, until there weren't enough of them to adequately support the concurrency needed by the clients, and eventually NFS would disappear entirely. I only discovered this when the fellow who went to reboot the hung systems remarked that there were only a couple of nfsd's running at the time. :-/ -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't"