Bug 1403780

Summary:	Incorrect incrementation of volinfo refcnt during volume start
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	glusterd	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bsrirama, bugs, rhs-bugs, storage-qa-internal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1403770
Clones:	1404104 1404105 (view as bug list)		Environment:
Last Closed:	2017-03-06 17:39:10 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:	1403770
Bug Blocks:	1404104, 1404105

Comment 1 Worker Ant 2016-12-12 11:20:52 UTC

REVIEW: http://review.gluster.org/16108 (glusterd: Do not increment refcnt of volinfo on every start) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Worker Ant 2016-12-13 05:08:30 UTC

REVIEW: http://review.gluster.org/16108 (glusterd: Handle volinfo->refcnt properly during volume start command) posted (#2) for review on master by Avra Sengupta (asengupt)

Comment 3 Worker Ant 2016-12-13 05:27:48 UTC

COMMIT: http://review.gluster.org/16108 committed in master by Atin Mukherjee (amukherj) 
------
commit 9b1c9395a397e337e4a0acac55b935cb1ce094b7
Author: Avra Sengupta <asengupt>
Date:   Mon Dec 12 16:41:23 2016 +0530

    glusterd: Handle volinfo->refcnt properly during volume start command
    
    While running the volume start command, the refcnt of the volume is
    incremented. At the end of the command, the refcnt should also be
    decremented. This is currently not the case.
    
    This patch, makes sure the refcnt is also decremented at the end of the
    volume start command.
    
    Change-Id: I017b5039be5948df41dde6bc89d2955d5d18971f
    BUG: 1403780
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/16108
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 4 Shyamsundar 2017-03-06 17:39:10 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.10.0, please open a new bug report.

glusterfs-3.10.0 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-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/