This action might not be possible to undo. Are you sure you want to continue?
Veritas Storage Foundation™ Cluster File System Release Notes
The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Product version: 5.1 Document version: 5.1.2
Copyright © 2010 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, Veritas, Veritas Storage Foundation are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com
please have the following information available: ■ ■ ■ ■ Product release level Hardware information Available memory. When you contact Technical Support. Technical Support’s primary role is to respond to specific queries about product features and functionality. make sure you have satisfied the system requirements that are listed in your product documentation.Technical Support Symantec Technical Support maintains support centers globally. 7 days a week Advanced features. Also. you should be at the computer on which the problem occurred. disk space. For example. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion.symantec.com/business/support/contact_techsupp_static. you can visit our Web site at the following URL: www. including Account Management Services ■ ■ ■ ■ For information about Symantec’s Maintenance Programs. the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates.com/business/support/index. The Technical Support group also creates content for our online Knowledge Base. and NIC information Operating system . Symantec’s maintenance offerings include the following: ■ A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers automatic software upgrade protection Global support that is available 24 hours a day.jsp Contacting Technical Support Customers with a current maintenance agreement may access Technical Support information at the following URL: www.jsp Before contacting Technical Support. in case it is necessary to replicate the problem.symantec.
such as address or name changes General product information (features. and chapter and section titles of the text on which you are reporting.■ ■ ■ ■ Version and patch level Network topology Router.symantec. Send suggestions for improvements and reports on errors or omissions. Include the title and document version (located on the second page).com . Send feedback to: sfha_docs@symantec. access our non-technical support Web page at the following URL: customercare. local dealers) Latest information about product updates and upgrades Information about upgrade assurance and maintenance contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals Documentation feedback Your feedback on product documentation is important to us. and IP address information Problem description: ■ ■ ■ Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes Licensing and registration If your Symantec product requires registration or a license key.symantec. gateway.com Customer service Customer Care information is available at the following URL: www. language availability.com/customercare Customer Service is available to assist with the following types of issues: ■ ■ ■ ■ ■ ■ ■ ■ ■ Questions regarding product licensing or serialization Product registration updates.
com Select your country or language from the site index. please visit our Web site at the following URL: www.com email@example.com. and Africa North America and Latin America customercare_apac@symantec. and global insight.Maintenance agreement resources If you want to contact Symantec regarding an existing maintenance agreement. and countermeasures to prevent attacks before they occur. Enterprise services that are available include the following: Symantec Early Warning Solutions These solutions provide early warning of cyber attacks. ensuring rapid response to real threats. Each is focused on establishing and maintaining the integrity and availability of your IT resources. Middle-East. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners.com semea@symantec. implementation. and awareness communication programs. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment. design. which enable you to manage your business risks proactively. Educational Services provide a full array of technical training. Managed Security Services These services remove the burden of managing and monitoring security devices and events. monitoring. security certification. expertise. Consulting Services Educational Services To access more information about Enterprise services. comprehensive threat analysis.com Additional enterprise services Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge. please contact the maintenance agreement administration team for your region as follows: Asia-Pacific and Japan Europe. security education. . and management capabilities.
2.pdf This document is Document version: 5.com/sf/5.Storage Foundation Cluster File System Release Notes This document includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of this release Changes in Storage Foundation Cluster File System Storage Foundation for Databases supported features System requirements Component product release notes Software limitations Fixed issues Known issues No longer supported Documentation Overview of this release Before you continue. It is online at: http://sfdoccentral. This document provides release information about the products in the Veritas Storage Foundation Cluster File System 5.1.1 product line: .1/aix/sfcfs_notes.symantec. make sure that you are using the current version of this guide.
See the Veritas Cluster Server Release Notes. review the Late-Breaking News TechNote on the Symantec Technical Support website: http://entsupport. including: ■ ■ ■ Determining if systems are ready to install or upgrade Veritas products Gathering deployment and usage information on Veritas products Receiving notifications about the latest updates for: ■ ■ ■ Patches Hardware Compatibility Lists (HCLs) Array Support Libraries (ASLs) . For the latest patches available for this release. Review this entire document before installing your Veritas Storage Foundation Cluster File System product.symantec. go to: http://vos.symantec. Enterprise.com/docs/334998 The hardware compatibility list (HCL) contains information about supported hardware and is updated regularly. and Enterprise HA) Veritas™ Volume Manager (VxVM) Veritas™ File System (VxFS) ■ ■ See the Veritas Storage Foundation Cluster File System Installation Guide.com/docs/330441 Before installing or upgrading Storage Foundation and High Availability Solutions products. Standard HA. About Veritas Operations Services Veritas Operations Services (VOS) is a Web-based application that is designed specifically for Veritas CommandCentral and Veritas Storage Foundation and High Availability products. For the latest information on supported hardware visit the following URL: http://entsupport. VOS increases operational efficiency and helps improve application availability.com/. This document does not contain release information for Veritas Cluster Server. review the current compatibility list to confirm the compatibility of your hardware and software. VOS automates and simplifies administrator tasks.8 Storage Foundation Cluster File System Release Notes Overview of this release ■ Veritas Storage Foundation™ Cluster File System (SFCFS) (Standard. For important updates regarding this release.symantec.
A license key is used during the installation of a software to identify that the user has the right to use the software. Previous releases of Veritas products required that you obtain a license key prior to installation. the product installer does not require that you enter a license key.1. Installation and upgrade Storage Foundation Cluster File System installation and upgrade includes the following changes in 5. A software license is a legal instrument governing the usage or redistribution of copyright protected software. The administrator and company representatives must ensure that a server or cluster is entitled to the license level for the products installed.com/ Changes in Storage Foundation Cluster File System This section describes the changes in Veritas Storage Foundation 5. go to: http://vos. The keyless license strategy does not eliminate the need to obtain a license. In this release of the Veritas products.symantec. The installer prompts for the product modes and options that you want to install. The installer prompts you to select one of the following licensing methods: ■ ■ Install a license key for the product and features that you want to install.1: Veritas keyless licensing This release of the Veritas products introduces the option to install without a license key. and then sets the required product level. Continue to install without a license key. .Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 9 ■ ■ Array Policy Modules (APMs) Determining whether your Veritas product configurations conform to best practices Managing server and environmental configuration data from a single Website Interpreting Unified Message Identifier (UMI) codes and their solutions Identifying and downloading patches for Veritas products ■ ■ ■ To access VOS. The installer required that you enter a valid license key before the Veritas software was installed. Symantec reserves the right to ensure entitlement and compliance through auditing.
you must install a valid license key corresponding to the license level entitled or continue with keyless licensing by managing the server or cluster with a management server. Table 1-1 5. or if you install or upgrade with a method other than the product installer. For more information about keyless licensing.1 Package name VRTScps Explanation of changes Package description New package. the product installer does not change the license keys that are already installed. If you do not comply with the above terms. it allows you to change the product level easily. and results in warning messages. Symantec recommends updating to keyless licensing for the following reasons: ■ ■ it enables 5. see the following URL: http://go. Use the vxlicinst command to install a valid product license key for the 5.0 Package Name N/A List of packages 5.1 functionality.10 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System Within 60 days of choosing this option. This option also requires that you manage the server or cluster with a management server. ■ You can also use the above options to change the product levels to another level that you are authorized to use. you must do one of the following to license the products: ■ Run the vxkeyless command to set the product level for the products you have purchased. Veritas Cluster Server Coordination Point Server .symantec. continuing to use the Veritas product is a violation of your end user license agreement.com/sfhakeyless If you upgrade to this release from a prior release of the Veritas software. For information about setting or changing the product level. Packaging updates Table 1-1 lists the updates related to packages for this release. See the vxkeyless(1m) manual page. see the Installation Guide for your Veritas product. If you upgrade with the product installer.1 products you have purchased. The existing license keys may not activate new features in this release.
Obsolete in 5. Obsolete in 5.Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 11 Table 1-1 5.x CMC release.0 by Symantec N/A VRTSsfmh New package. Veritas Cluster File System Documentation available Documentation in DVD media as PDFs. Veritas Cluster Server Enterprise Agents Veritas Storage Foundation Managed Host Volume Manager ASL/APM Symantec License Inventory Agent Veritas Enterprise Administrator action agent Veritas Cluster Server ACC Library 5.1.1. Not available for fresh installation.0MP3. VRTSccg VRTSsfmh Consolidated into VRTSsfmh. VRTSaa VRTSsfmh VRTSacclib N/A VRTSalloc N/A Veritas Storage Foundation Intelligent Storage Provisioning Symantec Product Authentication Service Veritas Cluster Server Agents for Storage Foundation Cluster File System Veritas Enterprise Administrator Central Control Grid VRTSat VRTSat No change. N/A SYMClma VRTSaslapm N/A New package. Delivered Veritas Cluster Management with 5. Delivered with 5.0MP3. Console Cluster Connector Obsolete in 5. Obsolete in 5. Consolidated into VRTSsfmh.1 Package name VRTSvcsea Explanation of changes Package description New package. VRTScavf VRTScavf No change.0MP3.0 Package Name N/A List of packages (continued) 5. VRTScfsdc N/A Obsolete in 5.x CMC release.1. User Documentation for Veritas Cluster Management Console VRTScmccc N/A VRTScmcdc N/A . Functionality dropped. Only available to upgrade customers. Obsolete in 5. Functionality dropped.
1 Package name N/A Explanation of changes Package description Obsolete in 5.1.symantec. Available Veritas Cluster Server Cluster for download from Manager http://go.0MP3. Functionality dropped.0MP3.x CMC release. Veritas Centralized Management for Storage Foundation Management Server VRTScs N/A VRTScscm N/A Obsolete in 5. Delieverd with SFM release. .com/vcsmc. Obsolete in 5. Veritas Cluster Management Console for multicluster environments VRTScmcs N/A Obsolete in 5.12 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System Table 1-1 5. Functionality dropped. Veritas Cluster Utility VRTScutil VRTScutil VRTScweb N/A Veritas Enterprise Administrator Central Server Documentation Veritas Storage Foundation Graphical User Interface for DB2 Veritas Storage Foundation for DB2 VRTSd2gui N/A VRTSdb2ed N/A Obsolete in 5.symantec. Available Veritas Cluster Server for download from Simulator http://go. Delivered with 5. Console for single cluster environments Obsolete in 5. Delivered with SFM release.0MP3.1.x CMC release.com/vcsmc Obsolete in 220.127.116.11.0MP3.0 Package Name VRTScmcm List of packages (continued) 5.1. Veritas Cluster Server Configuration Wizards Veritas Enterprise Administrator Central Server Documentation Veritas Cluster Server Oracle and RAC Configuration Wizards VRTScscw N/A VRTScsdoc N/A Obsolete in 5. Obsolete in 5. Obsolete in 5. Delivered with SFM release. Delivered Veritas Cluster Management with 5.1. VRTScsocw N/A VRTScssim N/A Obsolete in 5. Expanded to include few VCS packages.
Sybase Symantec Shared DBMS ASA repository no longer used in 5. VRTSddlpr N/A Obsolete in 5.Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 13 Table 1-1 5. Functionality dropped. Veritas Distributed Command Line Interface Veritas Disk Correlator Provider VRTSdcli N/A VRTSdcp N/A Obsolete in 5.1. Obsolete in 5.0 Package Name VRTSdbac List of packages (continued) 5. Obsolete in 5.1.0MP3.0MP3. Expanded to include DBED packages. Veritas Storage Foundation Documentation available Documentation for Databases in DVD media as PDFs.0MP3. Veritas Storage Foundation for Oracle VRTSdbed VRTSdbed VRTSdbms3 N/A Obsolete in 5.0MP3. Delieverd with SFM release. Veritas Device Discovery Functionality merged into Layer Services Provider VRTSob. Veritas Oracle Real Application Cluster Support Package Veritas Storage Foundation Common Utilities for Databases VRTSdbcom VRTSdbed Consolidated into VRTSdbed.1 Package name VRTSdbac Explanation of changes Package description No change. Veritas Datacenter Storage Agent Veritas Datacenter Storage Manager VRTSdsa N/A VRTSdsm N/A VRTSfas N/A Veritas FlashSnap Agent for Symmetrix Veritas Cluster Server Agents for Veritas FlashSnap Agent for Symmetrix VRTSfasag N/A . Functionality dropped.1. Obsolete in 5. Delieverd with SFM release. Obsolete in 5.1. VRTSdbdoc N/A Obsolete in 5.1. Obsolete in 5. Functionality dropped.0MP3.
Veritas File System Documentation available Documentation in DVD media as PDFs. VRTSgcsha N/A Veritas GCS high availability agents VRTSgcspr N/A Veritas SAN Global Configuration Server Object Bus Provider Veritas Global Lock Manager Veritas Group Messaging Services Symantec Infrastructure Core Services Common VRTSglm VRTSgms VRTSglm VRTSgms VRTSicsco N/A Obsolete in 5. No change. Consolidated into VRTSob. Delieverd with SFM release. Delieverd with SFM release. Obsolete in 5.0 Package Name VRTSfasdc List of packages (continued) 5. Consolidated into VRTSfssdk. VRTSgab VRTSgab Veritas Group Membership and Atomic Broadcast Veritas Generic Array Plug-in for Mapping Services VRTSgapms N/A Obsolete in 5.0MP3. Delieverd with SFM release. Obsolete in 5.Manual Pages Veritas File System SDK Manual Pages Veritas File System Management Services Provider Veritas File System SDK Veritas File System Provider Web Client Extension VRTSfsman VRTSvxfs VRTSfsmnd VRTSfssdk VRTSfspro VRTSob VRTSfssdk VRTSfsweb VRTSfssdk N/A No change. Delieverd with SFM release. No change.0MP3.14 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System Table 1-1 5.0MP3. Obsolete in 5.0MP3.0MP3. Veritas FlashSnap Agent for Symmetrix Documentation VRTSfsdoc N/A Obsolete in 5. No change. .0MP3.1. Consolidated into VRTSvxfs. Functionality dropped.1 Package name N/A Explanation of changes Package description Obsolete in 5. Veritas File System .
1.0 Package Name VRTSjre List of packages (continued) 5. Functionality Delivered with SFM release Obsolete in 5. No change VRTSobgui N/A Veritas Enterprise Administrator VRTSobweb N/A Veritas Enterprise Administrator Web Console VRTSodm VRTSorgui VRTSodm N/A Veritas Oracle Disk Manager Obsolete in 5. Functionality Delivered with SFM release.0MP3. No change. Graphical User Interface for Oracle Obsolete in 5.1.0MP3.1.1. Consolidated into VRTSsfmh. Symantec Private Branch Exchange Veritas Perl 5.8. VRTSmapro N/A Consolidated into VRTSob. VRTSllt VRTSllt No change. . VRTSsmf N/A Obsolete in 5. Veritas Java Runtime Environment Redistribution Symantec Java Runtime Environment Redistribution Veritas Low Latency Transport Veritas Storage Mapping Provider Veritas Storage Foundation Management host Veritas Enterprise Administrator Service Veritas Enterprise Administrator Core VRTSjre15 N/A Obsolete in 5. Functionality Delivered with SFM release.1.Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 15 Table 1-1 5.1 Package name N/A Explanation of changes Package description Obsolete in 5. No longer Veritas Storage Foundation supported. VRTSmh VRTSsfmh VRTSob VRTSob VRTSobc33 N/A Obsolete in 5.8 redistribution Symantec Service Management Framework VRTSpbx N/A VRTSperl VRTSperl No change. Obsolete in 5.1.
Obsolete in 5. Expanded to include agents previously included in VRTSvcsvr. Consolidated into VRTSvcs. VRTSvail N/A VRTSvcs VRTSvcs Veritas Cluster Server VRTSvcsag VRTSvcsag Veritas Cluster Server Bundled Agents VRTSvcsdb VRTSvcsea Veritas High Availability Agent for DB2 VRTSvcsdc N/A Obsolete in 5.16 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System Table 1-1 5.1. Consolidated into VRTSvcs. Functionality dropped. Functionality Delivered with SFM release. Consolidated into VRTSvcsea. Consolidated into VRTSvcsag. Obsolete in 5. Expanded to include few VCS packages.1. User Documentation for Documentation available Veritas Cluster Server in DVD media as PDFs.0MP3. .1. Consolidated into VRTSvcsea. Veritas Cluster Server English Message Catalogs Manual Pages for Veritas Cluster Server Veritas High Availability Agent for Oracle Veritas High Availability Agent for Sybase Veritas Cluster Server Agents for Veritas Volume Replicator Veritas Device Identification API Veritas Kernel Interface Symantec License Utilities VRTSvcsmg VRTSvcs VRTSvcsmn VRTSvcs VRTSvcsor VRTSvcsea VRTSvcssy VRTSvcsea VRTSvcsvr VRTSvcsag VRTSvdid N/A VRTSveki VRTSvlic VRTSveki VRTSvlic No change.0 Package Name VRTSspt List of packages (continued) 5. No change. Veritas Software Support Tools Veritas Storage Foundation for Sybase Veritas Array Providers VRTSsybed N/A Obsolete in 5.1 Package name VRTSspt Explanation of changes Package description No change. Consolidated into VRTSvcsea.
User Documentation for Documentation available Veritas Volume Replicator in DVD media as PDFs. Veritas VxMS Mapping Service.0MP3. Expanded to include Veritas File System VRTSfsman (man pages). Delivered with SFM release. User Documentation for Documentation available Veritas Volume Manager in DVD media as PDFs.0MP3.1.0MP3.0 Package Name VRTSvmdoc List of packages (continued) 5.On Linux: VRTSvxfs-common and VRTSvxfs-platform packages are consolidated into single VRTSvxfs package. Veritas Volume Server and Client Provider Veritas I/O Fencing VRTSvsvc N/A VRTSvxfen VRTSvxfs VRTSvxfen VRTSvxfs No change. Delivered Veritas Volume Replicator with SFM release.1. Application Libraries VRTSvxmsa N/A .Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 17 Table 1-1 5. Web Console Obsolete in 5.1 Package name N/A Explanation of changes Package description Obsolete in 5. Veritas Volume Replicator Management Services Provider VRTSvrpro N/A VRTSvrw N/A Obsolete in 5. Manual Pages for Veritas Volume Manager Veritas Volume Manager Management Services Provider Veritas Volume Manager Management Services Web Client Extensions VRTSvmman VRTSvxvm VRTSvmpro N/A VRTSvmweb N/A Obsolete in 5.0MP3. Consolidated into VRTSob. VRTSvrdoc N/A Obsolete in 5. Consolidated into VRTSob. Obsolete in 5. Functionality dropped. Consolidated into VRTSvxvm.
When you install with the product installer. Obsolete in 5. All filesets: installs all available filesets.On Linux: VRTSvxvm-common and VRTSvxvm-platform packages are consolidated into single VRTSvxvm package. . Option to install only the minimal packages The product installer now provides several options for which packages to install.0 Package Name VRTSvxvm List of packages (continued) 5. This change enables you to explicitly choose which functionality is installed. using the installation simulator. In previous releases. For each product.1. the recommended packages or all of the packages.1 Package name VRTSvxvm Explanation of changes Package description Expanded to include Veritas Volume Manager VRTSvxman (man binaries pages). you can install the minimal packages. Improved response file generation You can now create response files without performing a live installation. you can select from one of the following install options: ■ ■ ■ Minimal filesets: installs only the basic functionality for the selected product.18 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System Table 1-1 5. Recommended filesets: installs the full feature set without optional filesets. Symantec Web Server VRTSweb N/A Install options for Storage Foundation High Availability and the Storage Foundation Cluster File System High Availability The product installation programs now prompt you for whether you want to install the high availability packages when you are installing Storage Foundation or Storage Foundation Cluster File System. The product installer displays Storage Foundation High Availability and Storage Foundation Cluster File System High Availability on the product selection menu. the installed license key determined what functionality was installed.
bff fileset is also installed. Veritas extension for Oracle Disk Manager fileset is installed by default for Storage Foundation and Storage Foundation Cluster File System The Veritas extension for Oracle Disk Manager package is supported with a Storage Foundation license. Devices in VIO client appear as regular SCSI disks. Storage Foundation Cluster File System support with NPIV technology Storage Foundation Cluster File System now supports the AIX VIO environment where VIOS is configured with NPIV capable FC adapters connected to a NPIV capable SAN (SAN switch that is NPIV capable). In this release. For storage arrays which include features such as SCSI-3 or active/active multi-pathing. the VIO client environment is transparent to Storage Foundation Cluster File System and all the Storage Foundation Cluster File System commands behave the same way as they would in a regular physical AIX server.Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 19 When you install with a product install script. This functionality enables Storage Foundation Cluster File System (specifically. With NPIV. -recpkgs: displays the recommended filesets and patches. -allpkgs: displays all available filesets and patches. DMP) to treat these devices like any regular SAN storage array LUNs. you can use the following options to the install script: ■ ■ ■ -minpkgs: displays the filesets and patches required for basic functionality. so Storage Foundation Cluster File System identifies these LUNs based on the array properties where LUNs are provisioned from. For Storage Foundation Cluster File System. This functionality is supported for both Storage Foundation Cluster File System and Storage Foundation Cluster File System High Availability. when attached through the VIO Server this functionality is available for storage provisioned with NPIV. . Storage Foundation Cluster File System would claim the devices as vSCSI LUNs. the GMS VRTSgms. In the legacy VIO environment. The HCL support is identical to dedicated HBAs to LPARs/micro-partitions. the product installer now installs the required fileset for ODM by default when Storage Foundation is installed. with NPIV.. This release of Storage Foundation Cluster File System also provides DMP support for booting off (rootvg) NPIV devices. such as installsf.
The installer then gives an option to resume the installation or upgrade. Option to start or stop Storage Foundation Cluster File System HA After the installation and configuration is complete. These sample scripts include all of the relevant Symantec packages in the correct order for installation. See the Veritas Storage Foundation Cluster File System Installation Guide for more details.20 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System Option to create response file templates You can use the -makeresponsefile option of the installer to create response file templates. if required. uninstallation. The installer also generates a response file after each successful installer task. the next time you re-run it the installer discovers the presence of an installer instance. Installer does not proceed with installation in RSH/SSH disabled environments In the previous releases of Storage Foundation Cluster File System. Support for installer resilience If an installation or upgrade of Storage Foundation Cluster File System is interrupted. See the Veritas Storage Foundation Cluster File System Installation Guide for more details. Installation options for NIM The installer program can generate sample finish or configuration scripts that integrate with native installation tools. These response files contain the details that you provided to the installer questions in the form of values for the response file variables. You can use the product installer to stop or start the processes and load or unload the drivers. not upgrades. The response file also contains descriptions and explanations of the variables and their values. This feature is supported for installations. the installer installed and configured Storage Foundation Cluster File System only on the local system and the systems with which it could communicate. in certain secure enterprise environments where RSH or SSH communication was not enabled. or upgrade. See the Veritas Storage Foundation Cluster File System Installation Guide. the installer starts the processes that the installed products use. such as installation. configuration. .
With this release of Storage Foundation Cluster File System. The following information is displayed: ■ ■ ■ ■ Required operating system level Required patches Required disk space Other requirements . The Web-installer can perform the following functions: ■ ■ ■ ■ ■ ■ Install Storage Foundation Cluster File System HA Uninstall Storage Foundation Cluster File System HA Configure Storage Foundation Cluster File System HA Upgrade Storage Foundation Cluster File System HA Start and stop Storage Foundation Cluster File System HA Perform an installation precheck The installer program's default answer is no to configure optional features The installer's default answer to configure optional features is now no. Gathering requirements using the installer program You can use the -requirements option of the installer to gather the installation requirements. You can use a Web-interface to install and configure Storage Foundation Cluster File System HA. You must enter y if you want to configure certain optional features. the installer mandates the availability of either RSH or SSH communication between the systems to perform any installer task. Support for Web-based installer This release supports an interactive installation using the Web-based installer. Web-based installer also provides you with a similar option.Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 21 The installer also generated a response file that you could copy to the other systems in the cluster to identically install and configure Storage Foundation Cluster File System on other systems.
but stops the cluster during the addition of the node. . Based on the existing cluster configuration. which follow in outline: ■ When you perform a successful precheck. For RSH communication. IPv6 support for the installer programs You can now use the installer to install and configure Storage Foundation Cluster File System HA on systems with IPv4. ■ Selecting default systems for installation From the local system. the installer also configures the new node to use Symantec Product Authentication service and to use I/O fencing. then no default node names are provided. When found. and configuration options. Communication modes By default. installation. After a successful installation. the -rsh option is available. you have the option to continue with the configuration. or you can return to the configuration later. the installer program presents these as default nodes for installation. or mixed stack configurations. IPv6. The installation program can install on systems which may have heterogeneous (RSH and/or SSH) communication modes enabled. Adding a node using the -addnode option The -addnode option has been added to the installer to add a node to a running cluster. the installer program checks for the /etc/llthosts for node names. The following limitations apply: ■ ■ RSH is not supported on AIX SSH on AIX requires that you enable sshd. the installer program uses SSH for communication. you have the option to continue with the installation. If the llthosts file is not present. The installer program switches to RSH if password-less SSH is not enabled. The installer also supports adding a node to a single node cluster.22 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System Support to continue installation after a successful precheck The installer program has more sophisticated precheck. The installer programs supports mixed RSH and SSH modes on nodes in a cluster.
Supported paths for SFCFS upgrades that do not require a system reboot When you perform a typical upgrade using the installer program from SFCFS version 5. Changes related to the installer for cross-product upgrades This release includes the following change related to the cross-product upgrades. and upgrades on alternate boot disks for AIX. For example. If you try to perform a cross-product upgrade.30. the installer now gracefully exits with an error message.0. Refer to the Veritas Storage Foundation Cluster File System Installation Guide. the installer displays the following error message: SFCFS 5. if you choose to upgrade SFCFS 5.30. Upgrading SFCFS 5.1 is not supported.1.0.0 MP3 to SF Oracle RAC 5. Upgrades that follow any other upgrade paths require a reboot.00 directly to SFRAC 5.0 MP3 to SFCFS version 5.00 is installed. a system reboot is not required. Operations that you can perform using response files follow: ■ ■ ■ ■ Fresh installations Configurations Uninstallations Upgrades from previous supported releases Command options to help troubleshoot installations You can run the installer with the -debug option and the -trace option to troubleshoot an installation. Silent and automated installation enhancements for response files The installer program supports silent installations using response files. uninstallation.Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 23 Installer support for alternate boot disk The installer program supports install.1. .
monitor and report on Storage Foundation product environments.1 version of the stack product. See the appropriate product Installation Guides for upgrade instructions. Addition of Storage Foundation for Databases (SFDB) functionality Storage Foundation for Cluster File System previously provided enhanced I/O methods to improve database performance and a set of tools for ease of management of storage in a database environment: ■ ■ ■ ■ ■ ■ ■ Veritas extension for Oracle Disk Manager (ODM) Veritas extension for Cached Oracle Disk Manager (Cached ODM) Veritas Quick I/O Veritas Cached Quick I/O Storage Checkpoints FlashSnap Dynamic Storage Tiering For information on the I/O and database management features available with a Standard license: See the Veritas Storage Foundation Advanced Features Guide.com/vom.1.1. a version is available for download from http://go. See the Veritas Storage Foundation Cluster File System Installation Guide for supported upgrade paths. and then install the 5. . You must upgrade SF or SFHA to version 5.symantec.1: Veritas Enterprise Administrator Graphical User Interface The Veritas Enterprise Administrator (VEA) console is no longer packaged with Storage Foundation products. If you wish to continue using VEA. Storage Foundation Cluster File System Storage Foundation Cluster File System includes the following changes in 5.symantec. You can download this utility at no charge at http://go.com/vom. Symantec recommends use of Storage Foundation Manager to manage.24 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System The installer does not support a direct upgrade from a previous SFCFS version to SF Oracle RAC version 5.
0 to perform repository backup and restore and this command will be obsolete in release 5. This extended functionality is supported for configurations with single instance Oracle and includes the following: ■ ■ ■ ■ Database Checkpoints Database FlashSnap Database Cloning Database Dynamic Storage Tiering For information on using SFDB tools. The SFDB tools provide enhanced ease-of-use commands which can be run by a database administrator without root privilege to optimize storage for an Oracle database environment. ■ ■ Use the dbed_update command to create a new SQLite SFDB repository.1.1: ■ ■ ■ ■ ■ ■ SQLlite repository Multiple disk group support for FlashSnap Mapped mount points for individual volumes for Database Flashsnap clones Oracle Dataguard support Oracle Enterprise Manager (OEM) Plugin Cached ODM support SFDB feature changes If you are upgrading from Storage Foundation for Oracle (HA) 4. The functionality of sfua_db_config is now used to set user and group access to various SFDB directories. SFDB new features New features in the Storage Foundation for Databases tools package for database storage management for release 5.0 to Storage Foundation for Cluster File System 5. the Storage Foundation for Databases (SFDB) feature for enhanced management of Oracle databases is included with Enterprise licensing for Storage Foundation Cluster File System and Storage Foundation Cluster File System HA.Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System 25 For release 5. Commands which have changed: ■ sfua_db_config functionality is changed: this command is no longer needed to create a SFDB repository. see the Veritas Storage Foundation: Storage and Availability Management for Oracle Databases guide. sfua_rept_adm was used in release 5.1.1. the following changes in functionality will apply.x or 5. .
dbed_ckptrollback. vxdbts_fstatsummary. vxstorage_stats DBED providers(DBEDAgent). vxdbts_get_datafile_stats dbed_saveconfig. Veritas Storage Foundation Manager 2. dbed_ckptmount. dbdst_convert. and tablespace to LUN mapping. dbed_vmclonedb. ■ Storage statistics: commandsdbdst_makelbfs.1: ■ ■ ■ ORAMAP (libvxoramap) Storage mapping commands dbed_analyzer. dbed_ckptumount Quick I/O commands: qio_getdbfiles. dbed_ckptpolicy qio_convertdbfiles -f option which is used to check for file fragmentation dbed_scheduler ■ ■ ■ ■ The following features are longer supported in release 5.1: ■ Storage Foundation for DB2 tools . Java GUI. dbed_ckptdisplay. The sfua_rept_migrate command is added for migrating the SFDB repository from the 4. dbed_vmsnap ■ ■ ■ Database Dynamic Storage Tiering commands: dbdst_addvol. dbdst_classify. database to LUN mapping. dbed_ckptquota. However.26 Storage Foundation Cluster File System Release Notes Changes in Storage Foundation Cluster File System ■ The sfua_rept_util command is used to perform SQLite repository backup and restore. dbdst_report SFDB features which are no longer supported Commands which are no longer supported in release 5. dbdst_rmvol. ■ Commands which continue to be supported: ■ ■ dbed_update Database Storage Checkpoint commands: dbed_ckptcreate. dbdst_tbs_move. qio_recreate. dbed_clonedb. dbdst_partition_move.1 release.0 release to the 5.x or 5. dbdst_admin. dbed_checkconfig dbed_ckptplan. dbdst_preset_policy. dbed_ckptremove. dbdst_fiostat_collector. dbdst_show_fs. qio_convertdbfiles Database Flashsnap commands: dbed_vmchecksnap. The SFDB Oracle features can only be accessed through the command line interface.1 (a separately licensed product) can display Oracle database information such as tablespaces. dbdst_file_move. and dbed_dbprocli.
review the current compatibility list to confirm the compatibility of your hardware and software. visit the following URL: http://entsupport. see the Veritas Cluster Server Installation Guide. For the latest information on supported hardware. For the most current information on Storage Foundation Cluster File System products and single instance Oracle versions supported. See the Veritas Storage Foundation Cluster File System Administrator's Guide for more information. see: http://entsupport. See the cfsshare(1M) manual page.1 Hardware and software requirements The hardware compatibility list contains information about supported hardware and is updated regularly.symantec. .com/docs/330441 For information on specific HA setup requirements.com/docs/331625 System requirements This topic includes system requirements for 5.symantec.Storage Foundation Cluster File System Release Notes Storage Foundation for Databases supported features 27 ■ Storage Foundation for Sybase tools Clustered NFS Support This new Clustered NFS (CNFS) feature is expected to gracefully handle failure of any node and reclaim the advisory locks taken by NFS clients in such a way as to not accidentally lose any existing lock grants without notification. Storage Foundation for Databases supported features Note: Storage Foundation Cluster File System supports running SFDB tools with Oracle databases only. Before installing or upgrading Storage Foundation and High Availability Solutions products.
AIX 6. Disk space requirements Before installing any of the Veritas Storage Foundation products.com/docs/334998 Storage Foundation Cluster File System node requirements All nodes in a Cluster File System must have the same operating system version and update level. Use the "Perform a Preinstallation Check" (P) menu or the -precheck option of the product installer to determine whether there is sufficient space. all nodes in the cluster must have the same operating system version and update level.3 at one of the following levels: ■ ■ ■ TL7 with SP6 TL8 with SP4 or any higher TLs. The installation process terminates if the target systems do not meet the maintenance level requirements. For important updates regarding this release.28 Storage Foundation Cluster File System Release Notes System requirements Supported AIX operating systems This section lists the supported operating systems for this release of Veritas products. Product installation scripts verify the required update levels. For any Veritas cluster product. confirm that your system has enough free disk space.1 at one of the following levels: ■ ■ ■ TL0 with SP6 TL1 with SP2 or any higher TLs. # .symantec./installer -precheck . review the Late-Breaking News TechNote on the Symantec Technical Support website: http://entsupport. The minimum system requirements for this release are as follows: AIX 5.
If multicast networking is undesirable.pdf) Veritas Storage Foundation for Oracle RAC Release Notes (sfrac_notes.  Workaround: Add the set-addr entry for each local link into the /etc/llttab file. The component product release notes for this release are included as PDF files on the software disc: ■ ■ ■ Veritas Storage Foundation Release Notes (sf_notes.1 patches Symantec strongly recommends that you install Storage Foundation and High Availability Solutions (SFHA) 5. or unavailable in your environment. you add the following lines into the . Veritas Storage Foundation Cluster File System software limitations The following are software limitations in this release of Veritas Storage Foundation Cluster File System. For example. You add the entry to specify the address of the peer nodes that are available on the corresponding peer links. See the Veritas Cluster Server Release Notes for VCS software limitations. LLT over IPv6 UDP cannot detect other nodes while Storage Foundation Cluster File System tries to form a cluster LLT over IPv6 requires link-local scope multicast to discover other nodes when Storage Foundation Cluster File System tries to form a cluster. The patch for AIX is available at the following URL: https://vos. review all component product release notes before installing the product. use the address of the peer nodes to eliminate the need for the multicast traffic.1 Patch 1 immediately after you install SFHA 5.Storage Foundation Cluster File System Release Notes Component product release notes 29 Storage Foundation and High Availability Solutions 5.1.pdf) Software limitations The following sections describe Storage Foundation Cluster File System software limitations that exist in this release.pdf) Veritas Cluster Server Release Notes (vcs_notes.com/patch/detail/2956 Component product release notes In addition to reading these Release Notes.symantec.
If the Primary path is then enabled. the cluster-wide failover is triggered. All hosts in the cluster start using the Secondary path to the array. the hosts fail back to the Primary path. A/PF. and ALUA arrays. suppose that one of the hosts in the cluster is shut down or brought out of the cluster while the Primary path is disabled. if the disabled host is rebooted and rejoins the cluster before the Primary path is enabled. In this case. This is expected behavior. the node's IPv6 address is fe80::21a:64ff:fe92:1d70.APG. A/A-A. Cluster Volume Manager (CVM) fail back behavior for non-Active/Active arrays (1441769) This describes the fail back behavior for non-Active/Active arrays in a CVM cluster. enabling the path does trigger the failback. set-addr 1 link1 fe80::21a:64ff:fe92:1d70 set-arp 0 Workload partition environment The Veritas Storage Foundation Cluster File System is supported inside workload partition (WPAR) environment only through NFS mount options. Veritas Volume Manager software limitations The following are software limitations in this release of Veritas Volume Manager. It can not be enabled for files on Cluster File System. it does not trigger failback.30 Storage Foundation Cluster File System Release Notes Software limitations llttab file to specify the set-addr entry for a node. In this example. For A/P. When the disabled host is rebooted and rejoins the cluster. The remaining hosts in the cluster continue to use the Secondary path. When the Primary path is enabled. and ALUA arrays. When all of the Primary paths fail or are disabled in a non-Active/Active array in a CVM cluster. However. all of the hosts in the cluster will continue using the Secondary path. A/A-A. This behavior applies to A/P. . all of the hosts in the cluster will fail back to the Primary path. APG. Veritas File System software limitations The following are software limitations in this release of Veritas File System Cached ODM You can enable Cached ODM only for files on local file systems.
Table 1-2 Incident 1414489 1663269 Veritas Storage Foundation Cluster File System 5. Fixed an issue in which a clustered file system that was mounted on one node required fsck to be run. Fixed a panic in vxfs:vx_loadedele that was due to a NULL pointer dereference.0 MP3 RP2 fixed issues Description Fixed an issue in which Java threads hung on SFCFS functions. Fixed the duplicate mount entries found for a VxFS file system in a cluster. The vxfsckd -n command now initializes the nthrs variable. Incident 1286525 1518713 1539892 1591313 . Fixed the cause of a loop in the vx_dele_get_freespace() call due to a smap being marked bad.1 includes fixed issues from 5. 1714229 1805983 1854700 Table 1-3 Table 1-3 Veritas Storage Foundation Cluster File System 5. See the Veritas Cluster Server Release Notes for VCS fixed issues.0 and later unless otherwise noted.1 fixed issues Description Fixed an issue in ODM related to post commit transaction. Fixed the cause of inode errors on SFCFS file systems.1 release. Fixed a panic that was due to bad inode errors in an SFCFS environment.Storage Foundation Cluster File System Release Notes Fixed issues 31 Fixed issues The following sections describe Storage Foundation Cluster File System issues that were fixed in this release. Veritas Storage Foundation Cluster File System fixed issues All Veritas Storage Foundation Cluster File System 5. Table 1-2 describes fixed issues in the Veritas Storage Foundation Cluster File System 5.
Panic issue in voldiosio_start() as race window exists while handling duplicate DA records CR 6874695 .32 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-3 Veritas Storage Foundation Cluster File System 5. vxddladm disablevscsi does not work for this customer Incident 1822681 1822200 1819777 1810749 1805826 1804262 1797540 1795541 .0 MP3 RP2 fixed issues (continued) Description Fixed the cause of a hang that occurred after another node in the cluster crashed.0MP3 release.0 MP3 RP1 fixed issues Description Fixed the build script to compile packages to enable the storage keys feature.1 fixed issues Description memory leak in vxio/voldrl_cleansio_start.1 release.1 includes cumulative fixes for Veritas Volume Manager and Veritas Volume Replicator since the 5. Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5. Table 1-5 describes fixed issues in the Veritas Volume Manager 5. VxVM: vxdisk resize intermittently causes vxconfigd to dump core. VRAS:Diff sync failed when remaining sync size is 4TB. Incident 1600241 Table 1-4 Table 1-4 Veritas Storage Foundation Cluster File System 5.vxlustart -V deleted existing BEs panic in vol_klog_clear_trans on Solaris x86 VVR:File system I/O of size bigger than 256k fails with error ENXIO after 2TB(>2G blocks)offset. Incident 1487928 Veritas Volume Manager and Veritas Volume Replicator fixed issues The Storage Foundation Cluster File System 5. The following tables describe these fixed issues.
repl" DMP: System panic when perform excludearray operation with powerpath vxdctl settz and vxconfigd core dump if TZ environment variable is not set. -o delayrecover option does not work as expected for value of 0 kmsg layer: with heavy messaging in the cluster the receiver thread slows down processing kmsg layer: receiver side flowcontrol is not supported vol_find_ilock: searching of ilock is inefficient CVR:I/O hang in 4 node CVR cluster Oakmont::Primary slave hangs in volcvm_rvgrecovery_send_iocnt() TC remote_write_reconfigure_2.1 VVR:Disable Secondary logging through a tunable.d/bin/disk.1 fixed issues (continued) Description Sun: SC cannot open libvxvmsc. probably due to wrong disk capacity calculation Incident 1782036 1779257 1765779 1764972 1762561 1762534 1755869 1755830 1755810 1755788 1755735 1755707 1755689 1755628 1755519 1755466 1745992 1744672 1744224 1742702 .tc FMR3: multiple vxplex attach cmds running in parallel on a volume lead to clearing DCO map and subsequently lead to corruption vxvmconvert fails. tunable addition: gabmaxsend and receiver flowcontrol watermark kmsg: sender: the logic for resend of messages needs to be optimized kmsg: sender thread is woken up unnecessarily during flowcontrol for a broadcast message. Man Page change for vxiod vxdiskadm option 5 fails with "/usr/lib/vxvm/voladm.so after upgrade to 5.Storage Foundation Cluster File System Release Notes Fixed issues 33 Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5. sender thread may end up sending the same message multiple times (not resend) recovery I/Os get broken down to voliomem_chunk_size vxtask list shows the same taskid for parent and child tasks During recovery.
Unable to initialize EFI LUNs controlled by EMC Powerpath driver. vxprtvtoc "Syntax Error" occurs.unlabelled LUNs vanish from format until turned off VVR: Replication started with a checkpoint remains inconsistent/cant_sync after SRL is drained if the replication is interrupted Incorrect cur_pri_path updation for A/PG arrays leading to dmp database inconsistency VVR: VRAS: vradmin addsec fails with "V-5-52-502 Host name or IP XXX. System panic'd after 2 out of 4 paths to disk were removed.34 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5. VxVM volume device permissions change after running 'scgdevs' (Suncluster) command Incident 1739513 1733811 1732200 1728587 1728269 1725041 1722984 1718008 1715889 1711269 1710030 1678370 1678292 1677217 1676061 1674847 1673764 1673002 1653972 . vxconfigd loses licensing information Need to remove thousands of empty /tmp/vx." Memory leak in vold_dg_get_clone_disks() . Fixed an issue with vxconfigd not starting after a system reboot.1 fixed issues (continued) Description while mirroring 1 tb storage.ZZZ is not configured or available on the Primary. Unable to encapsulate an unmanaged EMC DMX PP LUN System hang showing kmsg receiver thread hogging CPU AIX: Issue with LUN size more than TB VM_VVR: RLINK disconnected and "vx" commands hung on Secondary while load in progress [SxRT sparc/x64] vxdmpadm get tpdnodename error DMP does not autofailback to the Primary paths following LCC card restoration.* directories.after 800gb all VM commands hangs System panic on voldco_isdirty code path while doing vxsnap make operation after upgrading from DCO version 10 [DMP][Usability] When NEW dmp_native_multipathing tunable is set to 'on' .YYY.
31. for no associated node in dmpnode VRAS: vradmind core dump if stats collection is enabled Incident 1638494 1638174 1637514 1594928 1592700 1591146 1589018 1588978 1555461 1545999 1545835 1543908 1541662 1538053 1537821 1531406 1530126 1517760 . Oracle process thread stuck into ogetblk() which leads to i/o hang. System panicked in DRL code when running flashsnap CVM_MSG_REQ_GSLOCK repeatedly resent resulting in hang VxVM private buffer's b_fsid field is not set properly.000 bytes . when aborted in between using vxevac Avoid unnecessary retries on error buffers when disk partition is nullified. which breaks PRM Race condition between Dynamic Reconfiguration thread and DMP error analysis code path lead to panic in gendmpiodone.1 fixed issues (continued) Description VVR:vxnetd stop causing 100% CPU & vx commands hanging oakmont:vxconfigd memory leak found Issues with tentative evacuation of disks. it leads to data corruption issue.Storage Foundation Cluster File System Release Notes Fixed issues 35 Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5. cvmvoldg monitor failed due to awk: Input line cannot be longer than 3. vxdmpadm getattr arrayname <array> partitionsize misreports DEFAULT partitionsize for subsequent entries DMP did not handle the failure in one half of the customer SAN Oracle hangs from time to time .1RP4 applied.VxVM 5. While running vxevac command. num_retries field is getting re-initialized to initial value leading to looping and delay in error handling time.VRTScavf 5.0 mirrored volume grow doesn't works well if "mirror=enclosure" option is used.0 MP3 on RHEL5 vxconfigd core dump during system boot after VxVM4. DMP : dmplinux_unplug() panic on linux.0.
causing panic at module unload time VxVM utility scripts assume DA name is a valid path name. User confused about snap operations when split to new DG vxdmpdebug fails to find ugettxt 1471771 1471581 1471487 1471263 1470732 1470251 1470102 1469351 1468647 . vxdisksetup should call 'mount' with complete pathname vxconfigd may hang if no SCSI timeout value is set while issuing various SCSI commands Critical Minimum Queue and Round-robin Improvements machine has panicked when added the disk from dg as a foreign device using "vxdmpadm addforeign". 1369599 Export API libvxvm_get_disks() and libvxvm_get_subpaths() should return the same path for the same device 1475697 1475691 1471821 1471784 Provide an API for checking multi. dmp disabled all paths of EVA8100 even though just unplugged primay FC cables For VxVM patches the postinstall script must not copy /usr/lib/libthread to /etc/vx/slib/ Incident 1510252 1506690 1503309 1483298 1480102 1475710 1475703.ownership and status of a diskgroup VxVM should recognize disks in use by ZFS or SVM 'initdmp' section in vxdctl manpage still incorrect [5. 5.36 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5.0MP3RP1 x64] vm can not create stripe-mirror/mirrorstripe/mirror volume with maxsize.0MP3 : vxconfigd dumps core if all paths are excluded. Man page for vxdctl does not include all options that are listed in -H. VxVM: DMP doesn't log error returned from below driver/SCSI. volslabd utilized 100% cpu time vxdmpadm getattr for failoverpolicy and tpdmode is giving usage error.1 fixed issues (continued) Description I/Omem chunks are not combined.
Need to examine package dependencies.Verification tool to detect corrupted DCO. "install-db" would be created if the vxio in "Defined" state..1 fixed issues (continued) Description no path disable event occurs during I/O error analysis in dmp when pulling a FC cable out with 5.Storage Foundation Cluster File System Release Notes Fixed issues 37 Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5.0MP3 [VxVM]Proper handling of DMP PGR ioctl's in case of errors/warnings from below driver. VVR: Rlink fail to connect due to failure of memory allocation for incoming message buffer VVR: Print warning message in syslog if it hit high water mark for latency protection Support cdsdisk format on devices that do not support scsi modesense on page 3 and page 4. Permissions set using vxedit is not consistent Incident 1463197 1460101 1443748 1443046 1441123 1437869 1437006 1433535 1430001 1425250 1424194 1422008 1421752 1415547 1409031 1402599 1398914 1396566 . In a clustered environment the recovery of volumes having DCO v20 taking lots of time with no I/O load System panic in vxio:voldrl_trans_copy VxFS Corruption Detected when DCM log plex are attached with mirrored volume and VVR is not configured. vx commands are hanging in EDC testing vxclustadm reinit doesn't allow new nodes to join CVM cluster After installed vm patch on AIX.1MP3 perf. especially wrt SUNWscpu.. High kernel CPU usage when DRL is turned on Tool request . DMP: Evaluation of DMP I/O statistics and TC development to verify correctness of the values displayed DDL: Data corruption protection activated message should be reported by vxdisk scandisks and vxdctl enable CLI VM: VVR: Not able to modify any of the volume manager kernel tunable on 4.
Panic in uphysdone due to double Iodone on the buffer vxconfigrestore -p returns with syntax error Enhance vxdiskadm to handle custom-made rootdisk and rootmirror Incident 1391652 1388324 1386592 1369610 1369597 1361625 1321282 1317186 1299512 1293910 1292633 1277808 1274204 1235023 1230827 1224778 1222625 1212256 1183283 1176510 .1 fixed issues (continued) Description No path disable event and I/O hang occurred when pulled out both paths of A/PG array with 4.0MP2RP8 Unresolved symbols in libvxvmsc.so tmp files not cleaned up after running vxdisksetup Error message from vxdg import misleading/incorrect when disk is write-protected vxlufinish uses wrong solaris command for unmounting alternate root environment . VVR: Write testcase for link-breakoff snapshot with RVG. get a reservation conflict vxdisk scandisk hung in site failure scenario (EDC Testing) Security: Remove tmp files in scripts before using them incorrect vxdg free output and vxconfigd core dump vxdmproot man page needs correction on arrays supported by DMP for SAN booting PFTO value is set for only one paths though the DMP node has multiple paths.should use luumount with use_all_paths=yes.x CVMCluster Agent doesn't handle non-C locales. Transaction aborted waiting for io drain vxdisksetup init succeeds but both prtvtoc & vxdiskunsetup fail with error "No Such Device" Write disable R2 device(SRDF)not seen after boot VCS 5.38 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5. vxbrk_rootmir fails if a volume name = end of another vol name V-5-1-4597 vxdg join failed.
Needs to manually import it and mount the volumes vxsnap refresh on SOSS fails with "VxVM vxvol WARNING V-5-1-10070 Failed to synchronize the volume(s)" APIs needed for checking whether diskgroup is shared and status of diskgroup Unable to set no limit for cmd logs using vxcmdlog -n no_limit FMR Refreshing a snapshot should keep the same name for the snap object INSTSNAPTMP marked dco log not getting deleted during vxrecover or volume restart a scsi-2 release is causing a panic cmhaltcl on one of the cluster nodes causes one of the disk groups to lose shared flag Incident 1172961 1153020 1123203 1114870 1082431 1082149 1068259 1060336 1037289 1020554 1016617 1012999 996429 990338 963951 818389 795129 .1 fixed issues (continued) Description AIX: VxVM should call uphysio() with a proper value for bufcnt argument CVM master's behavior with dgfailpolicy=leave in 5.0 differs from the description of manual vxconfigd hang in transaction commit while acquiring rwsleep write lock System panic in voliomem_seek() due to wrong calculation of no of dco I/O extents.Storage Foundation Cluster File System Release Notes Fixed issues 39 Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5. secondary not sending ack vxresize should not roll back if fsadm failed but disabled vxfs IO Errors during SVC node add/remove test sequence Diskgroup are not importing on every second or 3rd reboot. vxconfigd died requiring a reboot vxconvert command fails to convert for VPATH devices VVR:Primary hang in case of TCP replication. During VCS During cluster shutdown of a node.
Table 1-6 Veritas Volume Manager and Veritas Volume Replicator 5.0MP3 RP1 release. Fixed an issue with VxFS Corruption Detected when DCM log plex are attached with mirrored volume and VVR is not configured. Fixed an issue in a clustered environment the recovery of volumes having DCO v20 taking lots of time with no I/O load. Fixed an issue with the master node crashing if a node leaves before responding to the MV.1 key aware code. Fixed a panic in dmp_get_path_deferq while creating a volume.1 fixed issues (continued) Description Request to make voldrl_volumemax_drtregs a tunable unable to initialize EFI labeled >1tb PP devices vxdmpadm/vxdiskunsetup doesn't work well if tpdmode=native RFE : Failed to create more than 256 config copies in one DG CVM activation tag in vxprint -m output breaks vxprint vxdg split fails if the cvm master changes vxio reports "Illegal vminor encountered" even when there is no rootability If vxdg import returns error. Fixed an issue in FMR3.0MP3 RP1 fixed issues Description StorageKeys: Adding compilation flag for VxVM to make function pointer references to legacy modules work in AIX 6. Fixed an issue with siteread policy is not honored. I/Os initiating DCO updates for clearing DRL async clear region may not wait for its completion.serialization protocol. parse it Incident 786357 597517 543638 339282 339187 314738 298072 248925 Table 1-6 describes fixed issues in the Veritas Volume Manager 5. Incident 1512521 1455062 1449266 1443752 1443706 1441131 1441072 .40 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-5 Veritas Volume Manager and Veritas Volume Replicator 5.
Fixed an issue with vxconfigd core dumps. Fixed an issue with VVR I/O hanging due to the wrong generation number assignment after recovery. Fixed a secondary panic due to double free of message with TCP protocol and 16 connection.0MP3 RP1 fixed issues (continued) Description Fixed a bug in vxconfigbackupd script leading to 0 byte binconfig file being created. 1397879 1397712 .0 MP3. Fixed an issue with the cluster nodes panicking in voldco_or_pvmbuf_to_pvmbufcode after installing 5.Storage Foundation Cluster File System Release Notes Fixed issues 41 Table 1-6 Veritas Volume Manager and Veritas Volume Replicator 5. Fixed a CVR panic in VOLSIOQ_MORE due to corrupted volsioq_start queue. Fixed an issue with the vxsnap restore manual page is unable to properly freeze or thaw file systems in a CVM environment. Fixed an issue with vxesdlooping using 100% of one CPU. install-db would be created if the vxioin Defined state. Fixed an issue with vxdmpadm dumped core when executing vxdmpadm list dmpnode command. Enhanced the vxresize manual page to run from non-CVM master. Fixed an issue with after installing VM patch on AIX. Incident 1442369 1224659 1441020 1440837 1436917 1435471 1431279 1428106 1427284 1427267 1425919 1425434 1414441 1414381 1411636 1403123 Fixed an issue with vxconfigd sleeping and no vx commands were responding. Fixed a panic due to memory allocation failure in interrupt context. Fixed a secondary log error causing rlink disconnect after IBC unfreeze. Fixed an issue with CVR fails to connect rlinks followed by vxconfigd hangs on secondary. Fixed a system panic in vxio:voldrl_trans_copy. The vxsnap manual page includes mirror=enclosure parameter to avoid being mirrored on the same enclosure.
Fixed a system panic in vol_klog_start() due to accessing freed mv read_sio.42 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-6 Veritas Volume Manager and Veritas Volume Replicator 5. Fixed a system panic in vol_putdisk() code. Fixed an issue with VSCSI: A/P LB I/O policy not working with enabled DMP support on boot devices. Fixed a system panic in bcopy() due to null passed in from volioctl_copyin() Fixed a system panic due to memory allocation. Fixed an issue with vxcached never deletes old snaps when cache hits HWM. Fixed an issue with vxplexcore dumps during vxassist addlog due to DRL log length being less than 33 blocks. Incident 1396427 1389584 1389512 1387033 1385922 1376656 1372340 1368752 1364335 1364332 1364324 1364320 1314301 1266730 1230360 1192105 1182475 . Fixed the vxdg split failing if the CVM master changes.0. Created a command to verify whether the DMP is controlling the rootdisk. Fixed an issue with vxlustart. Able to force import diskgroup version 80 in VxVM 5. Fixed an issue when there are no mirrors to read.0MP3 RP1 fixed issues (continued) Description Enhanced DMP to handle failing IO when it is not able to interpret sense data. Fixed the vxtask command to display the resync progress subtask for shared volumes with DRL. VOL_READ_MIRRORS ioctl returns -1 instead of 1. Fixed an issue with the VM commands not working on DMP Enabled boot path. Fixed a issue with vxdmproot install causing machine to hang upon reboot. Fixed the vxdg -n [newdg] deport [origdg] command causing a memory leak.
0MP3 RP1 fixed issues (continued) Description Fixed an issue with VVR RU thread not starting nio after it is created from than waiting for all replicas to have NIO's created. Fixed an issue in which if a disk tag name contained long DBCS characters. The vxclustadmcommand has a segmentation fault when the main. Turning on the dmp_cache_open tunable no longer slows down the vxconfigd deamon when run with 2048 dual path LUNs.0 MP3 RP2 fixed issues Description You can now delete snap objects from a mounted volume. Incident 425273 Table 1-7 describes fixed issues in the Veritas Volume Manager 5. Added additional debug messages around the VE_BADPROTOV error message to improve debugging.binconfig file. the configuration daemon was not accessible.Storage Foundation Cluster File System Release Notes Fixed issues 43 Table 1-6 Veritas Volume Manager and Veritas Volume Replicator 5. Fixed the cause of a panic when a cluster had an empty RVG.cf file contains lines that are greater than 512 characters.0MP3 RP2 release. Fixed an issue in which the vxconfigbackup -p script sometimes created a zero-length . Table 1-7 Veritas Volume Manager and Veritas Volume Replicator 5. you could not mount a file system on the volume. Fixed the an issue in which some VxVM commands hung after disconnecting. Fixed the cause of a vxconfigd daemon core dump that occurred after reconnecting the FC site link and hearbeat link. Fixed an issue in which after converting a big volume group. then reconnecting to the FC site link. The vxconfigd daemon no longer hangs when an array is disconnected. Fixed an issue in which proper locks were not taken in all necessary places while modifying last_sent_seqno. Incident 850816 1097258 1108839 1184280 1195591 1222125 1224659 1286298 1287975 1314961 1321272 1321298 .
Fixed the cause of a system panic when mutex_panic() was called from vol_rwsleep_wrlock(). Changed message V-5-1-2140 from an error message to an informational message. Fixed an issuein which connect rlinks failed to be connected. Fixed an issue in which the vxconfigd daemon hung on a node that tried to become the master on site 2 when the Fibre Channel and heartbeat link was disabled at same time. Fixed an issue in which I/O got stuck in the drl_logbusy queue due to corruption of the age node LRU list. The appropriate number of I/O threads are now created for systems with more than 8 CPUs.44 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-7 Veritas Volume Manager and Veritas Volume Replicator 5. Incident 1370927 1374603 1380386 1388883 1393764 1408367 1411438 1414336 1414469 1416080 1421353 1425338 1445884 1446208 1446216 1449001 . Fixed an issue in which some disk devices did not appear in the vxdisk list command output. Fixed an issue in which the vxdisk -e list command dumped core. Fixed an issue in which LUN mapping changes on node 0 caused node 1 and node 2 to panic.0 MP3 RP2 fixed issues (continued) Description Fixed an issue in which the VTOC of disks in a cluster became corrupted. The dynamic multi-pathing tunable dmp_enable_restore value is now persistent when it is set to OFF. Fixed an issue in which the vxddladm listsupport alldid not display up-to-date information. Fixed an issue in which rebooting a controller caused the diskgroups to be disabled. Fixed a cause of data corruption in the dmp_bypass_iodone() call. which is used for enabling and disabling storage keys support. Fixed the cause of a system panic in the vol_change_disk() routine that was due to NULL pointer dereference. Enabled the auto-compiler flag selection. followed by vxconfigd hanging on a secondary node.
Fixed an issue in which the vxsnap make command caused the vxconfigd daemon to hang. DMP no longer uses the SCSI bypass on single path disks for path-suppressing TPD. The I/O buffer start time is no longer modified as part of error analysis. Fixed the cause of a vxconfigd daemon core dump that occurred in the ssb_increment_dg_abort() call. Fixed an issue in which the vxdmpadm -f disable enclosure command failed with a Segmentation Fault and dumped core. Fixed an issue in which the vxdg -s import oradg command failed with following error on a campus cluster: V-5-1-10978 Disk group oradg: import failed: requried lock not held in transaction Fixed the cause of a vxconfigd daemon core dump that occurred in the priv_get_all_udid_entry() call. Incident 1449264 1450348 1457132 1458792 1459831 1460582 1461314 1461338 1461717 1463547 1469487 1470548 1471003 1471658 1471754 .0 MP3 release. Fixed a potential hang/panic that was due to a race condition between an RU thread and a volume read completing during DCM replay. VxVM now correctly handles CPU affinity switching. Fixed an issue in which a campus cluster detached site could not be reattached. Fixed in issue in which the *unit_io and *pref_io tunables became set to 32 MB after upgrading from the Storage Foundation 5. Fixed the cause of a vxconfigd core dump that occurred when dynamically reconfiguring a LUN. Fixed an issue in which replication hung due to a deadlock on a secondary that had a TCP multiconnection and was managed by nmcom.0 MP1 release to the 5. Fixed the cause of data corruption when running the vxdmpadm disable pathand vxdmpadm disable ctlr commands.0 MP3 RP2 fixed issues (continued) Description Fixed the cause of a panic in dmp_get_path_deferq that occurred while creating a volume.Storage Foundation Cluster File System Release Notes Fixed issues 45 Table 1-7 Veritas Volume Manager and Veritas Volume Replicator 5.
Added an error message for attempting to import unwritable disks. Fixed the cause of a failover in the IOCTL context for coordinator disks. Fixed an issue in which VxVM performed a full re-sync of a volume that was created in the background when the volume’s diskgroup was imported. Fixed an issue in which a system that was upgraded to the 5. Fixed the cause of an I/O hang during and after CVM reconfiguration following a reboot of the master node.0 MP3 RP2 fixed issues (continued) Description Fixed the cause of the following error: build_devlink_list: readlink failed for /dev/vx/rdsk/ludg: Invalid argument The vxdmpadm start restorecommand now indicates that the restore daemon cannot be started when the dmp_enable_restore tunable is set to OFF.0 MP3 release could not be booted. Fixed the cause of a system panic in the vxdmp module that was due to a NULL pointer dereference. Incident 1471763 1471813 1472736 1473638 1475707 1477143 1479729 1479735 1480315 1482687 1483164 1483201 1483643 1484919 .46 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-7 Veritas Volume Manager and Veritas Volume Replicator 5. Fixed the cause of an I/O hang on the primary node after a secondary node crashed. The cluster volume manager failback protocol is now triggered when cur_pri is null and at least one DMP node of the same LUN group is DMPNODE_SHARED. Fixed an issue in which the Device Discovery Layer (DDL) sometimes set the unique disk identifier (UDID) value to INVALID. Fixed an issue in which disks with the NOLABEL state were usable via the CLI. Multiple disks set to INVALID resulted in the following error: VxVM vxio V-5-0-1056 new disk disk_id has a non-unique UDID Fixed an issue in which a raid 5 volume would not start on 3PAR Thin Provisioning LUNs. Fixed the cause of an I/O hang on a slave if the master (logowner) crashed with a data change map active.
1. Fixed an issue in which EFI disks were in an error state after installing the Storage Foundation 5.0 MP3 RP1 to SF 5.0 MP3 RP2 fixed issues (continued) Description Fixed an issue in which the vxtask -l list command displayed incorrect progress of the vxsnap addmir command. Fixed an issue in which the dmppolicy. Fixed an issue in which the vxconfigddaemon dumped core when the settag keyword was used to specify a long site name in a campus cluster. Fixed an issue in which the vxconfigbackup command failed to work on a diskgroup that had 2 TB LUNs. Fixed the cause of a vxconfigd hang that occurred due to a split brain condition on a cluster. and sar -d commands. Incident 1485379 1488084 1500389 1501165 1502842 1503168 1507291 1507935 1508462 1512352 1512805 1515581 1525121 1525819 . Fixed an issue in which the vxconfigrestore command failed with the following error: VxVM vxconfigrestore ERROR V-5-2-3706 Diskgroup configuration Fixed an issue in which two disks from different enclosures with the same array volume ID were treated as duplicate array volume IDs. iostat. which was used to link a snapshot volume to the source volume. Changed the V-5-1-2140 message from an error to a warning.infofile did not get updated after upgrading the packages from Storage Foundation (SF) 5. The vxrootadm command now automatically enables the use-nvramrc? variable. Fixed an issue in which recreating a shared diskgroup put CVMVolDg in an empty KSTATE and offlined clustered file systems. Fixed an issue in which the diskgroup for disks without a private region (nopriv disks) could not be imported.0 MP3 RP1 patches.Storage Foundation Cluster File System Release Notes Fixed issues 47 Table 1-7 Veritas Volume Manager and Veritas Volume Replicator 5. Fixed an issue in which setting the dmp_monitor_fabric value to ON triggered unexpected offlining of paths on a DMX4 array. Fixed an issue in which the vxdmpadm iostatcommand reported different amounts of read/write blocks than the vxstat.
Incident 1527247 1528368 1529157 1532363 1534038 1534379 1543803 1544051 1586879 1589022 1589172 1589881 1590314 1594325 1596811 . Fixed an issue in which the vxdg split command failed with the following error: Internal configuration daemon error Fixed an issue in which the vxconvertcommand failed to convert a volume group. Fixed an issue in which DMP stats sometimes used invalid I/O stats entries. Improved performance when re-enabling individual paths. Fixed an issue in which the vxdisksetupand vxdiskunsetup commands sometimes failed for EFI disks. which led to an I/O hang.0 MP3 RP2 fixed issues (continued) Description Fixed an issue in which the vxstat command showed twice the I/O activity on a mirror volume compared to the source volume. Fixed the cause of an I/O hang during the data change map transition after performing vxresize operations on the primary node. which made diskgroup imports fail. Fixed an issue in which the dump device was changed to none (dumps disabled) after encapsulating a boot disk.48 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-7 Veritas Volume Manager and Veritas Volume Replicator 5. Backed out *unit_ioand *pref_io changes that were made in the 5. Fixed an issue in which the incorrect bit was being checked for an EMC Symmetrix thin device. Fixed the cause of an infinite loop in the DMP error handling code path with a CLARIION array. The vxdisk -e listcommand output now includes a wider range of values for the TYPE and STATUS columns. Improved performance of the vxdisk online command when used on large configurations. which led to a panic on the host.0 release. The vxdmpadm getsubpaths dmpnodename command now validates the dmpnodenamevalue before getting the subpath information. Fixed an issue in which the vxdisk updateudid command is corrupted the UDID of a disk.
on a secodary node. rlink paused and generated the “Incorrect magic number or unexpected upid” error message.1 fixed issues Description The qiostat -l command now shows accurate hit percentages.1 includes cumulative fixes for Veritas File System since the 5.1 release. Fixed an issue in which I/O load balancing to LUNs between two VIO servers not working.3 SAN boot disk. Incident 1597868 1598145 1598706 1661938 1663338 1675221 1677416 1711339 1714619 Veritas File System fixed issues The Storage Foundation Cluster File System 5. Fixed the cause of a crash in the vxdmproot install command during startup on an AIX 5. The following tables describe these fixed issues. Table 1-8 describes fixed issues in the Veritas File System 5. VVR tunables can now be modified using the vxtune command. . and the secondary_log_err flag got set. Enhanced the vxconfigd daemon to take advantage of the AIX very large address space model.0 MP3 RP2 fixed issues (continued) Description Fixed an issue in which. which requires a very long full fsck.0MP3 release. Table 1-8 Incident 1477763 1603264 Veritas File System 5. Fixed the cause of a system crash that occurred while mirroring the rootdisk. Fixed a panic that occurred while removing Storage Checkpoints. Fixed an issue in which the vxdmpadm setattr enclosure command created identical disk attribute names. Fixed some CVM join and takeover issues that occurred in shared Active/Passive storage configurations that were due CVM sending messages that were more than 64k in size. Fixed the cause of the panic due to DMP calling iodone() twice.Storage Foundation Cluster File System Release Notes Fixed issues 49 Table 1-7 Veritas Volume Manager and Veritas Volume Replicator 5.
1745875 1804512 Table 1-9 describes fixed issues in the Veritas File System 5.1 fixed issues (continued) Description Fixed a mount failure that occurred while mounting file systems that are greater than 10 TB. Fixed the cause of hangs with the vxresizeand fsadm -bcommands on a VxFS file system. Fixed the cause of the fsclustadm cfsdeinit command failing with the "device busy" error. Fixed the cause of a core dump when running the quotacheck command with more than 30 quota-enabled file systems in the /etc/fstab file. Fixed an issue in which ODM randomly displayed the following error: ORA-17500: ODM err:ODM ERROR V-41-4-2-42-11 Resource temporarily unavailable 1298054 1299313 Fixed the cause of a panic in vx_unlockmap() due to a null ml_tranp pointer.0 MP3 RP2 fixed issues Description The VxFS cp command now has similar performance as the JFS2 cp command. Fixed a loop issue in which the vx_do_putpage() call due to the page going beyond i_wsize. Fixed an issue in which the dm_get_allocinfo() call failed with the EIO error for EXT4 inodes with indirects. Fixed the cause of an exception in the vx_vnmap_min() call that was due to the vx_fsext_info() call of a force umounted file system having a null fse_fsext_info pointer.50 Storage Foundation Cluster File System Release Notes Fixed issues Table 1-8 Incident 1744587 Veritas File System 5. Fixed a umount failure that returned EBUSY. Fixed a hang issue with the fsckptadm create command. Table 1-9 Incident 847454 Veritas File System 5. 1317905 1363639 1387074 1416745 1432323 1443034 .0 MP3 RP2 release.
Storage Foundation Cluster File System Release Notes Fixed issues 51 Table 1-9 Incident 1445008 Veritas File System 5. Fixed an issue in which calling vx_setext() while having the VX_GROWFILE flag set sometimes failed to grow the file or exposed uninitialized data. which caused DB2 to crash. flush_chunk_size. The vx_tflush_map() call no longer disables the file system when a map is marked bad without having an actual I/O error. Scanning of pages in v_write during putpage no longer causes GAB/LLT failure. Fixed a rounding-up of length issue in the vx_fsync_range() call. 1445131 1454783 1459329 1500197 1517415 1526568 1542572 1591301 1633530 1667628 1701842 Table 1-10 describes fixed issues in the Veritas File System 5. Fixed an issue with VxFS filesystems temporarily hang in vx_delay(). Implemented a new tunable. New VxFS tunables and new vxfsstat counters now increase the number of VMM buffers per PDT.c. Fixed a bug in the vx_ifree_scan_list() call in vx_iflush. . Table 1-10 Incident 1366772 1398904 1400046 Veritas File System 5. The vx_multi_bufinval () call now releases the CPU for a local mount with large extents.0 MP3 RP1 release. Fixed an issue in which a smap was marked bad due to punching a hole in the allocated AU. Fixed the cause of a core dump when running the ncheck command.0 MP3 RP1 fixed issues Description Fixed a performance issue. Fixed a cause of Concurrent I/O returning the ENOTSUP error to DB2. Fixed an issue with the fsapadm enforceckpt mount_point command that resulted in a core dump. which is used by the vx_putpage_dirty() and vx_mm_invalidatep() calls. which improves performance.0 MP3 RP2 fixed issues (continued) Description Fixed the cause of a system panic that occurred when auditing files on a VxFS file system.
Fixed a vxresize command failure to resize a volume.0 MP3 RP1 fixed issues (continued) Description Fixed a core dump caused by a VxFS function call while setting DST attributes. . Veritas Storage Foundation Cluster File System known issues The cfsshare share command may result in duplicate monitoring of the volumes (1871316) When you run the cfsshare share command to NFS-export a file system that is already present in VCS configuration. Fixed an issue with VxFS using too much CPU while looking for odd-sized extents (vxi_alloc_fail). 1412465 1414178 1415188 1423867 1487928 1517337 Known issues The following are known issues in this release of Storage Foundation Cluster File System. See the Veritas Cluster Server Release Notes for VCS known issues. which resulted in a malloc failure. Fixed a panic issue with lockcount of an FS thread upon thread_terminate(). Fixed a full fsck core dump that was caused by running out of swap space. However. there may be a case where multiple CVMVolDg resources get created to monitor different volumes within the same disk group.52 Storage Foundation Cluster File System Release Notes Known issues Table 1-10 Incident 1412160 Veritas File System 5. the CVMVolume attribute of each of the multiple CVMVolDg resources gets populated with more volumes than those required within the disk group. This results in duplicate monitoring of the volumes. but the command could resize the file system. Fixed the build script to compile packages to enable the storage keys feature. Optimized vx_convnodata_files().
Then in turn CVMVolDg and CFSMount resources will go to faulted state.Storage Foundation Cluster File System Release Notes Known issues 53 Workaround Manually edit the CVMVolume attribute in the main. SFCFS license keys are installed instead of the SFCFS HA license keys. The CVMVolDg and CFSMount resources may go to faulted state (1437947) If the timezone of a system is changed on the fly where there is CVMVolDg resources already in ONLINE state with the cluster running. SFCFS license keys are installed instead of SFCFSHA license keys if you aborted SFCFSHA installation at the licensing stage (1864906) For keyless licensing.0MP3RP2 to 5.1.cf file to include only the specific volumes that are relevant to each CVMVolDg resource. and license SFCFSHA by selecting L at installer task selection. . then during configuration. the CVMVolDg resources will be reported as OFFLINE in the next monitor cycle. Not all the objects are visible in the SFM GUI (1821803) After upgrading SF stack from 5. the volumes are not visible under the Volumes tab and the shared diskgroup is discovered as Private and Deported under the Disgroup tab in the SFM GUI. if you abort the installation process at the licensing stage for SFCFSHA or if you manually remove the license keys for SFCFSHA. Workaround Bring down the cluster using the hastop -all command before changing the timezone and then start the cluster by entering hastart on all the nodes. you must take either of the following actions: ■ Manually add the license key for SFCFSHA with the following command: # vxkeyless set SFCFSHAENT ■ Run the installer. Workaround Before configuring SFCFS HA.
Storage Foundation Cluster File System Release Notes Known issues
To resolve this known issue
On each manage host where VRTSsfmh 2.1 is installed, run:
# /opt/VRTSsfmh/adm/dclisetup.sh -U
Installer fails with a message that VRTSvlic is not installed
If you run the installer to configure, upgrade, or uninstall a cluster with three or more nodes, the installer may fail with a message that the VRTSvlic fileset is not installed. This failure occurs because of an installer timing issue.  Workaround: You can either try to start the installer script again which resolves the timing issue or you can use the -serial option of the installer.
If you modify resource names, Cluster Volume Manager cannot start (1444545)
If you modify the main.cf configuration file, do not change the CVM or CFS resource names. These names must appear in lower case. If you change them, CVM/CFS fails to start or go online. A Symantec technical note describes this issue in more detail. http://atlas.veritas.com/avf/aca-1/dispatch.exe/mynotes/lookup/309236/0
Hang occurs in rare case of double fault scenario (1835639)
A rare corner case can occur in AIX. This is a double-fault scenario, where first one array of a mirror=enclosure configuration is offlined/disabled and then a node crashes. If these two events happen then the VxFEN module as well as actual I/O load and VxVM transactions on surviving nodes may hang requiring reboot.
All the LUNS for a Storage Foundation Cluster File System host must be larger than 32MB (1471732)
All the LUNS presented to the host where Storage Foundation stack is installed, should be greater than 32MB in size. In case of smaller size disks are presented to host, the host may PANIC while trying to access these LUNS. One of the ways to prevent the host from PANIC on boot is to unmap or remove the small size LUNS from hosts view
Storage Foundation Cluster File System Release Notes Known issues
When master node loses access to complete storage, detached sites remain in RECOVER state even after reattaching and recovering the sites
In a campus cluster environment, if the master node loses access to complete storage, all but one of the sites is detached and the DCO volumes may get detached if the dgfailpolicy is set to dgdisable. If the detached sites are reattached and recovered, the site still remains in RECOVER state.  Workaround: Change the status of the site as described in the following procedure to resolve the issue. To change the status of the site
Log onto the CVM master node. Reattach the detached sites:
# vxdg -g dg_name reattachsite site_name
The site remains in RECOVER state.
Restore DCO volumes by unpreparing and preparing the volumes. Unprepare the volumes:
# vxsnap -g dg_name -f unprepare vol_name
Prepare the volumes:
# vxsnap -g dg_name prepare vol_name drl=on
Reattach the detached sites:
# vxdg -g dg_name reattachsite site_name
Verify that the state of the detached sites is now ACTIVE:
Veritas Storage Foundation for Databases (SFDB) tools known issues
The following are known issues with Storage Foundation for Databases (SFDB) tools.
Storage Foundation Cluster File System Release Notes Known issues
Reverse Resync not supported if database is created using Oracle Managed Files (1192729)
If an Oracle database is created with Oracle Managed Files (OMF), then reverse_resync operations would fail. The following errors are displayed:
oracle@swlx07:~> /opt/VRTSdbed/bin/dbed_vmsnap -S $ORACLE_SID \ -f sp4 -o reverse_resync_begin dbed_vmsnap started at 2007-12-28 12:02:42 SFORA dbed_vmsnap WARNING V-81-5725 After reverse_resync_commit is performed, you need to recreate the Authentication Password File using the ORAPWD utility. SFORA dbed_vmsnap ERROR V-81-4882 An error occurred while reconfiguring Oracle instance 'sfora'. SFORA dbed_vmsnap ERROR V-81-4881 Log file is at /tmp/dbed_vmclonedb.12313/nomount.log. SFORA dbed_vmsnap ERROR V-81-4918 Database sfora has not been correctly recovered. SFORA dbed_vmsnap ERROR V-81-4881 Log file is at /tmp/dbed_vmclonedb.12313/recover.log.
The reverse_resync operation for a database created with OMF is not supported in the 5.1 release. There is no workaround for this issue.
dbed_vmclonedb -p failed to create clonedb with modified pfile (852188)
If you are running the dbed_vmclonedb -p or the dbed_clonedb -p command, the pfile modification will fail if there is an unquoted or unescaped special character in the primary instance’s pfile. The following error will be displayed:
SFORA pfile_mod ERROR V-81-5781 Parse error in file /oracle/dbs/<pfile_name>. line 6: . SFORA dbed_vmclonedb WARNING V-81-5788 Pfile modification failed. Clone instance <CLONE SID> may not start.
Note: The primary instance’s pfile is saved at the time of snapshot creation. This issue occurs because Flashsnap commands do not create a VCS resource for the SNAP disk group. only the primary disk group is moved to another node.server_name=srv_name -f snapplan -r relocate_path # dbed_clonedb -S Prod1 -m mount_point -c ckpt_name ERROR V-81-4882 An error occurred while reconfiguring Oracle instance 'clone_SID' Database fails over during Flashsnap operations (1469310) In an SFHA environment. if the database fails over during Flashsnap operations such as the dbed_vmsnap -o resync command and various error messages appear.Storage Foundation Cluster File System Release Notes Known issues 57 Workaround To avoid this issue. . Clone command fails on an Oracle RAC database (1399393) The commands dbed_vmclonedb and dbed_clonedb will fail on an Oracle RAC database when the clone SID name contains the primary SID name in the beginning. make sure all special characters in the primary instance’s pfile are either placed within quotes or escaped. the pfile parser we use strictly enforces the pfile specification contained in the Oracle Reference Manual. which have “Prod” as the primary SID and “Prod1” as the clone SID. If you attempt to clone the database using that snapshot you will be using the saved pfile. You can check the Oracle Reference Manual for a list of special characters which must be either placed within quotes or escaped when used as pfile parameter values. not the current pfile. For example.server_name=srv_name -f snapplan -r relocate_path # dbed_vmclondb -S Prod -o mountdb \ new_sid=Prod1. However. the following commands. Oracle will process pfile correctly at startup even if a parameter values contains unquoted special characters. Storage Foundation for Databases (SFDB) tools support for using Oracle Data Guard with Oracle RAC (1801265) Storage Foundation for Databases (SFDB) tools do not support use of Data Guard with Oracle RAC in this release. Therefore you must create a new snapshot in order to ensure that the clone will use an updated pfile. produce the following error message: # dbed_vmclondb -S Prod -o recoverdb \ new_sid=Prod1. In some cases. As such. when the database fails over.
Snapplan snp for stand. Clone command fails if archive entry is spread on multiple lines (1764885) If you have a log_archive_dest_1 in single line in the init.ora file. After GCO migration. The dbed_vmchecksnap command may fail with the following error messages: $ dbed_vmchecksnap -S stand \ -H $ORACLE_HOME -f snp -o setdefaults -t dblxxeon02 SFORA vxsnapadm ERROR V-81-5907 open() /snap_data11r1/FLAS11r1/redo01. Flashsnap reverse resync command fails on offhost flashsnap cloning (1810711) Performing dbed_vmsnap -o reverse_resync_begin fails if an off-host clone has been created on the snapshot before.log failed (No such file or directory). DBED features are not integrated with GCO DBED features are not integrated with Global Cluster Option (GCO). SFORA vxsnapadm ERROR V-81-5526 Empty or open file /snap_data11r1/FLAS11r1/redo01.log failed. if the snapshot operation fails then dbed_vmsnap fails to reattach all the volumes.  Database FlashSnap snapplan creation and validation failed for standby database if standby redo log is mislocated (1873738) Mislocated standby redo log files may cause errors during Database FlashSnap snapplan creation and validation for standby database in a Oracle Data Guard environment. Reattach command fails in a multiple disk group environment if the snapshot operation fails (1840672) In a multiple disk group environment. be aware that DBED features will not be functional. This operation must be performed as root user.58 Storage Foundation Cluster File System Release Notes Known issues Clone command fails for instant checkpoint on Logical Standby database (1736516) The dbed_clonedb command does not work on Logical standby database when using instant checkpoint. then dbed_vmclonedb will work but dbed_vmcloneb will fail if you put in multiple lines for log_archive_dest_1. .
log Veritas Volume Manager known issues The following are known issues in this release of Veritas Volume Manager (VxVM). and VxVM transactions hang. . fencing. This may occur.log $ touch /snap_data11r1/FLAS11r1/redo02.log $ touch /snap_data11r1/FLAS11r1/redo03. if a node panics or loses power while one array of a mirror=enclosure configuration is offline or disabled. For example: $ touch /snap_data11r1/FLAS11r1/redo01. initialize the thin reclaim disk as cdsdisk format.Storage Foundation Cluster File System Release Notes Known issues 59 Workaround Create empty redo log files by using the touch command so that dbed_vmchecksnap can succeed without any errors. Existing disk groups and file systems will not be affected. Performing Thin Reclamation on sliced format disk causes data corruption (1834848) This issue occurs only for the Thin Reclamation feature on a sliced format disk. The vxdisk reclaim command or fsadm -R command option corrupts the data on the file system. because the thin reclamation feature is only supported from Storage Foundation Cluster File System 5. If performing the reclaiom is required. When reclaiming the thin disks within the disk group. The cluster may hang if a node goes down (1835718) The cluster may hang if a node goes down while one array is disabled or offline in a mirror=enclosure configuration. this issue occurs if the thin disks are initialized using sliced format. I/O loads. then the cluster. There is no workaround at this time. Workaround Avoid performing any reclaim operation on the disk group with thin reclaimation disk on it.0MP3 release and onwards.
This entry may be present if PowerPath disks were configured as foreign disks in Storage Foundation Cluster File System 4. Workaround There is no workaround for this issue. To view the format of the disk. The poor path failover time is not avoidable at this time. then the vxconvert utility may fail during conversion of LVM to VxVM. VxVM might report false serial split brain under certain scenarios (1834513) VxVM might detect and report a false serial split brain when all the following conditions are met: ■ One or more arrays that provide the shared storage for the cluster are being powered off . vxconvert failures if PowerPath disks are formatted as simple disks (857504) If a PowerPath disk is formatted as a simple disk (a foreign device). This release 5.0.1 does not support this scenario because it could result in data corruption or compromise application availability. use the vxdisk list command. This issue may also occur if the /etc/vx/darecs file contains an hdiskpower disk entry. which is more likely to happen with heavy I/O load. The requestleave policy is not supported if disk cache objects (DCOs) or dirty region logs (DRLs) are configured (1796617) When disk cache objects (DCOs) or dirty region logs (DRLs) are configured. and the entry was not changed after subsequent upgrades. The long failover time is due to the race between the I/O code path and the path failover code path. the dgfailpolicy should not be set to requestleave.60 Storage Foundation Cluster File System Release Notes Known issues The path failure due to filer panic in the netapp array may occasionally cause longer path failover time or longer I/O delay (1835139) The path failure due to filer panic in the netapp array may occasionally cause longer path failover time or the longer I/O delay which varies from 100 seconds to 400 seconds.
Installation with vxinstall will attempt to reinstall the Volume Manager from the beginning.1 Volume Manager without using the product installer. you may be prompted to reinstall it (1704161) If you remove pre-5.Storage Foundation Cluster File System Release Notes Known issues 61 ■ At the same time when the arrays are being powered off. enter y.d/vxprivutil set <device-path> ssbid=<dm id> The <dm id>. the following message is displayed: The Volume Manager appears to be installed already.n.?] (default: n) Workaround When you are prompted to reinstall. an operation that requires an internal transaction is initiated (such as VxVM configuration commands) In such a scenario. VxVM may start before all devices are scanned by the OS. Workaround After the fabric discovery is finished. After installing Volume Manager. a reinstallation may fail and could leave your system unusable.1 Volume Manager packages and then install 5. Are you sure you want to reinstall [y. issue the vxdisk scandisks command to bring newly discovered devices into the VxVM configuration. can be retrieved from the config copy by running the following command: /etc/vx/diag. Depending upon how your system is currently configured. This slow OS device discovery may result in malfunctioning of VM. fencing and VCS due to partial disks seen by VxVM. disk group import will fail with a split brain error and the vxsplitlines output will show 0 or 1 pools. which is also the ssbid.q. You should use vxdiskadm to add more disks to the system. run the following command: /etc/vx/diag. . Workaround: To recover from this situation.d/vxprivutil dumpconfig <device-path> VxVM starts before OS device scan is done (1635274) While working with some arrays.
which tends to reduce fragmentation and increase application performance.62 Storage Foundation Cluster File System Release Notes Known issues Note: This message is not displayed if you install Volume Manager with the product installer. the default setting for this tunable was 2048 file system blocks. the default was changed to the number of file system blocks equaling 1 GB.1 release. A larger max_seqio_extent_size value reduces the number of extents for DB2 data when adding a data file into a tablespace without explicit preallocation. Prior to the 5. DB2 begins to read ahead and pre-stage data in cache using efficient sequential physical I/Os. Workaround To correct this issue.0 MP3 release due to a change in the default setting for the tunable max_seqio_extent_size.0 MP3 release. nullifying the benefits. One such application is DB2.1 release compared to the VxFS 5. Hosting DB2 data on a single file system extent maximizes the potential for sequential pre-fetch processing. The max_seqio_extent_size tunable controls the amount of space that VxFS automatically preallocates to files that are allocated by sequential writes. the Veritas Enterprise Administrator (VEA) interface displays messages half in the new language and half in the previous language. The default value of max_seqio_extent_size was increased in 5. you need to change your language preferences (1666997) If you change the locale in your operating system. When DB2 detects an application performing sequential reads against database data. In the 5. the default value was restored to the original 2048 blocks.0 MP3 to increase the chance that VxFS will allocate the space for large files contiguously. If a file contains many extents. There are two separate benefits to having a larger max_seqio_extent_size value: . In the 5. To display localized characters on the VEA interface.0 MP3 release. Veritas File System known issues The following are known issues in this release of Veritas Storage Foundation. then pre-fetch processing is continually interrupted. change the language on your VEA Preferences screen. Possible write performance degradation with VxFS local mounts Some applications that allocate large files without explicit preallocation may exhibit reduced performance with the VxFS 5.
Copy those large files to new files. ■ In the 5. since VxFS can allocate the file in larger chunks. If your workload has lower performance with the VxFS 5.Storage Foundation Cluster File System Release Notes Known issues 63 ■ Initial allocation of the file is faster. Later application access to the file is also faster. but the current implementation can fail to reclaim such space in some situations. 2 3 4 5 Shut down any application that are accessing any large files that were created using the smaller tunable setting. the default value was changed back to its earlier setting because the larger 5. which is 1 GB divided by the file system block size. which is more efficient. Restart any applications were shut down earlier. you can use the vxtunefs command to increase this tunable to see if performance improves.1 TL2 Required APAR IZ41494. VxFS attempts to reclaim any unused preallocated space if the space is needed to satisfy other allocation requests. which will be allocated using the higher tunable setting. IBM fixed some issues in the D_REFUND feature through certain APARs.1 release. Rename the new files back to the original names.1 release and you believe that the above change could be the reason. Increasing this tunable also increases the chance that an application may get a spurious ENOSPC error as described above.0 MP3 value can lead to applications experiencing "no space left on device" (ENOSPC) errors if the file system is close to being full and all remaining space is preallocated to files. since accessing less fragmented files is also more efficient. which you must install to use the D_REFUND feature with VxFS. The dynamic vmm buffer allocation feature requires certain AIX APARs to be installed (1849083) VxFS supports the use of the dynamic vmm buffer allocation (D_REFUND) feature. so change this tunable only for file systems that have plenty of free space. which is packaged in SP3 .0 MP3 value.1 TL2 and later releases of AIX. which IBM added to AIX 6. To restore the benefits of the higher tunable value 1 Increase the tunable back to the 5. The TL of the operating system determines which APAR you must install: Operating system AIX 6. However.
jsp?pid=15107 Relevant component product release notes Read the relevant component product release notes before installing any version of Veritas Storage Foundation. The following documents are relevant component product release notes: .1 TL4 Required APAR IZ37627 IZ38189 No longer supported This section describes Storage Foundation Cluster File System features that are not supported in this release. VVR uses UDP as the default transport protocol for communicating between the primary and secondary. Documentation Product guides are available on the software disc in PDF format.1 documentation set is available at the following URL: http://www. The following features are not supported in this release of Storage Foundation Cluster File System products: ■ ■ ■ ■ The seconly feature in SFCFS Storage Expert The use of the vxvoladm command line utility Intelligent Storage Provisioning (ISP) VVR will use TCP as default protocol from next release In Storage Foundation Cluster File System 5. In future releases. Symantec's Veritas Storage Foundation Cluster File System documentation is also available on the Symantec website. the default protocol will be switched to TCP.1 TL3 AIX 6.64 Storage Foundation Cluster File System Release Notes No longer supported Operating system AIX 6.symantec.1 and previous releases.com/business/support/overview. Users will have the option to manually switch back to UDP. Symantec's Veritas Storage Foundation Cluster File System 5.
Table 1-11 Guide Title Guides in Veritas Storage Foundation documentation set Filename Veritas Storage Foundation and High Availability Getting getting_started. .txt sf_notes.pdf vxvm_admin.Storage Foundation Cluster File System Release Notes Documentation 65 ■ ■ ■ Veritas Cluster Server Release Notes (vcs_notes.pdf) Veritas Storage Foundation Release Notes (sf_notes.pdf) Veritas Storage Foundation for Oracle RAC Release Notes (sfrac_notes. comprise the Veritas Storage Foundation documentation set: Table 1-11 describes the guides in the Veritas Storage Foundation documentation set.pdf) Storage Foundation guides The following manuals.pdf Veritas Storage Foundation Cluster File System documentation The following Veritas Storage Foundation Cluster File System documentation is available with all Veritas Storage Foundation HA product suites: Table 1-12 describes the Veritas Storage Foundation Cluster File System (CFS) documentation set.pdf vxvm_tshoot.pdf sf_install.pdf Started Guide Veritas Storage Foundation read me first Veritas Storage Foundation Release Notes Veritas Storage Foundation Installation Guide Veritas Storage Foundation: Storage and Availability Management for Oracle Databases Veritas Storage Foundation Advanced Features Administrator's Guide Veritas File System Administrator’s Guide Veritas File System Programmer's Reference Guide Veritas Volume Manager Administrator’s Guide Veritas Volume Manager Troubleshooting Guide readme_first.pdf vxfs_admin.pdf vxfs_ref. along with the online help.pdf sf_advanced_admin.pdf sf_adv_ora.
66 Storage Foundation Cluster File System Release Notes Documentation Table 1-12 Guides in Veritas Storage Foundation Cluster File System documentation set Filename Guide Title Veritas Storage Foundation Cluster File System Release sfcfs_notes.pdf .pdf Veritas Cluster Server Agents for Veritas Volume Replicator Configuration Guide VCS Enterprise Agent for Oracle Installation and Configuration Guide VCS Enterprise Agent for DB2 Installation and Configuration Guide VCS Enterprise Agent for Sybase Installation and Configuration Guide vcs_vvr_agent.pdf sf_adv_ora.pdf Veritas Cluster Server Bundled Agents Reference Guide vcs_bundled_agents.pdf vcs_install.pdf sf_advanced_admin.pdf sfcfs_admin.pdf vcs_oracle_install. Table 1-13 Guide Title Veritas Cluster Server Release Notes Veritas Cluster Server Installation Guide Veritas Cluster Server Agent Developer’s Guide Guides in Veritas Cluster Server documentation set Filename vcs_notes.pdf vcs_sybase_install.pdf Notes Veritas Storage Foundation Cluster File System Installation Guide Veritas Storage Foundation Cluster File System Administrator’s Guide Veritas Storage Foundation: Storage and Availability Management for Oracle Databases Veritas Storage Foundation Advanced Features Administrator's Guide sfcfs_install.pdf vcs_db2_install.pdf vcs_agent_dev.pdf Veritas Cluster Server documentation The following Veritas Cluster Server documentation is available with all Veritas Storage Foundation HA product suites: Table 1-13 describes the Veritas Cluster Server documentation set.
If the MANPATH environment variable does not include /opt/VRTS/man.pdf Veritas Volume Replicator Planning and Tuning Guide vvr_planning.pdf Manual Pages The Veritas online manual pages are installed in the /opt/VRTS/man directory.pdf Release Notes Veritas Storage Foundation™ for Oracle RAC sfrac_admin.pdf Veritas Volume Replicator Advisor User’s Guide vvr_advisor_users. Table 1-14 Guide Title Veritas Volume Replicator Administrator’s Guide Guides in Veritas Volume Replicator documentation set Filename vvr_admin.pdf Installation and Configuration Guide Veritas Storage Foundation™ for Oracle RAC sfrac_notes. Table 1-15 Guide Title Guides in Storage Foundation for Oracle RAC documentation set Filename Veritas Storage Foundation™ for Oracle RAC sfrac_install. you can view the desired manual page by entering the following command: .Storage Foundation Cluster File System Release Notes Documentation 67 Veritas Volume Replicator documentation The following Veritas Volume Replicator documentation is available with the Veritas Volume Replicator option: Table 1-14 describes the Veritas Volume Replicator documentation set. This directory can be added to the MANPATH environment variable.pdf Administrator's Guide Veritas Storage Foundation: Storage and Availability Management for Oracle Databases sf_adv_ora.pdf Veritas Storage Foundation for Oracle RAC documentation The following Storage Foundation for Oracle RAC documentation is available with all Veritas Storage Foundation HA product suites: Table 1-15 describes the Storage Foundation for Oracle RAC documentation set.
68 Storage Foundation Cluster File System Release Notes Documentation # man -M /opt/VRTS/man manual_page_name .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.