Bug 770659

Summary: Removal of two bricks from striped-replicate of four bricks results in striped-replicate volume instead of plain replicate.
Product: [Community] GlusterFS Reporter: Vijaykumar Koppad <vkoppad>
Component: coreAssignee: Amar Tumballi <amarts>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: mainlineCC: bbandari, gluster-bugs, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 03:12:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.