[Gluster-users] Issues removing then adding a brick to a replica volume (Gluster 3.7.6)

[Lindsay Mathieson]

On 18/01/16 22:24, Krutika Dhananjay wrote:
>
>     However if I run it on VNA, it succeeds.
>
>
> Yes, there is a bug report for this @ 
> https://bugzilla.redhat.com/show_bug.cgi?id=1112158.
> The workaround, like you yourself figured, is to run the command on 
> the node with the highest uuid.
> Steps:
> 1) Collect output of `cat /var/lib/glusterd/glusterd.info | grep UUID` 
> from each of the nodes, perhaps into a file named 'uuid.txt'.
> 2) cat uuid.txt | sort
> 3) Pick the last gfid.
> 4) find out which of the glusterd.info files has the same uuid as this 
> selected uuid.
> 5) Run 'heal info full' on that same node.
>
> Let me know if this works for you.
>

Yup, that confirms that the node the heal full worked on (vna) has the 
highest uuid.

When I added the new vng brick and ran heal full from vna then it all 
worked as expected, all 80 shards were being healed *to* vng.


Could that same bug mess with adding bricks as well? when I tested this 
before from vnb node,  shards were being healed from the empty brick 
(vbg) to vna & vnb

-- 
Lindsay Mathieson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160119/cce16f25/attachment.html>