HP Tru64 UNIX and TruCluster Server Version 5.1B-6 Patch Summary and Release Notes

If this occurs, we recommend that you immediately do the following:
1. Use the following command to unmount the filesystem:
# cfsmgr -u -p [mountpoint]
2. If other mounted filesets exist in the same domain, unmount them (they should also be in
the "Not Served" state):
# cfsmgr -u -d [domain]
For steps on checking an AdvFS domain, see the AdvFS Administration Guide, Section 6.3.1,
steps 3-7.
3. Run diagnostics on the domain prior to remounting its file systems.
To verify the domain, you can use the AdvFS verify utility or the fixfdmn utility. If using
fixfdmn, we recommend first running it with the -n option to see what errors are found
prior to allowing fixfdmnn to fix them.
Once you have successfully verified the domain, remounting the domain's file systems in the
cluster should succeed.
If the domain cannot be immediately verified, we recommend that you do not remount the
original fileset until this can be done.
Note:
In rare cases, the warning message will be accompanied by a system panic. This will occur if CFS
error handling is unable to successfully unmount the underlying physical file system. If this
occurs, the console will direct you to use cfsmgr to unmount the domain on one of the remaining
nodes prior to rebooting the member.
This action will prevent the rebooted member from attempting to failover-mount the file system
and will minimize access to the domain. Prior to remounting the file system, it is advisable that
the domain be sanity-checked using the steps given above.
Tunable Attribute May Help Performance Problem
The tunable attribute cfs_clone_noccr, included in this patch kit , may correct a problem in
which cluster fileset writes that occur simultaneously with reads of the fileset clone on a cluster
client (for example, during a backup) may result in performance degradation. This occurs most
often when the clone file being read consists of many thousands of extents (for example, 20,000
or more).
If a degradation during cluster clone reads is noticeable (for example, the clone read appears to
be hanging and requires a long time to complete), set the value of cfs_clone_noccr to 1 on
the server of the given fileset. This sysconfig tunable attribute is set to 0 by default and should
be changed only when the degradation is noticeable.
Note that all filesets with clones that are served by the node on which the attribute is set will
also see this change. It may be advisable (though not required) to have those filesets whose clone
files have fewer extents be served by a different node during the time the tunable attribute is set.
AlphaServer ES47 or AlphaServer GS1280 Hangs When Added to Cluster
If after running clu_add_member to add an AlphaServer ES47 or AlphaServer GS1280 as a
member of a TruCluster the AlphaServer hangs during its first boot, try rebooting it with the
original V5.1B generic cluster kernel, clu_genvmunix.
Use the following instructions to extract and copy the V5.1B cluster genvmunix from your
original Tru64 UNIX kit to your AlphaServer ES47 or AlphaServer GS1280 system. In these
instructions, the AlphaServer ES47 or AlphaServer GS1280 is designated as member 5. Substitute
the appropriate member number for your cluster.
160 TruCluster Server Patches