* * * READ ME * * *
            * * * Symantec Storage Foundation HA 6.1.1 * * *
                      * * * Patch 6.1.1.200 * * *
                         Patch Date: 2014-12-15


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
   * KNOWN ISSUES


PATCH NAME
----------
Symantec Storage Foundation HA 6.1.1 Patch 6.1.1.200


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
RHEL6 x86-64


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSaslapm
VRTSllt
VRTSvxfs
VRTSvxvm


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec Cluster Server 6.1
   * Symantec Dynamic Multi-Pathing 6.1
   * Symantec File System 6.1
   * Symantec Storage Foundation 6.1
   * Symantec Storage Foundation Cluster File System HA 6.1
   * Symantec Storage Foundation for Oracle RAC 6.1
   * Symantec Storage Foundation HA 6.1
   * Symantec Volume Manager 6.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: VRTSvxfs-6.1.1.200
* 3660421 (3660422) On RHEL 6.6, umount(8) system call hangs if an application is watching for inode
events using inotify(7) APIs.
Patch ID: VRTSvxvm-6.1.1.100
* 3632970 (3631230) VRTSvxvm patch version 6.0.5 and 6.1.1 or previous will not work with RHEL6.6
update.
Patch ID: VRTSaslapm-6.1.1.200
* 3659363 (3665727) Array I/O POLICY is set to Single-active for SF6.1.1 with RHEL6.6
Patch ID: VRTSllt-6.1.1.100
* 3646467 (3642131) VCS support for RHEL 6.6

NOTE: For the incidents fixed in the previous patches please
refer to the product level readme files inside rpms folder.


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

Patch ID: VRTSvxfs-6.1.1.200

* 3660421 (Tracking ID: 3660422)

SYMPTOM:
On RHEL 6.6, umount(8) system call hangs if an application is watching for inode
events using inotify(7) APIs.

DESCRIPTION:
On RHEL 6.6, additional counters were added in the super block to track inotify
watches, these new counters were not implemented in VxFS.
Hence while doing umount, the operation hangs until the counter in the
superblock drops to zero, which would never happen since they are not handled in
VXFS.

RESOLUTION:
Code is modified to handle additional counters added in RHEL6.6.

Patch ID: VRTSvxvm-6.1.1.100

* 3632970 (Tracking ID: 3631230)

SYMPTOM:
VRTSvxvm patch version 6.0.5 and 6.1.1 will not work with RHEL6.6 update.

# rpm -ivh VRTSvxvm-6.1.1.000-GA_RHEL6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:VRTSvxvm               ########################################### [100%]
Installing file /etc/init.d/vxvm-boot
creating VxVM device nodes under /dev
WARNING: No modules found for 2.6.32-494.el6.x86_64, using compatible modules 
for 
2.6.32-71.el6.x86_64. 
FATAL: Error inserting vxio (/lib/modules/2.6.32-
494.el6.x86_64/veritas/vxvm/vxio.ko): Unknown symbol in module, or unknown 
parameter 
(see dmesg) ERROR: modprobe error for vxio. See documentation.
warning: %post(VRTSvxvm-6.1.1.000-GA_RHEL6.x86_64) scriptlet failed, exit 
status 1

#

Or after OS update, the system log file will have the following messages logged.

vxio: disagrees about version of symbol poll_freewait
vxio: Unknown symbol poll_freewait
vxio: disagrees about version of symbol poll_initwait
vxio: Unknown symbol poll_initwait

DESCRIPTION:
Installation of VRTSvxvm patch version 6.0.5 and 6.1.1 fails on RHEL6.6 due to 
the changes in poll_initwait() and poll_freewait() interfaces.

RESOLUTION:
The VxVM package has re-compiled with RHEL6.6 build environment.

Patch ID: VRTSaslapm-6.1.1.200

* 3659363 (Tracking ID: 3665727)

SYMPTOM:
vxdmpadm listapm output does not list any APM except default ones

[root@rpms]# vxdmpadm listapm
Filename           APM Name           APM Version  Array Types       State
================================================================================
dmpjbod.ko         dmpjbod                1        Disk              Active
dmpjbod.ko         dmpjbod                1        APdisk            Active
dmpalua.ko         dmpalua                1        ALUA              Not-Active
dmpaaa.ko          dmpaaa                 1        A/A-A             Not-Active
dmpapg.ko          dmpapg                 1        A/PG              Not-Active
dmpapg.ko          dmpapg                 1        A/PG-C            Not-Active
dmpaa.ko           dmpaa                  1        A/A               Active
dmpap.ko           dmpap                  1        A/P               Active
dmpap.ko           dmpap                  1        A/P-C             Active
dmpapf.ko          dmpapf                 1        A/PF-VERITAS      Not-Active
dmpapf.ko          dmpapf                 1        A/PF-T3PLUS       Not-Active
[root@rpms]#

DESCRIPTION:
For supporting RHEL6.6 update, dmp module is recomipled with latest RHEL6.6 
kernel version. During post install of the package
the APM modules fails to load due to mismatch in DMP and additional APM module 
kernel version.

RESOLUTION:
ASLAPM package is recompiled with RHEL6.6 kernel.

Patch ID: VRTSllt-6.1.1.100

* 3646467 (Tracking ID: 3642131)

SYMPTOM:
Low Latency Transport (LLT) fails to start on Red Hat Enterprise Linux 
(RHEL) 6 Update 6.

DESCRIPTION:
On RHEL 6.6, LLT fails to start due to kABI incompatibility. The 
following error appears: 

# rpm -ivh VRTSllt-6.1.1.000-RHEL6.x86_64.rpm 
Preparing...                ########################################### [100%]
   1:VRTSllt                ########################################### [100%]

# /etc/init.d/llt start
Starting LLT: 
LLT: loading module...
ERROR: No appropriate modules found.
Error in loading module "llt". See documentation.
LLT:Error: cannot find compatible module binary

Or after OS update, the following messages will be logged in the system log 
file: 

kernel: llt: disagrees about version of symbol ib_create_cq
kernel: llt: Unknown symbol ib_create_cq
kernel: llt: disagrees about version of symbol rdma_resolve_addr
kernel: llt: Unknown symbol rdma_resolve_addr
kernel: llt: disagrees about version of symbol ib_dereg_mr
kernel: llt: Unknown symbol ib_dereg_mr
kernel: llt: disagrees about version of symbol rdma_reject
kernel: llt: Unknown symbol rdma_reject
kernel: llt: disagrees about version of symbol rdma_disconnect
kernel: llt: Unknown symbol rdma_disconnect
kernel: llt: disagrees about version of symbol rdma_resolve_route
kernel: llt: Unknown symbol rdma_resolve_route
kernel: llt: disagrees about version of symbol rdma_bind_addr
kernel: llt: Unknown symbol rdma_bind_addr
kernel: llt: disagrees about version of symbol rdma_create_qp
kernel: llt: Unknown symbol rdma_create_qp

RESOLUTION:
VRTSllt package now includes RHEL 6.6 compatible kernel module.


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 hot-fix sfha-rhel6.6_x86_64-6.1.1.200-rpms.tar.gz to /tmp
2. Untar sfha-rhel6.6_x86_64-6.1.1.200-rpms.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/sfha-rhel6.6_x86_64-6.1.1.200-rpms.tar.gz
    # tar xf /tmp/sfha-rhel6.6_x86_64-6.1.1.200-rpms.tar
3. Install the hotfix
    # pwd /tmp/hf
    # ./installSFHA611P200 [<host1> <host2>...]

You can also use the 6.1.1MR installmr to install this patch together with 6.1.1:
# cd <6.1.1MR path>
# ./installmr -hotfix_path /tmp/hf [<host1> <host2>...]

Or, you can use the 6.1.1MR installmr to install this patch together with 6.1.1 and 6.1GA bits:
# cd <6.1.1MR path>
# ./installmr -hotfix_path /tmp/hf -base_path [<61GA path>] [<host1> <host2>...]
where the -base_path should point to the 6.1GA image directory.


Install the patch manually:
--------------------------
o Before-the-upgrade :-
  (a) Stop I/Os to all the VxVM volumes.
  (b) Umount any filesystems with VxVM volumes.
  (c) Stop applications using any VxVM volumes.
o Select the appropriate RPMs for your system, and upgrade to the new patch.
   # rpm -Uhv VRTSvxvm-6.1.1.100-RHEL6.x86_64.rpm VRTSaslapm-6.1.1.200-RHEL6.x86_64.rpm VRTSvxfs-6.1.1.200-RHEL6.x86_64.rpm VRTSllt-6.1.1.100-RHEL6.x86_64.rpm


REMOVING THE PATCH
------------------
# rpm -e  <rpm-name>


KNOWN ISSUES
------------
* Tracking ID: 3690067

SYMPTOM: The 'delayed allocation' (ie 'dalloc') feature on VxFS 6.1.1.100
p-patch can cause data loss or stale data.

 Dalloc feature is enabled by default for local mounted file system
and is not supported for cluster mounted file systems. Dalloc with sequential
extending buffer writes can possibly cause data loss or stale data. This issue
is seen only with 6.1.1.100 p patch.

WORKAROUND: disable the 'delayed allocation' ('dalloc') feature on the VxFS filesystems.

Following commands are used to disable dalloc.

1)For a filesystem which is already mounted
# vxtunefs -s -o dalloc_enable=0 $MOUNT_POINT

2) To make the value persistent across system reboot, add an entry to
/etc/vx/tunefstab
/dev/vx/dsk/$DISKGROUP/$VOLUME      dalloc_enable=0


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


OTHERS
------
NONE