Gluster users - Dec 2014 - Sudden interference between 2 independent gluster volumes

This is actually directly related to my problem is mentioned here on Monday:
"Folder disappeared on volume, but exists on bricks."

I probed node "A" from server "B", which caused all this. My
bad.
:(


No data is lost, but is there any way to recover the volume information in
/var/lib/glusterd on server "A", to separate it from "B"
again?


Thank you very much in advance,
Pb

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

On 12/04/2014 09:08 PM, Peter B. wrote:
> This is actually directly related to my problem is mentioned here on
Monday:
> "Folder disappeared on volume, but exists on bricks."
> 
> I probed node "A" from server "B", which caused all
this. My bad.
> :(
> 
> 
> No data is lost, but is there any way to recover the volume information in
> /var/lib/glusterd on server "A", to separate it from
"B" again?
How are you saying that volume information is overlapping each other? If
these volumes were created at different clusters they wouldn't have any
common data, would they?

~Atin
> 
> 
> Thank you very much in advance,
> Pb
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>