VERITAS Storage Foundation 4.1 Release Notes

VERITAS Storage Foundation Release Notes

New and Enhanced Features

◆ The largefiles option is now the default file size option for the mount command and

mkfs command.

◆ The delaylog option is now the default intent logging mount option. The change of the

default mount option from log to delaylog does not increase the risk of data loss, but

allows VxFS to cache data to improve performance. See the VERITAS File System

Administrator's Guide for more information.

◆ The default Storage Checkpoint creation mode is now removable.

◆ Operation of the intent log replay was improved to increase the speed of recovery after a file

system failure.

◆ The histlog function was implemented in the fsdb_vxfs command. The history log

records structural changes to the file system to aid in product support.

◆ Two new tunable parameters, inode_aging_count and inode_aging_size, for use

with the Storage Checkpoint API, were added to the vxtunefs command. See the

vxtunefs(1M) manual page for more information.

◆ More VxFS functions can be performed from the VES GUI. See the VERITAS Enterprise

Administrator (VEA 500 Series) Getting Started manual for more information.

◆ The vxfsu_get_ioffsets library call was renamed vxfs_get_ioffsets.

◆ vx_ninode and vxfs_bc_bufhwm can now be dynamically tuned without rebooting the

machine. The changes take effect immediately, although they can be optionally made to take

effect only after a reboot. See the VERITAS File System Administrator's Guide for more

information.

VERITAS Storage Foundation for Oracle

This release of VERITAS Storage Foundation for Oracle includes the following new features and

enhancements.

Storage Topology Analyzer

This release introduces functionality that maps tablespaces to physical disks and retrieves this

mapping information, including the percentage of disk space used by a tablespace. This

functionality is available using the CLI only.

Unified Message Identifiers

Logging, error, and warning messages are now saved to a log file with a standard-format Unique

Message Identifier. An example of the standardized format is: