Bug 1027171 - remove-brick :- If User executes 'gluster volume remove-brick <vol> <brick> commit' command before 'gluster volume remove-brick <vol> <brick> start' commands; it removes brick and ends in data loss
Summary: remove-brick :- If User executes 'gluster volume remove-brick <vol> <brick> c...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact:
URL:
Whiteboard:
Depends On: 1003914
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 10:18 UTC by Vijaikumar Mallikarjuna
Modified: 2016-05-11 22:47 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of: 1003914
Environment:
Last Closed: 2014-11-11 08:24:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Anand Avati 2013-11-06 11:16:25 UTC 
REVIEW: http://review.gluster.org/6233 (glusterd: Check if remove-brick is already committed or is not started) posted (#1) for review on master by Vijaikumar M (vmallika)
Comment 2 Anand Avati 2013-11-08 10:20:25 UTC 
REVIEW: http://review.gluster.org/6233 (glusterd: Do not allow remove-brick commit if the bricks are not decommissioned) posted (#2) for review on master by Vijaikumar M (vmallika)
Comment 3 Anand Avati 2013-12-04 02:12:08 UTC 
COMMIT: http://review.gluster.org/6233 committed in master by Anand Avati (avati) 
------
commit 8e21e00fc662abb4f6556d9a258fa9ec57a20ed0
Author: Vijaikumar M <vmallika>
Date:   Wed Nov 6 16:41:50 2013 +0530

    glusterd: Do not allow remove-brick commit if the bricks are not decommissioned
    
    Change-Id: Ibf47ea848bbb7ae37ccf91c40e5fe0e2338438b7
    BUG: 1027171
    Signed-off-by: Vijaikumar M <vmallika>
    Reviewed-on: http://review.gluster.org/6233
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
Comment 4 Niels de Vos 2014-09-22 12:32:34 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:24:28 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
Note You need to log in before you can comment on or make changes to this bug.