[Gluster-users] NFS mounts with glusterd on localhost - reliable or not?
mangoo at wpkg.org
Thu Jul 12 07:56:32 UTC 2012
are NFS mounts made on a single server (i.e. where glusterd is running)
supposed to be stable (with gluster 3.2.6)?
I'm using the following line in /etc/fstab:
localhost:/sites /var/ftp/sites nfs _netdev,mountproto=tcp,nfsvers=3,bg 0 0
The problem is, after some time (~1-6 hours), I'm no longer able to
access this mount.
[49609.832274] nfs: server localhost not responding, still trying
[49910.639351] nfs: server localhost not responding, still trying
[50211.446433] nfs: server localhost not responding, still trying
What's worse, whenever this happens, *all* other servers in the cluster
(it's a 10-server distributed volume) will destabilise - their load
average will grow, and eventually their gluster mount becomes
unresponsive, too (other servers use normal gluster mounts).
At this point, I have to kill all gluster processes, start glusterd
again, mount (on servers using gluster mount).
Is it expected behaviour with gluster and NFS mounts on localhost? Can
it be caused by some kind of deadlock? Any workarounds?
More information about the Gluster-users