[Gluster-users] Sudden interference between 2 independent gluster volumes

Joe Julian joe at julianfamily.org
Thu Dec 4 17:46:24 UTC 2014

If the volumes had the same names, I have no idea what the result of 
that would be.

If they had different names, it sounds like the volume data only sync'ed 
one direction. Theoretically, you can look in /var/lib/glusterd/vols and 
ensure that both volume directories exist on both servers (I would do 
this with glusterd stopped) without detaching them as peers.

On 12/04/2014 08:31 AM, Peter B. wrote:
> Status update:
> Server "A" and "B" now consider themselves gluster peers: Each one lists
> the other one as peer ($ gluster peer status).
> However, "gluster volume info <volume_name>" only lists the bricks of "B".
> To solve my problem and restore autonomy of "A", I think I could do the
> following:
> On server "A":
> 1) gluster peer detach "B"
> 2) Re-add the local bricks on "A" (which were already part of the game,
> but ain't anymore)
> Could this work?
> Is there anything I must watch out for, before re-adding the bricks of "A"
> back to volume "A" again?
> Sorry for asking so many questions here, but I'm progressively
> understanding the problem/situation better as we speak. Therefore the
> changing questions :)
> Sorry...
> Thanks again,
> Peter
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users

More information about the Gluster-users mailing list