vadud3 at gmail.com
2020-May-28 22:48 UTC
[Gluster-users] Failing to nfs mount gluster volume
[root at node1 ~]# uname -a 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 [root at node1 ~]# gluster --version glusterfs 7.5 ... [root at node1 ~]# gluster volume info Volume Name: gv0 Type: Replicate Volume ID: f33246a4-2e9a-4958-8aff-4cee815703bc Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: 192.168.1.121:/data/brick1/gv0 Brick2: 192.168.1.122:/data/brick2/gv0 Options Reconfigured: transport.address-family: inet storage.fips-mode-rchecksum: on nfs.disable: off performance.client-io-threads: off [root at node1 ~]# mount -v -t nfs -o vers=3 192.168.1.121:/gv0 /nfs_mount mount.nfs: timeout set for Thu May 28 22:48:39 2020 mount.nfs: trying text-based options 'vers=3,addr=192.168.1.121' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.1.121 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.1.121 prog 100005 vers 3 prot UDP port 20048 mount.nfs: mount(2): No such file or directory mount.nfs: mounting 192.168.1.121:/gv0 failed, reason given by server: No such file or directory -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200528/a2cb8ff8/attachment.html>
vadud3 at gmail.com
2020-May-29 16:42 UTC
[Gluster-users] Failing to nfs mount gluster volume
Turned off nfs-server service and now I am getting a different error message [root at node1 ~]# mount -vv -t nfs -o vers=3,mountproto=tcp 192.168.1.121:/gv0 /nfs_mount/ mount.nfs: timeout set for Fri May 29 16:43:30 2020 mount.nfs: trying text-based options 'vers=3,mountproto=tcp,addr=192.168.1.121,mountaddr=192.168.1.121' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=3,mountproto=tcp,addr=192.168.1.121,mountaddr=192.168.1.121' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=3,mountproto=tcp,addr=192.168.1.121,mountaddr=192.168.1.121' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: requested NFS version or transport protocol is not supported [root at node1 ~]# gluster volume info gv0 Volume Name: gv0 Type: Replicate Volume ID: f33246a4-2e9a-4958-8aff-4cee815703bc Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: 192.168.1.121:/data/brick1/gv0 Brick2: 192.168.1.122:/data/brick2/gv0 Options Reconfigured: nfs.register-with-portmap: on performance.client-io-threads: off nfs.disable: off storage.fips-mode-rchecksum: on transport.address-family: inet nfs.volume-access: read-write nfs.mount-udp: off On Thu, May 28, 2020 at 6:48 PM <vadud3 at gmail.com> wrote:> [root at node1 ~]# uname -a > 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 > > [root at node1 ~]# gluster --version > glusterfs 7.5 > ... > > [root at node1 ~]# gluster volume info > > Volume Name: gv0 > Type: Replicate > Volume ID: f33246a4-2e9a-4958-8aff-4cee815703bc > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp > Bricks: > Brick1: 192.168.1.121:/data/brick1/gv0 > Brick2: 192.168.1.122:/data/brick2/gv0 > Options Reconfigured: > transport.address-family: inet > storage.fips-mode-rchecksum: on > nfs.disable: off > performance.client-io-threads: off > > > [root at node1 ~]# mount -v -t nfs -o vers=3 192.168.1.121:/gv0 /nfs_mount > mount.nfs: timeout set for Thu May 28 22:48:39 2020 > mount.nfs: trying text-based options 'vers=3,addr=192.168.1.121' > mount.nfs: prog 100003, trying vers=3, prot=6 > mount.nfs: trying 192.168.1.121 prog 100003 vers 3 prot TCP port 2049 > mount.nfs: prog 100005, trying vers=3, prot=17 > mount.nfs: trying 192.168.1.121 prog 100005 vers 3 prot UDP port 20048 > mount.nfs: mount(2): No such file or directory > mount.nfs: mounting 192.168.1.121:/gv0 failed, reason given by server: No > such file or directory > > > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > >-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200529/cbe65f11/attachment.html>