>     0 12106 12099  28  -1  0   448  904 nfsrcv I    ??    0:29.76 find / ( ! -f
>   100 14266   553  32  60  0   140  252 -      R+   p3    0:00.38 grep nfs 
>   100  7491     1   0   2  0    88   60 nfscn2 D    p6-   0:47.85 df -k . 
> 
> nfs server aragorn:/usr/projects: not responding
> 
> goldberry (the client) runs 1.4.3A, aragorn (the server) runs 1.5.3.
> (they are pmax and i386, resp.)
> 
> aragorn needed to be rebooted to test some kernels while mounts from
> goldberry were still active.  I have recovered successfully from this
> before, but this time I'm stuck... how do I unwedged the client (besides
> rebooting)?

If you don't want to reboot, wait for the RPC calls to time out
(something like half-an-hour?).  To avoid this, make sure you mount
remount file systems with the interruptible flag (man mount_nfs), 
so the RPC call can be interrupted with a ctrl-c.  Even better,
use the automounter to control your NFS mounts, so that there's 
less chance of the client having the remote file system mounted
when the server goes down.

> 
> every time I think NFS is OK, it does something to remind me of its
> suckage.  ;)

Well, NFS can be great convenience.  But that convenience doesn't
come for free.

David S.


>