Bug 1047955

Summary: glusterd crashed, after initiating 'remove brick start'
Product: [Community] GlusterFS Reporter: Ravishankar N <ravishankar>
Component: glusterdAssignee: Ravishankar N <ravishankar>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: mainlineCC: bugs, gluster-bugs, grajaiya, sasundar, vagarwal, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.6.0beta1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1047747 Environment:
Last Closed: 2014-11-11 08:26:22 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: 1047747    
Bug Blocks:    

Comment 1 Anand Avati 2014-01-02 17:47:27 UTC
REVIEW: http://review.gluster.org/6629 (glusterd: update volinfo->subvol_count in newly added peers) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Anand Avati 2014-01-03 06:13:35 UTC
REVIEW: http://review.gluster.org/6629 (glusterd: update volinfo->subvol_count in newly added peers) posted (#2) for review on master by Ravishankar N (ravishankar)

Comment 3 Anand Avati 2014-01-03 14:22:32 UTC
COMMIT: http://review.gluster.org/6629 committed in master by Vijay Bellur (vbellur) 
------
commit d25d912835e01c40cb00a0ae93d49f68f9b3542b
Author: Ravishankar N <ravishankar>
Date:   Thu Jan 2 23:06:39 2014 +0530

    glusterd: update volinfo->subvol_count in newly added peers
    
    Update the subvol_count when a peer imports information about the friend
    volumes.
    
    Change-Id: Id3884bd5727ff22be7ed87f43a1ec1b5fe34813c
    BUG: 1047955
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: http://review.gluster.org/6629
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Gluster Build System <jenkins.com>

Comment 4 Niels de Vos 2014-09-22 12:34:23 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:26:22 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