I think I know now what happened: - 2 gluster volumes on 2 different servers: A and B. - A=production, B=testing - On server "B" we will soon expand, so I read up on how to add new nodes. - Therefore on server "B" I ran "gluster probe A", assuming that "probe" was just reading *if* A would be available. It seems that "probing" another node already writes configuration data onto them. That seems to be the reason why the data of the bricks didn't show up on the volume mountpoint on "A", because it was now already pointing to "B". Pb _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
