NFS client issue

Jason Joines support
Fri Jan 26 08:32:16 PST 2007


    I have a bunch of boxes backing themselves up to an NFS server.  One 
of them suddenly stopped working, it can no longer mount the NFS 
export.  Doesn't seem to be an issue with the server as all the other 
clients are still working just fine.

    The failing client is an old SuSE 8.1 box with a 2.4.19 kernel and 
the server is OpenSuSE 10.0 with a 2.6.13 kernel.  The output of the 
failed backup script reports "mount: RPC: Port mapper failure - RPC: 
Timed out".  portmap is running on the client and I've restarted it but 
that didn't help.
    The other clients are all SuSE with versions ranging from 8.0 to 10.0.

    I tried to do the mount manually a few times ( same server but 
different exports and local mount points ) and each resulted in a hung 
mount process.  The int option was used each time but none of the mount 
processes can be killed even those with the soft option.  The mount 
called from the script does not result in a hang, it just fails.  Only 
the manual attempts hang and have now been hung for over 18 hours.

    Using rpcinfo, the client can list the services registered with RPC 
on itself and on the server including portmapper, nfs, and mountd.  I'm 
using TCP.
    During one of the mount attempts I logged all the network traffic 
between the client and the server.  The client contacted portmap on the 
server and got replies, it then contacted mountd on the server and got 
replies.  However, it never sent anything to nfs on the server.

    Any ideas?


Jason Joines
=================================



More information about the Linux-users mailing list