These release notes support ptx/EFS V1.4.1. ptx/EFS lets you create large files and filesystems of up to 1 TB in length for the DYNIX/ptx® operating system. In conjunction with ptx/CFS, ptx/EFS lets you create large files and filesystems in a cluster environment.
Read this document before you install or run this release of ptx/EFS. For information on large-filesystem support, refer to the DYNIX®/ptx Programming Tools Guide. For more information on ptx/EFS, refer to the ptx/Enhanced File System (EFS) and ptx/Cluster File System (CFS) Administration Guide.
Use this version of ptx/EFS with the following products:
IBMTM NUMA-Q® 2000 systems or Symmetry® systems
DYNIX/ptx V4.5.1 or later
ptx/CLUSTERS V2.2.1 or later (optional)
ptx/SVM V2.2.1 or later (optional)
This release of ptx/EFS includes fixes for the following software defects:
(251444) It was possible for newfs to crash when a user error caused the usage message to be displayed.
(250746) When a filesystem was disabled, the EES message was only a warning level message and not a major level message.
(250712) It was possible to crash the system if asynchronous direct I/O was being performed with bad parameters.
(250711) When an inode was marked bad. the EES message was only a warning level message and not a major level message.
(250666) It was possible to hang the system if using asynchronous direct I/O when reading a hole.
(250665) fsadm would print improper values due to a printf format string.
(250585) When a filesystem would fill, ptx/EFS would not reset the counter indicating how many times the filesystem was filled in a certain amount of time.
(250469) When a filesystem would fill, the EES message would be only a warning level message and not a major level message.
(250425) When using vectored I/O, many requests would result when fewer than the requested number could be performed to optimize the operation.
(250303) When performing I/O over very large holes, it was possible to hang the process.
(249875) The mount command was not reporting the use of the nolargefile option.
(249804) The stavfs call was returning different values for read-only and read-write filesystems.
(249435) The df -k command was reporting negative values for a nearly empty filesystem.
(245332) The system would panic when a file was memory mapped and the internal states of the mapped and unmapped buffers were incorrect.
(244871) The EFS and CFS daemons were not documented in the efs(7) and cfs(7) manual pages.
(241500) No message was being sent to the system administrator when the root filesystem was filled.
ptx/EFS V1.4.0 included fixes for the following software defects:
(246648) Error messages appeared in the ktlog when default directory ACLs were inherited by files in the directory.
(245977) The shell script /etc/fs/efs/efs.cron, which can be added to the root crontab to reorganize mounted efs and cfs filesystems automatically, did not handle cfs filesystems.
(245441) During software installation through ptx/INSTALL, the compatibility_log did not show ptx/EFS as having a dependency on DYNIX/ptx. Therefore, it allowed ptx/EFS to be installed before DYNIX/ptx.
(245177) It was not possible to unmount a busy filesystem if the filesystem became disabled for some reason.
(244732) The ptx/ADMIN menu system would not let you allocate more than 64K inodes for a ptx/EFS filesystem.
(240555) ptx/EFS limited itself to one-half the total buffer cache. This was a problem on multiquad systems, where one quad could run out of buffers.
The software installation procedure is documented in the DYNIX/ptx and Layered Products Software Installation Release Notes.
If you install ptx/EFS for the root filesystem, create a custom miniroot using the buildmini command. Refer to the buildmini(1M) man page for more information.
Although ptx/EFS supports 1-KB and 2-KB filesystems, performance is better with 4-KB filesystems. In order for an mmap file to be handled correctly, all but the last extent of the file must be a multiple of 4-KB bytes. For 1-KB and 2-KB filesystems, ptx/EFS reallocates extents to be multiples of 4-KB bytes as needed, but performance is slower.
For more information on ptx/EFS, refer to the ptx/Enhanced File System (EFS) and ptx/Cluster File System (CFS) Administration Guide.
This release of ptx/EFS contains no known open problem reports.