Red Hat Bugzilla – Bug 119100
NFS statd fails to release locks during cleanup
Last modified: 2007-11-30 17:06:54 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Description of problem:
NFS statd fails to release locks during cleanup when client hostname
differs from the client's nodename. This is because the NLM and NSM
processes are split between kernel and userspace, so the userspace
process can perform a gethostbyname while the kernel space statd cannot.
This is a result of client configuration, but should be considered an
nfs bug as well.
This can be resolved by making the NSM and NLM hostnames match, or by
causing NSM to stop using dns lookup.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Change hostname
2. flock a file over NFS (succeeds)
3. reboot system
4. try to flock file again (fails)
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.