This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
fs-sol11_sparc-6.0.1.200
Sign in if you want to rate this patch.

 Basic information
Release type: Patch
Release date: 2012-09-20
OS update support: None
Technote: None
Documentation: None
Popularity: 622 viewed    137 downloaded
Download size: 13.61 MB
Checksum: 3409270026

 Applies to one or more of the following products:
VirtualStore 6.0.1 On Solaris 11 SPARC
Storage Foundation 6.0.1 On Solaris 11 SPARC
Storage Foundation Cluster File System 6.0.1 On Solaris 11 SPARC
Storage Foundation for Oracle RAC 6.0.1 On Solaris 11 SPARC
Storage Foundation HA 6.0.1 On Solaris 11 SPARC

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
2912412, 2912435, 2923805

 Patch ID:
None.

 Readme file  [Save As...]
                          * * * READ ME * * *
                 * * * Veritas File System 6.0.1 * * *
                      * * * Public Hot Fix 2 * * *
                         Patch Date: 2012-09-20


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas File System 6.0.1 Public Hot Fix 2


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris 11 SPARC


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvxfs


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation for Oracle RAC 6.0.1
   * Veritas Storage Foundation Cluster File System 6.0.1
   * Veritas Storage Foundation 6.0.1
   * Veritas Storage Foundation High Availability 6.0.1
   * Symantec VirtualStore 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.0.100.200
* 2912412 (2857629) File system corruption can occur requiring a full fsck of the 
system.
* 2912435 (2885592) vxdump to the vxcompress file system is aborted
* 2923805 (2590918) Delay in freeing unshared extents upon primary switch over.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following Symantec incidents:

Patch ID: 6.0.100.200

* 2912412 (Tracking ID: 2857629)

SYMPTOM:
When a new node takes over a primary for the file system, it could 
process stale shared extent records in a per node queue.  The primary will 
detect a bad record and set the full fsck flag.  It will also disable the file 
system to prevent further corruption.

DESCRIPTION:
Every node in the cluster that adds or removes references to shared extents, 
adds the shared extent records to a per node queue.  The primary node in the 
cluster processes the records in the per node queues and maintains reference 
counts in a global shared extent device.  In certain cases the primary node 
might process bad or stale records in the per node queue.  Two situations under 
which bad or stale records could be processed are:
    1. clone creation initiated from a secondary node immediately after primary 
migration to different node.
    2. queue wraparound on any node and take over of primary by new node 
immediately afterwards.
Full fsck might not be able to rectify the file system corruption.

RESOLUTION:
Update the per node shared extent queue head and tail pointers to correct values 
on primary before starting processing of shared extent records.

* 2912435 (Tracking ID: 2885592)

SYMPTOM:
vxdump of a file system which is compressed using vxcompress is aborted.

DESCRIPTION:
vxdump is aborted due to malloc() failure. malloc()fails due to a 
memory leak in vxdump command code while handling compressed extents.

RESOLUTION:
Fixed the memory leak.

* 2923805 (Tracking ID: 2590918)

SYMPTOM:
Upon new node in the cluster taking over as primary of the file system, 
there might be a significant delay in freeing up unshared extents.  This problem 
can occur only in the case when shared extent addition or deletions occurred 
immediately after primary switch over to different node in the cluster.

DESCRIPTION:
When a new node in the cluster takes over as primary for the file 
system, a file system thread in the new primary performs a full scan of the 
shared extent device file to free up any shared extents that have become 
completely unshared.  If heavy shared extent related activity such as additional 
sharing or unsharing of extents were to occur anywhere in the cluster while the 
full scan was being performed, the full scan could get interrupted.  Due to a 
bug, the full scan is marked as completed and scheduled further scans of the 
shared extent device are partial scans.  This will cause a substantial delay in 
freeing up some of the unshared extents in the device file.

RESOLUTION:
If the first full scan of shared extent device upon primary takeover 
gets interrupted, then do not mark the full scan as complete.



INSTALLING THE PATCH
--------------------
If the currently installed VRTSvxfs is below 6.0.100.000, you must 
upgrade VRTSvxfs to 6.0.100.000 level before installing this patch.

A system reboot MAY be required after installing this patch.

The VRTSvxfs patch may be installed either by using the included 
hotfix installer or entirely manually.

 *  To apply patch using the hotfix installer, execute the commands
    
        # cd <hotfix_directory> && ./installFS601P2  [ <node1> <node2>... ]
    
    where
      <hotfix_directory>
                is the directory where you unpacked this hotfix
      <node1>, <node2>, ...
                are the nodes to be patched.  If none are specified, you
                will be prompted to enter them interactively.
    
    For information about installer options, run  './installFS601P2 -help'.


 *  To apply the patch manually:

    It is suggested that you quiesce or terminate all applications which 
    perform I/O on VxFS filesystems.  After VxFS has completed queued 
    requests, you should unmount all quiescent VxFS filesystems.

    On each system to be patched, execute the commands shown below 
    where <package_location> is the absolute pathname of the package 
    file  VRTSvxfs.p5p :
    
        # pkg uninstall VRTSvxfs 
        # pkg unset-publisher Symantec 
        # pkg set-publisher -g <package_location>  Symantec 
        # pkg install -g <package_location>  VRTSvxfs


REMOVING THE PATCH
------------------
Note:  Uninstalling this patch will remove the entire VRTSvxfs package.
        If you need an earlier version of the package, reinstall it from 
        original source media (ref. steps 2-4 below).

    It is suggested that you quiesce or terminate all applications which 
    perform I/O on VxFS filesystems.  After VxFS has completed queued 
    requests, you should unmount all quiescent VxFS filesystems.

 1. On each system from which the patch will be removed, execute the command 
    
        # pkg uninstall VRTSvxfs 
    
    If you do not require VxFS, you can skip the remaining steps below.

 2. Locate the package archive from your original source media which contains 
    the VRTSvxfs package version that was installed prior to installing the 
    patch.  In most cases, this will be 
                <path_to_install_directory>/pkgs/VRTSpkgs.p5p
    
    Note the absolute pathname of the package archive for later use.

 3. On each system to revert to pre-patch condition, execute the commands 
    shown below to install the pre-patch version of VRTSvxfs:
    
        # pkg unset-publisher Symantec 
        # pkg set-publisher -g <orig_package_archive>  Symantec 
        # pkg install -g <orig_package_archive>  VRTSvxfs 
    
    where <orig_package_archive> is the pathname noted in the previous 
    step.

 4. Either reboot all systems to complete the reversion, or (if possible) 
    restart VxFS services and remount filesystems.  Note that rebooting may 
    be mandatory after uninstalling the patch.


SPECIAL INSTRUCTIONS
--------------------
You might need to reboot the system(s) in order for the new version of 
VxFS drivers to come into effect.


OTHERS
------
NONE



Read and accept Terms of Service