VERITAS File Systemª 3.5

Release Notes

HP-UX

November 2002 30-000861-011 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.

Copyright Copyright © 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, VERITAS , and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the USA and/or other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies. 18 November 2002. VERITAS Software Corporation 350 Ellis Street Mountain View, CA 94043 USA Phone 650–527–8000 Fax 650–527–2908 http://www.veritas.com

Data Encryption Standard (DES) Copyright Copyright © 1990 Dennis Ferguson. All rights reserved. Commercial use is permitted only if products that are derived from or include this software are made available for purchase and/or use in Canada. Otherwise, redistribution and use in source and binary forms are permitted. Copyright 1985, 1986, 1987, 1988, 1990 by the Massachusetts Institute of Technology. All rights reserved. Export of this software from the United States of America may require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting. WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. VERITAS File System Release Notes

This guide provides information on VERITAS File Systemª (VxFS) release 3.5. The 3.5 release of VxFS operates only on the HP-UX 11i 64-bit operating systems with the September 2002 HP-UX 11i version 1.0 (or later) release installed. VERITAS Cluster File System (CFS), the clustering functionality of VxFS, is a separately licensable feature of VxFS; however, installing VxFS and enabling the cluster feature does not create a cluster file system configuration (see “Using Cluster File Systems” on page 6 for more information). The VERITAS File System package includes VxFS software, documentation, and the optionally licensed VERITAS Quick I/Oª for Databases and VERITAS QuickLogª features. Review this entire document before installing VxFS. Topics in this guide include: ◆ New Features ◆ End of Product Support ◆ Using VERITAS Quick I/O and VERITAS QuickLog ◆ Using Cluster File Systems ◆ Compatibility With Previous Versions of VxFS ◆ Required HP-UX Patches ◆ VxFS Packages ◆ Documentation ◆ Command Summary ◆ Software Issues in VxFS ◆ Getting Help

1 New Features

New Features

VxFS Release 3.5 has the following new features and changes.

▼ New VERITAS Product Distribution Method The VERITAS software disc has an automated installation and licensing procedure that lets you install packages using an Installation Menu instead of installing from the command line. This automated installation process is valid only for new product installations and cannot be used to upgrade from previous product versions. VERITAS has also introduced a website from which you can quickly and easily obtain a license key for the products that you have purchased. The Product License and Installation Guide, included with the VERITAS software disc, provides complete information. Review the Product License and Installation Guide before installing VxFS.

▼ VERITAS Enterprise Administrator The VERITAS Enterprise Administrator (VEA) is the new global graphical user interface used by VERITAS products. Some major VxFS functions, such as mounting, defragmenting, and creating snapshot file systems can be performed through the VEA GUI. VEA is installed with the . See the VERITAS Volume Manager User’s Guide – VERITAS Enterprise Administrator for details on configuring the GUI and using VxFS functionality.

▼ VxFS Command Enhancements The vxdump command now enables backups at the file or directory level. The fsadm command now allows fragmentation reporting and operations on an individual file or directory, or on Storage Checkpoints. The vxrestore command now bypasses the system buffer cache when restoring data. This allows a system’s buffer cache to remain intact while doing an extensive restore operation which typically improves system performance. The vxrestore Ðc option preserves backwards compatibility by allowing vxrestore to use the buffer cache. The vxupgrade command can now upgrade an existing VxFS file system to the Version 4 disk layout while the file system remains online. The logiosize=size option was added to the mount command to enhance the performance of storage devices that employ a read-modify-write feature. To obtain the maximum performance from such devices, intent log writes can be done in 1024, 2048, or 4096 bytes.

2 VERITAS File System Release Notes New Features

▼ New and Enhanced Tunable Parameters The following tunables were added or updated for 3.5. The hsm_write_prealloc, read_ahead, and write_throttle parameters are set per-file-system. The vx_bc_bufhwm tunable is a global parameter.

hsm_write_prealloc Preallocates uninitialized space in a managed region of a file to improve performance when using HSM applications with VxFS.

read_ahead Detects complex read-ahead patterns in addition to sequential reads.

vx_bc_bufhwm Sets the maximum amount of memory (high water mark) that can be used by the VxFS metadata buffer cache. This is a global tunable parameter set in the HP-UX kernel.

write_throttle Alters the number of dirty pages generated before flushing to disk to take advantage of new disk storage technology.

See the vxtunefs(1M) manual page, and the performance chapter of the VERITAS File System Administrator’s Guide, for more information.

▼ New I/O Error Handling Policy The ioerror option was added to the mount command to provide four different ways to handle system I/O errors. These policies were implemented on VxFS in response to evolving storage technology functionality for which a single method of I/O error processing was no longer sufficient. One major behavior change is to disable a file system instead of marking inodes bad on disk—this will prevent inadvertent data loss. See the mount(1M) manual page for more information.

▼ New Default Intent Log Mode To increase performance, the mount command delaylog option has replaced the log option as the default for VxFS file systems. See the mount(1M) manual page for more information.

VERITAS File System Release Notes 3 New Features

▼ New Default File System Block Size The default block size is now 1024 bytes for all VxFS file systems, no matter how large the file system you create. Previously, the default block size was increased with larger file systems. You can still select a larger block size using the mkfs bsize option. See the mkfs(1M) manual page for more information.

▼ API for Obtaining VxFS Inode Field Offsets For open source utilities, such as LSOF, to support VxFS 3.5 file systems, the library vxfsutil was introduced. The library provides an API for accessing VxFS header file information because the header files are no longer public. See the vxfsu_get_ioffsets(3) manual page for details.

▼ VxFS System Activity Reporter The vxfsstat command displays VxFS file system statistics which can be used to analyze performance and aid in tuning. Similar to the sar(1M) command, vxfsstat gathers statistics on buffer cache, inode cache, and per-CPU usage. See the vxfsstat(1M) online manual page for detailed information.

▼ Support for Oracle Disk Manager (ODM) This release supports the Oracle Disk Manager driver. ODM is a custom storage interface for files and raw devices that achieves a higher degree of file administration and increased database performance. ODM features include atomic file naming, creation and deletion, asynchronous file I/O, reduction of system overhead by multiplexing requests and completions in one I/O system call, and the ability to determine file I/O attributes. The ODM Application Programming Interface (API) is targeted for the Oracle9i release, and will be available only with the VERITAS Database Edition.

▼ Forced Unmounts A VxFS-specific vxumount command is available in this release to perform forced unmounts (vxumount -o force)of VxFS file systems. This is useful in a variety of situations such as High Availability environments where a mounted file system could prevent timely failover. Any active process with I/O operations pending on an unmounted file system receives an I/O error (EIO). This command can cause data loss and must be used carefully. See the vxumount(1M) manual page for more information.

4 VERITAS File System Release Notes New Features

▼ File Access Time Disabling The Ðo noatime option was added to the mount command to disable access time updates. This improves performance in read-only environments by eliminating unneeded write operations.

▼ Storage Checkpoints A Storage Checkpoint is a frozen image of a mounted file system. The frozen image, or checkpoint, initially consists only of pointers to the file system’s data, so Storage Checkpoints require minimal space. As data blocks subsequently change in the file system, the Storage Checkpoint keeps track of the changes. A Storage Checkpoint therefore provides a consistent representation of a file system at a specific point-in-time by identifying modified data blocks and incorporating the original data into its own directory structure. These frozen images of VxFS file systems can be used in a variety of applications such as full and incremental online backups, fast error recovery, and product development testing. Storage Checkpoint replicas of real time databases can also be used for decision support and an assortment of database analyses. Features and applications includethe following: ◆ Storage Checkpoints are writable, and can be created, mounted, and removed with the fsckptadm utility and an added option to the mount command. ◆ Performance enhancements in maintaining data Storage Checkpoints (Storage Checkpoints that are complete images of the file system) makes using the Storage Rollback feature easier and more efficient, therefore more viable for backing up large databases. ◆ Multi-file system Storage Checkpoint creation allows database backups without having to shut down the database.

▼ Parallel Log Replay The fsck Ðo p option and fsck ÐP option allow a log replay on multiple file systems in parallel. The parallel fsck functionality improves system start-up times.

▼ VERITAS File System Quick Start Guide No Longer a Separate Manual For convenience and ease of reference, the VERITAS File System Quick Start Guide was incorporated into the VERITAS File System Administrator’s Guide as an appendix.

VERITAS File System Release Notes 5 End of Product Support

End of Product Support

This release is the last to support the VxFS Version 2 and Version 3 disk layouts. You can still mount these older disk layout versions, but you cannot create them using the VERITAS mkfs command. VERITAS recommends that you upgrade file systems using these older disk layouts to Version 4. See “Compatibility With Previous Versions of VxFS” below for information on upgrading. This is the last release to support the QuickLog statistic gathering functionality provided by the qlogstat command. Also, future releases of QuickLog will support only one VxFS file system per QuickLog device instead of the current 32 file systems per QuickLog device.

Using VERITAS Quick I/O and VERITAS QuickLog

The VERITAS File System package, VRTSvxfs, includes two separately licensed products, VERITAS Quick I/O for Databases and VERITAS QuickLog. These features are described in the VERITAS File System Administrator's Guide. A QuickLog license is included with VERITAS Editions products and VERITAS Foundation Suite. Quick I/O is available only with VERITAS Editions products. See “Getting Help” on page 21 for contact information on these products.

Using Cluster File Systems

Cluster File System (CFS) is the file system clustering functionality of VxFS. CFS is a separately licensable feature of VxFS that requires several other VERITAS products to enable communication services and provide shared disk storage resources. The VERITAS Volume ManagerTM (VxVM) and other packages are included with VxFS in the SANPoint Foundations Suite (SPFS) to provide a complete clustering environment. See “Getting Help” on page 21 for contact information on these products.

6 VERITAS File System Release Notes Compatibility With Previous Versions of VxFS

Compatibility With Previous Versions of VxFS

Note VERITAS recommends upgrading any previously installed VxFS file system to VxFS 3.5, disk layout Version 4.

VxFS 3.5 file systems employ disk layout Version 4. With the 3.5 release, you can no longer create Version 2 or Version 3 disk layout file systems, but the older disk layout file systems can still be mounted. You should begin upgrading any Version 2 or Version 3 disk layout file systems to Version 4 for them to be usable on future releases of VxFS. Cluster file systems and Storage Checkpoints require the Version 4 disk layout to operate. You can do disk layout upgrades online using the vxupgrade command (see the vxupgrade(1M) manual page for details). You can use vxfsconvert (see vxfsconvert(1M)) on unmounted file systems. Consider the following when planning disk layout upgrades: ◆ Version 2 disk layout file systems have an 8 million inode limit. ◆ Backup images of Version 2 and Version 3 disk layout file systems created by copy utilities, such as dd or volcopy, will not be unusable in the next release of VxFS. Use vxfsconvert to migrate volume-image backup copies of Version 2 and Version 3 disk layouts to Version 4.

VERITAS File System Release Notes 7 Required HP-UX Patches

Required HP-UX Patches

The 3.5 release of the VERITAS File System operates only on HP-UX 11i 64-bit operating systems with the September 2002 HP-UX 11i (11.11) version 1.0 (or later) release. The 3.5 release requires the following HP-UX patches. The VERITAS Volume Manager patches must be installed only if you are using VxFS in conjunction with VxVM:

HP-UX Patch ID Description PHCO_27101 VxVM rootability changes to mkboot command. PHCO_27209 VxVM rootability changes to insf command. PHKL_26761 VxFS. Required only for the operation of the vx_ninode tunable parameter. The vx_ninode parameter specifies the maximum number of inodes available in the VxFS in-memory inode cache. If not explicitly specified, the value of vx_ninode is based on how much physical memory is available on the system. See the VERITAS File System Administrator’s Guide for more information. PHKL_27096 VxVM rootability changes to HP-UX kernel.

Note Install all the latest required HP-UX patches before you install VxFS. You can use the swlist command to determine whether the correct update and patches are installed.

HP may release patches that supersede the ones in this list. To verify that you have the latest HP-UX patches, go to the VERITAS support website to view the patch list: http://seer.support.veritas.com/docs/250499.htm Alternatively, you can use Hewlett-Packard’s Patch Database offered under the Maintenance and Support section of the HP Services & Support - IT Resource Center. HP’s Patch Database provides fast, accurate searches for the latest recommended and superseded patches available for the VERITAS File System or VERITAS Volume Manager.

8 VERITAS File System Release Notes VxFS Packages

VxFS Packages

There are multiple software discs in the VERITAS product distribution. VxFS is on VERITAS Storage Solutions 3.5 for HP-UX Disc 1. The following file system packages in the file_system/pkgs directory of Disc 1:

◆ VRTSvxfs—VxFS software and online manual pages ◆ VRTSfsdoc—VxFS Documentation ◆ VRTSvlic—VERITAS products licensing facility ◆ VRTSfspro—VERITAS File System Management Services Provider ◆ VRTSob—VERITAS Enterprise Administrator Service ◆ VRTSobgui—VERITAS Enterprise Administrator

VRTSvxfs is the required VxFS binary package and VRTSfsdoc is the optional VxFS documentation package. VRTSvlic is the required licensing package for all VERITAS products. VRTSvlic may already be available on your system if you have installed another VERITAS product. VRTSfspro, VRTSob, and VRTSobgui are part of the VERITAS Enterprise Administrator (VEA ) GUI. These packages are typically installed by the VERITAS Volume Manger or VERITAS Foundation Suiteª and are not required for VxFS to operate. See the VERITAS File System Installation Guide for complete instructions on how to install the VxFS packages.

Note VxFS is a licensed product; you must obtain a license key before installing it. For information on obtaining a license key, see the VERITAS File System Installation Guide.

VERITAS File System Release Notes 9 Documentation

Documentation

The following documents accompany this VxFS release as Adobe Portable Document Format (PDF) files: ◆ VERITAS File System Installation Guide ◆ VERITAS File System Administrator’s Guide The VRTSvxfs package contains manual pages for VxFS commands and utilities. The VERITAS File System Release Notes are provided on the VERITAS software disc in the file vxfs_notes.pdf under the file_system/release_notes directory. Because product release notes are not installed by any packages, VERITAS recommends that you copy them from the software disc to the /opt/VRTSfsdoc directory so that they are available on your system for future reference.

Displaying Documentation Online

The VERITAS File System guides are provided on the VERITAS software disc under the file_system/docs directory as PDF files. To view or print PDF documents, you need the Adobe Acrobat Reader. The following two documents comprise the VxFS documentation set: ◆ VERITAS File System Installation Guide After installing the VRTSfsdoc package, you can access this guide in the following location: /opt/VRTSfsdoc/vxfs_ig.pdf. ◆ VERITAS File System Administrator’s Guide After installing the VRTSfsdoc package, you can access this guide in the following location /opt/VRTSfsdoc/vxfs_ag.pdf. See the VERITAS File System Installation Guide for VRTSfsdoc package installation information. The VRTSvxfs package contains manual pages for VxFS administration commands.

10 VERITAS File System Release Notes Documentation

Cluster File System Documentation

There is a separate documentation package named VRTScfsdc for the Cluster File System. The VRTScfsdc documentation package contains the same VERITAS File System Administrator’s Guide as VRTSfsdoc, but has a different installation guide that includes cluster administrative information, the VERITAS SANPoint Foundation Suite Installation and Configuration Guide. The online manual pages available with the VERITAS File System (listed under “Online Manual Pages” on page 12) are also available with the Cluster File System. There is a section in each VxFS manual page detailing any cluster functionality issues associated with that command (see “Using Cluster File Systems” on page 6).

VERITAS File System Release Notes 11 Documentation

Online Manual Pages

This release includes the following online manual pages as part of the VRTSvxfs package. The swinstall command installs VxFS manual pages in the /usr/share/man/fs/vxfs3.5 directory, and symbolic links to the VxFS manual pages in the /opt/VRTS/man directory. The /usr/share/man/fs/vxfs3.5 directory is automatically added to /etc/MANPATH when VxFS 3.5 is installed. Make sure that one of these directories goes before /usr/share/man in your MANPATH environment variable so that the latest version of the VxFS manual pages display.

Section 1 Description getext Gets attributes for a VxFS file system.

qioadmin1 VxFS Quick I/O for Databases cache administration utility.

qiomkfile1 Creates a VxFS Quick I/O device file.

qiostat1 VxFS Quick I/O for Databases statistics utility. setext Sets extent attributes on a file in a VxFS file system. Section 1M Description df_vxfs Reports the number of free disk blocks and inodes for a VxFS file system. extendfs_vxfs Extends the size of a VxFS file system. ff_vxfs Lists file names and inode information for a VxFS file system. fsadm_vxfs Resizes or defragments a VxFS file system. fscat_vxfs Cats a VxFS file system. fsck_vxfs Checks and repairs a VxFS file system.

fsckptadm5 VxFS Storage Checkpoint administration utility.

fsclustadm3, 4 Manages cluster-mounted VxFS file systems. fsdb_vxfs VxFS file system debugger. fstyp_vxfs Returns the type of file system on a specified disk partition. mkfs_vxfs Constructs a VxFS file system. mount_vxfs Mounts a VxFS file system. ncheck_vxfs Generates path names from inode numbers for a VxFS file system. newfs_vxfs Creates a new VxFS file system.

qlogadm2,4 Low level ioctl utility for the QuickLog driver.

qlogattach2,4 Attaches a previously formatted QuickLog volume to a QuickLog device.

qlogck2,4 Recovers QuickLog devices during the boot process.

12 VERITAS File System Release Notes Documentation

qlogclustadm2,4 Cluster QuickLog device administrative utility.

qlogdb2,4 QuickLog debugging tool.

qlogdetach2,4 Detaches a QuickLog volume from a QuickLog device.

qlogdisable2,4 Remounts a VxFS file system with QuickLog logging disabled.

qlogenable2,4 Remounts a VxFS file system with QuickLog logging enabled.

qlogmk2,4 Creates and attaches a QuickLog volume to a QuickLog device.

qlogprint2,4 Displays records from the QuickLog configuration.

qlogrec2,4 Recovers the QuickLog configuration file during a system failover.

qlogrm2,4 Removes a QuickLog volume from the configuration file.

qlogstat2,4 Prints statistics for running QuickLog devices, QuickLog volumes, and VxFS file systems.

qlogtrace2,4 Prints QuickLog tracing. quot_vxfs Summarizes ownership on a VxFS file system. quotacheck_vxfs VxFS file system quota consistency checker. vxdump Incremental file system dump. vxdiskusg Generates VxFS disk accounting data by user ID. vxenablef Enables DMAPI, HP_OnLineJFS, or VxFS functionality in the HP-UX kernel.

vxfsconvert2 Converts an unmounted file system to VxFS or upgrades a VxFS disk layout version.

vxfsstat4 Displays file system statistics. vxrestore Restores a file system incrementally. vxtunefs Tunes a VxFS file system. vxumount Unmounts a VxFS file system. vxupgrade Upgrades the disk layout of a mounted VxFS file system.

VERITAS File System Release Notes 13 Documentation

Section 4 Description fs_vxfs Format of a VxFS file system volume. inode_vxfs Format of a VxFS file system inode.

qlog_config2 QuickLog configuration file. tunefstab VxFS file system tuning parameters table. Section 7 Description

qlog2 VERITAS QuickLog device driver. vxfsio VxFS file system control functions.

1 Functionality available only with VERITAS Quick I/O for Databases feature 2 Functionality available only with VERITAS QuickLog feature 3 Functionality available only with VERITAS Cluster File System product 4 New in VxFS 3.5

14 VERITAS File System Release Notes Command Summary

Command Summary

Symbolic links to all VxFS command executables are installed in the /opt/VRTS/bin directory. Add this directory to the end of your PATH environment variable to access the commands.

Note The VxFS 3.5 vxtunefs command is installed in the /sbin/fs/vxfs3.5/bin directory. This directory is automatically added to /etc/PATH when VxFS 3.5 is installed. Make sure that you invoke the VxFS 3.5 vxtunefs for tuning VxFS 3.5. If the JFS/OnLineJFS 3.3 vxtunefs command in the /sbin directory executes on 3.5, an error is returned.

Command Description df Reports the number of free disk blocks and inodes for a VxFS file system. extendfs_vxfs Extends the size of a VxFS file system. ff Lists file names and inode information for a VxFS file system. fsadm Resizes or defragments a VxFS file system. fscat Cats a VxFS file system. fsck Checks and repairs a VxFS file system.

fsckptadm4 VxFS Storage Checkpoint administration utility.

fsclustadm3,4 Manages cluster-mounted VxFS file systems. fsdb VxFS file system debugger. fstyp Returns the type of file system on a specified disk partition. getext Gets extent attributes for a VxFS file system. mkfs Constructs a VxFS file system. mount Mounts a VxFS file system. ncheck Generates path names from inode numbers for a VxFS file system. newfs_vxfs Creates a new VxFS file system.

qioadmin1 VxFS Quick I/O for Databases cache administration utility.

qiomkfile1 Creates a VxFS Quick I/O device file.

qiostat1 VxFS Quick I/O for Databases statistics utility.

qlogadm2,4 Low level IOCTL utility for the QuickLog driver.

qlogattach2,4 Attaches a previously formatted QuickLog volume to a QuickLog device.

qlogck2,4 Recovers QuickLog devices during the boot process.

VERITAS File System Release Notes 15 Command Summary

Command Description

qlogclustadm2,4 Cluster QuickLog device administrative utility.

qlogdb2,4 QuickLog debugging tool.

qlogdetach2,4 Detaches a QuickLog volume from a QuickLog device.

qlogdisable2,4 Remounts a VxFS file system with QuickLog logging disabled.

qlogenable2,4 Remounts a VxFS file system with QuickLog logging enabled.

qlogmk2,4 Creates and attaches a QuickLog volume to a QuickLog device.

qlogprint2,4 Displays records from the QuickLog configuration.

qlogrec2,4 Recovers the QuickLog configuration file during a system failover.

qlogrm2,4 Removes a QuickLog volume from the configuration file.

qlogstat2,4 Prints statistics for running QuickLog devices, QuickLog volumes, and VxFS file systems.

qlogtrace2,4 Prints QuickLog tracing. quot_vxfs Summarizes ownership on a VxFS file system. quotacheck_vxfs VxFS file system quota consistency checker. setext Sets extent attributes on a file in a VxFS file system. vxdump Incremental file system dump. vxdiskusg Generates VxFS disk accounting data by user ID. vxedquota Edits user quotas for a VxFS file system. vxenablef Enables DMAPI, HP_OnLineJFS, or VxFS functionality in the HP-UX kernel.

vxfsconvert4 Converts an unmounted file system to VxFS or upgrades a VxFS disk layout version. vxfsstat Displays file system statistics. vxrestore Restores a file system incrementally. vxtunefs Tunes a VxFS file system. vxumount Unmounts a VxFS file system. vxupgrade Upgrades the disk layout of a mounted VxFS file system.

1 Functionality available only with VERITAS Quick I/O for Databases feature 2 Functionality available only with VERITAS QuickLog feature 3 Functionality available only with VERITAS Cluster File System product 4 New in VxFS 3.5

16 VERITAS File System Release Notes Software Issues in VxFS

Software Issues in VxFS

▼ New VxFS 3.5 Tunable Parameters Cannot Be Used With JFS/OnLineJFS 3.3 Three tunables, hsm_write_prealloc, read_ahead, and write_throttle were added in VxFS 3.5. The JFS/OnLineJFS 3.3 vxtunefs command does not recognize these tunables and will fail if the command tries to access them. If you deinstall VxFS 3.5, remove any VxFS 3.5 tunable settings from the /etc/vx/tunefstab file before reverting to JFS/OnLineJFS 3.3.

▼ The 3.3 JFS/OnLineJFS vx_maxlink Tunable Parameter Cannot be Set on VxFS 3.5 The vx_maxlink tunable limits the number of files and subdirectories that can be created under a single directory. With JFS/OnLineJFS 3.3, vx_maxlink can be set to a value of more than 32K –1. Some HP-UX system calls cannot support more than 32K –1 links to a file or directory, so VxFS 3.5 allows only up to 32K –1 entries in one directory. Because the vx_maxlink parameter is not tunable on VxFS 3.5, systems with directories containing more than 32K –1 entries may have problems accessing data when upgrading from JFS/OnLineJFS 3.3. If you have explicitly set the vx_maxlink tunable in JFS/OnLineJFS 3.3 to a value greater than 32K –1, contact VERITAS Technical Support before upgrading to VxFS 3.5 (see “Getting Help” on page 21 for contact information).

▼ Some VxFS Commands May Fail Due to Delay in Updating the mnttab File Because HP-UX does not sync /etc/mnttab file updates to disk for as much as 30 seconds, some VxFS commands that depend on information in mnttab may fail. This problem can occur when using the qlogenable/qlogdisable commands. The qlogenable command remounts a file system with the qlog= option. After running qlogenable, if the qlogdisable command is run before /etc/mnttab is updated, the command fails with the following error: mountpoint is not a QuickLog enabled file system If this problem occurs, wait 30 seconds and run qlogdisable again.

▼ Storage Checkpoints Do Not Work with HSM Products Storage Checkpoints cannot be created on a file system where the VERITAS Storage Migratorª is active, or with other hierarchical storage management (HSM) products that use the DMAPI interface.

▼ Quick I/O Files Cannot Be Sparse Files If you try to convert a sparse file to a Quick I/O file, the Oracle instance can fail if Oracle tries to write into an unallocated block. Specifically, datafiles used by the Oracle8i and Oracle9i temporary tablespace may be sparse files, so do not convert these to Quick I/O files. See the VERITAS Database Edition for Oracle Database Administrator’s Guide for more information.

VERITAS File System Release Notes 17 Software Issues in VxFS

▼ Non-standard Command Behavior When Using Access Control Lists (ACLs) The output of the ls Ðl command on VxFS file systems shows mask/CLASS_OBJ in place of group permissions if ACLs are in use on a file or a directory. You can determine the effective group permissions by using the getacl command. In the next release of VxFS, the behavior of ls Ðl will show effective group permissions, that is, GROUP_OBJ masked by CLASS_OBJ. The command changes mask/CLASS_OBJ instead of the group permissions if ACLs are in use on a file or a directory. GROUP_OBJ is not changed by chmod, and because effective group permissions are determined by GROUP_OBJ and CLASS_OBJ, the default group may not receive the permissions specified by chmod. Because ls Ðl shows mask only (which is changed by chmod), it only appears that the group permissions are changed as specified in chmod. Use of chmod command is not advisable on files with ACLs. Instead, use the getacl command to manipulate permissions. In the next release of VxFS, the behavior of both mask/CLASS_OBJ and GROUP_OBJ will be to change after executing the chmod command. Even in that case, using the getacl command is advisable for manipulating permissions. Even if the parent directory has default ACLs, umask is applied to a newly created file. According to POSIX standards, umask should be applied only if the parent directory does not have any default ACLs. In the next release of VxFS, this behavior will be made POSIX compliant. See the following manual pages for ACL-related information: aclsort(3C), chmod(1), getacl(1), ls(1), setacl(1), and uname(1).

▼ Data Integrity Issues with Disks and Disk Arrays with Write-back Caches Disk drives configured to use a write-back cache, or disk arrays configured with a volatile write-back cache, exhibit data integrity problems. The problems occur after a power failure, SCSI bus reset, or other event in which the disk has cached data, but has not yet written it to non-volatile storage. Contact your disk drive or disk array manufacturer to determine whether your disk drives use a write-back cache, and if the configuration can be changed to disable write-back caching.

▼ 100% Full File System Cannot Be Resized In some circumstances, the fsadm command cannot resize a 100% full file system due to lack of space for updating structural information. Check VxFS file systems on a regular basis and increase their size if they approach 100% capacity. If a file system is busy or too fragmented, the resize operation can also fail.

18 VERITAS File System Release Notes Software Issues in VxFS

▼ Under Some Conditions, fsadm Cannot Truncate a Directory The fsadm command cannot truncate a directory if it has only one extent that is more than two blocks in length, even if all the directory entries are deleted.

▼ A Change in the Method of Computing CUT Values May Cause Misleading Error Messages to Display. In this release, the method for computing the Current Usage Table (CUT) values for a Version 2 file system has changed. If a Version 2 file system is mounted on a system running VxFS 3.5, and that file system is subsequently used on an earlier version of VxFS, the following messages may display when performing a full fsck: vxfs fsck: incorrect CUT entry for filest 1, fix? (ynq) vxfs fsck: incorrect CUT entry for filest 999, fix? (ynq) This is expected and does not indicate file system corruption. Answer y to both questions. There is no need to perform a full fsck when moving such a file system to and from different versions of VxFS unless the file system is dirty, in which case a full fsck is required.

▼ Inode Limitation on File Systems Without Large File Support For a file system to have more than 8 million inodes, you must create it using the largefiles option of mkfs (the fsadm utility can also be used to set the largefiles flag on the file system). See the mkfs_vxfs(1M) and fsadm_vxfs(1M) manual pages for details.

▼ Some Fields Not Displayed by the fstyp Command The fstyp -v option shows the super-block. For the Version 4 disk layout, some information is no longer in the super-block, so fields such as nau, logstart, or logend display zeros. nau can be computed using the following formula: nau = (size + aulen - 1) / aulen fstyp -v displays the size and aulen fields. You can use mkfs ÐF vxfs -m raw_device_file to display many fields that are not part of super-block. See the mkfs_vxfs(1M) and mkfs(1M) manual pages for more information.

VERITAS File System Release Notes 19 Software Issues in VxFS

▼ File Sharing Option (FSO) Issues

Migration For customers using the VERITAS File Sharing Option, FSO is a part of Cluster File System (CFS), and can be used only on a configured cluster. FSO does not require a separate license from CFS, but the VRTSfso package must be installed. FSO works only on cluster volume manager (CVM) volumes and only on VxFS 3.5. So if you are using FSO with JFS 3.3 on raw UNIX devices, or on LVM volumes, you must migrate to VxFS 3.5. To migrate a file system using FSO to VxFS:

1. Create CVM volumes for all FSO file systems.

2. Use the dd command to copy all FSO file systems to the CVM volumes.

3. Mount the file systems with the FSO option and restart the application.

Failover The File Sharing with VxFS document says to run fsck using the mounted option after a node failure, but in VxFS 3.5, the fsck mounted option is not intended to be run from the command line. The file system internally invokes a log replay of a mounted file system during the cluster node recovery process after the primary node fails (see fsck_vxfs(1M) and mount_vxfs(1M) for more information). There is only one read-write node in an FSO cluster. If the read-write node fails, another node in the cluster is elected to be the read-write node (primary), and a log replay is automatically performed. The new primary is still mounted in read-only mode, so you must remount the file system in read-write mode:

1. Select a node to be the read-write node. If the selected node is same as the new primary, go to step 2. If not, use the fsclustadm (see fsclustadm(1M) to change the primary. On the selected primary, enter: # fsclustadm setprimary mount_point

2. Remount the file system from the new primary using the following options: # mount remount,rw,fso filesystem

20 VERITAS File System Release Notes Getting Help

Getting Help

For assistance with any of the VERITAS products, contact VERITAS Technical Support: ◆ U.S. and Canadian Customers: 1-800-342-0652 ◆ International: +1-650-527-8555 ◆ Email: [email protected]

For license information: ◆ Phone: 1-925-931-2464 ◆ Email: [email protected] ◆ Fax: 1-925-931-2487

For software updates: ◆ Email: [email protected] For information on purchasing VERITAS products: ◆ Phone: 1-800-258-UNIX (1-800-258-8649) or 1-650-527-8000 ◆ Email: [email protected]

For additional information about VERITAS and VERITAS products, visit the Web site at: http://www.veritas.com For software updates and additional technical support information, such as TechNotes, product alerts, and hardware compatibility lists, visit the VERITAS Technical Support Web site at: http://support.veritas.com

VERITAS File System Release Notes 21 Getting Help

The VRTSexplorer Diagnostic Program

The VRTSexplorer program is available to assist VERITAS Customer Support engineers in diagnosing technical problems associated with VERITAS products. You can download this program from the VERITAS FTP site or install it from the VERITAS software disc. For more information about the VRTSexplorer program, consult the README file located in the support directory.

Downloading VRTSexplorer from the Web

1. Use a web browser or the ftp program to download the VRTSexplorer program from the following URL: ftp://ftp.veritas.com/pub/support/VRTSspt-hpux.tar.Z Save the file to a temporary directory, such as /tmp, as shown in the example session below.

2. Log in as root on the system that is experiencing the problem. Extract the contents of the downloaded file to the directory /tmp/VRTSexplorer: # cd /tmp # zcat VRTSspt-hpux.tar.Z | tar xf -

3. Run the VRTSexplorer program located in the VRTSexplorer directory: # /tmp/VRTSexplorer/VRTSexplorer

4. When VRTSexplorer prompts for a destination directory for the information that it collects, press Return to accept the default directory /tmp, or enter an alternative path name of your own choice. VRTSexplorer writes the results of its analysis to a compressed tar file named VRTSexplorer_casenumber_hostname.tar.Z in the specified directory.

5. Use the file upload facility of your web browser, or the ftp program, to transfer the VRTSexplorer output file to the VERITAS Customer Support anonymous FTP site: ftp://ftp.veritas.com/incoming

6. Telephone VERITAS Technical Support at the number listed under “Getting Help”on page 21. Tell them that you have run VRTSexplorer and provide the name of the file that you transferred to the FTP site. Alternatively, if you have already been assigned a call ID number by Customer Support, send email to [email protected] and include your case ID number in the subject line.

22 VERITAS File System Release Notes Getting Help

Installing VRTSexplorer from the VERITAS Software Disc The file VRTSspt package is included on the VERITAS software disc under the /support directory. To load the software from the software disc:

1. Log in as superuser and place the VERITAS software disc into a CD-ROM drive connected to your system.

2. To determine the appropriate CD-ROM device name, enter: # ioscan -fn -C disk

3. Run the following commands to start PFS (Portable File System): # nohup pfs_mountd & # nohup pfsd &

4. Create a directory under which to mount the software disc and mount the disc using the appropriate CD-ROM drive name. For example: # mkdir -p /cdrom # /usr/sbin/pfs_mount -t rrip /dev/dsk/c3t2d0 /cdrom

5. Install the VRTSspt package: # swinstall -s /cdrom/file_system/support VRTSspt

6. The program is installed in the /opt/VRTSspt directory and takes approximately 500 KB of disk space. To run the program, enter:. # /opt/VRTSspt/VRTSexplorer/VRTSexplorer

7. Use the file upload facility of your web browser, or the ftp program, to transfer the VRTSexplorer output file to the VERITAS Customer Support anonymous FTP site: ftp://ftp.veritas.com/incoming

8. Telephone VERITAS Customer Support at the number listed under “Getting Help”on page 21. Tell them that you have run VRTSexplorer and provide the name of the file that you transferred to the FTP site. Alternatively, if you have already been assigned a call ID number by Customer Support, send email to [email protected] and include your case ID number in the subject line.

9. To remove the VRTSspt package, enter: # swremove VRTSspt

VERITAS File System Release Notes 23 Getting Help

24 VERITAS File System Release Notes