No one around can help with this situation?
The file finally got "corrupted" and it's impossible to read from
any of
the current mounted native gluster clients.
Reading the attributes, all flags are set as 0:
# file: dd29900f215b175939816f94c907a31b
trusted.afr.storage-client-6=0x000000000000000000000000
trusted.afr.storage-client-7=0x000000000000000000000000
trusted.gfid=0x59311906edf04464be5f00f505b3aebb
trusted.storage-stripe-1.stripe-count=0x3200
trusted.storage-stripe-1.stripe-index=0x3100
trusted.storage-stripe-1.stripe-size=0x31333130373200
so there should not be read as split brain from clients but we got the
following logs:
"split brain detected during lookup of"
thanks in advance,
Samuel.
On 4 March 2013 14:37, samuel <samu60 at gmail.com> wrote:
> Hi folks,
>
> We have detected a split-brain on 3.3.0 stripped replicated 8 nodes
> cluster.
> We've followed the instructions from:
> http://www.gluster.org/2012/07/fixing-split-brain-with-glusterfs-3-3/
> and we've manually recovered the information.
>
> The problem is that we've got 4 gluster native clients and from 2 of
them
> we got
> 0-storage-replicate-3: failed to open as split brain seen, returning EIO
> but from 2 of them we can access the recovered file.
>
> We're this information locally storage on clients so we can
"update" all
> of them and recover the information in a "coherent" manner?
>
> Thanks a lot in advance,
> Samuel.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130308/ce1adec6/attachment.html>