Code:
Nov 30 10:50:36 salmon kernel: [47191.400123] nfs: server 192.168.1.100 not responding, still trying
Nov 30 10:50:38 salmon kernel: [47193.682149] nfs: server 192.168.1.100 OK
Nov 30 10:50:56 salmon kernel: [47211.280408] nfs: server 192.168.1.100 not responding, still trying
Nov 30 10:50:58 salmon kernel: [47213.558906] nfs: server 192.168.1.100 OK
Nov 30 10:51:16 salmon kernel: [47231.150160] nfs: server 192.168.1.100 not responding, still trying
Nov 30 10:51:18 salmon kernel: [47233.428715] nfs: server 192.168.1.100 OK
The title for this post is perhaps wrong -- I suspect this may be a client-side issue.
My NFS client keeps timing out like shown above. It has been working fine for months, up until today. I had a share mounted as "default,udp" so tried removing the udp option. (I mainly use it for streaming content.) The problem persists. nfsstat returns no useful info, nor is there anything suspicious in the server's logs about nfs. On the client, the only thing an rgrep on /var/log returns is what I've included above -- and there are pages and pages of it. No packets are being dropped and the network is otherwise stable. tx/rx over all other protocols has been fine.
What on earth could be wrong? Where do I look next? I thought this happened to other people, but not to me? :-(
