* * * READ ME * * *
* * * Cluster Server Agent Extension for SFCFS Distribution 5.1 SP1 RP1 * * *
                         * * * P-patch 1 * * *
                         Patch Date: 2012-06-28


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
----------
Cluster Server Agent Extension for SFCFS Distribution 5.1 SP1 RP1 P-patch 1


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTScavf


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Storage Foundation for Oracle RAC 5.1 SP1
   * Veritas Storage Foundation Cluster File System 5.1 SP1


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: PVCO_03956

* 2694495 (Tracking ID: 2669724)

SYMPTOM:
CFSMount agent hit assert on monitor timeout with stack similar to the 
following:

VCSAssert()
VCSAgThreadTbl::add()
VCSAgRes::call_entry_point()
VCSAgIntState::process_res_fault()
VCSAgISMonitoring::timedout()
VCSAgRes::process_cmd()
vcsag_service_thread_join()
start_thread()

Also following messages will apear in the engine log:

Thread(4149205920) Agent is calling clean for resource(cfsmount12) because 1 
successive invocations of the monitor procedure did not complete within the 
expected time.
2010 Jul 23 21:30:09 swsfs2_01 AgentFramework[3942]: ASSERTION FAILED

DESCRIPTION:
The pthread cancellation is not processed cleanly by the library 
glibc routines used in monitor entry point. Due to this the cancellation 
cleanup handler was not getting called.

RESOLUTION:
Replaced the glibc function with the unix system call to avoid it, 
e.g fopen() replaced with open and fgets() replaced with read().

* 2788309 (Tracking ID: 2684573)

SYMPTOM:
The performance of the cfsumount(1M) command for the VRTScavf package is slow 
when some checkpoints are deleted.

DESCRIPTION:
When a checkpoint is removed asynchronously, a kernel thread is started to 
handle the job in the background. If an unmount command is issued before these 
checkpoint removal jobs are completed, the command waits for the completion of 
these jobs. A forced unmount can interrupt the process of checkpoint deletion 
and the remaining work is left to the next mount.

RESOLUTION:
The code is modified to add a counter in the vxfsstat(1M) command to determine 
the number of checkpoint removal threads in the kernel. The "-c" option is 
added to the cfsumount(1M) command to force unmount a mounted file system if 
the checkpoint jobs are running.

Patch ID: PVCO_03932

* 2235677 (Tracking ID: 2233524)

SYMPTOM:
Cfs mount point deletion using VCSCVM failing due to improper mount point search

DESCRIPTION:
The issue is because of a bug in "cfsmntadm delete <mount point>" where the
search for mount point to be deleted is not correct. The search for mount point
generates multiple mount points in result instead of single mount point, which
causes the failure in mount point deletion.

RESOLUTION:
When deleting the mount point, search for exact block device name in the list so
that the CFS resource name is got correctly.

* 2241317 (Tracking ID: 2215429)

SYMPTOM:
During VCSCVM internal testing, CAVF related tests fails on 4 node cluster.

DESCRIPTION:
The issue is result of wrong search of node-name in deletion of nodes using
cfsmntadm command.

RESOLUTION:
The script is modified to search for exact word match of node-name in deletion
process.


INSTALLING THE PATCH
--------------------
Installing CFS 5.0 SP1RP1 patch:

CFS 5.0(GA)  must be installed before applying these patches.

To verify

     # swlist -l product | egrep -i "VRTScavf"

  VRTScavf     5.1.100.000        Veritas File System Administration Model

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

Incase the patch is not registered, the patch can be registered
using the following command:

# swreg -l depot <patch_directory>  ,

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


REMOVING THE PATCH
------------------
Removing VxFS 5.0 SP1RP1 patches:

a)To remove the patch, enter the following command:

# swremove -x autoreboot=true PVCO_03956


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


OTHERS
------
NONE