No one around can help with this situation?<br><br>The file finally got "corrupted" and it's impossible to read from any of the current mounted native gluster clients.<br><br>Reading the attributes, all flags are set as 0:<br>
<br># file: dd29900f215b175939816f94c907a31b<br>trusted.afr.storage-client-6=0x000000000000000000000000<br>trusted.afr.storage-client-7=0x000000000000000000000000<br>trusted.gfid=0x59311906edf04464be5f00f505b3aebb<br>trusted.storage-stripe-1.stripe-count=0x3200<br>
trusted.storage-stripe-1.stripe-index=0x3100<br>trusted.storage-stripe-1.stripe-size=0x31333130373200<br><br>so there should not be read as split brain from clients but we got the following logs:<br>"split brain detected during lookup of"<br>
<br>thanks in advance,<br>Samuel.<br><br><br><div class="gmail_quote">On 4 March 2013 14:37, samuel <span dir="ltr"><<a href="mailto:samu60@gmail.com" target="_blank">samu60@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi folks,<br><br>We have detected a split-brain on 3.3.0 stripped replicated 8 nodes cluster.<br>We've followed the instructions from:<br><a href="http://www.gluster.org/2012/07/fixing-split-brain-with-glusterfs-3-3/" target="_blank">http://www.gluster.org/2012/07/fixing-split-brain-with-glusterfs-3-3/</a><br>
and we've manually recovered the information.<br><br>The problem is that we've got 4 gluster native clients and from 2 of them we got <br>0-storage-replicate-3: failed to open as split brain seen, returning EIO<br>
but from 2 of them we can access the recovered file.<br><br>We're this information locally storage on clients so we can "update" all of them and recover the information in a "coherent" manner?<br>
<br>
Thanks a lot in advance,<br>Samuel.<br>
</blockquote></div><br>