Red Hat Bugzilla – Bug 826465
Gluster - Backend: Unpredictable results when setting nfs.disable to on
Last modified: 2013-02-15 01:47:50 EST
Created attachment 587656 [details]
Volumes -> select volume -> Volume Options -> nfs.disable (by default set to "off") -> Edit -> change "off" to "on" -> OK -> the result is that nfs.disable remains "off" but a new key is added with the name "nfs.enable-ino32" and with the value "on".
I suspect that it could be a gluster bug.
1, Can yoy send me 'gluster --version' output of the host?
2. Can you attach respective vdsm log?
Created attachment 588014 [details]
Attaching vdsm.log (from a new run of the same flow).
glusterfs 3.3.0qa41 built on May 16 2012 23:00:40
This is happening because the "gluster volume set help-xml" command is not returning "nfs.disable" as one of the options. Assigning to Vijay for resolution.
*** Bug 826942 has been marked as a duplicate of this bug. ***
seems to me as duplicate of bug 828027. That bug is closed as fixed with below comment:
The patch has been accepted into both master & release-3.3 branches upstream.
The respective commits are,
4b09879 (glusterd: nfs.disable fix for "volume set help") for master, reviewed
948b9a5 (glusterd: nfs.disable fix for "volume set help") for release-3.3,
reviewed at http://review.gluster.org/3881
also checked on 3.4.0qa4, and below is the output
[root@thinkpad raghu]# gluster volume set help-xml | xmllint --format - | grep nfs.disable