Description of problem: Even if the geo-rep session is stopped, volume can't be stopped >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [root@redlemon ~]# gluster v stop master Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y volume stop: master: failed: geo-replication sessions are active for the volume 'master'. Use 'volume geo-replication status' command for more info. Use 'force' option to ignore and stop the volume. [root@redlemon ~]# gluster v geo stat NODE MASTER SLAVE HEALTH UPTIME ------------------------------------------------------------------------------------- redlemon.blr.redhat.com master ssh://10.70.43.25::slave Stopped N/A redcloud.blr.redhat.com master ssh://10.70.43.25::slave Stopped N/A redmoon.blr.redhat.com master ssh://10.70.43.25::slave Stopped N/A redwood.blr.redhat.com master ssh://10.70.43.25::slave Stopped N/A >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Version-Release number of selected component (if applicable):glusterfs-3.4.0.28rhs-1.el6rhs.x86_64 How reproducible:Happens everytime Steps to Reproduce: 1.create and start master and slave volume 2.create and start geo-rep relationship between master and slave. 3.stop the geo-rep session master and slave 4.try to stop the master volume. Actual results:It won't allow to stop the volume, until geo-rep session is deleted Expected results: It should allow to stop the volume, if the geo-rep is stopped. It shouldn't expect to delete the geo-rep session only. Additional info:
This is the patch http://review.gluster.org/6821 which is merged.
Fixed in Version: glusterfs-3.6.0.2-1
*** Bug 992939 has been marked as a duplicate of this bug. ***
Fixed as a part of the rebase, marking the bz for Denali
verified on the build glusterfs-3.6.0.12-1.el6rhs.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1278.html