[Bugs] [Bug 1212400] New: Attach tier failing and messing up vol info
bugzilla at redhat.com
bugzilla at redhat.com
Thu Apr 16 10:35:45 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1212400
Bug ID: 1212400
Summary: Attach tier failing and messing up vol info
Product: GlusterFS
Version: mainline
Component: tiering
Severity: urgent
Assignee: bugs at gluster.org
Reporter: annair at redhat.com
QA Contact: bugs at gluster.org
CC: bugs at gluster.org
Description of problem:
Attach tier is failing and also messing up the volume info (brick config)
Version-Release number of selected component (if applicable):
glusterfs-server-3.7dev-0.885.git0d36d4f.el6.x86_64
Steps to Reproduce:
1. Create a dispere volume
[root at dhcp35-166 ~]# gluster vol create volt1 disperse 6 redundancy 2
10.70.35.4:/b1 10.70.35.4:/b2 10.70.35.4:/b3 10.70.35.166:/b1 10.70.35.166:/b2
10.70.35.166:/b3 force
Volume Name: volt1
Type: Disperse
Volume ID: 2665b778-b7d9-4ace-94dd-d196bcd8d4ac
Status: Started
Number of Bricks: 1 x (4 + 2) = 6
Transport-type: tcp
Bricks:
Brick1: 10.70.35.4:/b1
Brick2: 10.70.35.4:/b2
Brick3: 10.70.35.4:/b3
Brick4: 10.70.35.166:/b1
Brick5: 10.70.35.166:/b2
Brick6: 10.70.35.166:/b3
2. Try attaching a tier (dist.rep) to the already created volume:
[root at dhcp35-166 ~]# gluster vol attach-tier volt1 replica 2 10.70.35.4:/b4
10.70.35.166:/b4 10.70.35.4:/b5 10.70.35.166:/b5 forcevolume add-brick: failed:
/b5 is already part of a volume
NOTE: b5 is a fresh brick and not used before, so not sure about it's
complaining
3.Now check the volume status:
Volume Name: volt1
Type: Distributed-Disperse
Volume ID: 2665b778-b7d9-4ace-94dd-d196bcd8d4ac
Status: Started
Number of Bricks: 1 x (4 + 2) = 10
Transport-type: tcp
Bricks:
Brick1: 10.70.35.166:/b5
Brick2: 10.70.35.4:/b5
Brick3: 10.70.35.166:/b4
Brick4: 10.70.35.4:/b4
Brick5: 10.70.35.4:/b1
Brick6: 10.70.35.4:/b2
Brick7: 10.70.35.4:/b3
Brick8: 10.70.35.166:/b1
Brick9: 10.70.35.166:/b2
Brick10: 10.70.35.166:/b3
4. Shows some wierd o/p "1 x (4 + 2) = 10"
Expected results:
1. Attach tier should succeed or fail completely
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list