+++ This bug was initially created as a clone of Bug #1120592 +++
Description of problem:
Have a distribute replicate volume (2x2), remove exactly one pair of bricks so that it becomes a replicate volume (1x2) and removing a brick from the volume by reducing the replica count to 1 fails with error message "volume remove-brick commit force: failed: Remove exactly 1 brick(s) from each subvolume.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have a distribute replicate volume of 2x2.
2. Remove a pair of bricks from the volume so that it becomes a replicate volume(1x2).
3. Remove another brick from the volume by reducing the replica count to 1 by running the command "gluster vol remove-brick <vol_name> replica 1 <brickpath> force.
It results in an error "volume remove-brick commit force: failed: Remove exactly 1 brick(s) from each subvolume.
user should be able to convert the volume to distribute type by reducing the replica count to 1.
--- Additional comment from RHEL Product and Program Management on 2014-07-17 04:53:20 EDT ---
Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
REVIEW: http://review.gluster.org/8326 (glusterd: update volinfo->subvol_count during remove-brick operation.) posted (#1) for review on master by Ravishankar N (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/8326 committed in master by Kaushal M (email@example.com)
Author: Ravishankar N <firstname.lastname@example.org>
Date: Thu Jul 17 08:30:52 2014 +0000
glusterd: update volinfo->subvol_count during remove-brick operation.
In glusterd_op_remove_brick(), volinfo->subvol_count was getting updated only if
the replica count was reduced due to which subvol_matcher_verify() gave false
errors under certain scenarios (see bug description).
updated subvol_count for every remove-brick operation.
Signed-off-by: Ravishankar N <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Atin Mukherjee <email@example.com>
Reviewed-by: Kaushal M <firstname.lastname@example.org>
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 , 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.