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
PG_CTLCLUSTER(8)					 Debian PostgreSQL infrastructure					  PG_CTLCLUSTER(8)

NAME
pg_ctlcluster - start/stop/restart/reload a PostgreSQL cluster SYNOPSIS
pg_ctlcluster [options] cluster-version cluster-name action -- [pg_ctl options] where action = start|stop|restart|reload|promote DESCRIPTION
This program controls the postmaster server for a particular cluster. It essentially wraps the pg_ctl(1) command. It determines the cluster version and data path and calls the right version of pg_ctl with appropriate configuration parameters and paths. You have to start this program as the user who owns the database cluster or as root. ACTIONS
start A log file for this specific cluster is created if it does not exist yet (by default, /var/log/postgresql/postgresql-cluster- version-cluster-name.log), and a PostreSQL server process (postmaster(1)) is started on it. Exits with 0 on success, with 2 if the server is already running, and with 1 on other failure conditions. stop Stops the postmaster(1) server of the given cluster. By default, "smart" mode is used, which waits until all clients disconnected. With the --force option the "fast" mode is used which rolls back all active transactions, disconnects clients immediately and thus shuts down cleanly. If that does not work, shutdown is attempted again in "immediate" mode, which can leave the cluster in an inconsistent state and thus will lead to a recovery run at the next start. If this still does not help, the postmaster process is killed. Exits with 0 on success, with 2 if the server is not running, and with 1 on other failure conditions. This mode should only be used when the machine is about to be shut down. restart Stops the server if it is running and starts it (again). reload Causes the configuration files to be re-read without a full shutdown of the server. promote Commands a running standby server to exit recovery and begin read-write operations. OPTIONS
-o option Pass given option as command line option to the postmaster process. It is possible to specify -o multiple times. See postmaster(1) for a description of valid options. pg_ctl options Pass given pg_ctl options as command line options to pg_ctl. See pg_ctl(1) for a description of valid options. FILES
/etc/postgresql/cluster-version/cluster-name/pg_ctl.conf This configuration file contains cluster specific options to be passed to pg_ctl(1). SEE ALSO
pg_ctl(1), pg_wrapper(1), pg_lsclusters(1), postmaster(1) AUTHOR
Martin Pitt <mpitt@debian.org> Debian 2012-10-08 PG_CTLCLUSTER(8)
All times are GMT -4. The time now is 11:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy