Você está na página 1de 30

VERITAS Storage Foundation 4.

0
Release Notes
AIX Maintenance Pack 3

November 2005

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. VERITAS Legal Notice Copyright 2005 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo, and Storage Foundation are trademarks or registered trademarks of VERITAS Software Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

VERITAS Software Corporation 350 Ellis Street Mountain View, CA 94043 USA Phone 6505278000 Fax 6505272908 www.veritas.com Third-Party Legal Notices
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.

ii

VERITAS Storage Foundation Release Notes

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 New and Enhanced Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Component Product Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Upgrading from AIX 5.2 to AIX 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Installing Storage Foundation 4.0 MP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Fixed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 VERITAS Volume Manager Fixed Issues for MP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 VERITAS File System MP3 Fixed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Fixed Issues for MP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Fixed Issues for MP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Open Software Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 VERITAS Volume Manager Software Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 VERITAS Volume Replicator Software Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 VERITAS File System Software Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Open Documentation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 VxFS Documentation Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 VxVM Documentation Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

iii

Software Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 VERITAS Volume Manager Software Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 VERITAS Volume Replicator Software Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . 24 VERITAS File System Software Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

iv

VERITAS Storage Foundation Release Notes

VERITAS Storage Foundation 4.0 MP3 Release Notes


Introduction
This document provides release information for upgrading VERITAS Storage Foundation to the Maintenance Pack 3 (MP3). The installation software disc upgrades an existing installation of the following VERITAS Storage Foundation product and platform combinations to MP3:

VERITAS Storage Foundation 4.0 for AIX 5.1 and 5.2 VERITAS Storage Foundation 4.0 MP1 for AIX 5.1 and 5.2 VERITAS Storage Foundation 4.0 MP2 for AIX 5.1 and 5.2 VERITAS Storage Foundation 4.0 or 4.0 MP2 for AIX 5.3

Note The MP3 release includes the fixes and updates from the MP2 and MP1 releases. The following components have been updated as part of this release:

VRTSalloc at revision level 1.0.0.3 VRTSvxfen.rte at revision level 4.0.3.0 VRTSvcsag.rte at revision level 4.0.3.0 VRTSob at revision level 3.2.4.6 VRTSvcs.msg.en_US at revision level 4.0.3.0 VRTSvcs.man at revision level 4.0.3.0 VRTSvcs.rte at revision level 4.0.3.0 VRTSllt.rte at revision level 4.0.3.0 VRTSgab.rte at revision level 4.0.3.0 VRTScssim.rte at revision level 4.0.3.0 VRTSvxvm at revision level 4.0.3.0 VRTSvxfs at revision level 4.0.3.0
1

New and Enhanced Features

Review this entire document before installing VERITAS Storage Foundation. Also see the VERITAS Storage Foundation 4.0 Release Notes. Note You must refer to the following TechNote on the VERITAS Technical Support website for the latest information on updates, patches, and software issues regarding this release: http://support.veritas.com/docs/269928.htm The information in this TechNote may be crucial for the correct operation of Storage Foundation. Current information on the availability of fixes to the AIX operating system is available in this TechNote. VERITAS Storage Foundation is a licensed product; you must obtain a license key before installation. For information on obtaining a license key, see the VERITAS Storage Foundation 4.0 Installation Guide.

New and Enhanced Features


This release includes the following new feature and enhancement:

Support for Virtual SCSI devices. See Usage of Virtual SCSI devices with VxVM on page 20 for applicable software issues and Virtual SCSI Limitations and Impact on page 24 for software limitations.

System Requirements
This release of VERITAS products requires the following minimum AIX 5.1, 5.2, or 5.3 operating system level to operate:

AIX 5.1 ML6 with APARs IY65263 and IY67577 AIX 5.2 ML4 with APARs IY67584, IY65717, and IY59620 AIX 5.3 ML3

Upgrade to AIX 5.1, 5.2, or 5.3 and then install the appropriate APARs before installing VERITAS Storage Foundation. Note The installation script for VERITAS Storage Foundation verifies that the installation of AIX is at the proper maintenance level before the upgrade begins. Additional requirements for APARs or other fixes are not verified by the install script. Refer to the following TechNote for any additional requirements that may exist: http://support.veritas.com/docs/269928.htm

VERITAS Storage Foundation Release Notes

Component Product Release Notes

The script will abort without upgrading any component of VERITAS Storage Foundation if the target system fails to meet the AIX maintenance level requirements.

Component Product Release Notes


In addition to reading these Release Notes, review all component product release notes before installing the product. The following component product release notes are included as PDF files on the VERITAS software disc under the storage_foundation/release_notes directory: VERITAS Volume Replicator Release Notes (vvr_notes.pdf) VERITAS Cluster Server Release Notes (vcs_notes.pdf) Because release notes are not installed by any packages and are not on the documentation disc, it is recommended that you copy them from the software disc to the /opt/VRTS/docs directory so they are available on your system for reference.

Patches
See System Requirements on page 2 for a list of applicable APARs (Authorized Program Analysis Reports). There are no additional patches that are required for this release.

Upgrading from AIX 5.2 to AIX 5.3


VERITAS Storage Foundation 4.0 will not operate properly on AIX 5.3 unless AIX 5.3 is at the required maintenance level or the applicable APARs are installed. See System Requirements on page 2 for the minimum required maintenance level of AIX 5.3 for VERITAS Storage Foundation 4.0. If your AIX installation is at 5.2 and you desire to upgrade to AIX 5.3, you must first upgrade Storage Foundation 4.0 to the MP3 level. Upgrading Storage Foundation on AIX 5.2 to MP3 will enable Storage Foundation to support AIX 5.3. However, before you upgrade to AIX 5.3 (after upgrading to MP3), you must temporarily disable Storage Foundation to prevent it from starting, until the upgrade to 5.3 is complete. It is necessary to avoid Storage Foundation operation until AIX 5.3 is upgraded to the required maintenance level. After the upgrade to 5.3 is complete, you can then enable Storage Foundation 4.0 operation.

Upgrading from AIX 5.2 to AIX 5.3

To upgrade from AIX 5.2 to AIX 5.3 1. Create the install-db file:
# touch /etc/vx/reconfig.d/state.d/install-db

2. Upgrade from AIX 5.2 to AIX 5.3. See the operating system documentation for more information. 3. Apply the necessary APARs. See System Requirements on page 2 for the APARs required for Storage Foundation. 4. Refer to the following TechNote for information on installing additional patches required for Storage Foundation 4.0 MP3, if any: http://support.veritas.com/docs/269928.htm 5. Enable Storage Foundation to start after a reboot:
# rm /etc/vx/reconfig.d/state.d/install-db # shutdown -Fr

6. Reboot the system.

VERITAS Storage Foundation Release Notes

Installing Storage Foundation 4.0 MP3

Installing Storage Foundation 4.0 MP3


There is a software disc for upgrading existing installations of Storage Foundation to the MP3 level in this product distribution. For new installations, use the software disc for installing Storage Foundation 4.0, and then use the MP3 disc to upgrade Storage Foundation to the MP3 level. The VERITAS software disc for MP3 has an automated installation and licensing procedure that lets you upgrade currently installed 4.0 packages using the VERITAS product installer instead of upgrading from the command line. Caution Uninstalling the MP3 upgrade or rolling back to the previous configuration is not supported. The VERITAS product installer is the recommended method to license and upgrade the product. The installer also enables you to configure the product, if necessary, verify pre-upgrade requirements, and view the products description. At most points during an upgrade, you can use type b (back) to return to a previous section of the upgrade procedure. The back command is context-sensitive, so it returns to the beginning of a grouped section of questions. If an upgrade procedure hangs, use Controlc to stop and exit the program. There is a short delay before the script exits. The following sample procedure is based on the upgrade of a system named aix650fs1. Default responses are enclosed by parentheses. Press Return to accept defaults.

To install Storage Foundation 4.0 MP3 1. Log in as superuser. 2. Check the state of the VEA service:
# /opt/VRTS/bin/vxsvcctrl status

3. Stop the VEA service if it is running:


# /opt/VRTS/bin/vxsvcctrl stop

4. Verify that there are no VxFS Storage Checkpoints or file systems mounted:
# mount | grep vxfs

5. If applicable, unmount the Storage Checkpoints and file systems:


# unmount /checkpoint_name # unmount /file_system

Installing Storage Foundation 4.0 MP3

6. Insert the disc containing the VERITAS software into the CD-ROM drive and mount the disc:
# mount -o ro /dev/cdrom /mnt

7. Change to the directory where you mounted the disc:


# cd /mnt

8. Invoke the common installer, specifying the system you wish to upgrade:
# ./installmp aix650fs1 VERITAS MAINTENANCE PACK 3 4.0 INSTALLATION PROGRAM . . . Checking OS version on aix650fs1..................... AIX 5.3.0 Initial system check completed successfully. Press [Return] to continue:

9. Press Return to continue. A list of MP3 filesets to be installed is displayed.


installmp will install the following VERITAS Maintenance Pack 3 filesets: VRTSveki VRTSvxvm VRTSvxfs VRTSalloc VRTSddlpr VRTSfppm VRTSfsman VRTSfspro VRTSob VRTSobgui VRTSvmpro VRTScpi.rte VERITAS Kernel Interface VERITAS Volume Manager Binaries VERITAS File System VERITAS Volume Manager Intelligent Storage Provisioning VERITAS Device Discovery Layer Services Provider VERITAS File Placement Policy Manager VERITAS File System Manual Pages VERITAS File System Management Services Provider VERITAS Enterprise Administrator Service VERITAS Enterprise Administrator VERITAS Volume Manager Management Services Provider VERITAS Cross Product Installation Framework

Press [Return] to continue:

VERITAS Storage Foundation Release Notes

Installing Storage Foundation 4.0 MP3

10. Press Return. The utility begins checking the installation requirements for the system.
Checking system installation requirements: Checking VERITAS Maintenance Pack 3 installation requirements on aix650fs1: Checking VRTSveki fileset .......... version 1.0.0.0 installed Checking VRTSllt.rte fileset .................... not installed Checking VRTSgab.rte fileset .................... not installed . . . Checking file system space ........ required space is available Backing up 4.0 MP3 configuration files . Done installmp will install or reinstall the following filesets on aix650fs1: VRTSveki VRTSvxvm VRTSvxfs VRTSalloc VRTSfppm VRTSfsman VRTSfspro VRTSvmpro VERITAS Enterprise Administrator processes must be stopped before adding patches. Do you want to stop these processes and install patches on aix650fs1? [y,n,q] (y)

11. Press Return to accept the default reply. Ensure that the requirements not verified by the installer have been manually verified before proceeding.
Checking vxsvc process .................................. running Stopping vxsvc ............................................. Done Checking vxfsckd process ............................ not running Checking odm driver ........................... odm module loaded Unloading odm module on aix650fs1 .......................... done Checking vxgms driver ......... vxgms check command not installed Checking vxfs driver ......................... vxfs module loaded Unloading vxfs module on aix650fs1 ......................... Done Checking vxsvc process .............................. not running Checking veki driver ................................ not running Installation requirement checks completed successfully. Press [Return] to continue:

Installing for the First Time

12. Press Return to continue. The patches will install.


Installing VERITAS Maintenance Pack 3 4.0.2.0 on aix650fs1: Installing Installing Installing Installing Installing Installing Installing Installing VRTSveki 1.0.2.0 on aix650fs1 ..... VRTSvxvm 4.0.3.0 on aix650fs1 ..... VRTSvxfs 4.0.3.0 on aix650fs1 ..... VRTSalloc 1.0.0.3 on aix650fs1 .... VRTSfppm 4.0.2.0 on aix650fs1 ..... VRTSfsman 4.0.2.0 on aix650fs1 .... VRTSfspro 4.0.2.0 on aix650fs1 .... VRTSvmpro 4.0.2.0 on aix650fs1 .... Done Done Done Done Done Done Done Done 1 2 3 4 5 6 7 8 of of of of of of of of 8 8 8 8 8 8 8 8 steps steps steps steps steps steps steps steps

VERITAS Maintenance Pack 3 installation completed successfully. Press [Return] to continue:

13. Press Return to continue. The installation process will complete.


Restoring Backed up configuration files on fs6304lp2 ....... Done Installation of VERITAS Maintenance Pack 3 4.0.2.0 has completed successfully.

Installing for the First Time


For new installations, first install VERITAS Storage Foundation 4.0, then upgrade to the MP3 level. Review and follow the installation procedure for Storage Foundation 4.0 described in the VERITAS Storage Foundation 4.0 Installation Guide. Follow the procedures in this document to upgrade Storage Foundation to the MP3 level.

VERITAS Storage Foundation Release Notes

Fixed Issues

Fixed Issues
The MP3 release is a cumulative upgrade and includes fixes and updates from the MP2 and MP1 releases.

VERITAS Volume Manager Fixed Issues for MP3


The following are fixed issues in this release of VxVM:

Incident 278693 272454

Description This fix added support for virtual SCSI disks. The fix enabled the vxinitrd daemon to add the new loadable module, diskdumplib to allow the system to boot. This fix prevented vxdg split failures after pulling and reconnecting the primary path cable. This fix enabled upgrades to AIX 5.3 and VRTS SF 4.0MP1 from causing existing diskgroups to disappear. This fix allowed the DMP failover to use the temporary state (NODE_SUSPECT) for all LUNs on failed path. In DMP, this fix enabled gen_select_aa_path() to not choose NODE_QUIESCED path if available. This fix corrected a panic in dmp_find_node when path index is max_path_idx. This fix prevented vxfenadm from reporting 11 bad keys from dmpnode. In DDL, this fix corrected the problem where the LUN serial number extraction for EMC arrays with page 83 support was broken in 4.1. This fix enabled smitty interfaces to set slab allocation consumption. This fix corrected the condition where vxconfigd core dumped on the primary master running testcases with slave as the logowner. This fix prevented vxconfigd from core dumping during a SAN cable-pull test. This fix corrected an assertion failure in iodone() due to a B_DONE set when the I/O buffer passed.

294107

314649

369387

380288

381294 381927 389747

389929 406452

408776 410286

Fixed Issues

Incident 411136

Description This fix corrected master takeover failures if even a single disk in the system has stale PGR keys. This fix corrected false SSB hits on the master when the slave and one of arrays are brought down together. This fix prevented the SHARED DG DEPORT from consuming too much time with large number of disks. This fix corrected the CVM I/O quiesce time during if the vxclust step4 took too long. This fix corrected I/O failures during NDU process on Cx600. This fix enabled disks marked offline during NetApp filer ownership change (fail over/back). This corrected the problem where AIX 4.0 MP2 - vxdg flush did not return. This fix corrected SCSI reservation conflicts during auto import of a shared dg due to SCSI-3 PGR issue. This fix enabled ACVCS changes for PGR on private DGs. This fix prevented invalid LUN Serial Number (duplicates) and the ASL from excluding devices.

411138

414369

418082

419071 429853

492163 493670

498781 498783

VERITAS File System MP3 Fixed Issues


The following are fixed issues in this release of VxFS:

Incident 153702

Description This correction resolved the problem where a file truncation fails to free up excessive allocated space, when the file system is full. Since the implemented fix does not handle this failure in the presence of storage checkpoint(s) in the file system, this resolution is only a partial fix.

10

VERITAS Storage Foundation Release Notes

Fixed Issues

Incident 154569

Description This fix corrected two lsfs issues: - A condition where the /sbin/helpers/vxfs/lsfs command was not able to differentiate between a block device or a mount point - A condition where a /usr/sbin/lsfs was generating an incorrectly formatted file descriptor. The lsfs command displays characteristics of file systems, such as mount points, automatic mounts, permissions, and file system size.

154024

This corrected the problem where the AIX Work Load Manager (WLM) was returning an incorrect generation count for an inode in a VxFS file system. This fix enabled VxFS to not reject the O_DEFER flag when specified with an open() system call.This flag is now quietly ignored when specified. This fix resolved the problem which caused 64-bit applications linked with VERITAS Mapping Services to crash. This fix corrected a problem that caused AIX 5.3 to crash when accounting was enabled for VxFS file systems. This problem was due to the VFS pointer not initializing properly when accounting was enabled.

155004

155131

149896

Fixed Issues for MP2


These are the fixed issues in the MP2 release of AIX 4.0.

VERITAS Volume Manager MP2 Fixed Issues


The following are fixed issues in this release of VxVM:

Incident 208013

Description Previously during transient path or transient cable failures, DMP was panicking in vxdmp_qd_path_iodone. The restore daemon with check_disabled_policy sometimes hung due to redundant code in DMP. A panic during volume grow operation with FastResync objects is fixed in this release.

236494

265696

11

Fixed Issues

Incident 277979

Description Running vxplex and vxsnap used to run into the Operation requires transaction error due to incorrect handling of VE_RESTART. The Space Optimized Snapshot operation hung when a cache object is corrupted. This fix prevented vxcache stat from showing space usage greater than what was allocated. Previously, DMP was panicking when all fiber channel paths were removed or disabled. Multiple issues were fixed on volumes larger than 1 TB with FastResync objects. I/O hung if a chained buffer list contained a buffer that used IOMEM segments. This fix corrected vxmake failures due to a vxconfigd core dump during memory allocation in huge VxVM configuration environments. There was a panic due to zero byte memory allocation in vol_cache_iogen_internal.

278089 278090

279112

288927 291709 292977

296257

VERITAS Volume Replicator MP2 Fixed Issues


The following are fixed issues in this release of VVR:

Incident 279096

Description After a disk failure on the Secondary, the secondary_log_err flag on the Primary was not cleared even after the disk on the Secondary was fixed. In UDP mode, RLINKs would not connect after the data ports were changed. If an RVG contained more than 256 volumes and online statistics collection was enabled, a memory leak occurred in the vradmind daemon. In some cases, the vradmind daemon would dump core when renaming a disk group. The vradmin command could fail with an incorrect error message about network disconnection when the network connection was available. This problem was caused by the stats ioctls being called while the command was in progress.

295171 355524

364962

364965

12

VERITAS Storage Foundation Release Notes

Fixed Issues

Incident 364966

Description The vradmin startrep or the vradmin resumerep commands would give warnings about RLINKs not being in the CONNECT state when the RLINKs were in CONNECT state. In some cases, the vradmin repstatus command did not display the value of the Logging to field.

364979

VERITAS Volume Replicator Web Console Fixed Issues The following are fixed issues in this release of VVR Web Console:

Incident 13389

Description In VRW, the Summary page displayed the following message even when RDSs existed on the host:

There is no RDS found on the local host.


217179 If the interactive commands addvol, stoprep, or migrate were executed in the VRW command window, the command dialog box would hang.

VERITAS Volume Replicator VERITAS Enterprise Administrator Fixed Issues The following are fixed issues in this release of VVR VEA:

Incident 86327

Description Primary-Primary configuration error was not displayed when the VVR VEA connected to the new Primary. However, when connected to the earlier Primary (using File > Connect menu option), the RDS and RVG views displayed the Primary-Primary Configuration error in the Configuration tab. Sometimes certain icons in VVR VEA were not refreshed or updated to reflect the correct state of the object being represented. Associate Volume and Dissociate Volume operations that were performed using VVR VEA would fail and report an error when performed on an RDS with no Secondary RVG.

86328

219197

13

Fixed Issues

VERITAS File System MP2 Fixed Issues


The following are fixed issues in this release of VxFS:

Incident i139288

Description Running the cfgmgr on systems with VEKI and ODM displayed misleading error messages, such as the following:

cfgmgr: 0514-604 Cannot access the CuDv object class in the device configuration database
These messages have been suppressed. i141917 Changed the fscdstask script to disallow CDS operations on Storage Checkpoints and snapshots, and to report the violation of limits in primary filesets and Storage Checkpoints. Performing a full fsck no longer disables sockets in the event of a missing parent directory. Resolved a fsck failure to validate the structural quota file when the size of the quotas file exceeded 2 GB. Optimized the file system internal thread allocation mechanism for managing CDS values to avoid a failure to create threads. Resolved the problem with removing a mount points configuration using the cfsmntadm delete command. Resolved the failure to tune mounted Storage Checkpoints using the vxtunefs command. Resolved the problem with adding a new node to a VCS service group for cluster file systems. Improved the file system internal transaction flushing to improve performance with Postmark. Significant improvement was made to the memory allocation scheme of VxFS in installations booted with the 32-bit AIX kernel. The new scheme uses a separate virtual memory segment for memory allocation, which enables the VxFS kernel to allocate more memory beyond the memory limit imposed by the pinned memory pool. Resolved the issue with creating VxFS file systems in volume sets with more than 241 volumes.

i143900

i147407

i147939

i150371

i150406

i150409

i150529

i151652

i151777

14

VERITAS Storage Foundation Release Notes

Fixed Issues

Incident i152189

Description Resolved a race condition resulting in a crash when two threads attempted to update the same flag that is used in processing a file system transaction. CFS agents were changed to retry operations when the ECONNREFUSED error is received from hscmds. Eliminated a limitation in the VxFS Directory Name Lookup Cache (DNLC) imposed by large CPU IDs that would cause infrequent, but unpredictable results, such as granting access to a deleted file. Resolved the inconsistent file permissions found on different nodes in a cluster file system. VxFS now supports ACLs on special files and pipes. Improved performance of write operations by eliminating an unnecessary lock contention. Reduced the wait time of the VxFS file system check daemon (vxfsckd) while log replay operations completed. This reduction improves the overall amount of time spent to failover a server. Avoid copying the mode bits used with JFS or JFS2 directories when copying to a VxFS file system.

i152235

i152278

i152379

i152398 i152455

i152830

i153698

15

Fixed Issues

Fixed Issues for MP1


These are the fixed issues in the MP1 release of AIX 4.0.

VERITAS Volume Manager MP1 Fixed Issues


The following are fixed issues in this release of VERITAS Volume Manager:

Incident 236494

Description Previously, the restore daemon with check_disabled_policy sometimes hung due to redundant code in DMP. This issue has been fixed. A panic during the volume grow operation with FastResync objects has been fixed in this release. Running vxplex and vxsnap used to run into the Operation requires transaction error due to incorrect handling of VE_RESTART. The Space Optimized Snapshot operation hung when a cache object is corrupted. vxcache stat could show space usage greater than what was allocated. DMP was panicking when all fiber channel paths were removed or disabled. Multiple issues were fixed on volumes larger than 1 TB with FastResync objects. Previously, the I/O hung if a chained buffer list contained a buffer that used IOMEM segments. vxmake could fail due to a vxconfigd core dump during memory allocation in huge VxVM configuration environments. There was a panic due to zero byte memory allocation in vol_cache_iogen_internal.

265696

277979

278089 278090 279112 288927 291709

292977

296257

16

VERITAS Storage Foundation Release Notes

Fixed Issues

VERITAS Volume Replicator MP1 Fixed Issues


The following are fixed issues in this release of VERITAS Volume Replicator:

Incident 272651

Description The maximum length of the DCM has been increased to 256K by default; you can now explicitly specify up to 2 MB. An attempt to resume replication on the Secondary caused the VVR Primary host to panic under certain circumstances. For an RVG containing multiple RLINKs, the VVR Primary host could panic under certain circumstances. After detaching, dissociating and reassociating the Secondary RLINK, the vradmin migrate command would leave the RDS in a Secondary-Secondary configuration. In some cases, the vradmin command did not wait for the interval specified in the IPM_HEARTBEAT_TIMEOUT environment variable before timing out an attempt to communicate with the vradmind daemon.

275805

286984

i146499

i150056

VERITAS File System MP1 Fixed Issues


The following are fixed issues in this release of VxFS.

Incident 144338

Description Insufficient access checking was performed during an attempt to create an existing file with non-exclusive access permission bits. With such an attempt, the existing file is recreated instead of being denied. However, the failure of checking access and the denial of access occurred only when the process that attempted to create was the owner of the existing file. On AIX, a vx_vmm_buf_count that is too high on a 32-bit kernel can exhaust the kernel heap. This issue has been fixed. Previously, an inode leak would occur when there was a failure to read the inode from disk. The errant inode was left allocated. This has been fixed by freeing the inode when there is an error. Updated vx_mapbad messages with the code location where the message was generated from, and also removed the bitmap and imap summary.

148379

148573

148574

17

Fixed Issues

Incident 148924

Description Previously, a remount for a file system from ro to rw did not process device extended operations. This has been fixed. Previously, fscdsconv on a promoted Storage Checkpoint would fail. This was due to new structural metadata being added which the fscdsconv binary was unaware. This has been fixed. Junk data could not be readily found in non-sparse VxFS files after a system crash. This has been fixed. A non-root user could change ownership of a file to root. This has been fixed by following the restricted chown semantics by default. System panic when turning quotas on or off. This is fixed by doing a copy-in of the user data before operating on it. File system full fsck reported that the CUT entries for certain filesets were incorrect because the offset that it calculated did not tally with the actual CUT offset on-disk. This was due to the incorrect calculation done within fsck for the CUT offset. This has been fixed by correcting the logic of CUT offset calculation in fsck. In the case of a multi-volume file system, fsck replay could write wrong superblock info if VX_DCE_FSSIZE extended operation was set on the device. This is fixed by updating free space in the superblock if the size has been already updated in fsck when adding a new device. Kernel panic when attempting to mount a VxFS file system read only when one of the IFILT inodes has been cleared due to either corruption or fsck. The fix is to skip setting up clone linkage for ilist inodes if the file system is mounted read only. VxFS fsck is a 64-bit compiled binary and requires a 64-bit run time environment. Without the 64-bit run time environment loaded, the fsck binary fails. To find if the system has been enabled with the 64-bit run time environment, run the following command:

149066

149244

149327

149401

149566

149681

150160

150263

# lsitab -a | grep load64bit


To enable the 64-bit run time environment, run the following command.

# smitty load64bit
151092 hastop -local hung when the file system is disabled. This was because the file system offline script was not run in this case, hence the file system was never unmounted. This was fixed by running the offline script, which tries to do an unmount. If the unmount does not succeed, a force unmount is done. Fixed credential memory leak in some places in the code. VERITAS Storage Foundation Release Notes

151904 18

Open Software Issues

Incident 152238

Description A putpage of a file that has a lot of dirty pages could block indefinitely if there is a getpage operation going on the same file. This has been fixed by failing read-ahead when there are no free buffers available. When trying to create a File System Snapshot, where the snapshot volume is greater than 2 TB in size, the operation failed. This was due to the fact that the snapsize variable is an unsigned integer. This is fixed by making snapsize an unsigned 64-bit. Manual pages for Cluster File System agents and utilities have been added to the VRTScavf.bff package.

152270

152462

Open Software Issues


Open issues listed in the VERITAS Storage Foundation 4.0 Release Notes still apply unless they appear in Fixed Issues on page 9. The 4.0 set of Release Notes was included with Storage Foundation 4.0 and is also available here: http://ftp.support.veritas.com/pub/support/products/Foundation_Suite/271310.pdf In addition, the following open software issues apply to this MP3 release.

VERITAS Volume Manager Software Issues


The following sections contain information about known problems and issues in this release of VxVM:

Converting an EMC Powerpath Simple Disk Type Into an auto:aixdisk


This section is applicable only if your configuration has VxVM/DMP using EMC Powerpath devices. In Storage Foundation 4.0 and earlier releases, EMC Powerpath devices could be defined by persistent disk access records using the vxdisk define command and being identified as simple disks. If an EMC powerpath disk is defined as a persistent disk access record, the following procedure must be followed to convert the disk from a simple disk to an auto:aixdisk.

To convert a VxVM-defined disk 1. Use the vxddladm rmforeign command on the disks:
# vxddladm rmforeign blockpath=/dev/hdiskpower* \ charpath=/dev/rhdiskpower*
19

Open Software Issues

If hdiskpower disks are added individually using the vxddladm addforeign command, the vxddladm rmforeign command also must be run individually on those disks. 2. Exclude native devices from the vxdmpadm command by using option 16 of the vxdiskadm command. VxVM had an issue in 4.0 in which defining disks as foreign devices would claim native devices as well. Excluding native devices from the vxdmpadm command bypasses this issue. 3. Before performing the 4.0 to 4.0.3.0 upgrade, include native devices for the vxdmpadm command by using option 17 of the vxdiskadm command.

Usage of Virtual SCSI devices with VxVM

Portable Data Containers (PDC), which translate to format=cdsdisk, are not supported. By default VxVM tries to create cdsdisk during disk initialization. To avoid this action, create the directory /etc/defaults and the file /etc/defaults/vxdisk and add format=aixdisk. By default, disk initialization creates aixdisk rather than cdsdisk. Since there is no support for PDC, users must turn off CDS (cross-platform data sharing). To turn off CDS create /etc/defaults/vxdg and add cds=off, which means CDS/PDC is turned off all the time. If initializing the disk needs to be done manually without the above entries, use the following syntax, vxdisk -f init <disk> format=aixdisk. The parameter format=aixdisk in command line need not be mentioned, if /etc/defaults/vxdisk with suggested entry (format=aixdisk) exists already.

With the above default entries, vxdiskadm does not require any steps specific to Virtual SCSI devices. It will by default create non-PDC diskgroup with format=aixdisk. See Virtual SCSI Limitations and Impact on page 24 for more information about Virtual SCSI.

vxconfigd Dumps Core When Disk Group Goes to SSB State


The vxconfigd daemon dumps core when the disk group goes to the SSB state. [277934]

20

VERITAS Storage Foundation Release Notes

Open Software Issues

Error When Converting A/P Devices With Multiple Ports


An error displays when converting A/P devices with multiple ports using vxconvert. To avoid this error, before running vxconvert, the system must be reconfigured to recognize single ports. Reboot the system after reconfiguring, and ensure that there is only a single path to each A/P device. [366234]

VERITAS Volume Replicator Software Issues


For a list of the known issues in VVR 4.0, see the VERITAS Volume Replicator 4.0 Release Notes, which were included in VVR 4.0. Also, the VERITAS Volume Replicator 4.0 Release Notes are available online at: http://ftp.support.veritas.com/pub/support/products/Volume_Replicator/271305.pdf

VERITAS Cluster Server Agents for VERITAS Volume Replicator Software Issues
The following sections contain information about known problems and issues in this release of VERITAS Cluster Server (VCS) Agents for VERITAS Volume Replicator (VVR): Limitations in the RVGSnapshot Agent Fire drill setup (fdsetup) supports applications using one disk group only. The RVGSnapshot agent does not support volume sets.

VERITAS Volume Replicator Web Console Software Issues


The following sections contain information about known problems and issues in this release of VERITAS Volume Replicator Web Console (VRW): Error in VRW on Certain Versions of AIX Note that this issue existed in VRW 4.0. For certain versions of the AIX operating system, such as 5200-01 and 5100-06, starting VRW gives the following error message:
tzmappings: Illegal format at near line 11.

This message indicates a timezone mapping error. The application will start but may not behave correctly. Make sure you perform the following workaround:
# cd /opt/VRTSjre/jre1.4/lib # native2ascii tzmappings > tzmappings.new # mv tzmappings.new tzmappings

You need not restart VRW or the VERITAS Web Server (VRTSweb). [219704]
21

Open Software Issues

Volume Type Not Shown Correctly in VRW Views The volume type in the RVG views and the RDS views are not shown correctly for stripe-mirror or concat-mirror volumes. This issue applies to VRW 4.0 also. [9854]

VERITAS File System Software Issues


The following sections contain information about known issues in this release of VxFS.

NBU Client and Storage Foundation


With earlier releases of the VERITAS Net Backup (NBU) client, backup and restore operations may fail to back up or restore ACLs, if ACLs are present. In case of such failures, the NBU client reports errors such as EINVAL or ENOTSUP. The NBU client must be upgraded to one of the releases below before upgrading or installing Storage Foundation 4.0 MP3, regardless of whether ACLs are being used or not. The releases of the NBU client listed below will work on previous releases of Storage Foundation products. Storage Foundation 4.0 MP3 supports the following releases of NBU:

NB_51_3_M NB_50_5_M NB_45_9_M NB_45_9_F

Limited Support for APV


Storage Foundation support for Advanced Power Virtualization (APV) of AIX 5.3 is limited to micro-partitioning of CPUs, Virtual Ethernet, and Virtual SCSI devices. As application workloads vary across different systems, the workload imposed on Storage Foundation, network interfaces, virtual SCSI devices and CPUs must be appropriate for the deployment of APV solutions within a virtual partition installed with Storage Foundation. Sharing of ethernet devices or CPUs across multiple partitions may be inappropriate with a high level of workload, which can result in degradation of performance depending on the degree of virtualization implemented within a partition. Lower throughput may also be experienced when virtual SCSI devices are used to store user data or file system data. Partitioning of other I/O devices is not currently supported with Storage Foundation.

22

VERITAS Storage Foundation Release Notes

Open Documentation Issues

Open Documentation Issues


VxFS Documentation Errata
Incorrect Disk Layout Maximum File and File System Sizes in the VxFS Administrators Guide
Below are the correct maximum file and file system sizes for disk layout Version 4 and 6: The Version 4 disk layout supports file sizes up to 1 terabyte with the largefiles flag set and 2 gigabytes with the nolargefiles flag set, and file system sizes up to 1 terabyte. The Version 6 disk layout can theoretically support files up to 8 terabytes (2 ) and file systems up to 8 exabytes (2 ). The maximum file system size that can be created is currently restricted to 2 blocks. For a file system to take advantage of greater than 1 terabyte support, it must be created on a VERITAS Volume Manager volume, and only on a 64-bit kernel operating system. The maximum file system size on the 32-bit kernel versions of AIX 5.1, 5.2, and 5.3 and the 64-bit kernel version of AIX 5.1 is still 1 terabyte, while the maximum file size is 1 terabyte with the largefiles flag set and 2 gigabytes with the nolargefiles flag set. For the 64-bit kernel versions of AIX 5.2 and 5.3, the maximum file size is 8 terabytes with the largefiles flag set and 2 gigabytes with the nolargefiles flag set, while the maximum size of the file system you can create depends on the block size:
40 63 35

Block Size

Currently-Supported Maximum File System Size 68,719,472,624 sectors (. 32 TB) 137,438,945,248 sectors (. 64 TB) 274,877,890,496 sectors (. 128 TB) 549,755,780,992 sectors (. 256 TB)

1024 bytes 2048 bytes 4096 bytes 8192 bytes

If you specify the file system size when creating a file system, the block size defaults to the appropriate value as shown above. See the mkfs(1M) manual page for more information.

23

Software Limitations

VxVM Documentation Errata


Incorrect References in the VxVM Adminstrators Guide
The VERITAS Volume Manager Administrators Guide contains references to the VERITAS Volume Manager Migration Guide. These references should refer to the VERITAS Storage Foundation Migration Guide.

Software Limitations
This section lists the software limitations for this release that may affect operation.

VERITAS Volume Manager Software Limitations


Virtual SCSI Limitations and Impact
The following information is for Virtual SCSI support:

Currently VxVM does not support portable data containers (PDC) on Virtual SCSI devices. By default all Virtual SCSI devices are supported as native type devices as aixdisk types. Currently Virtual SCSI devices do not support SCSI-3 reservation, which prevents SFRAC functionality.

VERITAS Volume Replicator Software Limitations


Unsupported Internet Protocol Versions
VVR does not support IPv6. All nodes in a VVR environment must use IPv4. [e135504]

RAID-5 Volume
VVR does not support Volume Manager RAID-5 volumes as part of RVGs. Hardware RAID-5 is supported.

24

VERITAS Storage Foundation Release Notes

Getting Help

Disk Group Split and Join


VVR does not support Disk Group Split and Join. This means that you cannot use Disk Group Split and Join on data volumes in an RVG. However, you can take snapshots of data volumes and use DGSJ on the snapshots.

Importing a Disk Group with VVR Objects


If a private disk group containing VVR objects is imported on two nodes, as well as the problems documented for VxVM objects, the SRL is corrupted and a full resynchronization of the Secondary is required.

VERITAS File System Software Limitations


Migrating Logical Volume Manager Groups
Migrating Logical Volume Manager (LVM) volume groups to VERITAS Storage Foundation converts only JFS file systems to VxFS. LVM volumes containing JFS2 file systems are skipped and are not converted to VxFS.

Getting Help
For technical assistance, visit http://support.veritas.com and select phone or email support. This site also provides access to resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and the VERITAS customer email notification service. Use the Knowledge Base Search feature to access additional product information, including current and past releases of product documentation. Diagnostic tools are also available to assist in troubleshooting problems associated with the product. These tools are available on disc or can be downloaded from the VERITAS FTP site. See the README.VRTSspt file in the support directory for details. For license information, software updates and sales contacts, visit https://my.veritas.com/productcenter/ContactVeritas.jsp. For information on purchasing product documentation, visit http://webstore.veritas.com.

25

Getting Help

26

VERITAS Storage Foundation Release Notes