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
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
cmdeleteconf(1m)														  cmdeleteconf(1m)

NAME
cmdeleteconf - Delete either the cluster or the package configuration SYNOPSIS
cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...] DESCRIPTION
cmdeleteconf deletes either the entire cluster configuration, including all its packages, or only the specified package configuration. If neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all its packages. If the local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration. If only the package_name is specified, the configuration of package_name in the local cluster is deleted. If both cluster_name and pack- age_name are specified, the package must be configured in the cluster_name, and only the package package_name will be deleted. cmdelete- conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the con- figuration version. The local cluster is the cluster that the node running the cmdeleteconf command belongs to. Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can delete the configuration. To delete the cluster configuration, halt the cluster first. To delete a package configuration you must halt the package first, but you do not need to halt the cluster (it may remain up or be brought down). To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete all packages with STORAGE_GROUP defined. While deleting the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration. In this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster. If the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config- uration before doing any other Serviceguard command. Options cmdeleteconf supports the following options: -f Force the deletion of either the cluster configuration or the package configuration. -v Verbose output will be displayed. -c cluster_name Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster. -p package_name Name of an existing package to delete from the cluster. The package must be halted already. There should not be any packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only). RETURN VALUE
Upon completion, cmdeleteconf returns one of the following values: 0 Successful completion. 1 Command failed. EXAMPLES
The high availability environment contains the cluster, clusterA , and a package, pkg1. To delete package pkg1 in clusterA, do the following: cmdeleteconf -f -c clusterA -p pkg1 To delete the cluster clusterA and all its packages, do the following: cmdeleteconf -f -c clusterA AUTHOR
cmdeleteconf was developed by HP. SEE ALSO
cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m). Requires Optional Serviceguard Software cmdeleteconf(1m)
All times are GMT -4. The time now is 06:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy