Veritas File System 5.1 SP1 Release Notes

Features no Longer Supported
• Disk Layout Version 4 and Version 5 file system for shared (cluster) mounts
VxFS 5.1 SP1 supports shared (cluster) mount only for file systems with disk layout version 6
or 7. If you have a shared (cluster) mounted file system with disk layout versions 4 or 5, you
must mount this file system locally (without the -o cluster mount option) and upgrade the
disk layout to version 6 or 7 before mounting it with the -o cluster mount option.
• I/O error mount options
In VxFS 5.1 SP1, only the ioerror=disable and ioerror=mdisable mount options are
supported for clustered file systems. Other ioerror mount options are not supported. For
more information, see mount_vxfs (1M).
Known Limitations
• Quick I/O, ODM, mount -o cio, and the VX_CONCURRENT advisory are mutually exclusive
The VX_CONCURRENT advisory cannot be set on a file that is actively open by Quick I/O or
ODM. A file that has the VX_CONCURRENT advisory set may not be concurrently opened by
Quick I/O or ODM. Quick I/O and ODM access are not allowed for any files on a file system
that is mounted with the mount -o cio option.
• Support for creating DLV 4 file system(s)
Creation of DLV 4 file system(s) using the mkfs command is not supported in this release of
VxFS 5.1 SP1. A patch will be released in future to enable creation of DLV 4 file system(s).
However, DLV 4 file system(s) created in earlier VxFS versions can still be mounted.
Known Problems and Workarounds
The following known problems exist for VxFS 5.1 SP1:
NOTE: For information on the Known Problems and Workarounds in VxFS 5.0.1 in the HP-UX
11i v3 operating system, see Veritas File System 5.0.1 Release Notes, HP-UX 11i v3, First Edition,
November 2009 available at the HP Business Support Center .
• Problem
Enabling the read_ahead parameter (setting the parameter value to '2') for enhanced read
operations, can result in the I/O being transiently frozen. Under heavy load, the system can
take several minutes to recover from this state.
Workaround
HP recommends not to enable the read_ahead parameter under heavy load.
• Problem
Shrinking a file system using either the fsadm command or vxresize command can take
a long time to complete in some cases, such as if the shrink size is large and a large extent
of a file is overlapping with the area to be shrunk.
Workaround
One possible workaround is to use the vxtunefs command and set write_pref_io and
write_nstream to high values, such that write_pref_io multiplied by write_nstream
is around 8 MB.
10 Veritas File System 5.1 SP1 Release Notes