<div dir="ltr"><div><div><div><div><div><div><div>Hey,<br><br></div>From the getfattr output you have provided, the directory is clearly not in split brain.<br></div><div>If all the bricks are being blamed by others then it is called split brain.<br>In your case only client-13 that is Brick-14 in the volume info output had a pending entry heal on the directory.<br></div>That is the last replica subvol which consists of the bricks<br><br>Brick13: glusterserver03.mydomain.local:/bricks/video/brick3/safe<br>Brick14: glusterserver04.mydomain.local:/bricks/video/brick3/safe<br>Brick15: glusterserver05.mydomain.local:/bricks/video/brick3/safe (arbiter)<br></div><br></div>Which got healed as part of the heal you ran, or part of the self heal crawl and pending xattrs got reset to all zeros.<br></div>Which file are you not able to access? Can you give the getfattr output of that file and give the shd log<br>and the mount log where you were not able to access the file.<br><br></div>Regards,<br></div>Karthik<br><div><div> <div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 24, 2018 at 2:00 PM, Luca Gervasi <span dir="ltr">&lt;<a href="mailto:luca.gervasi@gmail.com" target="_blank">luca.gervasi@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div>I&#39;m trying to fix an issue with a Directory Split on a gluster 3.10.3. The effect consist of a specific file in this splitted directory to randomly be unavailable on some clients.</div><div>I have gathered all the informations on this gist: <a href="https://gist.githubusercontent.com/lucagervasi/534e0024d349933eef44615fa8a5c374/raw/52ff8dd6a9cc8ba09b7f258aa85743d2854f9acc/splitinfo.txt" target="_blank">https://gist.<wbr>githubusercontent.com/<wbr>lucagervasi/<wbr>534e0024d349933eef44615fa8a5c3<wbr>74/raw/<wbr>52ff8dd6a9cc8ba09b7f258aa85743<wbr>d2854f9acc/splitinfo.txt</a></div><div><br></div><div>I discovered the splitted directory by the extended attributes (lines 172,173, 291,292, </div><div><div>trusted.afr.dirty=<wbr>0x000000000000000000000000</div><div>trusted.afr.vol-video-client-<wbr>13=0x000000000000000000000000</div></div><div>Seen on the bricks </div><div>* /bricks/video/brick3/safe/<a href="http://video.mysite.it/htdocs/" target="_blank">vide<wbr>o.mysite.it/htdocs/</a> su glusterserver05 (lines 278 ro 294)</div><div>* /bricks/video/brick3/safe/<a href="http://video.mysite.it/htdocs/" target="_blank">vi<wbr>deo.mysite.it/htdocs/</a> su glusterserver03 (lines 159 to 175)</div><div><br></div><div>Reading the documentation about afr extended attributes, this situation seems unclear (Docs from [1] and [2])</div><div>as own changelog is 0, same as client-13 (glusterserver02.mydomain.<wbr>local:/bricks/video/brick3/<wbr>safe)</div><div>as my understanding, such &quot;dirty&quot; attributes seems to indicate no split at all (feel free to correct me).</div><div><br></div><div>Some days ago, I issued a &quot;gluster volume heal vol-video full&quot;, which endend (probably) that day, leaving no info on /var/log/gluster/glustershd.<wbr>log nor fixing this split.</div><div>I tried to trigger a self heal using &quot;stat&quot; and &quot;ls -l&quot; over the splitted directory from a glusterfs mounted client directory, without having the bit set cleared.</div><div>The volume heal info split-brain itself shows zero items to be healed (lines 388 to 446).</div><div><br></div><div>All the clients mount this volume using glusterfs-fuse.</div><div><br></div><div>I don&#39;t know what to do, please help.</div><div><br></div><div>Thanks.</div><div><br></div><div>Luca Gervasi</div><div><br></div><div>References:</div><div>[1] <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/Recovering_from_File_Split-brain.html" target="_blank">https://access.redhat.com/<wbr>documentation/en-US/Red_Hat_<wbr>Storage/2.1/html/<wbr>Administration_Guide/<wbr>Recovering_from_File_Split-<wbr>brain.html</a></div><div>[2] <a href="https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html/administration_guide/sect-managing_split-brain" target="_blank">https://access.redhat.com/<wbr>documentation/en-us/red_hat_<wbr>gluster_storage/3.3/html/<wbr>administration_guide/sect-<wbr>managing_split-brain</a></div></div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br></div></div></div></div>