* * * READ ME * * *
                       * * * InfoScale 7.0 * * *
                         * * * Patch 100 * * *
                         Patch Date: 2015-10-01


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
----------
InfoScale 7.0 Patch 100 (Adds RHEL6.7 support)


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


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSamf
VRTSdbac
VRTSgab
VRTSllt
VRTSvxfen
VRTSvxfs
VRTSvxvm


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Availability 7.0
   * InfoScale Enterprise 7.0
   * InfoScale Foundation 7.0
   * InfoScale Storage 7.0


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: VRTSvxvm-7.0.0.100-RHEL6
* 3851219 (3776520) Filters are not updated properly in lvm.conf file in VxDMP initrd(initial 
ramdisk) while enabling Dynamic Multipathing (DMP) Native Support.
* 3851231 (3802750) VxVM (Veritas Volume Manager) volume IO-shipping functionality is not disabled 
even after the user issues the correct command to disable it.
* 3851242 (3823283) While unencapsulating a boot disk in SAN environment(Storage Area Network),
Linux operating system sticks in grub after reboot.
Patch ID: VRTSvxfs-7.0.0.100-RHEL6
* 3790562 (3736398) NULL pointer dereference panic in lazy unmount.
* 3807368 (3807366) The man pages included in the VRTSvxfs, VRTSfsadv and
VRTSfssdk packages have an incorrect product version.
* 3816107 (3812914) On RHEL 6.5 and RHEL 6.4 latest kernel patch, umount(8) system call hangs if an
application watches for inode events using inotify(7) APIs.
Patch ID: VRTSamf-7.0.0.100-RHEL6
* 3853083 (3794154) Veritas Cluster Server (VCS) does not support Red Hat Enterprise Linux 6 Update 7
(RHEL6.7).
Patch ID: VRTSvxfen-7.0.0.100-RHEL6
* 3853083 (3794154) Veritas Cluster Server (VCS) does not support Red Hat Enterprise Linux 6 Update 7
(RHEL6.7).
Patch ID: VRTSgab-7.0.0.100-RHEL6
* 3853083 (3794154) Veritas Cluster Server (VCS) does not support Red Hat Enterprise Linux 6 Update 7
(RHEL6.7).
Patch ID: VRTSllt-7.0.0.100-RHEL6
* 3853083 (3794154) Veritas Cluster Server (VCS) does not support Red Hat Enterprise Linux 6 Update 7
(RHEL6.7).
Patch ID: VRTSdbac-7.0.0.100-RHEL6
* 3852335 (3852338) 7.0.0 vcsmm module does not load with RHEL6.7 (2.6.32-573.el6.x86_64)


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

Patch ID: VRTSvxvm-7.0.0.100-RHEL6

* 3851219 (Tracking ID: 3776520)

SYMPTOM:
Filters are not updated properly in lvm.conf file in VxDMP initrd while enabling 
DMP Native Support leading to root Logical Volume (LV) mounted on OS 
device upon reboot.

DESCRIPTION:
From LVM version 105, global_filter were introduced as part of lvm.conf file. 
VxDMP updates initird lvm.conf file with the filters required for DMP 
Native Support to function. While updating the lvm.conf, VxDMP checks for the 
filter field to  be updated whereas ideally we should check for 
global_filter field to be updated in the latest LVM version. This leads to 
lvm.conf file not having the proper filters leading to the issue.

RESOLUTION:
Code changes have been made to properly update global_filter field in lvm.conf 
file in VxDMP initrd.

* 3851231 (Tracking ID: 3802750)

SYMPTOM:
Once VxVM (Veritas Volume Manager) volume IO-shipping functionality is turned 
on, it is not disabled even after the user issues the correct command to disable 
it.

DESCRIPTION:
VxVM (Veritas Volume Manager) volume IO-shipping functionality is turned off by 
default. The following two commands can be used to turn it on and off:
	vxdg -g <dgname> set ioship=on
	vxdg -g <dgname> set ioship=off

The command to turn off IO-shipping was not working as intended due to a problem 
with IO-shipping flags not being reset properly.

RESOLUTION:
Code changes have been done to correctly reset IO-ship flags when the user 
issues the CLI command.

* 3851242 (Tracking ID: 3823283)

SYMPTOM:
After taking reboot, OS sticks in grub. Manual kernel load is required to make
operating system functional.

DESCRIPTION:
During unencapsulation of a boot disk in SAN environment, multiple entries
corresponding to root disk are found in by-id device directory. As a result, a
parse command will fail leading to create an improper menu file in grub. This
menu file defines the device path from where kernel and other modules will be
loaded.

RESOLUTION:
Proper modifications in code base is done to handle the multiple entries for SAN
boot disk.

Patch ID: VRTSvxfs-7.0.0.100-RHEL6

* 3790562 (Tracking ID: 3736398)

SYMPTOM:
Panic in the lazy unmount path during deinit of VxFS-VxVM API.

DESCRIPTION:
The panic is caused when an exiting thread drops the last reference
to a lazy-unmounted VxFS file-system where that fs is the last VxFS mount in the
system. The exiting thread does unmount, which then calls into VxVM to
de-initialize the private FS-VM API(as it is the last VxFS mounted fs). 
The function to be called in VxVM is looked-up via the files under /proc, this
requires an opening of a file but the exit processing has removed the structs
needed by the thread to open a file.

RESOLUTION:
The solution is to cache the de-init function (vx_fsvm_api_deinit)
when the VxFS-VxVM API is initialized, so no function look-up is needed during
an unmount. The cached function pointer can then be called during the last
unmount bypassing the need to open the file by the exiting thread.

* 3807368 (Tracking ID: 3807366)

SYMPTOM:
The man pages included in the VRTSvxfs, VRTSfsadv and VRTSfssdk
packages identify the product version incorrectly as 6.2, instead of the correct
7.0.

DESCRIPTION:
Man pages included in the packages identify the product version
they document. For the man pages included in the 7.0 release, this version was
incorrectly mentioned as 6.2.  The online versions of the man pages available
from SORT have previously been updated to mention the correct version.

RESOLUTION:
The versions in the man pages have been corrected and updated man
pages have been included in the packages.

* 3816107 (Tracking ID: 3812914)

SYMPTOM:
On RHEL 6.5 and RHEL 6.4 latest kernel patch, umount(8) system call hangs if an
application watches for inode events using inotify(7) APIs.

DESCRIPTION:
On RHEL 6.5 and RHEL 6.4 latest kernel patch, additional OS counters were added in
the super block to track inotify Watches. These new counters were not implemented
in VxFS for RHEL6.5/RHEL6.4 kernel. 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:
The code is modified to handle additional counters added in super block of
RHEL6.5/RHEL6.4 latest kernel.

Patch ID: VRTSamf-7.0.0.100-RHEL6

* 3853083 (Tracking ID: 3794154)

SYMPTOM:
Veritas Cluster Server (VCS) does not support Red Hat Enterprise Linux 6 Update 7
(RHEL6.7).

DESCRIPTION:
VCS did not support RHEL versions released after RHEL6 Update 6.

RESOLUTION:
VCS support for Red Hat Enterprise Linux 6 Update 7 (RHEL6.7) is now introduced.

Patch ID: VRTSvxfen-7.0.0.100-RHEL6

* 3853083 (Tracking ID: 3794154)

SYMPTOM:
Veritas Cluster Server (VCS) does not support Red Hat Enterprise Linux 6 Update 7
(RHEL6.7).

DESCRIPTION:
VCS did not support RHEL versions released after RHEL6 Update 6.

RESOLUTION:
VCS support for Red Hat Enterprise Linux 6 Update 7 (RHEL6.7) is now introduced.

Patch ID: VRTSgab-7.0.0.100-RHEL6

* 3853083 (Tracking ID: 3794154)

SYMPTOM:
Veritas Cluster Server (VCS) does not support Red Hat Enterprise Linux 6 Update 7
(RHEL6.7).

DESCRIPTION:
VCS did not support RHEL versions released after RHEL6 Update 6.

RESOLUTION:
VCS support for Red Hat Enterprise Linux 6 Update 7 (RHEL6.7) is now introduced.

Patch ID: VRTSllt-7.0.0.100-RHEL6

* 3853083 (Tracking ID: 3794154)

SYMPTOM:
Veritas Cluster Server (VCS) does not support Red Hat Enterprise Linux 6 Update 7
(RHEL6.7).

DESCRIPTION:
VCS did not support RHEL versions released after RHEL6 Update 6.

RESOLUTION:
VCS support for Red Hat Enterprise Linux 6 Update 7 (RHEL6.7) is now introduced.

Patch ID: VRTSdbac-7.0.0.100-RHEL6

* 3852335 (Tracking ID: 3852338)

SYMPTOM:
VRTSdbac patch version does not work with RHEL6.7 (2.6.32-573.el6.x86_64 
kernel) and is unable to load the vcsmm module on RHEL6.7.

DESCRIPTION:
Installation of VRTSdbac patch version 7.0.0 fails on RHEL6.7 as 
the VCSMM module is not available on RHEL6.7 kernel 2.6.32-573.el6.x86_64. 
The system log file logs the following messages:
Starting VCSMM: 
ERROR: No appropriate modules found.
Error in loading module "vcsmm". See documentation.
Error : VCSMM driver could not be loaded.
Error : VCSMM could not be started.
Error : VCSMM could not be started.

RESOLUTION:
The VRTSdbac package is re-compiled with RHEL6.7 kernel in the build 
environment to mitigate the failure.



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 infoscale-rhel6.7_x86_64-Patch-7.0.0.100.tar.gz to /tmp
2. Untar infoscale-rhel6.7_x86_64-Patch-7.0.0.100.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/infoscale-rhel6.7_x86_64-Patch-7.0.0.100.tar.gz
    # tar xf /tmp/infoscale-rhel6.7_x86_64-Patch-7.0.0.100.tar
3. Install the hotfix
    # pwd /tmp/hf
    # ./installVRTSinfoscale700P100 [<host1> <host2>...]

You can also install this patch together with 7.0 GA release using Install Bundles
1. Download Infoscale Solutions 7.0
2. Extract the tar ball into the /tmp/infoscale7.0/ directory
3. Change to the /tmp/infoscale7.0 directory by entering:
    # cd /tmp/infoscale7.0
4. Invoke the installr script with -patch_path option where the -patch_path option 
should point to the 7.0.0.100 directory.   
    # ./installr -patch_path [<patch path>] [<host1> <host2>...]

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 <rpm-name>


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


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


OTHERS
------
NONE