Red Hat Bugzilla – Bug 993247
server: fds are not closed even after the file is reopened
Last modified: 2014-04-17 07:45:15 EDT
REVIEW: http://review.gluster.org/5499 (protocol/server: Relax lktable finodelk del_locker check) posted (#1) for review on master by Pranith Kumar Karampuri (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/5499 committed in master by Anand Avati (email@example.com)
Author: Pranith Kumar K <firstname.lastname@example.org>
Date: Mon Aug 5 22:20:19 2013 +0530
protocol/server: Relax lktable finodelk del_locker check
Client xlator issues finodelk using anon-fd when the fd is not
opened on the file. This can also happen between attempts to re-open
the file after client disconnects. It can so happen that lock is taken
using anon-fd and the file is now re-opened and unlock would come with
re-opened fd. This will lead to leak in lk-table entry, which also
holds reference to fd which leads to fd-leak on the brick.
Don't check for fds to be equal for tracking finodelks.
Since inodelk is identified by (gfid, connection, lk-owner)
fd equality is not needed.
Signed-off-by: Pranith Kumar K <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Anand Avati <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report.
glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.