These release notes support ptx/EFSTM V1.3.7. 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.
Use this version of ptx/EFS with the following products:
IBM® NUMA or Symmetry® systems
DYNIX/ptx V4.4.10
ptx/CLUSTERS V2.1.4 (optional)
ptx/SVM V2.1.4 (optional)
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.
The following documentation is available on the HTML documentation CD:
This section lists the following problem report summaries:
This release of ptx/EFS includes fixes for the following software defects:
(251997) An MMU panic occurred because vx_fsetauadd called vx_kmem_free.
(252620) The system panicked when diskio was run with various options.
(252959) mkfs dumped core because NULL in fill_ilist was passed to the iinit() function.
(253784) The system panicked because of an unrecoverable MMU fault.
(254890) vx_iremount dropped VX_IRWUNLOCK twice if there was an error.
(254910) Writes in vx_do_putpage() were extremely slow.
(255088) ptx/EFS mistakenly marked inodes created by NFS clients (GID -2) as bad.
(255260) A process that tried to get a block that it owns hung the system.
(255428) A race condition for the IPTR lock occurred between vx_inull and vx_inactive_cache_flush.
This release of ptx/EFS contains no known open problem reports.