Bug 763523 - (GLUSTER-1791) remove-brick during rebalance
remove-brick during rebalance
Status: CLOSED CURRENTRELEASE
Product: GlusterFS
Classification: Community
Component: cli (Show other bugs)
3.1-alpha
All Linux
low Severity medium
: ---
: ---
Assigned To: shishir gowda
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-10-04 08:55 EDT by Lakshmipathi G
Modified: 2015-12-01 11:45 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: RTP
Mount Type: nfs
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lakshmipathi G 2010-10-04 05:58:09 EDT
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 07:05:50 EDT
PATCH: http://patches.gluster.com/patch/5237 in master (Additional status check for rebalance in progress)
Comment 2 Lakshmipathi G 2010-10-04 08:55:39 EDT
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.