Bug 765306 (GLUSTER-3574) - Rebalance operation should not start if one of the brick is offline
Summary: Rebalance operation should not start if one of the brick is offline
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3574
Product: GlusterFS
Classification: Community
Component: core
Version: pre-release
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
: GLUSTER-3585 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-16 11:41 UTC by shylesh
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description shylesh 2011-09-16 11:41:10 UTC
1. Create a distribute volume with two bricks
2. Bring down one of the brick 
3. Initiate rebalance on this volume


Bug
----
output 
=======

[root@GVSA-GMCQA1 export]# gluster volume rebalance two-brick start 
starting rebalance on volume two-brick has been successful
[root@GVSA-GMCQA1 export]# gluster volume rebalance two-brick status
rebalance step 1: layout fix in progress
[root@GVSA-GMCQA1 export]# gluster volume rebalance two-brick status
rebalance completed


======================================

Rebalance should not start

Comment 1 Anand Avati 2011-09-22 02:30:49 UTC
CHANGE: http://review.gluster.com/481 (This will prevent rebalance to be started when a brick is down, or) merged in master by Vijay Bellur (vijay)

Comment 2 shishir gowda 2011-09-22 02:32:27 UTC
*** Bug 3585 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.