nfs problem ...

[K.C. Chan]

all,
I am getting this nfs error message:

nfs server not responding, timed out
nfs_statfs: statfs error = 5

This may be due to the server having high load, but I do not see this on the nfs server? Any way to narrow down the problem?

Thanks.

[Ivan Ferreira]

You should troubleshoot using nfsstat, showmount, rpcinfo, ping and tcpdump. Also, check the system load on the NFS server.

Is this error just temporal or once it appears you must reboot something?

[Sung Oh]

Hi Chan,

you can use this guide line for narrow down the problem.
http://www.unet.univie.ac.at/aix/aixbman/commadmn/nfs_problem.htm

Regards,
Sung

[K.C. Chan]

Both the server and client is on a gig nic. both have mtu set to 9000. The server runs fedora 4 and the client is redhat 7.x. There are other clients, but they are on fedora and they have no issue with it. Would an mtu of 9000 on the client running redhat 7.x be the cause of the timeout?

[john kingsley]

What mount options are your using?
How man nfsd processes are you starting on the server?

[K.C. Chan]

8 nfsd on the server.

using autofs, the mount options is:
-ro,noatime,intr,soft,rsize=8192,wsize=8192

check proc, it is listed as:
ro,noatime,v3,rsize=8192,wsize=8192,soft,intr,udp,lock,

Any idea? Thanks.

[john kingsley]

Does the filesystem successfully mount on the RH7 client?

On the NFS client side, you could try dropping the rsize & wsize to 1024.

Is everything on the same network switch? It's possible that your nework equipment has an MTU set 1500. Can you try to set the MTUs of your systems back to 1500 to eliminate the MTU as the problem?

[MrMichaelWill]

Chances are that you only have v2 support in the nfs client of rh7.3 but have told your server to only offer v3?

Michael