Multiple NFS resources may cause the NFS daemon to restart upon service group failover.
Article ID: 100020931
Updated On:
Resolution
The NFS daemon restart is an undesired result of running multiple NFS resources on a single node of the cluster.
It is not recommended to have multiple NFS resources on any single node of a cluster.
It is recommended to change the cluster configuration so that multiple NFS resources will never be online on a single node of the cluster.
To implement the change, complete the following steps-
1) Delete the NFS resource that currently exists in each service group.
2) Create a separate parallel service group in the cluster that has only the NFS resource contained in it. This service group will always be online on all cluster nodes.
3) Use a proxy resource in each additional service group with NFS shares. The proxy resource will point to the NFS resource in the parallel NFS group.
4) Create any desired dependency links between each NFS share (parent resource for this link) and the proxy (child resource for this link) in each service group.
5) Each service group with NFS shares should have its own NFSRestart resource, so that it is possible to clear the NFS locks specific to its NFS shares.
Was this article helpful?
Yes
No
Powered by
