So in the end the recompile of nfs-common didn't fix my issue after all. It took a couple of days and then it happened again. I think my issue might be slightly different. I have multiple clients connecting to the same mount points. The Ubuntu Lucid client loses connectivity to the mount points on the server even when the other clients can still access them. Processing using those mounts go in to the D state. Nothing but a reboot regains access to the mounts.
Right now I am trying out an Ubuntu Mainline Kernel to see if my issue is with Ubuntu patches to the kernel.
So in the end the recompile of nfs-common didn't fix my issue after all. It took a couple of days and then it happened again. I think my issue might be slightly different. I have multiple clients connecting to the same mount points. The Ubuntu Lucid client loses connectivity to the mount points on the server even when the other clients can still access them. Processing using those mounts go in to the D state. Nothing but a reboot regains access to the mounts.
Right now I am trying out an Ubuntu Mainline Kernel to see if my issue is with Ubuntu patches to the kernel.
Specifically: 2.6.37- 999-generic_ 2.6.37- 999.20101208113 4_amd64. deb 2.6.37- 999-generic_ 2.6.37- 999.20101208113 4_amd64. deb 2.6.37- 999_2.6. 37-999. 201012081134_ all.deb
linux-image-
linux-headers-
linux-headers-
https:/ /wiki.ubuntu. com/Kernel/ MainlineBuilds
Wondering if I should be testing with http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v2.6.34- lucid/ instead of http:// kernel. ubuntu. com/~kernel- ppa/mainline/ daily/current/