Bug 835494
Summary: | Volume creation fails and gives error "<brickname> or a prefix of it is already part of a volume", eventhough that brick is not part of any volume. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Rachana Patel <racpatel> | ||||
Component: | glusterd | Assignee: | bugs <bugs> | ||||
Status: | CLOSED DEFERRED | QA Contact: | amainkar | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.3.0 | CC: | bugs, gluster-bugs, powernerd, rwheeler | ||||
Target Milestone: | --- | Keywords: | Triaged | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 852293 (view as bug list) | Environment: | |||||
Last Closed: | 2014-12-14 19:40:28 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | DP | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 852293 | ||||||
Attachments: |
|
Description
Rachana Patel
2012-06-26 10:59:00 UTC
Created attachment 594431 [details]
Nth server log
This is resolvable by removing the attributes from the brick(s) that are failing to add. use setfattr -x trusted.gfid dir/brick setfattr -x trusted.glusterfs.volume-id dir/brick on serverN as work-around is available not treating as higher priority. Surely need to document the scenario work-around is there but if volume has not been created (due to any reason) then it should not set attributes for those briucks The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug. If there has been no update before 9 December 2014, this bug will get automatocally closed. |