Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: NFS active/active cluster with gluster and NFS-ganesha, I can create dirs, but not files!
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
Old 04-13-2020
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.
 

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. ... (1 Reply)
Discussion started by: masterpengu
1 Replies

LEARN ABOUT OPENSOLARIS

scversions

scversions(1M)						  System Administration Commands					    scversions(1M)

NAME

       scversions - Sun Cluster version management

SYNOPSIS

       scversions [-c]

DESCRIPTION

       Note -

	 Beginning  with  the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
	 still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more  infor-
	 mation about the object-oriented command set, see the Intro(1CL) man page.

       The  scversions	command  commits  the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
       arguments, the scversions command prints a message indicating whether a commitment is needed.

OPERANDS

       The following operands are supported:

       -c	    Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.

		    When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
		    into  the  cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
		    rectly with other nodes in the cluster.  When the cluster is in this state, some administrative actions might be disabled  and
		    some new functionality introduced in the upgrade might be unavailable.

		    When  you  run  this  command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
		    internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new  func-
		    tionality becomes available and any administrative restrictions are removed.

		    If	a  node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
		    command has no effect because the cluster is already running at the highest possible level of functionality.

		    If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
		    ple,  if  that  node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
		    sions.  You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.

EXIT STATUS

       0	    Success

       non-zero     Failure

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWsczu			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Evolving			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       scinstall(1M)

Sun Cluster 3.2 						    17 Aug 2007 						    scversions(1M)
All times are GMT -4. The time now is 11:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy