Bug 1478964

Summary: Creating dispersed volume per documentation returns an error
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Cal Calhoun <ccalhoun>
Component: doc-Administration_GuideAssignee: storage-doc
doc-Administration_Guide sub component: 3.2 Release QA Contact: Nag Pavan Chilakam <nchilaka>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: medium    
Priority: unspecified CC: aspandey, asriram, bkunal, ccalhoun, lbailey, nchilaka, rhs-bugs, storage-doc
Version: rhgs-3.2   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1480042 (view as bug list) Environment:
Last Closed: 2019-01-07 01:07:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Cal Calhoun 2017-08-07 15:15:23 UTC 
Document URL: 
  https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/html/administration_guide/sect-Recommended-Configuration_Dispersed

Section Number and Name: 
  11.12. Recommended Configurations - Dispersed Volume
  Example 1

Describe the issue: 
  When creating a 4+2 dispersed volume per these instructions, the create command returns an error.  This has been replicated in my local test environment.

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.

Suggestions for improvement: 
  The docs should be changed to reflect the need for the 'force' option if this is indeed a supported configuration.
 
Additional information: 
  Ultimately the customer wants to create a 2x(4+2) Distributed-Dispersed volume utilizing 12 bricks on 3 nodes.  The error when trying to create even a simple dispersed volume leads them to believe it may not be a supported configuration.

Please let me know if you need any additional information.
Comment 16 Bipin Kunal 2017-08-11 10:51:11 UTC 
looks fine to me.
Comment 18 Cal Calhoun 2017-08-14 21:12:53 UTC 
Sorry to weigh in so late on this but it looks like a great solution.  The customer is quite happy knowing that his use case will be supported and is fully aware that it is not 'optimal'.  This clarifies that quite well.
Comment 19 Nag Pavan Chilakam 2018-08-30 07:44:25 UTC 
looks good to me, hence moving to verified