I have seen exactly the same nfs: not responding errors on some of my Solaris Servers. I also examined NFS at a very low level and showed no problems. Then I stumbled upon an article in NOW that explained the error to be harmless, more a nuisance than anything else. The performance of servers showing this error vs those not is virtually identical.

However,I did not observe this error; 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

Are you seeing any performance drops?

Aaron

-----Original Message----- From: Premanshu Jain [mailto:Premanshu.Jain@synopsys.com] Sent: Tuesday, March 11, 2003 9:26 AM 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