ptx®/NFS® V4.7.2 is a subset of Sun Microsystems.® NFSSRC V3 based on ONC+ 2.1, ported and enhanced to run on IBM® NUMA and Symmetry® 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.
For more information about ptx/NFS, refer to the following manual, which is available on the documentation CD or at http://webdocs.numaq.ibm.com/:
For more information about NIS+ products, refer to the following hard copy manuals:
This section lists the following problem report summaries:
The numbers in parentheses identify the problems in the IBM problem-tracking system.
This section lists fixed software defects that have been reported against this release of ptx/NFS.
(239314) When an automount was created through the ptx/ADMIN menu system for direct or indirect maps, the option for the type of mount was positionally dependent.
(241176) The system panicked during parallel creat(), unlink(), chmod() and chown() operations on an NFS-mounted filesystem.
(248292) rpc.rstatd passed an incorrect buffer size to getkerndata, which resulted in warning error messages.
(253956) ptx/NFS was continously writing "host down" messages to the log.
(253977) An error in the ptx/ADMIN NFS menus resulted in a filesystem export with anon=root.
(254154) Unwanted error messages filled up the ktlog and the ees_log.
(254156) An incorrect NFS version string was used in EES logging.
(255257) While the system was reading from an NFS file that was memory mapped, ptx/NFS returned extra zero bytes.
(255282) The system panicked when it tried to create a symbolic link between an NFS filesystem and a local filesystem.
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.