by I've got 6 Linux machines. The RAID file server is 2.0.36. One client is
2.0.36, the other four clients are 2.2.6/7. Each of the 2.2.6/7 clients
periodically complains about the NFS server not responding.
Typically:
messages.4:May 13 18:43:35 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 13 18:43:35 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 13 18:45:24 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 13 19:53:54 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 13 20:36:06 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 13 20:55:02 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 13 20:55:02 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 14 10:32:14 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 14 10:32:14 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 14 12:05:57 gene3 kernel: nfs: server gene0 not
responding, still trying
messages.4:May 14 12:06:00 gene3 kernel: nfs: server gene0 not
responding, still trying
(gene3 = 2.2.6, gene0 = 2.0.36)
The 2.0.36 client has never had a problem.
I'm wondering: is this a problem with 2.2.6/7 as an NFS client, or is
this a problem with 2.0.36 as an NFS server? Before I upgrade the
kernels (either 2.2.6/7 -> 2.2.9) or 2.0.36 -> 2.2.9, I would like to
get some feedback from people that may be aware of patches/fixes/issues
on this matter.
Thanks!
Martin K