Sounds like RPC is working fine for you, otherwise NIS would have problems. Two thoughts, from when I've seen this in the past, for you:
1) Make sure you are using NFSv2. Linux NFSv3 is still fairly buggy.
2) Explicity define your read and write sizes. You might want to spec the retransmit as well, for now try adding the following client side mount options and see if things get better, if not tune the size alittle. Also don't use the intr option. use the options like this: mount -o rsize=8192,wsize=8192 server:/mount/point /localmount
If these don't work for you, then sorry to say, it's a networking issue. Double check your NIC settings on the Linux client to make sure you are full duplex 100, if that's what your Filer is using. Use the linux tool "mii-tool" to check. Using "mii-tool -v" you can see what the current state is, and then use the tool again to force.
If you exhast these, let me know. But one of the above should fix the problem.
benr.
On Mon, Mar 10, 2003 at 02:25:51PM -0800, Premanshu Jain wrote:
A few RedHat 7.2 nfs clients mounting a F840 volume via automount error out with the following. I have looked into everyting including NIS timeouts, filer sysstat, network performance and everything looks to be fine. Intrestingly all the other non linux Clients accessing the same auto-mount are working perfectly.
Mar 9 06:35:12 linuxclient kernel: nfs: server filer OK Mar 9 06:35:13 linuxclient last message repeated 52 times Mar 9 06:35:31 linuxclient kernel: nfs: server filer not responding, still trying Mar 9 06:35:41 linuxclient kernel: nfs: server filer OK Mar 9 06:35:54 linuxclient kernel: nfs: server filer not responding, still trying Mar 9 06:36:34 linuxclient kernel: nfs: server filer OK Mar 9 06:36:46 linuxclient kernel: nfs: server filer not responding, still trying Mar 9 06:38:36 linuxclient kernel: nfs: task 41929 can't get a request slot Mar 9 06:38:41 linuxclient kernel: nfs: task 43328 can't get a request slot