Red Hat CLUSTER SUITE FOR ENTERPRISE LINUX 5.1 : Installation guide : Page 131

...

</nfserver>

</fs>

...

</service>

When configuring a system to use the nfsserver resource agent for use with NFSv3 and NFSv4,

you must account for the following limitations:

Configure only one nfsserver resource per cluster. If you require more, you must use restricted

failover domains to ensure that the two services in question can never start on the same host.

Do not reference a globally-configured nfsserver resource in more than one service.

Do not mix old-style NFS services with the new nfsserver in the same cluster. Older NFS

services required the NFS daemons to be running; nfsserver requires the daemons to be

stopped when the service is started.

When using multiple file systems, you will be unable to use inheritance for the exports; thus reuse

of nfscli ent resources in services with multiple file systems is limited. You may, however,

explicitly define target and path attributes for as many nfscl i ents as you like.

7.9. Verifying a Configurat ion

Once you have created your cluster configuration file, verify that it is running correctly by performing

the following steps:

1. At each node, restart the cluster software. That action ensures that any configuration

additions that are checked only at startup time are included in the running configuration. You

can restart the cluster software by running service cman restart. For example:

[root@ example-01 ~]# servi ce cman restart

Stopping cluster:

Leaving fence domain... [ OK ]

Stopping gfs_controld... [ OK ]

Stopping dlm_controld... [ OK ]

Stopping fenced... [ OK ]

Stopping cman... [ OK ]

Waiting for corosync to shutdown: [ OK ]

Unloading kernel modules... [ OK ]

Unmounting configfs... [ OK ]

Starting cluster:

Checking Network Manager... [ OK ]

Global setup... [ OK ]

Loading kernel modules... [ OK ]

Mounting configfs... [ OK ]

Starting cman... [ OK ]

Waiting for quorum... [ OK ]