Occurance of a split brain situation is only under a specific sequence of
events and modifications and the filesystem cannot decide which of the two
copies of the file is updated. It might so happen that the two changes were
actually the same "change" and hence the two copies of your file might match
md5sum (in which case you can delete one arbitrarily). If not, you need to
know how your application works and which of the file (inspecting the
content) is more appropriate to be deleted.

Avati

On Wed, May 4, 2011 at 5:54 PM, Martin Schenker <
[email protected]> wrote:

> Hi all!
>
> Is there anybody who can give some pointers regarding which file to choose
> in a "split brain" condition?
>
> What tests do I need to run?
>
> What does the hex AFR code actually show? Is there a way to pinpoint the
> "better/worse" file for deletion?
>
> On pserver12:
>
> # file: mnt/gluster/brick0/storage/pserver3-19
> trusted.afr.storage0-client-5=0x3f0000010000000000000000
>
> On pserver13:
>
> # file: mnt/gluster/brick0/storage/pserver3-19
> trusted.afr.storage0-client-4=0xd70000010000000000000000
>
> These are test files, but I'd like to know what to do in a LIFE situation
> which will be just around the corner.
>
> The Timestamps show the same values, so I'm a bit puzzled HOW to choose a
> file.
>
> pserver12:
>
> 0 root@de-dc1-c1-pserver12:~ # ls -al
> /mnt/gluster/brick0/storage/pserver3-19
> -rw-r--r-- 1 vcb root 3456106496 Apr 29 17:40
> /mnt/gluster/brick0/storage/pserver3-19
>
> 0 root@de-dc1-c1-pserver12:~ # ls -alu
> /mnt/gluster/brick0/storage/pserver3-19
> -rw-r--r-- 1 vcb root 3456106496 Apr 28 16:18
> /mnt/gluster/brick0/storage/pserver3-19
>
> pserver13:
>
> 0 root@de-dc1-c1-pserver13:~ # ls -al
> /mnt/gluster/brick0/storage/pserver3-19
> -rw-r--r-- 1 vcb root 3456106496 Apr 29 17:40
> /mnt/gluster/brick0/storage/pserver3-19
>
> 0 root@de-dc1-c1-pserver13:~ # ls -alu
> /mnt/gluster/brick0/storage/pserver3-19
> -rw-r--r-- 1 vcb root 3456106496 Apr 28 16:18
> /mnt/gluster/brick0/storage/pserver3-19
>
> Best, Martin
>
> _______________________________________________
> Gluster-users mailing list
> [email protected]
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users

Reply via email to