<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I took one of the gfids and found the actual path to the file on the brick. I then did:<div class=""><br class=""></div><div class=""><font face="Courier" class="">getfattr -d -m . -e hex <ACTUAL_PATH></font></div><div class=""><br class=""></div><div class=""><span style="font-family: Courier;" class="">security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000</span></div><div class=""><div class=""><font face="Courier" class="">trusted.afr.<VOLNAME>-client-6=0x000000020000000100000000</font></div><div class=""><font face="Courier" class="">trusted.afr.dirty=0x000000000000000000000000</font></div><div class=""><font face="Courier" class="">trusted.bit-rot.version=0x02000000000000005a7e0cdb000196c6</font></div><div class=""><font face="Courier" class="">trusted.gfid=<b class="">0xa65bac27fd504c899ba4457675ed5518</b></font></div><div class=""><font face="Courier" class="">trusted.pgfid.eb6d6fa2-339e-4dd7-a642-ca755d5f47cf=0x00000001</font></div></div><div class=""><br class=""></div><div class="">Which must mean that client-6 had a problem with both the data and metadata.</div><div class=""><br class=""></div><div class="">I then went to client-6 and issued the same getfattr command:</div><div class=""><br class=""></div><div class=""><div class=""><font face="Courier" class="">getfattr -d -m . -e hex <ACTUAL_PATH></font></div><div class=""><font face="Courier" class="">security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000</font></div><div class=""><font face="Courier" class="">trusted.afr.dirty=0x000000000000000000000000</font></div><div class=""><font face="Courier" class="">trusted.bit-rot.version=0x02000000000000005a7e0cdb00018323</font></div><div class=""><font face="Courier" class="">trusted.gfid=<b class="">0x06df01f614fa40fda3b628265ba36318</b></font></div><div class=""><font face="Courier" class="">trusted.pgfid.eb6d6fa2-339e-4dd7-a642-ca755d5f47cf=0x00000001</font></div></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class="">As you can see, the gfid is different between the clients for the same file path. Doing a file operation on this file via the mount results in Input/Output error. Doing a stat on the parent directory doesn’t do anything either.</div><div class=""><br class=""></div><div class="">What’s a good way to mover forward from here?</div><div class=""><br class=""></div><div class="">Unrelated: what’s <b class="">dht.linkto</b> attribute used for?</div><div class=""><br class=""></div><div class="">Thanks!</div><div class=""> Sergei</div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Mar 24, 2021, at 4:49 PM, Sergei Gerasenko <<a href="mailto:gerases@gmail.com" class="">gerases@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">I’m running gluster version 3.10.5 across 8 machines. All of the volumes are Distributed-Replicate. One of the volumes shows a never-going-away list of 13 files when I execute:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">gluster volume heal <VOLNAME> info</font></div><div class=""><br class=""></div><div class="">I’ve tried to run:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">gluster volume heal <VOLNAME> </font></div><div class=""><br class=""></div><div class="">… but nothing happens.</div><div class=""><br class=""></div><div class="">Most of the files show grid’s but there’s one that is a path. The files belong to one brick. There are about 4 clients that are version 3.12.15 and I’ve come across some info that higher version clients can create this problem, but I doubt it’s a problem.</div><div class=""><br class=""></div><div class="">What can I do to resolve this manually since gluster can’t seem to auto-heal them? I’ve searched high and low and can’t find any recipes.</div><div class=""><br class=""></div><div class="">Thanks much for any info,</div><div class=""> Sergei</div></div></div></blockquote></div><br class=""></div></body></html>