Gudrun Mareike Amedick
2019-Nov-28 10:27 UTC
[Gluster-users] Trying to fix files that don't want to heal
Hi, I have a distributed dispersed volume with files that don't want to heal. I'm trying to fix them manually.? 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 files. They look like this: # getfattr -m. -d -e hex $brick/somepath/libssl.so.1.1 getfattr: Removing leading '/' from absolute path names # file: $brick/$somepath/libssl.so.1.1 trusted.ec.config=0x0000080602000200 trusted.ec.dirty=0x00000000000000010000000000000000 trusted.ec.size=0x00000000000a0000 trusted.ec.version=0x00000000000000040000000000000005 trusted.gfid=0xdd7dd64f6bb34b5f891a5e32fe83874f trusted.gfid2path.0c3a5b76c518ef60=0x34663064396234332d343730342d343634352d613834342d3338303532336137346632662f6c696273736c2e736f2e312e31 trusted.gfid2path.578ce2ec37aa0f9d=0x31636136323433342d396132642d343039362d616265352d6463353065613131333066632f6c696273736c2e736f2e312e31 trusted.glusterfs.quota.1ca62434-9a2d-4096-abe5-dc50ea1130fc.contri.3=0x00000000000292000000000000000001 trusted.glusterfs.quota.4f0d9b43-4704-4645-a844-380523a74f2f.contri.3=0x00000000000292000000000000000001 trusted.pgfid.1ca62434-9a2d-4096-abe5-dc50ea1130fc=0x00000001 trusted.pgfid.4f0d9b43-4704-4645-a844-380523a74f2f=0x00000001 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 hardlinks: find??$brick/$somepath ?-samefile??$brick/$someotherpath/libssl.so.1.1 $brick/$somepath/libssl.so.1 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 I fix that? Kind regards Gudrun Amedick -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 6743 bytes Desc: not available URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20191128/8af72b30/attachment.bin>
Ashish Pandey
2019-Nov-29 05:38 UTC
[Gluster-users] Trying to fix files that don't want to heal
Hey Gudrun, Could you please try to use the scripts and try to resolve it. We have written some scripts and it is in final phase to get merge - https://review.gluster.org/#/c/glusterfs/+/23380/ You can find the steps to use these scripts in README.md file --- Ashish ----- Original Message ----- From: "Gudrun Mareike Amedick" <g.amedick at uni-luebeck.de> To: "Gluster-users" <gluster-users at gluster.org> Sent: Thursday, November 28, 2019 3:57:18 PM Subject: [Gluster-users] Trying to fix files that don't want to heal Hi, I have a distributed dispersed volume with files that don't want to heal. I'm trying to fix them manually. 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 files. They look like this: # getfattr -m. -d -e hex $brick/somepath/libssl.so.1.1 getfattr: Removing leading '/' from absolute path names # file: $brick/$somepath/libssl.so.1.1 trusted.ec.config=0x0000080602000200 trusted.ec.dirty=0x00000000000000010000000000000000 trusted.ec.size=0x00000000000a0000 trusted.ec.version=0x00000000000000040000000000000005 trusted.gfid=0xdd7dd64f6bb34b5f891a5e32fe83874f trusted.gfid2path.0c3a5b76c518ef60=0x34663064396234332d343730342d343634352d613834342d3338303532336137346632662f6c696273736c2e736f2e312e31 trusted.gfid2path.578ce2ec37aa0f9d=0x31636136323433342d396132642d343039362d616265352d6463353065613131333066632f6c696273736c2e736f2e312e31 trusted.glusterfs.quota.1ca62434-9a2d-4096-abe5-dc50ea1130fc.contri.3=0x00000000000292000000000000000001 trusted.glusterfs.quota.4f0d9b43-4704-4645-a844-380523a74f2f.contri.3=0x00000000000292000000000000000001 trusted.pgfid.1ca62434-9a2d-4096-abe5-dc50ea1130fc=0x00000001 trusted.pgfid.4f0d9b43-4704-4645-a844-380523a74f2f=0x00000001 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 hardlinks: find $brick/$somepath -samefile $brick/$someotherpath/libssl.so.1.1 $brick/$somepath/libssl.so.1 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 I fix that? Kind regards Gudrun Amedick ________ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users at gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20191129/8630b23d/attachment.html>