* * * READ ME * * *
                * * * Veritas File System 5.0 MP2 * * *
                      * * * Rolling Patch 8 * * *
                         Patch Date: 2012-12-17


This document provides the following information:

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


PATCH NAME
----------
Veritas File System 5.0 MP2 Rolling Patch 8


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


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas File System 5.0 MP2
   * Veritas Storage Foundation for Oracle RAC 5.0 MP2
   * Veritas Storage Foundation Cluster File System 5.0 MP2
   * Veritas Storage Foundation 5.0 MP2
   * Veritas Storage Foundation High Availability 5.0 MP2
   * Veritas Storage Foundation for Oracle 5.0 MP2


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
HP-UX 11i v2 (11.23)


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

Patch ID: PHKL_43392, PHCO_43391

* 2834293 (Tracking ID: 2750860)

SYMPTOM:
On a large file system(4TB or greater), the performance of the write(1) 
operation with many small request sizes may degrade, and many threads may be 
found sleeping with the following stack trace:
real_sleep
sleep_one
vx_sleep_lock
vx_lockmap
vx_getemap
vx_extfind
vx_searchau_downlevel
vx_searchau_downlevel
vx_searchau_downlevel
vx_searchau_downlevel
vx_searchau_uplevel
vx_searchau
vx_extentalloc_device
vx_extentalloc
vx_te_bmap_alloc
vx_bmap_alloc_typed
vx_bmap_alloc
vx_write_alloc3
vx_recv_prealloc
vx_recv_rpc
vx_msg_recvreq
vx_msg_process_thread
kthread_daemon_startup

DESCRIPTION:
For a cluster-mounted file system, the free-extend-search algorithm is not 
optimized for a large file system (4TB or greater), and for instances where 
the number of free Allocation Units (AUs) available can be very large.

RESOLUTION:
The code is modified to optimize the free-extend-search algorithm by skipping 
certain AUs. This reduces the overall search time.

* 2867635 (Tracking ID: 2867633)

SYMPTOM:
The internal noise test on a locally mounted file system hits 
an "vx_delxwri_reclaim:1a" assert.

DESCRIPTION:
The vx_delxwri_reclaim() function is called from the vx_write_alloc() function 
only if the fault flag is not set and the error type is as follows: no space, 
volume disabled, or quota exceeded. This condition occurs due to the wrong 
conditions set when the vx_delxwri_reclaim() function is called from the 
vx_write_alloc() function.

RESOLUTION:
The code is modified to correct the conditions when the vx_delxwri_reclaim() 
function is called from the vx_write_alloc() function.

* 2870307 (Tracking ID: 2693010)

SYMPTOM:
The formatted uncompressed files created by the catman(1M) command for Veritas 
File System (VxFS) man pages remain available even after the removal of the 
VxFS package.

DESCRIPTION:
Currently, the formatted compressed files created by the catman(1M) command for 
VxFS man pages are not removed during the removal/uninstall of patches.

RESOLUTION:
The code is modified in the postremove and preinstall/postinstall packaging 
scripts to cleanup any remaining formatted uncompressed files created by the 
catman(1M) command.

* 2904377 (Tracking ID: 2599590)

SYMPTOM:
Expansion of a 100% full file system may panic the machine with the following 
stack trace.
 
bad_kern_reference()
$cold_vfault()
vm_hndlr()
bubbledown()
vx_logflush()
vx_log_sync1()
vx_log_sync()
vx_worklist_thread()
kthread_daemon_startup()

DESCRIPTION:
When 100% full file system is expanded intent log of the file system is 
truncated and blocks freed up are used during the expansion. Due to a bug the 
block map of the replica intent log inode was not getting updated thereby 
causing the block maps of the two inodes to differ. This caused some of the in-
core structures of the intent log to go NULL. The machine panics while de-
referencing one of this structure.

RESOLUTION:
Updated the block map of the replica intent log inode correctly. 100% full file 
system now can be expanded only If the last extent in the intent log contains 
more than 32 blocks, otherwise fsadm will fail. To expand such a file-system, 
some of the files should be deleted manually and resize be retried.

* 2988680 (Tracking ID: 2988678)

SYMPTOM:
The manual page for the setext(1m) command does not mention the license 
requirement correctly.

DESCRIPTION:
A full license is not required for the setext(1m) operation. This information is 
not mentioned in the manual page.

RESOLUTION:
The manual page is modified to mention that a full license is not required for 
the setext(1m) operation.


INSTALLING THE PATCH
--------------------
To install the VxFS 5.0-MP2RP8 patch:

a) To install this patch on a CVM cluster, install it one  system at a time so that all the nodes are not brought dow
n  simultaneously.

b) The VxFS 5.0(GA) must be installed before applying these   patches.

c) To verify the VERITAS file system level, execute:

     # swlist -l product | egrep -i 'VRTSvxfs'

  VRTSvxfs     5.0.01.04        VERITAS File System

Note: VRTSfsman is a corequisite for VRTSvxfs. So, VRTSfsman also needs to be installed with VRTSvxfs.

    # swlist -l product | egrep -i 'VRTS'

  VRTSvxfs      5.0.01.04      Veritas File System
  VRTSfsman     5.0.01.02      Veritas File System Manuals

d) All prerequisite/corequisite patches must be installed. The Kernel patch requires a system reboot for both install
ation and removal.

e) To install the patch, execute the following command:

# swinstall -x autoreboot=true -s <patch_directory>    PHKL_43392 PHCO_43391

If the patch is not registered, you can register it using the following command:

# swreg -l depot <patch_directory> 

The <patch_directory>     is the absolute path where the patch resides.


REMOVING THE PATCH
------------------
To remove the VxFS 5.0-MP2RP8 patch:

a) Execute the following command:

# swremove -x autoreboot=true PHKL_43392 PHCO_43391


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE