Description of problem: we have a nfs option nfs.mount-rmtab, which is used to "Set the location of the cache file that is used to list all the NFS-clients that have connected through the MOUNT protocol" and the file name is " /var/lib/glusterd/nfs/rmtab" The gluster volume set help, describing the nfs.mount-rmtab option wrongly points the path for rmtab file as "/var/lib/glusterd/rmtab" whereas it should be "/var/lib/glusterd/nfs/rmtab" Version-Release number of selected component (if applicable): glusterfs-3.5 How reproducible: always Actual results: Option: nfs.mount-rmtab Default Value: /var/lib/glusterd/rmtab Description: Set the location of the cache file that is used to list all the NFS-clients that have connected through the MOUNT protocol. If this is on shared storage, all GlusterFS servers will update and output (with 'showmount') the same list. Expected results: Default Value: /var/lib/glusterd/nfs/rmtab Additional info:
REVIEW: http://review.gluster.org/8874 (nfs: 'gluster volume help' should show the correct path for nfs.mount-rmtab) posted (#1) for review on release-3.5 by Niels de Vos (ndevos)
COMMIT: http://review.gluster.org/8874 committed in release-3.5 by Niels de Vos (ndevos) ------ commit 34e15ded17e4682b5f1db8986faa8c273c014857 Author: Niels de Vos <ndevos> Date: Sun Sep 28 14:03:05 2014 +0200 nfs: 'gluster volume help' should show the correct path for nfs.mount-rmtab This has been fixed in newer releases with a more invasive change: - build: make GLUSTERD_WORKDIR rely on localstatedir http://review.gluster.org/8246 For this release, it is sufficient to only correct the help text. Change-Id: Id5db126e3b5f8b98c2810d5b5a6f7079200df612 BUG: 1147243 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/8874 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
The first (and last?) Beta for GlusterFS 3.5.3 has been released [1]. Please verify if the release solves this bug report for you. In case the glusterfs-3.5.3beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-October/018990.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
The second Beta for GlusterFS 3.5.3 has been released [1]. Please verify if the release solves this bug report for you. In case the glusterfs-3.5.3beta2 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions have been made available on [2] to make testing easier. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019359.html [2] http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.5.3beta2/
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.5.3, please reopen this bug report. glusterfs-3.5.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/announce/2014-November/000042.html [2] http://supercolony.gluster.org/pipermail/gluster-users/