[Bugs] [Bug 1480099] More useful error - replace 'not optimal'

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1480099

Ashish Pandey <aspandey at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|bugs at gluster.org            |aspandey at redhat.com



--- Comment #1 from Ashish Pandey <aspandey at redhat.com> ---
When creating a 4+2 dispersed volume as shown without --force command, the
command returns an error saying "This setup is not optimal".

Presumably this is because there are multiple bricks in a volume stored on the
same server, but 'optimal' has no distinct meaning. It would be more useful to
say WHY this setup isn't generally considered a good idea, and give the user
some idea of what would need to be corrected to be 'optimal' rather than just
saying that it isn't optimal.


Example (from documentation) below:

# gluster volume create testvol disperse-data 4 redundancy 2 transport tcp \
rhgs3-1:/mnt/bricks/brick1/data \
rhgs3-1:/mnt/bricks/brick2/data \
rhgs3-2:/mnt/bricks/brick1/data \
rhgs3-2:/mnt/bricks/brick2/data \
rhgs3-3:/mnt/bricks/brick1/data \
rhgs3-3:/mnt/bricks/brick2/data

volume create: testvol: 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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.