<div dir="ltr">Hello,<br>today in my 2 nodes replica set I&#39;ve found split-brain. Command &#39;ls&#39; start told &#39;Input/output error&#39;.<br>But command &#39;gluster v heal VOLNAME info split-brain&#39; does not show problem files:<br># gluster v heal repofiles info split-brain<br>Brick dist-int-master03.xxx:/storage/gluster_brick_repofiles<br>Number of entries in split-brain: 0<br><br>Brick dist-int-master04.xxx:/storage/gluster_brick_repofiles<br>Number of entries in split-brain: 0<br>#<br>In output of &#39;gluster v heal VOLNAME info&#39; I see problem files (/xxx/keyrings/debian-keyring.gpg, /repos.json), but without split-brain markers:<br># gluster v heal repofiles info<br>Brick dist-int-master03.xxx:/storage/gluster_brick_repofiles<br>/xxx/keyrings/debian-keyring.gpg<br>&lt;gfid:09ec49c9-911a-4b83-abe8-080fe79e7c69&gt;<br>&lt;gfid:35c51b11-a7fb-496d-9e88-6d5a54fda7da&gt;<br>/repos.json<br>&lt;gfid:4f5cb2b5-30e2-43b0-a935-cfc42af883bf&gt;<br>&lt;gfid:9d2fc354-37c0-47a7-b9f3-379504cba797&gt;<br>&lt;gfid:cd86a246-9fc4-47d2-bb4d-67566677f77a&gt;<br>&lt;gfid:b932eed0-07e9-45c5-943e-7478e9f654b4&gt;<br>&lt;gfid:28bf2ffe-948c-4c7d-bce6-966242338581&gt;<br>&lt;gfid:ee5659ae-1335-42c5-a852-790387b4213b&gt;<br>&lt;gfid:fdfb6b8c-3c04-435a-b8d3-8d8341b66409&gt;<br>Number of entries: 11<br><br>Brick dist-int-master04.xxx:/storage/gluster_brick_repofiles<br>Number of entries: 0<br>#<br><br>I couldn&#39;t solve split-brain by new standard command:<br># gluster v heal repofiles  split-brain bigger-file /repos.json<br>Lookup failed on /repos.json:Input/output error<br>Volume heal failed.<br>#<br><br>Additional info:<br># gluster v info<br> Volume Name: repofiles<br> Type: Replicate<br> Volume ID: 4b0e2a74-f1ca-4fe7-8518-23919e1b5fa0<br> Status: Started<br> Number of Bricks: 1 x 2 = 2<br> Transport-type: tcp<br> Bricks:<br> Brick1: dist-int-master03.xxx:/storage/gluster_brick_repofiles<br> Brick2: dist-int-master04.xxx:/storage/gluster_brick_repofiles<br> Options Reconfigured:<br> performance.readdir-ahead: on<br> client.event-threads: 4<br> server.event-threads: 4<br> cluster.lookup-optimize: on<br># cat /etc/issue<br>Ubuntu 14.04.3 LTS \n \l<br># dpkg -l | grep glusterfs<br>ii  glusterfs-client                        3.7.5-ubuntu1~trusty1                amd64        clustered file-system (client package)<br>ii  glusterfs-common                        3.7.5-ubuntu1~trusty1                amd64        GlusterFS common libraries and translator modules<br>ii  glusterfs-server                        3.7.5-ubuntu1~trusty1                amd64        clustered file-system (server package)<br>#<br><br>I have 2 questions:<br>1. Why &#39;gluster v heal VOLNAME info split-brain&#39; doesn&#39;t show actual split-brain? Why in &#39;gluster v heal VOLNAME info&#39; I doesn&#39;t see markers like &#39;possible in split-brain&#39;?<br>How I can monitor my gluster installation if these commands doesn&#39;t show problems?<br>2. Why &#39;gluster volume heal VOLNAME split-brain bigger-file FILE&#39; doesn&#39;t solve split-brain? I understand that I can solve split-brain remove files from brick but I thought to use this killer feature.<br><br>Best regards,<br>Igor<br></div>