Description of problem: Since snapshot commands would internally trigger barrier brick op, barrier option should not be exposed to the customer and should have NO_DOC doctype.
REVIEW: http://review.gluster.org/8572 (barrier: features.barrier should be a NO_DOC) posted (#1) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/8572 (barrier: features.barrier should be a NO_DOC) posted (#2) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/8572 committed in master by Kaushal M (kaushal) ------ commit 88159becd90d40323ecfc24cf40813538c9204cc Author: Atin Mukherjee <amukherj> Date: Sat Aug 30 17:41:01 2014 +0530 barrier: features.barrier should be a NO_DOC features.barrier is turned on/off internally by snapshot feature and hence it should not be exposed to the customer and this option should not be documented. Change-Id: Id9a421f94e291f1dc77044904bb18dd730c2d43e BUG: 1135691 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/8572 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal>
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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user