These release notes support ptx/EFSTM V1.3.6. 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-Q® or Symmetry® systems
DYNIX/ptx V4.4.2, V4.4.4, V4.4.5, and V4.4.7 or later
ptx/CLUSTERS V2.0.2, V2.1.1, V2.1.2, V2.1.3 or later (optional)
ptx/SVM V2.0.3, V2.1.1, V2.1.2, V2.1.3 or later (optional)
This release of ptx/EFS includes fixes for the following software defects:
(245177) It was not possible to unmount a busy filesystem if the filesystem became disabled for some reason.
(245332) A system panic occurred in vx_eio_rmiolist() via vx_eio_reuse() because a pointer was not correctly filled in.
(245820) The system panicked while it was booting when root was a ptx/EFS filesystem.
(246318) ptx/EFS keeps track of EIO buffers for all extents, excluding mmap regions, and adjusts the EIO buffers if an underlying extent is extended. The system panicked if extents were extended for a file that had mmap regions.
(246648) Error messages appeared in the ktlog when default directory ACLs were inherited by files in the directory.
(247493) A panic occurred in vx_fsflushi() because a filesystem inode was dereferenced before an inode lock was placed on it.
(248080) A panic occurred during a ptx/CTC transition because of a conflict between an unmount operation and a sync operation.
(249549) ptx/EFS dump could take hours to dump a single file if that file was sparse but did not have any indirect extents.
(249772) ptx/EFS ASYNC DIO did not handle sparse reads, resulting in a system panic.
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/EFS and ptx/CFS Administration Guide.
This release of ptx/EFS contains no known open problem reports.