Bug 764081 (GLUSTER-2349)
| Summary: | replace-brick does not happen | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Saurabh <saurabh> |
| Component: | cli | Assignee: | Amar Tumballi <amarts> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.1.2 | CC: | anush, gluster-bugs, vraman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | RTNR | Mount Type: | --- |
| Documentation: | DNR | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Anush Shetty
2011-02-01 07:48:54 UTC
I am using a distribute-replicate volume and trying to replace a brick
details are here,
gluster> volume info repdist
Volume Name: repdist
Type: Distributed-Replicate
Status: Started
Number of Bricks: 3 x 2 = 6
Transport-type: tcp
Bricks:
Brick1: domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdist
Brick2: domU-12-31-39-0A-31-D2.compute-1.internal:/mnt/repdist
Brick3: domU-12-31-39-00-C9-C2.compute-1.internal:/mnt/repdist1
Brick4: domU-12-31-39-16-F9-F5.compute-1.internal:/mnt/repdist1
Brick5: domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdistadd
Brick6: domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdistadd2
gluster>
______________________________________________________________________
gluster> volume replace-brick
Usage: volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> {start|pause|abort|status}
gluster> volume replace-brick repdist domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdistadd domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdistadd3 start
replace-brick started successfully
gluster> volume replace-brick repdist domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdistadd domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdistadd3 status
replace-brick status unknown
gluster> volume info repdist
Volume Name: repdist
Type: Distributed-Replicate
Status: Started
Number of Bricks: 3 x 2 = 6
Transport-type: tcp
Bricks:
Brick1: domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdist
Brick2: domU-12-31-39-0A-31-D2.compute-1.internal:/mnt/repdist
Brick3: domU-12-31-39-00-C9-C2.compute-1.internal:/mnt/repdist1
Brick4: domU-12-31-39-16-F9-F5.compute-1.internal:/mnt/repdist1
Brick5: domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdistadd
Brick6: domU-12-31-39-10-76-40.compute-1.internal:/mnt/repdistadd2
effectively replace-brick does not happen.
Saurabh, You have to do 'replace-brick .... commit' before that new configuration taking effect. Please re-open this bug if you see if its not happening after you do the commit also. |