REVIEW: http://review.gluster.org/7162 (Glusterd/Remove-brick: Reconfigure the nfs server volfile upon remove-brick start) posted (#2) for review on master by susant palai (spalai)

REVIEW: http://review.gluster.org/7162 (Glusterd/Remove-brick: Reconfigure the nfs server volfile upon remove-brick start) posted (#3) for review on master by susant palai (spalai)

REVIEW: http://review.gluster.org/7162 (Glusterd/Remove-brick: Reconfigure the nfs server volfile upon remove-brick start) posted (#4) for review on master by susant palai (spalai)

REVIEW: http://review.gluster.org/7162 (Glusterd/Remove-brick: Reconfigure the nfs server volfile upon remove-brick start) posted (#5) for review on master by susant palai (spalai)

REVIEW: http://review.gluster.org/7162 (Glusterd/Remove-brick: Reconfigure the nfs server volfile upon remove-brick start) posted (#6) for review on master by susant palai (spalai)

REVIEW: http://review.gluster.org/7162 (Glusterd/Remove-brick: Reconfigure the nfs server volfile upon remove-brick start) posted (#7) for review on master by susant palai (spalai)

COMMIT: http://review.gluster.org/7162 committed in master by Vijay Bellur (vbellur) 
------
commit 53194718bb2aed6b88084cafd9e84a4350663ac6
Author: Susant Palai <spalai>
Date:   Thu Feb 27 06:50:15 2014 +0000

    Glusterd/Remove-brick: Reconfigure the nfs server volfile upon remove-brick start
    
    Problem : For remove-brick start operation  all client volfiles are reconfigured
    except nfs server volfile. Hence, even after layout is fixed by the rebalance
    process, the nfs clients dont see the change and go on creating directories and
    files in the decommissioned brick which leads to data loss after remove-brick
    commit.
    
    Solution : Reconfigure the nfs server volfile for remove-brick start
    
    credit: kaushal
            spalai
    
    Change-Id: Ib8cd8b45a9e1f888d5e00dff65cdf77c1613a2af
    BUG: 1070734
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/7162
    Reviewed-by: Kaushal M <kaushal>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>
    Reviewed-by: Vijay Bellur <vbellur>

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/

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