I have a problem with NFS on a small network. I have a linux server
(RedHat 6.2) and two clients -- one linux (RedHat 6.2) and one windows
98. I'm mounting home directories and more from the linux server to
the linux client. I am also running samba on the linux server.
I've gotten this problem with kernels 2.2.14, 2.2.24, and 2.4.20.
If the windows machine is off, then everything works perfectly. As
soon as the windows machine boots up and gets to the login prompt, any
programs on my linux client that are using the mounted directories
start to hang (between 2 and 20 seconds at a time). The problem goes
away as soon as the windows machine shuts off.
In /var/log/messages, I get messages like this:
Mar 13 11:55:21 localhost kernel: nfs: server jumpany not responding,
Mar 13 11:55:21 localhost kernel: nfs: server jumpany OK
and like this:
Mar 13 10:49:25 localhost kernel: nfs: task 28963 can't get a request slot
Mar 13 10:49:25 localhost kernel: nfs: task 28964 can't get a request slot
Mar 13 10:49:25 localhost kernel: nfs: task 28965 can't get a request slot
This problem occurs even if the windows machine is not being used.
I haven't found any mention of this problem on the net, and the FAQs
don't seem to mention it. I realize it might just be a tuning
problem, but it's so clearly tied to the presence of the Windows
machine on the net that it seems like it might be something else.
I'm not even sure where to start looking for the cause of this. If
it's some kind of network congestion, how do I find out what kind of
traffic, and how much?
Any suggestions are appreciated.