Bug 763523 (GLUSTER-1791) - remove-brick during rebalance
Summary: remove-brick during rebalance
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1791
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.1-alpha
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-04 12:55 UTC by Lakshmipathi G
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: RTP
Mount Type: nfs
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Lakshmipathi G 2010-10-04 09:58:09 UTC
checking status on brick1 after remove-brick operation succeeded on brick2
---------
brick1# /opt/glusterfs/3.1.0qa39//sbin/gluster volume rebalance utar status
rebalance not started: rebalanced 610 files of size 418350048 (total files scanned 1687)

Comment 1 Vijay Bellur 2010-10-04 11:05:50 UTC
PATCH: http://patches.gluster.com/patch/5237 in master (Additional status check for rebalance in progress)

Comment 2 Lakshmipathi G 2010-10-04 12:55:39 UTC
after starting rebalance - remove-brick failed with following message on brick1 but it succeeded on brick2.

brick1# /opt/glusterfs/3.1.0qa39//sbin/gluster volume rebalance utar status
rebalance step 1: layout fix in progress: fixed layout 5

brick1# /opt/glusterfs/3.1.0qa39//sbin/gluster volume remove-brick utar 10.214.231.112:/mnt/UNTAR/
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
Remove Brick unsuccessful
-------
brick2# /opt/glusterfs/3.1.0qa39//sbin/gluster volume remove-brick utar 10.214.231.112:/mnt/UNTAR
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
Remove Brick successful


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