OCF_HEARTBEAT_NFSSER(7) | OCF resource agents | OCF_HEARTBEAT_NFSSER(7) |
NAME
ocf_heartbeat_nfsserver - Manages an NFS server
SYNOPSIS
nfsserver [start | stop | monitor | meta-data | validate-all]
DESCRIPTION
Nfsserver helps one to manage the Linux nfs server as a failover-able resource in Linux-HA. It depends on Linux specific NFS implementation details, so is considered not portable to other platforms yet.
SUPPORTED PARAMETERS
nfs_init_script
(optional, string, default "auto detected")
nfsv4_only
(optional, boolean, default false)
nfs_no_notify
(optional, boolean, default false)
nfs_notify_foreground
(optional, boolean, default false)
nfs_smnotify_retry_time
(optional, integer, no default)
nfs_server_scope
If the server scope is different, the client should not attempt to reclaim locks. In this situation, no lock reclaim is possible. Any attempt to re-obtain the locks with non-reclaim operations is problematic since there is no guarantee that the existing filehandles will be recognized by the new server, or that if recognized, they denote the same objects. It is best to treat the locks as having been revoked by the reconfiguration event.
For lock reclaim to even be attempted, we have to define and set the same server scope for NFSD on all cluster nodes in the NFS failover cluster.
This agent won't "guess" a suitable server scope name for you, you need to explicitly specify this. But without it, NFSv4 lock reclaim after failover won't work properly. Suggested value: the failover "service IP".
(optional, string, no default)
nfs_ip
(optional, string, no default)
nfs_shared_infodir
(optional, string, no default)
rpcpipefs_dir
(optional, string, default "/var/lib/nfs/rpc_pipefs")
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
stop
monitor
meta-data
validate-all
EXAMPLE CRM SHELL
The following is an example configuration for a nfsserver resource using the crm(8) shell:
primitive p_nfsserver ocf:heartbeat:nfsserver \ op monitor depth="0" timeout="20s" interval="10s"
EXAMPLE PCS
The following is an example configuration for a nfsserver resource using pcs(8)
pcs resource create p_nfsserver ocf:heartbeat:nfsserver \ op monitor OCF_CHECK_LEVEL="0" timeout="20s" interval="10s"
SEE ALSO
http://clusterlabs.org/
AUTHOR
ClusterLabs contributors (see the resource agent source for information about individual authors)
11/10/2024 | resource-agents 4.16.0-1 |