Description of problem:
gluster vol set nfs-ganesha.enable off must unexport a volume that
was already exported via nfs-ganesha. This is doesn't happen when ganesha sources above v2.1 are used.
Version-Release number of selected component (if applicable):
nfs-ganesha v2.1 and above
Steps to Reproduce:
1. Export a volume testvol via nfs-ganesha
2. Execute, gluster vol set testvol nfs-ganesha.enable off
showmount -e localhost,
testvol shouldn't be an export anymore
This happens because of a change in upstream nfs-ganesha.
REVIEW: http://review.gluster.org/8390 (gluster vol set nfs-ganesha.enable off fails to unexport volume.) posted (#1) for review on master by Meghana M (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/8390 committed in master by Vijay Bellur (email@example.com)
Author: Meghana Madhusudhan <firstname.lastname@example.org>
Date: Tue Jul 29 18:51:21 2014 +0530
gluster vol set nfs-ganesha.enable off fails to unexport volume.
Due to a parameter type change in upstream nfs-ganesha
( v2.1 and above ), gluster vol set <volname> nfs-ganesha.enable
off doesn't unexport the volume in question if it was already
A minor change in the hook script would result in the
Signed-off-by: Meghana Madhusudhan <email@example.com>
Reviewed-by: soumya k <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Humble Devassy Chirammal <firstname.lastname@example.org>
Reviewed-by: Vijay Bellur <email@example.com>
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.