ptx®/NFS® V4.8.1 is a subset of Sun Microsystems® NFSSRC V3 based on ONC+ 2.1, ported and enhanced to run on NUMA systems. It supports filesystems larger than 2 GB and files up to 2 GB.
This version of ptx/NFS requires the following products:
For more IBM NUMA product compatibility information, consult the DYNIX/ptx and Layered Products Software Installation Release Notes.
For information on installing ptx/NFS, refer to the DYNIX/ptx and Layered Products Software Installation Release Notes.
The following documentation is available on the online documentation CD and at http://webdocs.numaq.ibm.com/:
ptx/NFS Administration Guide
For more information about NIS+ products, refer to the following hard-copy manuals:
The following sections list open and fixed software in this release of ptx/NFS:
The numbers in parentheses identify the problems in the IBM NUMA problem-tracking system.
The following software defects are fixed in this release of ptx/NFS:
(254154) Unwanted messages filled up the logs and the disk.
(254055) A debug message mistakenly appeared in str_kudp.c.
(253930) The nfsd daemon reported an unnecessary error when starting up.
(254156) An incorrect NFS version string was used in EES logging.
(253956) ptx/NFS continuously wrote host down messages to logs. Now it writes to the logs only if the previous occurrence of the same message happened more than 15 minutes previously.
(250264) Some ptx/NFS EES messages contained the wrong product version numbers.
(239314) The automounter had problems with the auto.master file options. When the last option was parsed, it caused an error message to be logged in ktlog.
This section lists fixed and open software defects that have been reported against this release of ptx/NFS.
(253977) An awk error in the ptx/NFS menu for adding an NFS export resulted in the record added to the exports file having an unneeded "anon" argument.
(253951) The ptx/NFS automounter did not mount filesystems on demand all of the time.
This section lists open problems in this release of ptx/NFS.
Occasionally, for no apparent reason, the automounter dumps core.
Workaround. First, unmount all the automount /tmp mount points, and then restart the automounter.
The mount_nfs(1M) man page does not include a description of the new mount -o vers= option.
Workaround. None.
The access list in /etc/exports does not understand the short names of the machines that are allowed to mount a filesystem.
Workaround. Provide the fully qualified domain name (FQDN) of the client as an argument to the access option in /etc/exports.