From owner-freebsd-hackers Wed May 7 16:10:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA23850 for hackers-outgoing; Wed, 7 May 1997 16:10:06 -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 QAA23809; Wed, 7 May 1997 16:09:58 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id TAA12926; Wed, 7 May 1997 19:08:48 -0400 (EDT) Date: Wed, 7 May 1997 19:08:48 -0400 (EDT) From: Brian Tao To: FREEBSD-STABLE , FREEBSD-HACKERS Subject: NFS service mysteriously stopping on 2.2-RELENG? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The 2.2-970420-RELENG NFS server I put together for a client is humming along quite nicely, now that I've done fiddling with it. However, there is an intermittent problem with the three BSD/OS clients attached to it. One two occasions in the past week, all three clients will "lose" the NFS server. One client is running BSD/OS 2.1 with NFSv2 UDP mounts, and the other two are BSD/OS 3.0 with NFSv3 TCP mounts. In addition to the "nfs server not responding" syslog messages, the TCP clients occasionally log this: May 7 04:14:26 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.4 May 7 05:38:45 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.2 May 7 05:38:45 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.3 May 7 05:38:45 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.1 May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.1 May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.2 May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.3 May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.4 I haven't seen this reported on the BSD/OS 2.1 UDP client yet. Sending a SIGKILL to the nfsd's on the FreeBSD server and restarting them with "nfsd -t -u 8" clears things right up. Unfortunately, I don't have any more information than this at the time, but there is a monitor script taking regular snapshots of the process table, nfsstat and netstat now. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't"