[Gluster-users] Unable to self-heal permissions/ownership of '/' (possible split-brain)

[Dan Bretherton]

Hello all-

I have set up two new servers each with two RAID 5 arrays.  I am trying
to distribute the load across the two RAID arrays on each server by
creating a distributed, replicated volume.  This is the output from
"gluster volume info".

Volume Name: marine2
Type: Distributed-Replicate
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 192.171.166.86:/vg1lv0/glusterfs
Brick2: 192.171.166.87:/vg1lv0/glusterfs
Brick3: 192.171.166.86:/vg2lv0/glusterfs
Brick4: 192.171.166.87:/vg2lv0/glusterfs
Options Reconfigured:
performance.quick-read: off

The volume seems to be working normally, but I am seeing the following
messages repeated in my volume log file:

[2010-11-25 10:27:06.867368] I [afr-common.c:672:afr_lookup_done]
marine2-replicate-0: split brain detected during lookup of /.
[2010-11-25 10:27:06.867454] I [afr-common.c:716:afr_lookup_done]
marine2-replicate-0: background  meta-data data self-heal triggered. path: /
[2010-11-25 10:27:06.867614] I [afr-common.c:672:afr_lookup_done]
marine2-replicate-1: split brain detected during lookup of /.
[2010-11-25 10:27:06.867633] I [afr-common.c:716:afr_lookup_done]
marine2-replicate-1: background  meta-data data self-heal triggered. path: /
[2010-11-25 10:27:06.868174] E
[afr-self-heal-metadata.c:524:afr_sh_metadata_fix] marine2-replicate-0:
Unable to self-heal permissions/ownership of '/' (possible split-brain).
Please fix the file on all backend volumes
[2010-11-25 10:27:06.868265] E
[afr-self-heal-metadata.c:524:afr_sh_metadata_fix] marine2-replicate-1:
Unable to self-heal permissions/ownership of '/' (possible split-brain).
Please fix the file on all backend volumes
[2010-11-25 10:27:06.868483] I
[afr-self-heal-common.c:1526:afr_self_heal_completion_cbk]
marine2-replicate-0: background  meta-data data self-heal completed on /
[2010-11-25 10:27:06.868541] I
[afr-self-heal-common.c:1526:afr_self_heal_completion_cbk]
marine2-replicate-1: background  meta-data data self-heal completed on /

I don't understand why a self heal is ever necessary on "/".  These
presumably are the brick directories (/vg1lv0/glusterfs etc), which are
all owned by root and have the same permissions.  Is this something I
should be worried about, and if not how can I stop these warnings?
-Dan.