Scrub and bitd reconfigure functions not been calling if quota is not enabled 0n that valume.
REVIEW: http://review.gluster.org/10622 (glusterd: bitd and scrub reconfiguring functions not been calling.) posted (#1) for review on master by Anand Nekkunti (anekkunt)
REVIEW: http://review.gluster.org/10622 (glusterd: bitd and scrub re configuring functions not been calling.) posted (#2) for review on master by Anand Nekkunti (anekkunt)
REVIEW: http://review.gluster.org/10622 (glusterd: bitd and scrub reconfiguring functions not been calling.) posted (#3) for review on master by Anand Nekkunti (anekkunt)
REVIEW: http://review.gluster.org/10622 (glusterd: bitd and scrub reconfiguring functions not been calling.) posted (#4) for review on master by Anand Nekkunti (anekkunt)
REVIEW: http://review.gluster.org/10622 (glusterd: Invoking daemon reconfigure functions correctly) posted (#7) for review on master by Anand Nekkunti (anekkunt)
COMMIT: http://review.gluster.org/10703 committed in release-3.7 by Krishnan Parthasarathi (kparthas) ------ commit 8cbca98c1c13c632a616ceedd5b1bbf5ed57a4b6 Author: anand <anekkunt> Date: Thu May 7 12:23:25 2015 +0530 glusterd: Invoking daemon reconfigure functions correctly Problem : Scrub and bitd reconfigure functions were not invoking if quota is not enabled. Reason : In glusterd_svcs_reconfigure, if quota is not enabled then it is returning in the middle of the function without calling bitd and scrub reconfigure functions. Fix : If quota is not enable on volume, skip quota reconfigure and continue for other daemon reconfigure. This patch also address the state dump issue for bitd and quotad (logs the scrub and bitd info into state dump). Change-Id: I39ea004b70c95543c08496245be595b3ea044a29 BUG: 1219355 Signed-off-by: anand <anekkunt> Reviewed-on: http://review.gluster.org/10622 Reviewed-by: Atin Mukherjee <amukherj> Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal> (cherry picked from commit 5faf4801bd6839cec58324a45dec31f977992236) Reviewed-on: http://review.gluster.org/10703 Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
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.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user