NFS active/active cluster with gluster and NFS-ganesha, I can create dirs, but not files! Post: 303045800

Sponsored Content

Top Forums UNIX for Advanced & Expert Users NFS active/active cluster with gluster and NFS-ganesha, I can create dirs, but not files! Post 303045800 by Linusolaradm1 on Monday 13th of April 2020 05:52:02 PM

04-13-2020

Registered User

NFS active/active cluster with gluster and NFS-ganesha, I can create dirs, but not files!

Following this fantastic guide I finally setup an active working active/active nfs4 cluster.
The setup is not too difficult: two servers with ganesha+glusterfs other two with haproxy and keepalived.
The cluster works fine, from one client I have mount the nfs share called "nfshare" without problem

Code:

mount -t nfs4

nfsserver:/nfsshare on /mnt type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.2.0.170,local_lock=none,addr=10.2.0.7)

I have created some dirs on mnt and works perfect(there are replicated on nfsgluster servers). I have also rebooted for testing the nfs server one or two, and after a very little downtime (2 seconds) the connection is up and working.
The problem is..mkdir works, but every file operation(dd,cp,touch) fails(stuck,freeze until ctrl+c is pressed).

On both the nfs servers and keepalived servers there is no problem with selinux

Code:

grep -i denied /var/log/audit/audit.log

What can be?Why mkdir works and file operation not?

--- Post updated at 05:52 PM ---

Solution found, ganesha was misconfigured, I have forgot to add the ports for services.

Linusolaradm1

View Public Profile for Linusolaradm1

Find all posts by Linusolaradm1

We Also Found This Discussion For You

1. AIX

Very Active NFS and Disk Usage

Here is the scenario... NFS share that is accessed every few minutes by approx 70 systems (AIX 5.3/6.1). Filesystem space is being eaten up rapidly according to df however du numbers really never change. lsof and fuser cannot see any unlinked files on either the NFS server or remote clients. ...

LEARN ABOUT HPUX

cmrunnode

cmrunnode(1m)															     cmrunnode(1m)

NAME

       cmrunnode - run a node in a high availability cluster

SYNOPSIS

       cmrunnode [-v] [node_name...]  [-t | -w none]

DESCRIPTION

       cmrunnode  causes  a node to start its cluster daemon to join the existing cluster.  This command verifies the network configuration before
       causing the node to start its cluster daemon.

       To start a cluster on one of its nodes, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the clus-
       ter configuration file. See access policy in cmquerycl(1m).

       Starting  a node will not cause any active packages to be moved to the new node.  However, if a package is DOWN, has its switching enabled,
       and is able to run on the new node, that package will automatically run there.

       If node_name is not specified, the cluster daemon will be started on the local node and will join the existing cluster.

   Options
       cmrunnode supports the following options:

	      -v   Verbose output will be displayed.

	      -t   Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. The	-w
		   option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet
		   any external dependencies such as EMS resources, package subnets, and storage.

	      node_name...
		   Start the cluster daemon on the specified node(s).

	      -w none
		   By default network probing is performed to check that the network connectivity is the same as when the cluster was  configured.
		   Any	anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should
		   only be used if this network configuration is known to be correct from a recent check.

RETURN VALUE

       cmrunnode returns the following value:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       Run the cluster daemon on the current node:

	      cmrunnode

       Run the cluster daemons on node1 and node2:

	      cmrunnode node1 node2

AUTHOR

       cmrunnode was developed by HP.

SEE ALSO

       cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmruncl(1m), cmviewcl(1m), cmeval(1m).

						      Requires Optional Serviceguard Software					     cmrunnode(1m)

We Also Found This Discussion For You

1. AIX

Very Active NFS and Disk Usage

Discussion started by: masterpengu

LEARN ABOUT HPUX

cmrunnode