Bug 84134 - NFS locks not released when client side application dies.
Summary: NFS locks not released when client side application dies.
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2003-02-12 17:42 UTC by Robert Jones
Modified: 2007-11-30 22:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-02 04:30:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:433 0 normal SHIPPED_LIVE Updated kernel packages available for Red Hat Enterprise Linux 3 Update 3 2004-09-02 04:00:00 UTC

Description Robert Jones 2003-02-12 17:42:17 UTC
Description of problem: When an application dies unexpectedly while holding a 
file lock on an NFS mounted filesystem, the nfs-utils doesn't clean up the NFS 

Version-Release number of selected component (if applicable): nfs-utils-0.3.3-

How reproducible: Every time.

Steps to Reproduce:
1. Run an application that writes data to an NFS mounted drive.
2. Terminate the application with a kill -9
Actual results: The there are still read and write locks on the file belonging 
to the dead processes' PID.

Expected results: There would be no locks held.

Additional info:

Comment 1 Maxim Bunin 2003-07-24 13:28:14 UTC
I noticed the same problem on  hp-ux based nfs server and linux based nfs clients

Comment 2 Ernie Petrides 2004-05-04 00:09:37 UTC
Targeting this for RHEL3 U3, changing component to kernel.  -ernie

Comment 3 Ernie Petrides 2004-05-04 04:11:40 UTC
A fix for this problem has just been committed to the RHEL3 U3
patch pool (in kernel version 2.4.21-15.1.EL).

Comment 4 John Flanagan 2004-09-02 04:30:31 UTC
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.