+++ This bug was initially created as a clone of Bug #1074429 +++ Description of problem: ----------------------- Replace brick operation with data migration has been deprecated. And this support for "replace-brick" with data migration should be removed from gluster-cli Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHS 2.1 Update2 - glusterfs-3.4.0.59rhs-1.el6rhs How reproducible: ----------------- Not Applicable Steps to Reproduce: ------------------- Not Applicable Actual results: --------------- replace-brick with data migration was allowed from gluster-cli Expected results: ----------------- replace-brick with data migration should not be allowed Additional info: ---------------- I ran in to data corruption / data loss cases, when performing replace brick using "replace-brick" command. It is high-time to disable this replace-brick with data migration from gluster-cli But replace-brick with force commit could be a useful scenario, where the dead brick could be replaced with new brick, without data migration. So, replace-brick with "commit force", should only allowed from gluster-cli
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#3) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#4) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#5) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#6) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#7) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#8) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#10) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/10101 (glusterd: remove replace brick with data migration support form cli/glusterd) posted (#11) for review on master by Gaurav Kumar Garg (ggarg)
COMMIT: http://review.gluster.org/10101 committed in master by Kaushal M (kaushal) ------ commit 07e3f407b311c80e3437b1f650cae62f814d995b Author: Gaurav Kumar Garg <ggarg> Date: Fri Mar 27 15:20:03 2015 +0530 glusterd: remove replace brick with data migration support form cli/glusterd Replace-brick operation with data migration support have been deprecated from gluster. With this fix replace brick command will support only one commad gluster volume replace-brick <VOLNAME> <SOURCE-BRICK> <NEW-BRICK> {commit force} Change-Id: Ib81d49e5d8e7eaa4ccb5830cfec2bc081191b43b BUG: 1094119 Signed-off-by: Gaurav Kumar Garg <ggarg> Reviewed-on: http://review.gluster.org/10101 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal>
pre-release version is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user