[ovirt-users] GlusterFS Centos 7 unable to mount NFS on gluster members

[Donny Davis]

Here is a quick rundown of the system, and the problem.

 

All hosts on centOS 7 fully up to date

GlusterFS is running on 6 servers, 3x2 distribute/replicate. 

CTDB is running on all hosts

I am unable to mount via nfs the exported volume on any of the gluster
server members.

 

I am able to mount, read, write, umount from any server that is not a
gluster member. 

 

Topology - all are hostnames that are resolvable 

Gluster Members

Node1

Node2

Node3

Node4

Node5

Node6

 

CTDB Virtual IP/Hostname

SharedNFS

 

Test Machine

Test1

 

Gluster Volumes

Engine

Data

 

I am trying to bring up hosted-engine using nfs using the gluster members

I run hosted-engine -deploy

Nfsv3

 

Host:/path sharednfs:/engine

Error while mounting specified storage path: mount.nfs: an incorrect mount
option was specified

 

Ok well lets try that without using the hosted-engine script

 

Mount -v -t nfs -o vers=3 sharednfs:/engine /tmp

mount.nfs: timeout set for Mon Jan 12 22:00:08 2015

mount.nfs: trying text-based options 'vers=3,lock=Flase,addr=192.168.0.240

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 192.168.0.240 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: portmap query retrying: RPC: Program not registered

mount.nfs: prog 100005, trying vers=3, prot=6

mount.nfs: trying 192.168.0.240 prog 100005 vers 3 prot TCP port 38465

mount.nfs: mount(2): Invalid argument

mount.nfs: an incorrect mount option was specified

 

 

[root at node4 ~]# systemctl status rpcbind

rpcbind.service - RPC bind service

   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; enabled)

   Active: active (running) since Mon 2015-01-12 20:01:13 EST; 1h 57min ago

  Process: 1349 ExecStart=/sbin/rpcbind -w ${RPCBIND_ARGS} (code=exited,
status=0/SUCCESS)

Main PID: 1353 (rpcbind)

   CGroup: /system.slice/rpcbind.service

           L-1353 /sbin/rpcbind -w

 

Jan 12 20:01:13 node4 systemd[1]: Starting RPC bind service...

Jan 12 20:01:13 node4 systemd[1]: Started RPC bind service.

Jan 12 21:19:22 node4 systemd[1]: Started RPC bind service.

 

 

Ummm: this makes no sense:. 

[root at test1 ~]# mount -v -o vers=3 -t nfs 192.168.0.240:/engine /tmp

mount.nfs: timeout set for Mon Jan 12 20:02:58 2015

mount.nfs: trying text-based options 'vers=3,addr=192.168.0.240

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 192.168.0.240 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: portmap query retrying: RPC: Program not registered

mount.nfs: prog 100005, trying vers=3, prot=6

mount.nfs: trying 192.168.0.240 prog 100005 vers 3 prot TCP port 38465

192.168.0.240:/engine on /tmp type nfs (rw,vers=3)

 

 

 

On the test machine mounts the nfs share with no problems. I have confirmed
this does not work on a single machine that is part of the gluster.  And any
other machine is able to mount the exact same share, with the exact same
parameters: on the exact same OS:.

 

I am at a loss

 

Donny D

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150112/ea82c5c3/attachment-0001.html>