<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hey Gudrun,<br></div><div><br></div><div>Could you please try to use the scripts and try to resolve it. <br></div><div>We have written some scripts and it is in final phase to get merge - <br></div><div><a href="https://review.gluster.org/#/c/glusterfs/+/23380/">https://review.gluster.org/#/c/glusterfs/+/23380/</a></div><div><br></div><div>You can find the steps to use these scripts in README.md file<br></div><div><br></div><div>---<br></div><div>Ashish<br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Gudrun Mareike Amedick" <g.amedick@uni-luebeck.de><br><b>To: </b>"Gluster-users" <gluster-users@gluster.org><br><b>Sent: </b>Thursday, November 28, 2019 3:57:18 PM<br><b>Subject: </b>[Gluster-users] Trying to fix files that don't want to heal<br><div><br></div>Hi,<br><div><br></div>I have a distributed dispersed volume with files that don't want to heal. I'm trying to fix them manually. <br><div><br></div>I'm currently working on a file that is present on all bricks, GFID exists in .glusterfs-structure and getfattr shows identical attributes for all<br>files. They look like this:<br><div><br></div># getfattr -m. -d -e hex $brick/somepath/libssl.so.1.1<br>getfattr: Removing leading '/' from absolute path names<br># file: $brick/$somepath/libssl.so.1.1<br>trusted.ec.config=0x0000080602000200<br>trusted.ec.dirty=0x00000000000000010000000000000000<br>trusted.ec.size=0x00000000000a0000<br>trusted.ec.version=0x00000000000000040000000000000005<br>trusted.gfid=0xdd7dd64f6bb34b5f891a5e32fe83874f<br>trusted.gfid2path.0c3a5b76c518ef60=0x34663064396234332d343730342d343634352d613834342d3338303532336137346632662f6c696273736c2e736f2e312e31<br>trusted.gfid2path.578ce2ec37aa0f9d=0x31636136323433342d396132642d343039362d616265352d6463353065613131333066632f6c696273736c2e736f2e312e31<br>trusted.glusterfs.quota.1ca62434-9a2d-4096-abe5-dc50ea1130fc.contri.3=0x00000000000292000000000000000001<br>trusted.glusterfs.quota.4f0d9b43-4704-4645-a844-380523a74f2f.contri.3=0x00000000000292000000000000000001<br>trusted.pgfid.1ca62434-9a2d-4096-abe5-dc50ea1130fc=0x00000001<br>trusted.pgfid.4f0d9b43-4704-4645-a844-380523a74f2f=0x00000001<br><div><br></div>pgfid is "parent gfid" right? Both GFID's refer to a dir in my volume, both of those dirs contain a file named libssl.so.1.1. They seem to be<br>hardlinks:<br><div><br></div>find $brick/$somepath -samefile $brick/$someotherpath/libssl.so.1.1<br>$brick/$somepath/libssl.so.1<br><div><br></div>This exceeds the limits of my GlusterFS knowledge. Is that something that can/should happen? If not, is it the reason that file won't heal and how do<br>I fix that?<br><div><br></div>Kind regards<br><div><br></div>Gudrun Amedick<br>________<br><div><br></div>Community Meeting Calendar:<br><div><br></div>APAC Schedule -<br>Every 2nd and 4th Tuesday at 11:30 AM IST<br>Bridge: https://bluejeans.com/441850968<br><div><br></div>NA/EMEA Schedule -<br>Every 1st and 3rd Tuesday at 01:00 PM EDT<br>Bridge: https://bluejeans.com/441850968<br><div><br></div>Gluster-users mailing list<br>Gluster-users@gluster.org<br>https://lists.gluster.org/mailman/listinfo/gluster-users<br></div><div><br></div></div></body></html>