Bug 1103636

Summary: glusterfsd crashed when quota was enabled, then disabled and enabled again
Product: [Community] GlusterFS Reporter: Raghavendra G <rgowdapp>
Component: quotaAssignee: Raghavendra G <rgowdapp>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: mainlineCC: bugs, gluster-bugs, mkudlej, nsathyan, rgowdapp, sgraf, ssamanta, ssampat
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.6.0beta1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1095267 Environment:
Last Closed: 2014-11-11 08:33:52 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: 1095267    
Bug Blocks:    

Comment 1 Anand Avati 2014-06-02 08:50:14 UTC
REVIEW: http://review.gluster.org/7876 (features/quota: unref and set priv->rpc_clnt to NULL once disabled.) posted (#4) for review on master by Raghavendra G (rgowdapp)

Comment 2 Anand Avati 2014-06-03 05:59:51 UTC
REVIEW: http://review.gluster.org/7876 (features/quota: unref and set priv->rpc_clnt to NULL once disabled.) posted (#5) for review on master by Raghavendra G (rgowdapp)

Comment 3 Anand Avati 2014-06-05 10:32:27 UTC
COMMIT: http://review.gluster.org/7876 committed in master by Raghavendra G (rgowdapp) 
------
commit a89e35727e3a9a7226c7a16479935b7109b11663
Author: Raghavendra G <rgowdapp>
Date:   Mon May 26 10:35:45 2014 +0530

    features/quota: unref and set priv->rpc_clnt to NULL once disabled.
    
    Change-Id: Ic1a6bc36b26cf31f00644bd674b24daa11745e64
    BUG: 1103636
    Signed-off-by: Raghavendra G <rgowdapp>
    Reviewed-on: http://review.gluster.org/7876
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Gluster Build System <jenkins.com>

Comment 4 Niels de Vos 2014-09-22 12:41:39 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 5 Niels de Vos 2014-11-11 08:33:52 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users