Description of problem: gluster volume heal does nothing Version-Release number of selected component (if applicable): 3.7.13 How reproducible: inside one of bricks: [root@father brick]# ls -l gstatus-0.64-3.el7.x86_64.rpm -rw-r--r-- 2 root root 52268 июл 11 13:00 gstatus-0.64-3.el7.x86_64.rpm [root@father brick]# [root@father brick]# > gstatus-0.64-3.el7.x86_64.rpm [root@father brick]# ls -l gstatus-0.64-3.el7.x86_64.rpm -rw-r--r-- 2 root root 0 июл 11 13:54 gstatus-0.64-3.el7.x86_64.rpm [root@father brick]# so now file has 0 length. try to heal: [root@father brick]# gluster volume heal pool Launching heal operation to perform index self heal on volume pool has been successful Use heal info commands to check status [root@father brick]# ls -l gstatus-0.64-3.el7.x86_64.rpm -rw-r--r-- 2 root root 0 июл 11 13:54 gstatus-0.64-3.el7.x86_64.rpm [root@father brick]# nothing! [root@father brick]# gluster volume heal pool full Launching heal operation to perform full self heal on volume pool has been successful Use heal info commands to check status [root@father brick]# ls -l gstatus-0.64-3.el7.x86_64.rpm -rw-r--r-- 2 root root 52268 июл 11 13:00 gstatus-0.64-3.el7.x86_64.rpm [root@father brick]# full heal is OK.
After the discussion on gluster-users we came to the following conclusion: "I think it will be wise to add full heal interval to self-heal daemon." So converting this as RFE to implement the same.
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.