Bug 1223225
Summary: | cli correction: if tried to create multiple bricks on same server shows replicate volume instead of disperse volume | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Bhaskarakiran <byarlaga> |
Component: | disperse | Assignee: | Ashish Pandey <aspandey> |
Status: | CLOSED ERRATA | QA Contact: | Bhaskarakiran <byarlaga> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | rhgs-3.1 | CC: | annair, asrivast, mzywusko, nsathyan, pkarampu, rhs-bugs, storage-qa-internal, vagarwal |
Target Milestone: | --- | ||
Target Release: | RHGS 3.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.1-6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-29 04:44: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: | |||
Bug Depends On: | |||
Bug Blocks: | 1202842, 1223636 |
Description
Bhaskarakiran
2015-05-20 07:23:48 UTC
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 |