* * * READ ME * * *
* * * Cluster Server Agent Extension for SFCFS Distribution 6.0.5 * * *
                      * * * Patch 6.0.5.400 * * *
                         Patch Date: 2016-02-24


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
----------
Cluster Server Agent Extension for SFCFS Distribution 6.0.5 Patch 6.0.5.400


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


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


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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.0.500.400
* 3516607 (3093407) cfsmntadm utility may throw error when one node is sub-string of other.
Patch ID: 6.0.500.100
* 2933827 (2720034) The vxfsckd(1M) daemon does not restart after being killed manually.
* 3516604 (3142109) The CFSMountAgent script does not parse the MountOpt properly if -O overlay (native fs option) is used.
Patch ID: 6.0.500.000
* 3399337 (3410837) The error message has an issue when the user uses the cfsumount(1M) to unmount a mount point which has a samba parent resource.
Patch ID: 6.0.300.000
* 2933754 (2715175) 4 node cluster shutdown time takes 30 minutes
* 2949033 (2942776) CFS mount issues/VxVM - Mount fails when volumes in vset is not ready


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

Patch ID: 6.0.500.400

* 3516607 (Tracking ID: 3093407)

SYMPTOM:
When one host name in a Cluster is a sub-string of other host name(with
super-string differentiated by hyphen ('-')(e.g.: abc, abc-01), cfsmntadm
utility may throw error for some commands as follows: -

# cfsmntadm modify /swapmnt/ add abc="rw"
  Nodes are being added...
  Error: V-35-117: abc already associated with cluster-mount /swapmnt
  Nodes added to cluster-mount /swapmnt

DESCRIPTION:
cfs_lib.sh uses "grep -w" to extract the host name from the node list, which is
bound to fail if the cluster has host names as described in

RESOLUTION:
Modified cfs_lib.sh to use "grep -x" instead of "grep -w", in order to match the string exactly.

Patch ID: 6.0.500.100

* 2933827 (Tracking ID: 2720034)

SYMPTOM:
The vxfsckd(1M) daemon does not restart after being killed manually.

DESCRIPTION:
When the vxfsck process is killed manually, all the processes may not be killed 
and there might be some process still running. Starting of the new vxfscd fails 
since the cleanup of these processes is not done correctly.

RESOLUTION:
The script is modified to clean-up/kill existing vxfsckd daemons correctly 
before re-starting them.

* 3516604 (Tracking ID: 3142109)

SYMPTOM:
The CFSMountAgent script does not parse the MountOpt properly if the  -O overlay (native fs option) is used.

DESCRIPTION:
The CFSMountAgent script lacks logic to parse the -O option. The problem is as follows:

Assuming MountOpt attribute as follows:
MountOpt @lonu0261 = "suid, rw -O", 

CFSMountAgent script translates it to this:
-o cluster, suid, rw,-O, mntlock=VCS

So the native option AO is treated as a part of specific_options. As a result, the Mount(1M) command fails with the following error:
UX:vxfs mount: ERROR: V-3-21298: illegal -o suboption -- -O

RESOLUTION:
The CFSMountAgent script has been modified to parse the -O option correctly.

Patch ID: 6.0.500.000

* 3399337 (Tracking ID: 3410837)

SYMPTOM:
The error message has an issue when the user uses the cfsumount(1M) to unmount a mount point which has a samba parent resource.

DESCRIPTION:
The cfsunmount(1M) script uses "hares --value" to get the mount point. 
If the mount point which has samba parent resource is still mounted, then Cfsunmount(1M) gives an error message such as "Error: V-35-201: Cannot unmount 
/cifsdg/datavol2 on l111053, dependent [ ] currently mounted on l111053".

RESOLUTION:
The error message is appropriately changed for a better judgment.

Patch ID: 6.0.300.000

* 2933754 (Tracking ID: 2715175)

SYMPTOM:
cfsumount command runs slowly on large file system, there are some file system
reconfigure threads in the kernel.

schedule
vx_svar_sleep_unlock
vx_event_wait
vx_async_waitmsg
vx_msg_broadcast
vx_dele_rebuild
vx_dele_assumption
vx_recover
vx_recover_evanesce
vx_kthread_init
kernel_thread

DESCRIPTION:
When unmounting a file system, the cfsumount will try to offline the file system
on all nodes in parallel. If the primary file system node gets unmounted first,
the process of reconfigure will be initiated to migrate the primary to other
nodes, however, the reconfigure is unnecessary for cfsumount command. For large
file systems, reconfigure process involves much work and may take a long time.

RESOLUTION:
Unmount the secondary nodes first to avoid unnecessary file system reconfigure.

* 2949033 (Tracking ID: 2942776)

SYMPTOM:
CFSmount is failing with the error ENXIO or EIO on volume vset device. The error
messages look like
UX:vxfs mount.vxfs: ERROR: V-3-20005: read of super-block on
/dev/vx/dsk/sfsdg/vol1 failed: No such device or address
or
UX:vxfs mount.vxfs: ERROR: V-3-20005: read of super-block on
/dev/vx/dsk/sfsdg/vol2 failed: Input/output error

DESCRIPTION:
If the volume set is in ENABLED state but some underlying volumes are not ready
or in DISABLED state, the mount will fail with ENXIO or EIO.

RESOLUTION:
Code changes in cfsmntadm has been made to monitor the volume states in CVMVolDG 
agent.



INSTALLING THE PATCH
--------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch cavf-sol11_x64-Patch-6.0.5.400.tar.gz to /tmp
2. Untar cavf-sol11_x64-Patch-6.0.5.400.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/cavf-sol11_x64-Patch-6.0.5.400.tar.gz
    # tar xf /tmp/cavf-sol11_x64-Patch-6.0.5.400.tar
3. Install the hotfix
    # pwd 
    /tmp/hf
    # ./installCAVF605P4 [<host1> <host2>...]

You can also install this patch together with 6.0.1 GA release and 6.0.5 Patch release
    # ./installCAVF605P4 -base_path [<601 path>] -mr_path [<605 path>] [<host1> <host2>...]
where the -mr_path should point to the 6.0.5 image directory, while -base_path to the 6.0.1 image.

Install the patch manually:
--------------------------
1. pkg uninstall VRTScavf
2. pkg unset-publisher Symantec
3. pkg unset-publisher Veritas
4. pkg set-publisher -g <complete path of  package>    Veritas
5. pkg install --accept -g <complete path of package>    VRTScavf


REMOVING THE PATCH
------------------
1. pkg uninstall VRTScavf


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


OTHERS
------
NONE