Hey Premanshu,
There are multitude of things that can cause this
* Very busy "linuxclient"
* Lossy network(do you have a mix 10/100/GigE network)
* Look at your switch and make sure that there are no errors(hardware, fcs etc)
Fixes:
* Switch to tcp on filer for nfs
* Move to RH 7.3 and 2.4.20-ac2 if you can.
What switch are you using and what is the relative position of the linux clients on that switch(same switch, same bridge on the switch etc)
On Mon, 10 Mar 2003, Premanshu Jain wrote:
Date: Mon, 10 Mar 2003 14:25:51 -0800 (PST) From: Premanshu Jain Premanshu.Jain@synopsys.com To: toasters@mathworks.com Subject: Weired Linux error
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
/dev/null
devnull@adc.idt.com