I never did manage to figure this out.
All attempts to replace-brick failed inexplicably; we could add-brick
but then still not remove-brick the old one, and the new bricks didn't
seem to be functioning properly anyway.
Eventually we just sucked it up and caused a couple of hours of downtime
across all production servers while we brought up a whole new gluster
cluster and moved everything to it.
That's been the final straw for us though -- we're going to ditch
Gluster across the company as soon as possible. It's too risky to keep
using it.
It's been unreliable and unpredictable, and if anything version 3.3 has
been worse than 3.2 for bugs. (And I have no faith at all that 3.4 is an
improvement)
-Toby
On 07/08/13 11:44, Toby Corkindale wrote:
On 06/08/13 18:24, Toby Corkindale wrote:
Hi,
I'm getting some confusing "Incorrect brick" errors when attempting to
remove OR replace a brick.
gluster> volume info condor
Volume Name: condor
Type: Replicate
Volume ID: 9fef3f76-525f-4bfe-9755-151e0d8279fd
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: mel-storage01:/srv/brick/condor
Brick2: mel-storage02:/srv/brick/condor
gluster> volume remove-brick condor replica 1
mel-storage02:/srv/brick/condor start
Incorrect brick mel-storage02:/srv/brick/condor for volume condor
If that is the incorrect brick, then what have I done wrong?
Note that the log files don't seem to be any use here, they just report:
E [glusterd-brick-ops.c:749:glusterd_handle_remove_brick] 0-: Incorrect
brick mel-storage02:/srv/brick/condor for volume condor
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
