* * * READ ME * * *
               * * * Veritas File System 5.0.1 RP3 * * *
                         * * * P-patch 1 * * *
                         Patch Date: 2011.05.26


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 RP3 P-patch 1


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:

Patch ID: PHKL_42076

* 2080404 (Tracking ID: 2079457)

SYMPTOM:
Disk block and inode quota hard limit can crossed on CFS if soft limit
is 0.

DESCRIPTION:
On CFS if the soft limit is 0, both disk block and inode
allocations upto twice of hard limit get succeeded. In case of CFS, a flag is
set on per node quota record when soft limit is crossed. This flag should have
been set at the beginning in this case as soft limit is 0.

RESOLUTION:
If soft limit is 0, set the flag indicating that soft limit is
already crossed on per node quota record from the beginning.

* 2092080 (Tracking ID: 2030289)

SYMPTOM:
/
The mount operation of a full file system, with no empty block available, on 
the secondary node fails with the following error message:
" UX:vxfs mount: ERROR: V-3-26149: Cannot mount <device path> due to lack of 
free space."

The file system is not mountable even after a full fsck operation is performed.

/Problem

DESCRIPTION:
/
When a file system is mounted on a secondary node, some metadata files such as 
IFLOG, are created in pair with a match inode. Because it is a full file system 
with no empty block, the match inode for IFLOG cannot be created. These 
incomplete pairs remain on the disk and are not cleaned by the full fsck 
operation and eventually lead to an unmountable file system.

/

RESOLUTION:
/
The code has been modified to discard the incomplete pairs of inodes before 
trying to create new pairs.

* 2275534 (Tracking ID: 1475345)

SYMPTOM:
write() system call hangs for over 10 seconds on VxFS 3.5 on 11.23

DESCRIPTION:
While performing a transaction we used to flush one buffer(transaction space
asynchronously) at a time from logged writes which causes delay.

RESOLUTION:
Flush  all the dirty buffers on the file in one attempt through synchronous
flush, which we can free up a large amount of transaction space.

* 2340747 (Tracking ID: 2334061)

SYMPTOM:
When file system is mounted with tranflush option, operations requiring metadata
update take comparatively more time.

DESCRIPTION:
When VxFS file system is mounted with tranflush option, we flush transaction
metadata on the disk and wait for 100 milliseconds before
flushing next transaction. This delay is affecting severely operation of various
commands on the VxFS file system.

RESOLUTION:
Since the flushing is synchronous and is performed in loop, 100 milliseconds
delay is too much. To solve the problem, the delay is reduced to a more
reasonable 2 milliseconds value from 100 milliseconds.

* 2343169 (Tracking ID: 2343158)

SYMPTOM:
/
When the vx_ninode variable is being tuned with a value less than 
(250*vx_nfreelists), the following message is displayed:
"vmunix: ERROR: mesg 112: V-2-112: The new value requires changes to Inode 
table which can be made only after a reboot"

/Problem

DESCRIPTION:
/
The message does not clearly state whether the current tuning operation is 
completed and what is the final value of the vx_ninode variable.

/

RESOLUTION:
/
The message is modified to display the value of the vx_ninode variable after 
the operation is complete.

* 2347301 (Tracking ID: 2272072)

SYMPTOM:
GAB panics the box because VCS engine "had" did not respond. The lobolt
wraps around.

DESCRIPTION:
As per HP the lbolt wraps around after 498 days uptime. In VxFS we
flush VxFS meta data buffers based on their age. The age calculation happens
taking lbolt in account.

Due to lbolt wrapping we didn't flush the buffers. So lot of meta data IO's
stop. Hence the panic.

RESOLUTION:
In function where we do take decision of flushing dirty buffers we
handle condition if lbolt has wrapped. If it is then assign current lbolt time
to the last update time of dirtylist.

* 2347309 (Tracking ID: 2302426)

SYMPTOM:
System panics when multiple 'vxassist mirror' commands are running 
concurrently with following stack strace:

0)  panic+0x410 
1)  unaligned_hndlr+0x190 
2)  bubbleup+0x880  ( ) 
+-------------  TRAP #1  ---------------------------- 
|  Unaligned Reference Fault in KERNEL mode 
|    IIP=0xe000000000b03ce0:0 
|    IFA=0xe0000005aa53c114    <--- 
|  p struct save_state 0x2c561031.0x9fffffff5ffc7400 
+-------------  TRAP #1  ---------------------------- 
LVL  FUNC  ( IN0, IN1, IN2, IN3, IN4, IN5, IN6, IN7 ) 
3)  vx_copy_getemap_structs+0x70 
4)  vx_send_getemapmsg+0x240 
5)  vx_cfs_getemap+0x240 
6)  vx_get_freeexts_ioctl+0x990
7)  vxportal_ioctl+0x4d0 
8)  spec_ioctl+0x100 
9)  vno_ioctl+0x390 
10) ioctl+0x3c0
11) syscall+0x5a0

DESCRIPTION:
Panic is caused because of de-referencing an unaligned address in CFS message
structure.

RESOLUTION:
Used bcopy to ensure proper alignment of the addresses.


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_42076 PHCO_41727

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_42076 PHCO_41727


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