Bug 1399916

Summary:	[SAMBA-CIFS] : IO hungs in cifs mount while graph switch on & off
Product:	[Community] GlusterFS	Reporter:	rjoseph
Component:	libgfapi	Assignee:	rjoseph
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sudhir D <sdharane>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.9	CC:	bugs, rgowdapp, rhs-smb, rjoseph, sbhaloth, sdharane, vdas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1397754	Environment:
Last Closed:	2017-03-08 10:23:55 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:	1396449, 1397754
Bug Blocks:

Comment 1 Worker Ant 2016-11-30 09:20:58 UTC

REVIEW: http://review.gluster.org/15978 (gfapi: glfs_subvol_done should NOT wait for graph migration.) posted (#1) for review on release-3.9 by Rajesh Joseph (rjoseph)

Comment 2 Worker Ant 2017-01-07 13:58:37 UTC

COMMIT: http://review.gluster.org/15978 committed in release-3.9 by Niels de Vos (ndevos) 
------
commit e5dceb2e43fb1c7268516941950607edbfe3ecb1
Author: Rajesh Joseph <rjoseph>
Date:   Tue Nov 22 22:25:42 2016 +0530

    gfapi: glfs_subvol_done should NOT wait for graph migration.
    
    In graph_setup function glfs_subvol_done is called which
    is executed in an epoll thread. glfs_lock waits on other
    thread to finish graph migration. This can lead to dead lock
    if we consume all the epoll threads.
    
    In general any call-back function executed in epoll thread
    should not call any blocking call which waits on a network
    reply either directly or indirectly, e.g. syncop functions
    should not be called in these threads.
    
    As a fix we should not wait for migration in the call-back path.
    
    > Reviewed-on: http://review.gluster.org/15913
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Smoke: Gluster Build System <jenkins.org>
    > Reviewed-by: Niels de Vos <ndevos>
    > CentOS-regression: Gluster Build System <jenkins.org>
    (cherry picked from commit 17d10b42fc4041442e6cd0bfda45944edea498c6)
    
    Change-Id: If96d0689fe1b4d74631e383048cdc30b01690dc2
    BUG: 1399916
    Signed-off-by: Rajesh Joseph <rjoseph>
    Reviewed-on: http://review.gluster.org/15978
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana>
    Reviewed-by: Niels de Vos <ndevos>

Comment 3 Kaushal 2017-03-08 10:23:55 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.9.1, please open a new bug report.

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

[1] http://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html
[2] https://www.gluster.org/pipermail/gluster-users/