REVIEW: http://review.gluster.org/13470 (TIER: avoid reset of ctr-enabled during the issue of gluster v reset) posted (#1) for review on master by hari gowtham (email@example.com)
COMMIT: http://review.gluster.org/13470 committed in master by Jeff Darcy (firstname.lastname@example.org)
Author: hari <email@example.com>
Date: Thu Feb 18 16:58:28 2016 +0530
TIER: avoid reset of ctr-enabled during the issue of gluster v reset
Signed-off-by: hari <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
Reviewed-by: Dan Lambright <firstname.lastname@example.org>
Tested-by: hari gowtham <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
Reviewed-by: Jeff Darcy <firstname.lastname@example.org>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.