Description of problem: Using advisory locking on NFS mounts from a NetApp filer, locks are released cleanly if the process locking the file exits normally. However, if the process aborts, the lock is not reliably removed. Version-Release number of selected component (if applicable): Tested in RH9 and also with AS 2.1 2.4.9-e12 enterprise How reproducible: Code to shoe the problem, and a proposed patch, are available at http://sourceforge.net/mailarchive/forum.php?thread_id=3213117&forum_id=4930 Steps to Reproduce: 1. Run application which uses advisory locking to lock a file from a remote NFS server 2. Kill application 3. Actual results: The record of the file lock is not released. Expected results: The file lock should be released when the process holding the lock exits. Additional info: Additional discussion of this issue: The original report is at http://www.ussg.iu.edu/hypermail/linux/kernel/0312.0/1284.html Further discussion is at http://www.ussg.iu.edu/hypermail/linux/kernel/0312.1/0462.html
I have experienced this same problem running Oracle RAC on RHEL3 Update 4. The database would not restart due to the existence of the stale locks.
We fixed this by starting statd with -n $HOSTNAME while HOSTNAME was set to the simple hostname in /etc/sysconfig/network. For some reason, statd was using the FQDN while the filer wanted to see the simple hostname.
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: http://www.redhat.com/security/updates/errata/ 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.