Serviceguard NFS Toolkit for Linux Version A.01.03 Release Notes, July 2005

Serviceguard NFS for Linux Version A.01.03 Release Notes
Known Problems and Workarounds
Chapter 114
• Export the filesystem with an assigned filesystem identification.
NOTE Refer to the README File for more detailed information.
A new configuration file called hanfs.conf has been introduced in this
version, which provides the choice of monitoring the rpc.rquotad
daemon (which is an optional daemon).
JAGad91624: NFS remote mount table discrepancy on
package fail over
What is the problem? The counter number of remote mount entries in
the /var/lib/nfs/rmtab may or may not be correct after running NFS
packages for a long period. This problem does not disrupt any client
access of NFS files.
Each entry in the /var/lib/nfs/rmtab file contains three fields. These
fields are: Client IP address, Exported file system , and Counter
number of the exported file system mounted by a client.
An rmtab file, for example, may contain the following entries:
128.12.148.2:/expo/pkg1fs:0x00000001
128.12.148.3:/expo/pkg1fs:0x00000001
128.12.148.2:/expo/pkg2fs:0x00000001
The counter field, in normal case, contains 0x00000001 (e.g. the counter
can be 2 if the same client mounted the same file system twice). The
counter may or may not be updated correctly when a client un-mounts
the file system.
What is the workaround?
The system administrator needs to be aware of the counter number that
may not be consistent with the number of clients currently mounting the
file systems. If the file, /var/lib/nfs/rmtab, or the counter number
becomes too large, take the ollowing steps in order to maintain the file:
1. Verify that clients are not currently mounting the file systems.
2. Verify that all NFS packages are running on all nodes in the cluster.
3. On each node, perform: