Description of problem:
EC volume getting created without any redundant brick
The disperse-count is 4 disperse-data is 4 and redundnant count is 0
Ideally this should fail and used to fail
Version-Release number of selected component (if applicable):
I am seeing this issue even on latest 3.3.1-async ie 3.8.4-54.13
However, this was not the case previously, so don't know when the regression got introduced
Steps to Reproduce:
1.Create an EC volume with disperse-count is 4 disperse-data is 4 and redundnant count is 0
[root@dhcp42-53 ~]# gluster volume create test-dispersed disperse 4 disperse-data 4 10.70.42.53:/bricks/brick2/dispersed 10.70.42.160:/bricks/brick2/dispersed 10.70.42.138:/bricks/brick2/dispersed 10.70.42.164:/bricks/brick2/dispersed 10.70.42.40:/bricks/brick2/dispersed 10.70.42.159:/bricks/brick2/dispersed 10.70.42.53:/bricks/brick1/dispersed 10.70.42.160:/bricks/brick1/dispersed 10.70.42.138:/bricks/brick1/dispersed 10.70.42.164:/bricks/brick1/dispersed 10.70.42.40:/bricks/brick1/dispersed 10.70.42.159:/bricks/brick1/dispersed
volume create: test-dispersed: success: please start the volume to access data
It is sucessful.
Volume Name: test-dispersed
Volume ID: 8d85f62b-7122-4b7f-8fb2-06fe66ad29e5
Snapshot Count: 0
Number of Bricks: 3 x (4 + 0) = 12
The above example is for a distributed-dispersed volume
Adding logs for a dispersed volume
[root@dhcp42-53 ~]# gluster volume create test-dispersed1 disperse 4 disperse-data 4 10.70.42.53:/bricks/brick2/dispersed1 10.70.42.160:/bricks/brick2/dispersed1 10.70.42.138:/bricks/brick2/dispersed1 10.70.42.164:/bricks/brick2/dispersed1
volume create: test-dispersed1: success: please start the volume to access data
Volume Name: test-dispersed1
Volume ID: ab9251ba-02c8-49c7-9b3c-2ac0409ff104
Snapshot Count: 0
Number of Bricks: 1 x (4 + 0) = 4
REVIEW: https://review.gluster.org/21478 (cluster/ec : Prevent volume create without redundant brick) posted (#1) for review on master by Sunil Kumar Acharya
COMMIT: https://review.gluster.org/21478 committed in master by "Sunil Kumar Acharya" <email@example.com> with a commit message- cluster/ec : Prevent volume create without redundant brick
EC volumes can be created without any redundant brick.
Updated the conditional check to avoid volume create without
Signed-off-by: Sunil Kumar Acharya <firstname.lastname@example.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.
glusterfs-6.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.