REVIEW: http://review.gluster.org/11412 (ganesha: volinfo is not persisted after modifying options) posted (#1) for review on master by Rajesh Joseph (rjoseph)
COMMIT: http://review.gluster.org/11412 committed in master by Niels de Vos (ndevos) ------ commit b15ba49546172786fb0416dd5a2802f638cacbb2 Author: Rajesh Joseph <rjoseph> Date: Thu Jun 25 16:10:29 2015 +0530 ganesha: volinfo is not persisted after modifying options ganesha disables gluster NFS when it is enabled. Gluster NFS is disabled by storing nfs.disable as "on" in volinfo of each volume in the cluster. But volinfo is not persisted after the change. Due to which wrong info is passed in handshake leading to volume checksum mismatch. Bug: 1235751 Change-Id: Icd642f5068cc934bb77676fb8ef71b958a7b7384 Signed-off-by: Rajesh Joseph <rjoseph> Reviewed-on: http://review.gluster.org/11412 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Meghana M <mmadhusu> Reviewed-by: soumya k <skoduri> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos>
changing version to mainline in order to retire pre-release. If you know the appropriate, correct version for this bug, please set it.
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 [1] a while back, and packages for several distributions should be available by now. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/