Hi , for the gfid I use method 2 described in https://docs.gluster.org/en/latest/Troubleshooting/gfid-to-path/ . Once you identify the file you can check the extended attributes on all bricks for any mismatch. Usually the gfid is the culprit on replica volumes.
By the way, what is your volume type (gluster vol info) ? Best Regards, Strahil Nikolov На 2 юли 2020 г. 15:00:01 GMT+03:00, gluster-devel-requ...@gluster.org написа: >Send Gluster-devel mailing list submissions to > gluster-devel@gluster.org > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gluster.org/mailman/listinfo/gluster-devel >or, via email, send a message with subject or body 'help' to > gluster-devel-requ...@gluster.org > >You can reach the person managing the list at > gluster-devel-ow...@gluster.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Gluster-devel digest..." > > >Today's Topics: > > 1. heal info output (Emmanuel Dreyfus) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Thu, 2 Jul 2020 03:05:27 +0200 >From: m...@netbsd.org (Emmanuel Dreyfus) >To: gluster-devel@gluster.org (Gluster Devel) >Subject: [Gluster-devel] heal info output >Message-ID: <1osw8ax.rmfglc10lttijm%m...@netbsd.org> > >Hello > >gluster volume heal info show me questionable entries. I wonder if >these >are bugs, or if I shoud handle them and how. > >bidon# gluster volume heal gfs info >Brick bidon:/export/wd0e_tmp >Status: Connected >Number of entries: 0 > >Brick baril:/export/wd0e >/.attribute/system ><gfid:7f3a4aa5-7a49-4f50-a166-b345cdf0616c> >Status: Connected >Number of entries: 2 > >(...) >Brick bidon:/export/wd2e ><gfid:d616f804-0579-4649-8d8e-51ec4cf0e131> ><gfid:f4eb6db3-8341-454b-9700-81ad4ebca61e> >/owncloud/data ><gfid:43b80fd9-a577-4568-b400-2d80bb4d25ad> ><gfid:7253faad-6843-4321-a63f-17671237d607> ><gfid:da055475-43c0-4157-b4f1-30b3647bc0b6> ><gfid:02f4f38e-f351-4bb8-bd43-cad64ba5a4f5> > >There are three cases: >1) /.attribute directory is special on NetBSD, it is where extended >attributes are stored for the filesystem. The posix xlator takes care >of >screening it, but there must be some other softrware component that >should learn it must disregeard it. Hints are welcome about where I >should look at. > >2) /owncloud/data is a directory. mode, owner and groups are the same >on bricks. Why is it listed here? > >3) <gfid:...> What should I do with this? _______________________________________________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
