Veritas Storage Foundation (tm) and High Availability Solutions 4.1 to 4.1 Maintenance Pack 4 for Linux - Late Breaking News and cross references to product documentation

Article:TECH38970  |  Created: 2010-01-18  |  Updated: 2010-08-09  |  Article URL http://www.symantec.com/docs/TECH38970
Article Type
Technical Solution

Product(s)

Environment

Issue



Veritas Storage Foundation (tm) and High Availability Solutions 4.1 to 4.1 Maintenance Pack 4 for Linux - Late Breaking News and cross references to product documentation


Solution




To locate the most current product patch releases including Maintenance Packs, Rolling Patches, and Hot Fixes visit  https://vos.symantec.com/patch/matrix


VOS (Veritas Operation Services) Portal:
 https://vos.symantec.com

VOS Portal Contains:

    - Risk Assessments
    - Installation Assessment Services (Installation and Upgrade preparation)
    - VOS Searchability (Error Code Lookup, Patches, Documentation, Systems, Reports)
    - Detailed Reports (Product and License Usage)
    - Notification Signup (VOS Notification Widget)




Documentation

4.1 MP4 Documentation List  http://entsupport.symantec.com/docs/307514
4.1 MP3 Documentation List  http://entsupport.symantec.com/docs/307513
4.1 MP2 Documentation List  http://entsupport.symantec.com/docs/307512
4.1 MP1 Documentation List  http://entsupport.symantec.com/docs/307511
4.1 Documentation List  http://entsupport.symantec.com/docs/307510

Man pages and error messages are available at  
vos.symantec.com/documents


Downloads

4.1 Maintenance Pack 4 for Linux Disc 1 - Red Hat Enterprise Linux 4  
http://entsupport.symantec.com/docs/289307
4.1 Maintenance Pack 4 for Linux Disc 2 - SUSE Linux Enterprise Server 9  
http://entsupport.symantec.com/docs/289308
4.1 Maintenance Pack 4 for Linux Disc 3 - SUSE Linux Enterprise Server 10 -  
http://entsupport.symantec.com/docs/289309
4.1 Maintenance Pack 4 for Linux Disc 4 - Red Hat Enterprise Linux 5  
http://entsupport.symantec.com/docs/289310
4.1 Maintenance Pack 4 for Linux Disc 5 - VERITAS Storage Foundation Basic for Red Hat Enterprise Linux 5  
http://entsupport.symantec.com/docs/289312

Patches are available on Patch Central  https://vias.symantec.com/labs/patch


Tools

VIAS (Veritas Installation Assessment Service)   https://vias.symantec.com 
Health Check  https://vias.symantec.com/labs/vhcs
Error Code Lookup  https://vias.symantec.com/labs/vels
VIMS (Veritas Inventory Management Service)  https://vias.symantec.com/labs/vims
Veritas Operations Services (VOS) Labs  https://vias.symantec.com/labs
       


Veritas Storage Foundation and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 3

Veritas Storage Foundation and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 3 for Linux is now available.

For more information, see  
http://entsupport.symantec.com/docs/315416

SLES 10
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux - ( sles10_i586 )  http://entsupport.symantec.com/docs/315357
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux - ( sles10_ia64 )  http://entsupport.symantec.com/docs/315383      
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux - ( sles10_x86_64 )  http://entsupport.symantec.com/docs/315382

RHEL 5
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( rhel5_i686 )  http://entsupport.symantec.com/docs/315381      
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( rhel5_ia64 )  http://entsupport.symantec.com/docs/315380    
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( rhel5_x86_64 )  http://entsupport.symantec.com/docs/315379  
 
SLES 9
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( Sles9_ia64 )  
http://entsupport.symantec.com/docs/315394
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( Sles9_i586 )  
http://entsupport.symantec.com/docs/315395
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( Sles9_x86_64 )  
http://entsupport.symantec.com/docs/315355

RHEL 4
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( RHEL4_x86_64 )  
http://entsupport.symantec.com/docs/315412
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( RHEL4_ia64 )  
http://entsupport.symantec.com/docs/315411
Veritas Storage Foundation HA 4.1 MP4 RP3 for Linux ( RHEL4_i686 )  
http://entsupport.symantec.com/docs/315404


Storage Foundation and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 3 known issues

The following known issues are missing in the Read This First document.

I/O does not failback to the primary path after the primary path is enabled, and enabling and disabling DMP multiple times causes the Volume Manager configuration daemon (vxconfigd) to hang in a Storage Foundation for Oracle RAC environment. (1434685)


Workaround:
 
Set the dmp_retry_timeout value to 1.

Use the following command to set the dmp_retry_timeout value:

# vxdmpadm settune dmp_retry_timeout=1


 
Enabling and disabling DMP multiple times causes the Volume Manager configuration daemon (vxconfigd) to hang. (1447508)


Workaround:

A patch will be made available for this issue. The link to the patch will be provided here when it is available.



Documentation

Product documentation, man pages and error messages for the 4.1 release are available at  
http://sfdoccentral.symantec.com/index.html

Storage Foundation and High Availability 4.1 MP4 Product Family Documentation  
http://entsupport.symantec.com/docs/307514

Storage Foundation and High Availability 4.1 MP3 Product Family Documentation  
http://entsupport.symantec.com/docs/307513

Storage Foundation and High Availability 4.1 MP2 Product Family Documentation  
http://entsupport.symantec.com/docs/307512

Storage Foundation and High Availability 4.1 MP1 Product Family Documentation  
http://entsupport.symantec.com/docs/307511

Storage Foundation and High Availability 4.1 Product Family Documentation  
http://entsupport.symantec.com/docs/307510



Linux Kernel Support Statement

All kernels and updates which apply to the supported distributions are supported unless they change kABI compatibility. This means Red Hat Updates and Suse Linux Enterprise Server Support Packs which do not change kernel ABI are automatically supported by Symantec for Storage Foundation and Veritas Cluster server the moment they are released by Red Hat or Novell. When an update or support pack DOES change kABI we will note it in this document. Note: While Red Hat Updates almost never change kABI, the majority of Suse Linux Enterprise Server Support Packs DO change kABI.


 
Cluster Volume Manager (CVM) fail back behavior for non-Active/Active arrays

This describes the fail back behavior for non-Active/Active arrays in a CVM cluster. This behavior applies to A/P, A/PF, APG, A/A-A, and ALUA arrays.

When all of the Primary paths fail or are disabled in a non-Active/Active array in a CVM cluster, the cluster-wide failover is triggered. All hosts in the cluster start using the Secondary path to the array. When the Primary path is enabled, the hosts fail back to the Primary path.

However, suppose that one of the hosts in the cluster is shut down or disabled while the Primary path is disabled. If the Primary path is then enabled, it does not trigger failback. The remaining hosts in the cluster continue to use the Secondary path. When the disabled host is rebooted and rejoins the cluster, all of the hosts in the cluster will continue using the Secondary path. This is expected behavior.

If the disabled host is rebooted and rejoins the cluster before the Primary path is enabled, enabling the path does trigger the failback. In this case, all of the hosts in the cluster will fail back to the Primary path. [e1441769]



Veritas Cluster Server (VCS) Support

VCS requires that all nodes in the cluster use the same processor architecture and run the same operating system version.



SLES10 SP2 Issues

Novell's recently-released Service Pack 2 to their Suse Linux Enterprise Server 10 (SLES10) release changes kABI and is therefore not eligible for automatic support by Symantec with Storage Foundation and Veritas Cluster Server products.  Symantec will release a patch to enable supported use of SLES10 SP2 with SF HA products: 4.1 Maintenance Pack 4, rolling patch 3. The anticipated date for this rolling patch is late November 2008. Check this document for updates.


SLES9 SP4 Issues

Novell's recently-released Service Pack 4 to their Suse Linux Enterprise Server 9 (SLES9) release changes kABI and is therefore not eligible for automatic support by Symantec with Storage Foundation and Veritas Cluster Server products.  Symantec has a patch to enable supported use of SLES9 SP4 with SF HA products: 4.1 Maintenance Pack 4, rolling patch 2.


Veritas Storage Foundation and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 2

Veritas Storage Foundation and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 2 for Linux is now available:

Veritas Storage Foundation (tm) and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 2 Read This First  
http://entsupport.symantec.com/docs/304004

Veritas Storage Foundation (tm) and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 2 - sf_ha.4.1.40.20.rhel5.tar.gz   http://entsupport.symantec.com/docs/304003   
 
Veritas Storage Foundation (tm) and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 2 - sf_ha.4.1.40.20.sles9.tar.gz   http://entsupport.symantec.com/docs/304002 

Veritas Storage Foundation (tm) and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 2 - sf_ha.4.1.40.20.sles10.tar.gz   http://entsupport.symantec.com/docs/304001 
 
Veritas Storage Foundation (tm) and High Availability Solutions 4.1 Maintenance Pack 4 Rolling Patch 2 - sf_ha.4.1.40.20.rhel4.tar.gz   http://entsupport.symantec.com/docs/304000 
   
 
Veritas Storage Foundation 4.1 Maintenance Pack 4 Rolling Patch 1 for Linux

4.1 Maintenance Pack 4 Rolling Patch 1 is available at  
http://support.veritas.com/docs/293918


Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 4 for Linux

Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 4 (MP4) adds support for Red Hat Enterprise Linux 5. The 4.1 MP4 release is available from  https://fileconnect.symantec.com and it is also available from the support web site. For more information, see the Related Documents.


Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 4 Issues

The following is a known issue:

Upgrading the Operating System Removes the VRTSperl Package (1031435)

If you upgrade the operating system to one of the supported operating systems,
this removes the existing VRTSperl package. You must manually install the
correct VRTSperl package for the new operating system before running the
installmp script.


The following known RHEL5 issue is missing in the Release Notes.

Programs that use data from non-root local file systems fail during shutdown on RHEL5

On RHEL5, Red Hat has made changes to the system startup procedure that cause the non-root local file systems that are listed in /etc/fstab to be accessed while the root file system is still read-only. As the startup procedures for Volume Manager (VxVM) and File System (VxFS) need to write to the root file system, the shutdown scripts set an option to delay the startup. Each file system that is hosted on a VxVM volume, or mounted using the VxFS driver, is marked with the option "_netdev" to delay the mount until after the root file system is loaded and available. So, such file systems are mounted later (by S25netfs) and unmounted earlier (by K75netfs) than normal for entries in /etc/fstab. Programs using data from one of these file systems that start before S25netfs and stop after K75netfs cannot access the files properly and may suffer from failures during shutdown.

Workaround: Renumber the startup scripts. The startup scripts for affected programs should be moved to have numbers greater than 25, while the shutdown scripts should have numbers less than 75. Any ordering between multiple affected scripts should be preserved during the renumbering to reflect any other existing dependencies.

Incident 1096551 - Using the rpm Command to upgrade to MP4 on a SLES 9 system
The rpm -U command does not install the modules in the VRTSvxvm-platform package correctly on a SUSE Linux Enterprise Server 9 system. To install this package, you should instead use the following commands to remove the existing package and to install the new package:
 
# rpm -ev VRTSvxvm-platform
 
# rpm -ivh VRTSvxvm-platform-4.1.40.00-MP4_SLES9.<arch>.rpm

where <arch> is i586 or x86_64 as appropriate.


Incident 1035427 - Potential Problems with EMC CLARiiON Arrays in a Cluster
It is recommended that you do not create shared volumes on an EMC CLARiiON array that has been configured in explicit failover mode (also known as non-autotrespass or A/PF mode). A shared volume that has been created on such an array may be disabled due to intermittent I/O errors if the primary active path fails and there is only one secondary path that is available for failover. If the primary active path has failed
or has been disabled, running the "vxdctl enable" or "vxdisk scandisks" commands may also cause the volume to be disabled. The recommended workaround is to operate the array in A/P mode.

RHEL 5 and SLES 10 are not supported for Storage Foundation for Oracle RAC
The 4.1 MP4 release does not support the Storage Foundation for Oracle RAC product for the RHEL 5 and SLES 10 operating systems. The Storage Foundation for Oracle RAC product is not available in the installation menu for these operating systems.

Mounting the special file system nfsd before starting nfs daemons
On SLES 10 SP1 systems, whenever an NFS resource is faulted and fails over to the second node, the clients on accessing the exported file system may see 'Stale NFS handle' errors. This has been resolved by mounting the special file system nfsd before starting nfs daemons. For more information, see 288679 in the related documents section below.

Incident 1039891 - For VCS bundled agents on Linux, the Disk reservation module does not get loaded on SLES10 SP1. For more information, see 288680 in the related documents section below.

Incident 1042555 - The HP StorageWorks 1500cs Modular Smart Array (MSA1500) is not supported for use with the I/O Fencing feature of Veritas Storage Foundation for Oracle RAC. If this array is used, DMP path failover functions incorrectly. If a path to one node of the cluster is disabled while I/O is taking place from or to any shared disk groups, the following error message is displayed:

      VxVM vxio V-5-0-137 DMP_SETIOPATH ioctl failed with status = ffffffff

In addition, some paths become disabled on other nodes, and these paths fail to recover even if they are re-enabled. For more information, see  
http://entsupport.symantec.com/docs/289896


Known issues using version 8.01.07 of the QLogic HBA driver are documented in the VERITAS Storage Foundation 4.1 Maintenance Pack 4 Release Notes. See the Release Notes for more information:  
http://entsupport.symantec.com/docs/288552



Daylight Savings Time Change
For information about Daylight Savings Time issues, refer to this TechNote:  
http://support.veritas.com/docs/286461


Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 3 for Linux is now available (10/25/06)
Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 3 (MP3) adds support for SLES 10.
See the Related Documents section below for more information.


Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 3 Known Issues

The following are the upgrade paths for 4.1 MP3:

SLES 9 or RHEL 4 - Install 4.1, then install 4.1 MP3

SLES 10 - Install 4.1 MP3


Veritas Volume Manager

Incident 801138

Using Hitachi HDS 9xxx, Hitachi HDS AMS500, or HP EVA arrays with multiple active paths:

When using multiple active paths to an Hitachi HDS 9xxx, AMS500, HP EVA 4000, 6000 or 8000 array in a cluster environment, the device queue can become full if the queue depth is set too large. This can lead to I/O stalling or hanging.

This behavior has been seen with IBM System Storage DS4800 disk arrays.

To change the queue depth, do either of the following:

- Change the queue depth in the HBA firmware (refer to your HBA documentation for details)

or

- Change the queue depth by using the Linux sysfs interface

  To adjust the queue depth for a device, echo the new value to the sysfs queue_depth file. For example, to set the queue depth to 8 for the device sdx:

      # echo 8 > /sys/block/sdx/device/queue_depth

  It is necessary to change the queue depth for all active and passive subpaths. These changes are non-persistent and should be enabled during system startup.

  For example, to adjust the device queue depth of all devices that are connected to controller 1, add the following lines to the end of the /etc/vx/vxvm-startup file:

      for disk in `vxdmpadm getsubpaths ctlr=c1 | awk '$1 ~ /^sd/{print $1}'`
      do
            echo 8 > /sys/block/$disk/device/queue_depth
      done


Incident 788988

Unable to remove the VRTSweb package

When uninstalling Storage Foundation Enterprise, the uninstallsf script displays an error message such as the following:

      Uninstalling VRTSweb 4.2 on LxVM11
      ERROR 3 of 23 steps CPI WARNING V-9-10-1514 Removal of VRTSweb 4.2 did not
      complete successfully.
      error: %postun(VRTSweb-4.2-GA2_GENERIC.noarch) scriptlet failed, exit status 1

This behavior has been seen on a SUSE Linux Enterprise Server 10 system.

The workaround is to use the rpm command to remove the VRTSweb package manually:

      # rpm -e --noscripts VRTSweb-4.2-GA2_GENERIC


Incident 797047

Unable to recover failed paths (SuSE 10)

DMP may be unable to recover a failed path. In such cases, a reboot is required to recover
all devices that are connected via the path.

Use the vxdmpadm getsubpaths command to verify the state of the failed devices after the
path has been restored, and the devices have been re-scanned by DMP. If the devices are not
in the ENABLED state, another reboot may be required.


Incident 796027

Disabling all paths may cause uncorrectable write errors (IBM System Storage DS4800)

When using an IBM System Storage DS4800 with multiple active paths in a clustered environment,
disabling all primary paths may result in I/O failure, and the following message will be
displayed on the console:

      VxVM vxio V-5-0-137 DMP_SETIOPATH ioctl failed with status = ffffffff

After the failed paths are restored, a reboot might be required on a SuSE 10 system.


Incident 819200

Unable to perform path failover when an array side path fails (QLogic, SuSE 10)

If a path failure occurs between a fiber switch and an array, path failover may not occur,
and messages such as the following will appear on the console:

      qla2xxx 0000: Abort command issued -- 1 b73c 2002

If the I/O does not continue once the path has been restored, a reboot may be required to
recover the failed devices.


Veritas File System

Incident 795160

SuSE SLES10 'fsck -t <filesystem>' does not work correctly

Under SuSE SLES10 'fsck -t vxfs <filesystem>' does not seem to invoke the correct fsck sub-program.

This issue is specific to SuSE SLES10 and has been reported to SuSE under bugzilla 205671. The previous short term workaround was to specify the full fsck sub-program pathname:
'/sbin/fsck.vxfs <filesystem>'

A patch is now available to resolve this issue:  
http://support.novell.com/techcenter/psdb/286c206d70f263c8fc3da1dc2fab3ce7.html


Veritas Volume Replicator (VVR)

VVR is now supported on SLES10, starting with VVR 4.1 MP3.  Veritas Volume Replicator 4.1 Release Notes are provided with this release for reference. However, for the latest information about VVR, including fixed issues for 4.1 MP3 and instructions for installing on SLES 10, refer to the Veritas Storage Foundation 4.1 MP3 Release Notes.


Previous Release Issues

IA-64 machine on RHEL 4 or later on Veritas File System 4.1 or 4.1 MP1 may cause Linux kernel panic, mostly during installation. For details see  
http://support.veritas.com/docs/282282

On Suse with critical bugzillas pending,  Symantec does not recommend and support users to run NFS. The following issues are currently not resolved on Suse:
[Bug 141542]sm-notify should have an option to notify clients using virtual name (for failover across subnets)
[Bug 65532] when nfs restarted on , it gives permission denied error
[Bug 148009]  statd creates file for a client only once.
Bug 95374] New: lockd does not continuously retry reclaiming lock if client is not able to contact server
[Bug 95007] umount fails on nfs server side

Following issues are currently not resolved on RedHat:
Issue 87838 - [Bug 143897] NFS can't handle minor number greater than 255
Issue #69397 ([RHEL4] lockd does not enter grace period if nfsd restarts on machine acting as both nfs server and nfs client


Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 2 for Linux is now available (04/21/06)
Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 2 adds support for RHEL4 Update 3 (largesmp kernel).


Storage Foundation and Cluster File Solutions 4.1 Maintenance Pack 1 for Linux is now available (12/22/05)
Symantec has just released Maintenance Pack 1 for Storage Foundation and Cluster File Solutions 4.1 which adds support for RHEL4 U2, SLES9 SP3,  as well as async I/O support for Veritas File System.  As expected, all known issues and bug fixes have been provided to enhance the products functionality and performance.  This update provides performance enhancements over SLES9 SP2,  as well as additional kernel support.

Support for Suse Linux Enterprise Server 9:  
http://support.veritas.com/docs/280990


Support for Red Hat Enterprise Linux 4:    
http://support.veritas.com/docs/280991


(11/04/05) Original SLES9 SP2 kernel has an issue that is incompatible with Veritas Volume Manager dynamic multipathing (DMP).
For SUSE SLES9 SP2 installations, kernel version 2.6.5-7.201 or greater is required because versions 2.6.5-7.191 (SP2) and 2.6.5-7.193 have a bug [Incident 425945] that stops DMP failover from working. This is fixed in the 2.6.5-7-201 kernel version, which is available from the SUSE Linux maintenance Web site:

   
http://www.novell.com/linux/suse

(11/04/05) Supported service pack: Suse Linux Enterprise Server 9 Service Pack 2
Storage Foundations and High Availability Solutions 4.1 for Linux now supports SLES9 SP2 with the release of RP1.  The patch is now available and can be found on the here: http://support.veritas.com/docs/277561.

Note: Currently, there is an issue with SLES9 SP2 support on IA64 due to the removal of the sfdisk binary utility that Volume Manager uses to manage non-CDS disks. Symantec is currently working with Novell to identify a solution for this situation.  The sfdisk utility is available in SP1 and could be used from there.  Additional details will follow when support compliance is identified.

Addendum to the Storage Foundation and High Availability Solutions Getting Started Guide

* Typing errors in Getting Started Guide

In the Known Issues section of the Storage Foundation and High Availability Solutions Getting Started Guide, there are two typing errors in the procedure for "Problem Installing on Remote Systems With Japanese Locale." On page 37, the line:

  LANG=3D"C"

should read

  LANG="C"

The line:

  LANG=3Dja_JP.eucJP

should read

  LANG=ja_JP.eucJP

This issue applies to other supported international locales, not just the Japanese locale.  This issue will not allow customers to do remote push installations of VERITAS Cluster Server or other clustered products unless this language resolution is put in place.


Incorrect version indicators shown in the Veritas File System Programmer's Reference Guide

The PDF version of the Veritas File System Programmer's Reference Guide (part number N17443H) installed with the VRTSmnd package still displays "Prerelease" and April and July 2005 dates on the title page and text pages. The content of this document has been fully reviewed and is of final release quality. A version with the prerelease indicators removed and an updated date of August 2005 is available on the Veritas documentation disc and on the Symantec Support site:
http://support.veritas.com/docs/277961

Oracle RAC may force all nodes to panic in a RAC cluster if VCSMM is called to deregister a node twice.

VCSMM will panic if a slave process deregisters twice. This happens because Oracle does not follow the SKGXN API correctly and tries to register a slave process twice. This happens rarely and only under heavy loads. If this happens, current VCSMM will panic the node. A patch will be made available in the near future.

Veritas Cluster Server Installation Guide for 4.1 Documentation correction

LLT supports Cluster ID numbers between 0 and 65535

Cluster ID is a unique number that the LLT module uses to identify a cluster.
The LLT module for VCS 4.1 and later supports an integer value between 0 and 65535 for the cluster ID. The LLT configuration file /etc/llttab contains this value.

The Veritas Cluster Server Installation Guide for 4.1 mentions that the cluster ID is an integer between 0 and 255. But LLT actually supports an integer value up to 65535.

Workaround:
Though the installvcs program does not support a cluster id value that is greater than 255, you can manually change the cluster ID value in the /etc/llttab file.
For example, if your /etc/llttab file content is as follows, you can change the line "set-cluster 2" to "set-cluster 50000"

      set-node north
      set-cluster 2
      link eth1 eth1 - ether -
      link eth2 eth2 - ether -

After you edit the /etc/llttab file, you must restart LLT for this change to take effect.


Veritas 4.1 Storage Foundation Cluster File System Installation and Administration Guide Documentation Issues

Veritas 4.1 Storage Foundation Cluster File System Installation and Administration Guide steps 6 and 9 in the "Adding a Node" section on page 25-26 are incorrect.

They should read as follows:

   6. On the newly added node, start LLT:

        # /etc/init.d/llt start

   9. On the newly added node, start GAB:

        # /etc/init.d/gab start


Veritas 4.1 Storage Foundation Cluster File System Installation and Administration Guide step 2 in the "Configuring SFCFS and CVM Agents" section on page 27 is incorrect.

It should read as follows:

   2. If there are any dependencies, take them offline on all the nodes:

        # hagrp -offline cvm -sys system01
        # hagrp -offline cvm -sys system02


Veritas 4.1 Storage Foundation Cluster File System Installation and Administration Guide steps are missing in the "Configuring SFCFS and CVM Agents" section on page 28.

Add the following steps after step 13:

  14. On the newly added node, set the activation mode for all shared disk groups:

        # cfsdgadm add <diskgroup> <system03>=sw

  15. On the newly added node, add CFS mount points:

        # cfsmntadm modify <cfsmount_point> add system03=<options>




Legacy ID



277033


Article URL http://www.symantec.com/docs/TECH38970


Terms of use for this information are found in Legal Notices