Subject: i386 nfs locking up
To: None <current-users@NetBSD.ORG>
From: Robert Dobbs <banshee@gabriella.resort.com>
List: current-users
Date: 11/17/1994 02:01:42
Two i386 machines running nfs, one serving to the other.  After I initiate
something like a kernel compile on the NFS mounted /usr/src, its runs for
a long while and then locks up.

On the server side:
Server Info:
  Getattr   Setattr    Lookup  Readlink      Read     Write    Create    Remove
    56199        18     91726        16     31002       102        10         0
   Rename      Link   Symlink     Mkdir     Rmdir   Readdir    Statfs  RdirLook
        0         0         0         0         0     11177        77         0
   GLease    Vacate     Evict
        0         0         0
Server Ret-Failed
            16485
Server Faults
            0
Server Cache Stats:
   Inprog      Idem  Non-idem    Misses
      208      1009         0    189318
Server Lease Stats:
   Leases     PeakL   GLeases
        0         0         0

The Client Side reports nfs server not responding.  When the client is
in this state, anything like "df" or a cd to the nfs file system locks
down that process.
Nov 16 21:18:30 atrium /netbsd: nfs server gabriella:/usr/src: not responding
Nov 16 21:22:57 atrium /netbsd: nfs server gabriella:/usr/src: is alive again
Nov 16 21:28:53 atrium /netbsd: nfs server gabriella:/usr/src: not responding
Nov 16 22:03:05 atrium /netbsd: nfs server gabriella:/usr/src: is alive again
Nov 16 22:36:48 atrium /netbsd: nfs server gabriella:/usr/src: not responding
Nov 16 22:37:09 atrium /netbsd: nfs server gabriella:/usr/src: not responding
Nov 16 22:37:50 atrium /netbsd: nfs server gabriella:/usr/src: not responding
Nov 16 23:15:21 atrium /netbsd: nfs server gabriella:/usr/src: is alive again
Nov 16 23:15:21 atrium last message repeated 2 times
Nov 16 23:16:46 atrium /netbsd: nfs server gabriella:/usr/src: not responding

I'd appreciate email off of this alias regarding NFS if you've been using
it.  I plan to move things to our sgi and mount a file system from there
and see if I can't isolate the problem to the client side.

-john