Bug 770659 - Removal of two bricks from striped-replicate of four bricks results in striped-replicate volume instead of plain replicate.
Summary: Removal of two bricks from striped-replicate of four bricks results in stripe...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-28 09:23 UTC by Vijaykumar Koppad
Modified: 2014-08-25 00:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 03:12:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Vijaykumar Koppad 2011-12-28 09:23:14 UTC
Description of problem:

Volume Name: doa
Type: Replicate
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.1.11.139:/root/bricks/doa/d1
Brick2: 10.1.11.139:/root/bricks/doa/d2
Options Reconfigured:
geo-replication.indexing: on
features.quota: on 

root@ubuntu11-QA1:~# gluster volume add-brick doa stripe 2 10.1.11.138:/root/bricks/doa/d1 10.1.11.138:/root/bricks/doa/d2
Add Brick successful
root@ubuntu11-QA1:~# gluster volume info
 
Volume Name: doa
Type: Striped-Replicate
Status: Started
Number of Bricks: 1 x 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.1.11.139:/root/bricks/doa/d1
Brick2: 10.1.11.139:/root/bricks/doa/d2
Brick3: 10.1.11.138:/root/bricks/doa/d1
Brick4: 10.1.11.138:/root/bricks/doa/d2
Options Reconfigured:
geo-replication.indexing: on
features.quota: on
root@ubuntu11-QA1:~# gluster volume remove-brick doa replica 2 10.1.11.139:/root/bricks/doa/d2 10.1.11.138:/root/bricks/doa/d2
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
Remove Brick successful
root@ubuntu11-QA1:~# gluster volume info
 
Volume Name: doa
Type: Striped-Replicate
Status: Started
Number of Bricks: 0 x 2 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.1.11.139:/root/bricks/doa/d1
Brick2: 10.1.11.138:/root/bricks/doa/d1
Options Reconfigured:
geo-replication.indexing: on
features.quota: on

Comment 1 Amar Tumballi 2012-03-30 03:12:15 UTC
[root@supernova ~]# gluster volume remove-brick rpl replica 2 supernova:/tmp/export/rpl3  supernova:/tmp/export/rpl4
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
Removing bricks from stripe-replicate configuration is not allowed without reducing replica or stripe count explicitly.

[root@supernova ~]# gluster volume remove-brick rpl stripe 1 supernova:/tmp/export/rpl3  supernova:/tmp/export/rpl4
wrong brick type: stripe, use <HOSTNAME>:<export-dir-abs-path>
Usage: volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ... {start|pause|abort|status|commit|force}
[root@supernova ~]# 

One cannot reduce the 'stripe' count. The command given in above exercise are not valid. Not a bug.


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