Description of problem: For several days, we have had an issue with a high amount of failed heal entries in one of our Gluster nodes. Enviroment running 2 nodes, 3 Gluster volumes replicated on the 2 nodes. gluster_volume_info:cluster.quorum-count: 1 gluster_volume_info:cluster.quorum-type: fixed Version-Release number of selected component (if applicable): glusterfs-3.7.5-19.el7rhgs.x86_64 glusterfs-api-3.7.5-19.el7rhgs.x86_64 glusterfs-cli-3.7.5-19.el7rhgs.x86_64 glusterfs-client-xlators-3.7.5-19.el7rhgs.x86_64 glusterfs-fuse-3.7.5-19.el7rhgs.x86_64 glusterfs-libs-3.7.5-19.el7rhgs.x86_64 glusterfs-server-3.7.5-19.el7rhgs.x86_64 pcp-pmda-gluster-3.10.6-2.el7.x86_64 For some reason some files are being healed but constantly increasing the number on thousands potential files to health according to the statics. for some reason those are are not being healed.
Extending the 1st comment/description all clients are using glusterfs.fuse with the acl mount option the number of unhealed files are increasing by thousands every day during at least 5 days.
Hello Ravi, From comment #17, it looks like we were not able to completely RCA this issue. Is there anything more which can be done with existing data? Apart from this, in comment #16, I had some questions. Could you please have a look and reply to that. -Bipin Kunal
I even see that this bug was earlier marked as dependent on bug #1339765 but it was removed later removed, Any reason for that? -Bipin Kunal