REVIEW: http://review.gluster.org/9845 (glusterd/quota : remove quota-deem-statfs and quota-timeout values when quota is disabled.) posted (#1) for review on release-3.6 by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/9845 (glusterd/quota : remove quota-deem-statfs and quota-timeout values when quota is disabled.) posted (#2) for review on release-3.6 by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/9845 (glusterd/quota : remove quota-deem-statfs and quota-timeout values when quota is disabled) posted (#3) for review on release-3.6 by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/9845 (glusterd/quota : remove quota-deem-statfs and quota-timeout values when quota is disabled.) posted (#4) for review on release-3.6 by Sachin Pandit (spandit)
REVIEW: http://review.gluster.org/9845 (glusterd/quota : remove quota-deem-statfs and quota-timeout values when quota is disabled.) posted (#5) for review on release-3.6 by Sachin Pandit (spandit)
COMMIT: http://review.gluster.org/9845 committed in release-3.6 by Raghavendra Bhat (raghavendra) ------ commit 6de7d1b23f3385d273e49977f2683ea90ee5ebed Author: Sachin Pandit <spandit> Date: Mon Oct 13 04:57:54 2014 +0530 glusterd/quota : remove quota-deem-statfs and quota-timeout values when quota is disabled. problem : If quota is disabled then all the options associated with quota is removed, except quota-deem-statfs and quota-timeout. When gluster volume info is issued then the user can see that quota is disabled whereas quota-deem-statfs and quota-timeout values still exist. Solution : remove quota-deem-statfs and quota-timeout option when quota is disabled NOTE : If features.quota-deem-statfs is turned on, it takes quota limits into consideration while estimating fs size. Change-Id: I8cca6a8f47d2355799228643aedc8fc03896cfad BUG: 1200258 Signed-off-by: Sachin Pandit <spandit> Reviewed-on: http://review.gluster.org/8924 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijaikumar Mallikarjuna <vmallika> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas> Signed-off-by: Sachin Pandit <spandit> Reviewed-on: http://review.gluster.org/9845 Reviewed-by: Raghavendra Bhat <raghavendra>
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-v3.6.3, please open a new bug report. glusterfs-v3.6.3 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] https://www.gluster.org/pipermail/gluster-users/2015-April/021669.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user