© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I am running fully up to date Gutsy server and am getting what I think is the same problem as is reported here. After an indeterminate amount of time and/or activity, the [lockd] process on the server goes from S state to D state and all queries from clients result in messages such as:
Feb 28 07:59:36 balin kernel: [73693.569139] lockd: server dimen not responding, still trying
and hang forever.
I tried stopping and then starting nfs-common and nfs-kernel-server but the [lockd] process remains and in state D. Killing it explicitly has no apparent effect. A new [lockd] process appears in the process table after the restart of nfs-kernel-server but it appears not to be used.
The only remedy appears to be to reboot the server and then it seems all the clients.
It seems that the solution to the problem may now be known, so I guess the question is when will an update to the Gutsy kernel be issued? I guess it goes without saying that it would be good if the kernel issued with Hardy does not have this problem?
Thanks.