<div dir="ltr">I am running gluster 7.5 on CentOS 7 which does not have gnfs compiled. <div><br></div><div>I had to build it from source with <font face="monospace">./configure --enable-gnfs --without-libtirpc</font>[1] and then I could nfs mount the gluster volume</div><div><br></div><div>[1] <a href="https://docs.gluster.org/en/latest/Developer-guide/Building-GlusterFS/">https://docs.gluster.org/en/latest/Developer-guide/Building-GlusterFS/</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 29, 2020 at 12:42 PM <<a href="mailto:vadud3@gmail.com">vadud3@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Turned off nfs-server service and now I am getting a different error message<div><br></div><div>[root@node1 ~]# mount -vv -t nfs -o vers=3,mountproto=tcp 192.168.1.121:/gv0 /nfs_mount/<br>mount.nfs: timeout set for Fri May 29 16:43:30 2020<br>mount.nfs: trying text-based options 'vers=3,mountproto=tcp,addr=192.168.1.121,mountaddr=192.168.1.121'<br>mount.nfs: prog 100003, trying vers=3, prot=6<br>mount.nfs: portmap query retrying: RPC: Program not registered<br>mount.nfs: prog 100003, trying vers=3, prot=17<br>mount.nfs: portmap query failed: RPC: Program not registered<br>mount.nfs: trying text-based options 'vers=3,mountproto=tcp,addr=192.168.1.121,mountaddr=192.168.1.121'<br>mount.nfs: prog 100003, trying vers=3, prot=6<br>mount.nfs: portmap query retrying: RPC: Program not registered<br>mount.nfs: prog 100003, trying vers=3, prot=17<br>mount.nfs: portmap query failed: RPC: Program not registered<br>mount.nfs: trying text-based options 'vers=3,mountproto=tcp,addr=192.168.1.121,mountaddr=192.168.1.121'<br>mount.nfs: prog 100003, trying vers=3, prot=6<br>mount.nfs: portmap query retrying: RPC: Program not registered<br>mount.nfs: prog 100003, trying vers=3, prot=17<br>mount.nfs: portmap query failed: RPC: Program not registered<br>mount.nfs: requested NFS version or transport protocol is not supported<br></div><div><br></div><div>[root@node1 ~]# gluster volume info gv0<br><br>Volume Name: gv0<br>Type: Replicate<br>Volume ID: f33246a4-2e9a-4958-8aff-4cee815703bc<br>Status: Started<br>Snapshot Count: 0<br>Number of Bricks: 1 x 2 = 2<br>Transport-type: tcp<br>Bricks:<br>Brick1: 192.168.1.121:/data/brick1/gv0<br>Brick2: 192.168.1.122:/data/brick2/gv0<br>Options Reconfigured:<br>nfs.register-with-portmap: on<br>performance.client-io-threads: off<br>nfs.disable: off<br>storage.fips-mode-rchecksum: on<br>transport.address-family: inet<br>nfs.volume-access: read-write<br>nfs.mount-udp: off<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 28, 2020 at 6:48 PM <<a href="mailto:vadud3@gmail.com" target="_blank">vadud3@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>[root@node1 ~]# uname -a<br>Linux node1 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux<br></div><div><br></div><div>[root@node1 ~]# gluster --version<br>glusterfs 7.5<br></div><div>...</div><div><br></div><div>[root@node1 ~]# gluster volume info<br><br>Volume Name: gv0<br>Type: Replicate<br>Volume ID: f33246a4-2e9a-4958-8aff-4cee815703bc<br>Status: Started<br>Snapshot Count: 0<br>Number of Bricks: 1 x 2 = 2<br>Transport-type: tcp<br>Bricks:<br>Brick1: 192.168.1.121:/data/brick1/gv0<br>Brick2: 192.168.1.122:/data/brick2/gv0<br>Options Reconfigured:<br>transport.address-family: inet<br>storage.fips-mode-rchecksum: on<br>nfs.disable: off<br>performance.client-io-threads: off<br></div><div><br></div><div><br></div>[root@node1 ~]# mount -v -t nfs -o vers=3 192.168.1.121:/gv0 /nfs_mount<br>mount.nfs: timeout set for Thu May 28 22:48:39 2020<br>mount.nfs: trying text-based options 'vers=3,addr=192.168.1.121'<br>mount.nfs: prog 100003, trying vers=3, prot=6<br>mount.nfs: trying 192.168.1.121 prog 100003 vers 3 prot TCP port 2049<br>mount.nfs: prog 100005, trying vers=3, prot=17<br>mount.nfs: trying 192.168.1.121 prog 100005 vers 3 prot UDP port 20048<br>mount.nfs: mount(2): No such file or directory<br>mount.nfs: mounting 192.168.1.121:/gv0 failed, reason given by server: No such file or directory<div><br></div><div><br clear="all"><div><br></div>-- <br><div dir="ltr">Asif Iqbal<br>PGP Key: 0xE62693C5 KeyServer: <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>A: Because it messes up the order in which people normally read text.<br>Q: Why is top-posting such a bad thing?<br><br></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr">Asif Iqbal<br>PGP Key: 0xE62693C5 KeyServer: <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>A: Because it messes up the order in which people normally read text.<br>Q: Why is top-posting such a bad thing?<br><br></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Asif Iqbal<br>PGP Key: 0xE62693C5 KeyServer: <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>A: Because it messes up the order in which people normally read text.<br>Q: Why is top-posting such a bad thing?<br><br></div>