On 07/15/2016 08:23 PM, Rob Janney wrote:
Currently we are on 3.6: glusterfs 3.6.9 built on Mar 2 2016 18:21:17
That version does not have the real-time gfapi based version of the
`info split-brain` command and it just prints prior event history from
the selfheal daemon's memory. You can
Currently we are on 3.6: glusterfs 3.6.9 built on Mar 2 2016 18:21:17
Yes, the file gfid file still was present at
/.glusterfs/ab/da/abdab36b-b90b-4201-98fe-7a36059da81d
On Thu, Jul 14, 2016 at 7:51 PM, Ravishankar N
wrote:
>
>
> On 07/15/2016 02:24 AM, Rob Janney
On 07/15/2016 02:24 AM, Rob Janney wrote:
I have a 2 node cluster that reports a single file as split brained ..
but the file itself doesn't exist on either node.
What is the version of gluster you are running?
I did not find this scenario in the split brain docs, but based on
other
I have a 2 node cluster that reports a single file as split brained .. but
the file itself doesn't exist on either node. I did not find this scenario
in the split brain docs, but based on other scenarios I deleted the gfid
file and then ran a full heal, however; it still complains about split
Hi there,
I have a split-brain situation on one of my volumes. The part that I'm not
clear on is that it would appear to be on the root of the volume.
[2015-04-13 22:07:35.729798] E
[afr-self-heal-common.c:2262:afr_self_heal_completion_cbk]
0-www-conf-replicate-0: background meta-data