* * * READ ME * * *
                 * * * Veritas File System 5.0.1 * * *
                         * * * P-patch 3 * * *
                         Patch Date: 2011.02.23


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.1 P-patch 3


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


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas File System 5.0.1


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
HP-UX 11i v3 (11.31)


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

   * 2246611 (Tracking ID: 2206065)                                     

     SYMPTOM: CFS panic in vx_irtyhold_locked() with following stack:   
     panic+0x410 ( 0xe00000000057dee0, 0xe00000010064cbc8 )              
     bad_kern_reference+0xa0 ( 0x53, 0x9fffffff5d547400, 0x10010031, 0x30
     ) $cold_pfault+0x2c0 (0xe00000173219a980, 0x1, 0x10010031, 0x30,   
     0x53 ) vm_hndlr+0x1590 ( 0x9fffffff5d547400, 0x30 ) bubbleup+0x880 (
     ) +------------- TRAP #1 ---------------------------- | Data Access
     Rights Fault in KERNEL mode | IIP=0xe000000000be4b40:0 | IFA=0x30 |
     p struct save_state 0xff42031.0x9fffffff5d547400 +-------------    
     TRAP #1 ---------------------------- vx_itryhold_locked+0x160      
     (0xe00000139f7a0598 ) vx_iget+0x830 (                              
     0xe0000012d1abf080, 0xe000001295b34e80, ..) vx_attr_iget+0x60 (     
     0x9fffffff5d547840, 0x2004, ..) $cold_vx_dexh_load+0x30            
     (0xe0000013ab4fd660, 0x2004, ..) $cold_vx_dexh_init+0x550          
     (0xe0000013ab4fd660,..) vx_lookup+0x400 ( 0xe0000012d628a400,      
     0x9fffffff5d547a40,..) lookuppnvp(inlined) lookuppn(inlined)       
     lookupname+0x3b0( 0x9fffffff5d5479c0, 0x9fffffff5d547a41, 0x1,..)  
     vn_open+0xf0( 0x6000000001a73816, 0x0, 0x801, 0x1a0,.)              
     copen(inlined) open+0x1b0(..) syscall+0x5d0(                       
     0x5, 0x9fffffff5d547c00, 0x0 ) Also there would be a similar message
     in syslog at the same time: VxFS ALERT : Some driver called vnode  
     release improperly.                                                

     DESCRIPTION: The panic is caused due to inode freelist corruption  
     caused by a race condition whereby vx_inactive and rwlock          
     revokation as part of cfs inode deinitializations on a large       
     directory inode will both call VN_RELE on the internal LDH         
     attribute inode. These 2 VN_RELE’s may happen at the same time as  
     we do not take spin lock on the freelist in vx_inactive. Thus the  
     freelist may get corrupted and later when this inode on the        
     freelist is referenced by freelist modification code, it would     
     result in panic.                                                   

     RESOLUTION: The directory inode's internal attribute inode is      
     expunged in the rwlock revokation and not done at vx_inactive.     

   * 2246612 (Tracking ID: 2246579)                                     

     SYMPTOM: Filesystem corruptions and system panic when attempting to
     extend a 100%-full disk layout version 5(DLV5) VxFS filesystem     
     using fsadm(1M).                                                   

     DESCRIPTION: The behavior is caused by filesystem metadata that is 
     relocated to the intent log area inadvertently being destroyed when
     the intent log is cleared during the resize operation.             

     RESOLUTION: Refresh the incore intent log extent map by reading the
     bmap of the intent log inode before clearing it.                   


INSTALLING THE PATCH
--------------------
To install the VxFS 5.0.1-11.31 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 down simultaneously.
 

b) The VxFS 11.31 pkg with revision 5.0.31.5 must be installed before applying the patch.

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

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

  VRTSvxfs     5.0.31.5        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.31.5      Veritas File System
  VRTSfsman     5.0.31.5      Veritas File System Manuals

d)All prerequisite/corequisite patches have to be installed.The Kernel patch requires a system reboot for both installation and removal.
  

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

# swinstall -x autoreboot=true -s <patch_directory>  PHKL_41864

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.1-11.31 patch:

a) Execute the following command:

# swremove -x autoreboot=true PHKL_41864


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