The default value from help for option 'self-heal-daemon' is incorrect. The default value for 'cluster.self-heal-daemon' shows 'off' in the help, but from the source and operationally, the actual default is 'on': # gluster volume set help | less Option: cluster.self-heal-daemon Default Value: off Description: This option applies to only self-heal-daemon. Index directory crawl and automatic healing of files will not be performed if this option is turned off. I didn't check the defaults for any other volume options to see if they were correct.
REVIEW: http://review.gluster.org/6706 (cluster/afr: Change default_value for option self-heal-daemon) posted (#1) for review on master by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/6706 committed in master by Vijay Bellur (vbellur) ------ commit e435b4b059946fa823b2e22e29899cb256a48bef Author: Vijay Bellur <vbellur> Date: Wed Jan 15 11:47:26 2014 +0530 cluster/afr: Change default_value for option self-heal-daemon Change-Id: Ic3c8e179a63e82a4e416aea620796f8bb3236c7c BUG: 1052759 Signed-off-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/6706 Reviewed-by: Kaushal M <kaushal> Tested-by: Gluster Build System <jenkins.com>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users