The Gluster NFS server has it's own NLM (nlockmgr) implementation. You
said that you have the nfslock service on. Can you turn that off and
On Tue, Jan 27, 2015 at 11:21 AM, David F. Robinson
If that was true, wouldn't it not "Connection refused" because
the kernel nfs is listening?
On January 26, 2015 9:43:34 PM PST, Kaushal M
Seems like you have the kernel NFS server running. The
`rpcinfo -p` output you provided shows that there are other
mountd, nfs and nlockmgr services running your system.
Gluster NFS server requires that the kernel nfs services be
disabled and not running.
~kaushal
On Tue, Jan 27, 2015 at 10:56 AM, David F. Robinson
[root@gfs01bkp ~]# gluster volume status homegfs_bkp
Status of volume: homegfs_bkp
Gluster process
Port Online Pid
------------------------------__------------------------------__------------------
Brick gfsib01bkp.corvidtec.com:/__data/brick01bkp/homegfs
_bkp
49152 Y 4087
Brick gfsib01bkp.corvidtec.com:/__data/brick02bkp/homegfs
_bkp
49155 Y 4092
NFS Server on localhost
N/A N N/A
Task Status of Volume homegfs_bkp
------------------------------__------------------------------__------------------
Task : Rebalance
ID : 6d4c6c4e-16da-48c9-9019-__dccb7d2cfd66
Status : completed
------ Original Message ------
Sent: 1/26/2015 11:51:13 PM
Subject: Re: v3.6.2
On 01/27/2015 07:33 AM, Pranith Kumar Karampuri wrote:
On 01/26/2015 09:41 PM, Justin Clift wrote:
On 26 Jan 2015, at 14:50, David F. Robinson
I have a server with v3.6.2 from which I
cannot mount using NFS. The
FUSE mount works, however, I cannot get
the NFS mount to work. From
/var/log/message:
Jan 26 09:27:28 gfs01bkp mount[2810]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:27:53 gfs01bkp mount[4456]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:29:28 gfs01bkp mount[2810]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:29:53 gfs01bkp mount[4456]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:31:28 gfs01bkp mount[2810]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:31:53 gfs01bkp mount[4456]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:33:28 gfs01bkp mount[2810]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:33:53 gfs01bkp mount[4456]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:35:28 gfs01bkp mount[2810]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
Jan 26 09:35:53 gfs01bkp mount[4456]:
mount to NFS server
'gfsib01bkp.corvidtec.com
failed: Connection refused, retrying
I also am continually getting the
following errors in
/var/log/glusterfs:
[root@gfs01bkp glusterfs]# tail -f
etc-glusterfs-glusterd.vol.log
[2015-01-26 14:41:51.260827] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:41:54.261240] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:41:57.261642] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:00.262073] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:03.262504] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:06.262935] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:09.263334] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:12.263761] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:15.264177] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:18.264623] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:21.265053] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
[2015-01-26 14:42:24.265504] W
[socket.c:611:__socket_rwv]
0-management: readv on
/var/run/__1f0cee5a2d074e39b32ee5a81c70e6__8c.socket
failed (Invalid
argument)
I believe this error message comes when the
socket file is not present.
I see the following commit which changed the
location of the sockets.
May be Atin may know more. about this: +Atin.
Can we get the output of 'gluster volume status' for
the volume which
you are trying to mount?
~Atin
Pranith
^C
Also, when I try to NFS mount my
gluster volume, I am getting
Any chance there's a network or host based
firewall stopping some of
the ports?
+ Justin
--
An open source, distributed file system
scaling to several
petabytes, and handling thousands of clients.
My personal twitter:
twitter.com/realjustinclift
_________________________________________________
Gluster-devel mailing list
_________________________________________________
Gluster-users mailing list
------------------------------------------------------------------------
Gluster-devel mailing list
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
