Bug 1011761

Summary:	NFS crashed
Product:	[Community] GlusterFS	Reporter:	santosh pradhan <spradhan>
Component:	nfs	Assignee:	santosh pradhan <spradhan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.4.0	CC:	gluster-bugs, kparthas, rajesh, rhinduja, rhs-bugs, rwheeler, saujain, surs, vagarwal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	959190	Environment:
Last Closed:	2014-04-17 13:14:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	958043, 959190
Bug Blocks:

Comment 1 Anand Avati 2013-09-25 05:57:47 UTC

REVIEW: http://review.gluster.org/5996 (gNFS: avoid double fd unref in opendir) posted (#1) for review on release-3.4 by Santosh Pradhan (spradhan)

Comment 2 Anand Avati 2013-09-25 06:02:30 UTC

REVIEW: http://review.gluster.org/5996 (gNFS: avoid double fd unref in opendir) posted (#2) for review on release-3.4 by Santosh Pradhan (spradhan)

Comment 3 Anand Avati 2013-09-25 06:50:29 UTC

COMMIT: http://review.gluster.org/5996 committed in release-3.4 by Vijay Bellur (vbellur) 
------
commit 22e982e31bc232f3d9597a41f49e715428e010ce
Author: Santosh Kumar Pradhan <spradhan>
Date:   Wed Sep 25 11:24:28 2013 +0530

    gNFS: avoid double fd unref in opendir
    
    Noticed that the fd_unref was called on the fd regardless of the return
    value at nfs3svc_opendir_readdir_cbk(), hence removing an extra unref in
    the negative case in nfs_inode_opendir_cbk, which fixes the spurious
    fd_unref().
    
    Back port of: http://review.gluster.org/4943 (Rajesh Amaravathi)
    
    Change-Id: Ibddf487c7890407d01befedd65eefb10cb9c989f
    BUG: 1011761
    Signed-off-by: Santosh Kumar Pradhan <spradhan>
    Reviewed-on: http://review.gluster.org/5996
    Reviewed-by: Rajesh Joseph <rjoseph>
    Tested-by: Gluster Build System <jenkins.com>

Comment 4 Niels de Vos 2014-04-17 13:14:36 UTC

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.4.3, please reopen this bug report.

glusterfs-3.4.3 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should already be or become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

The fix for this bug likely to be included in all future GlusterFS releases i.e. release > 3.4.3. In the same line the recent release i.e. glusterfs-3.5.0 [3] likely to have the fix. You can verify this by reading the comments in this bug report and checking for comments mentioning "committed in release-3.5".

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/5978
[2] http://news.gmane.org/gmane.comp.file-systems.gluster.user
[3] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137