Limitations of Serviceguard NFS

File locks are not maintained when an NFS server package moves to an adoptive node. Any applications that use file locking must reclaim their locks after an NFS server package fails over. An application that loses its file lock as a result of an NFS package failover will not be notified. If the server is also an NFS client, any file locks it holds will be lost.

A system administrator may need to manually maintain or remove persistent file-lock states for the failed node. The previous file-lock states may remain available on the failed node.

	NOTE: In versions A.02.00 and A.03.01 of the NFS toolkit, you can eliminate the above limitations by enabling the File Lock Migration feature. (For more information, see the “Overview of the NFS File Lock Migration Feature” section). IPv6 addresses are not supported by NFS toolkit for NFS version 3 file lock migration feature.