HP Serviceguard Toolkit for NFS on Linux Version A.03.03.01 Release Notes (December, 2012)

be installed on top of the NFS Toolkit version A.03.03.00 only. You must use the
nfstkitupdate command to install A.03.03.01 on Redhat.
Installation
The HP Serviceguard NFS toolkit is available as a tar file that you must extract to get the rpm for
NFS toolkit. For more information about installing this toolkit, see HP Serviceguard NFS Toolkit
User Guide available at:
http://www.hp.com/go/linux-serviceguard-docs.
Documentation available for this version
The document available with HP Serviceguard Toolkit for NFS A.03.03.01 on Linux is HP
Serviceguard Toolkit for NFS on Linux User Guide. This user guide is available at http://
www.hp.com/go/linux-serviceguard-docs.
Patches and fixes in this version
This section describes the required patches, and problems fixed in HP Serviceguard Toolkit for
NFS A.03.03.01 on Linux.
Required and recommended patches
At the time of publication, a patch is not required nor recommended for HP Serviceguard Toolkit
for NFS A.03.03.01 on Linux.
However, this is subject to change without notice. For the most current information, contact your
HP representative.
Fixes
This release of HP Serviceguard toolkit for NFS on Linux contains fix for the following problems:
• QXCR1000869191: If the fsid option is not specified for XFS attribute values in package
configuration file, a stale FH error might appear on NFS clients, when NFS server package
fails over to an adoptive node.
Known problems and workarounds
This section describes the list of known problems and workarounds for the HP Serviceguard toolkit
for NFS A.03.03.01 on Linux. However, this is subject to change without notice. For the latest
information contact your HP support representative.
• During a package failover, the NFS server might receive status information messages such
as:
◦ Input/output error
◦ Stale NFS file handle
◦ Write error: Stale NFS file handle
Workaround: Try to remount the NFS shares at the client side.
• If the package fails over during a user file access, the client node might experience a
momentary hang.
Workaround: No manual steps are required. Access mount point continues as soon as the
package completes failover to the other node.
• The NFS client might not receive a crash event notification when it sends an initial lock request
to the NFS server. If the NFS package fails over to an adoptive node, before the client entry
Patches and fixes in this version 5