Description of problem: ======================= Correction to be made for the cli output. if multiple bricks are created on the same server, the output shows replicate volume instead of disperse volume. [root@ninja ~]# gluster v create testvol disperse 11 redundancy 3 ninja:/rhs/brick1/testvol1 transformers:/rhs/brick1/testvol2 interstellar:/rhs/brick1/testvol3 ninja:/rhs/brick2/testvol4 transformers:/rhs/brick2/testvol5 interstellar:/rhs/brick2/testvol6 ninja:/rhs/brick3/testvol7 transformers:/rhs/brick3/testvol8 interstellar:/rhs/brick3/testvol9 ninja:/rhs/brick4/testvol10 transformers:/rhs/brick4/testvol11 volume create: testvol: failed: Multiple bricks of a *replicate volume* are present on the same server. This setup is not optimal. Use 'force' at the end of the command if you want to override this behavior. [root@ninja ~]# Version-Release number of selected component (if applicable): ============================================================= [root@ninja ~]# gluster --version glusterfs 3.7.0 built on May 15 2015 01:31:12 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. [root@ninja ~]# How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://code.engineering.redhat.com/gerrit/50817 Master - http://review.gluster.org/11250 3.7 http://review.gluster.org/11251
verified on 3.7.1-6 build and is correct. Marking this as fixed. [root@ninja ~]# gluster v create vol3 disperse 6 transformers:/rhs/brick7/vol3-1 interstellar:/rhs/brick7/vol3-2 transformers:/rhs/brick8/vol3-3 interstellar:/rhs/brick8/vol3-4 transformers:/rhs/brick9/vol3-5 interstellar:/rhs/brick9/vol3-6 The optimal redundancy for this configuration is 2. Do you want to create the volume with this value ? (y/n) y volume create: vol3: failed: Multiple bricks of a disperse volume are present on the same server. This setup is not optimal. Use 'force' at the end of the command if you want to override this behavior. [root@ninja ~]#
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html