You might try this: http://joejulian.name/blog/fixing-split-brain-with-glusterfs-33/ and wait for the self-heal to replace the file. In most cases it works, but sometimes the gluster client stills reports split brain (even all xattr flags are cleared). In that case you may try to clear the cache on the clients by issuing ( http://linux-mm.org/Drop_Caches): echo 3 > /proc/sys/vm/drop_caches If the client still see the file as split brain, you shall have to umount and mount again the gluster volume. Hope it helps, Samuel. On 11 April 2013 01:48, Robert Hajime Lanning <lanning at lanning.cc> wrote: > On 04/10/13 03:44, Daniel Mons wrote: > [snip] > > >> Option 1) Delete the file from the "bad" brick >> >> > I would do this. Then trigger a self-heal. > > -- > Mr. Flibble > King of the Potato People > > ______________________________**_________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.**org/mailman/listinfo/gluster-**users<http://supercolony.gluster.org/mailman/listinfo/gluster-users> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130411/9ac07ade/attachment-0001.html>
