Just to clarify my patch only takes care of introducing the required changes in 3.9 and not in 3.8. A seperate patch needs to be sent out to ensure nfs service comes up for the volumes which were created pre upgrade to 3.8 and have default configuration.<span></span><br><br>On Monday 10 October 2016, Jiffin Tony Thottan <<a href="mailto:jthottan@redhat.com">jthottan@redhat.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I am trying to list out glusterd issues with the 3.8 feature "Gluster NFS being off by default".<br>
<br>
As per current implementation,<br>
<br>
1.) On a freshly installed setup with 3.8/3.9, if u create a volume, then Gluster NFS won't<br>
<br>
come by default and in the vol info we can see " nfs.disable on"<br>
<br>
2.) For existing volumes(created in 3.7 or below), there are two possibilities<br>
<br>
a.) if there are only volumes with default configuration, Gluster NFS won't come up and in<br>
<br>
vol info "nfs.disable on" won't displayed. In volume status command pid of Gluster NFS<br>
<br>
will be N/A.<br>
<br>
b.) if there is a volume with explicit "nfs.disable off" set , then after upgrade Gluster NFS will<br>
<br>
come and export all the existing volumes and vol info will have similar value as a.)<br>
<br>
Currently three bugs[1,2,3] have opened to address these issues.<br>
<br>
As per 3.8 release note, gluster nfs should be up for all existing volumes with default<br>
<br>
configuration. We are planning to change this behavior from 3.9 onwards and Atin send out a patch[4]<br>
<br>
With his patch after upgrade all the existing volumes with default configuration will have<br>
<br>
nfs.disable value set to on explicitly in the vol info. So Gluster NFS won't export that volume at all<br>
<br>
and gluster v status does not display status of Gluster NFS server.<br>
<br>
This patch also solves bugs 2 and 3 as well<br>
<br>
[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1383006" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1383006</a> - gluster nfs not coming for existing volumes on 3.8<br>
<br>
[2] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1383005" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1383005</a> - getting n/a entry in volume status command<br>
<br>
[3] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1379223" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1379223</a> - nfs.disable: on" is not showing in Vol info by default<br>
for the 3.7.x volumes after updating to 3.9.0<br>
<br>
[4] <a href="http://review.gluster.org/#/c/15568/" target="_blank">http://review.gluster.org/#/c/<wbr>15568/</a><br>
<br>
Regards,<br>
Jiffin<br>
<br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a>Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://www.gluster.org/mailman<wbr>/listinfo/gluster-devel</a><br>
</blockquote><br><br>-- <br>--Atin<br>