* * * READ ME * * * * * * InfoScale 7.1 * * * * * * Patch 100 * * * Patch Date: 2016-05-30 NOTE: ---- The installer of this patch is updated on Dec. 5, 2016 to fix the following issue. Incident: 3906226 SYMPTOM: The VRTSaslapm RPM is not installed during the installation of version 7.1 along with the patch infoscale-rhel6.8_x86_64-Patch-7.1.0.100. DESCRIPTION: The installer fails to install the VRTSaslapm RPM during the installation of version 7.1 along with the patch infoscale-rhel6.8_x86_64-Patch-7.1.0.100. RESOLUTION: The installer code is now modified to install the RPM at the time of installation. 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.1 Patch 100 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- RHEL6 x86-64 PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSllt VRTSvxvm BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * InfoScale Availability 7.1 * InfoScale Enterprise 7.1 * InfoScale Foundation 7.1 * InfoScale Storage 7.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: VRTSllt-7.1.0.100 * 3880682 (3880681) Veritas Infoscale Availability does not support Red Hat Enterprise Linux 6 Update 8 (RHEL6.8). Patch ID: VRTSvxvm-7.1.0.100 * 3882137 (3880936) vxvmconvert hangs on RHEL 6.8. * 3882253 (3879234) dd read on the Veritas Volume Manager (VxVM) character device fails with Input/Output error while accessing end of device. * 3886205 (3868154) When DMP Native Support is set to ON, dmpnode with multiple VGs cannot be listed properly in the 'vxdmpadm native ls' command * 3886207 (3795622) With Dynamic Multipathing (DMP) Native Support enabled, Logical Volume Manager (LVM) global_filter is not updated properly in lvm.conf file. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: VRTSllt-7.1.0.100 * 3880682 (Tracking ID: 3880681) SYMPTOM: Veritas Infoscale Availability does not support Red Hat Enterprise Linux 6 Update 8 (RHEL6.8). DESCRIPTION: Veritas Infoscale Availability does not support RHEL versions later than RHEL6 Update 7. RESOLUTION: Veritas Infoscale Availability support for Red Hat Enterprise Linux 6 Update 8 (RHEL6.8) is now introduced. Patch ID: VRTSvxvm-7.1.0.100 * 3882137 (Tracking ID: 3880936) SYMPTOM: vxvmconvert hangs while analysing the LVM Volume Groups for further conversion. DESCRIPTION: The issue occurs due to additional messages in the duplicate warnings when executing "pvdisplay" command. The "PV UUID"s are not properly extracted because the keyword used to extract them is not correct. RESOLUTION: The code has been modified to extract PV UUIDs correctly. * 3882253 (Tracking ID: 3879234) SYMPTOM: dd read on the Veritas Volume Manager (VxVM) character device fails with Input/Output error while accessing end of device like below: [root@dn pmansukh_debug]# dd if=/dev/vx/rdsk/hfdg/vol1 of=/dev/null bs=65K dd: reading `/dev/vx/rdsk/hfdg/vol1': Input/output error 15801+0 records in 15801+0 records out 1051714560 bytes (1.1 GB) copied, 3.96065 s, 266 MB/s DESCRIPTION: The issue occurs because of the change in the Linux API generic_file_aio_read. Because of lot of changes in Linux API generic_file_aio_read, it does not properly handle end of device reads/writes. The Linux code has been changed to use blkdev_aio_read which is a GPL symbol and hence cannot be used. RESOLUTION: Made changes in the code to handle end of device reads/writes properly. * 3886205 (Tracking ID: 3868154) SYMPTOM: When DMP Native Support is set to ON, and if a dmpnode has multiple VGs, 'vxdmpadm native ls' shows incorrect VG entries for dmpnodes. DESCRIPTION: When DMP Native Support is set to ON, multiple VGs can be created on a disk as Linux supports creating VG on a whole disk as well as on a partition of a disk.This possibility was not handled in the code, hence the display of 'vxdmpadm native ls' was getting messed up. RESOLUTION: Code now handles the situation of multiple VGs of a single disk * 3886207 (Tracking ID: 3795622) SYMPTOM: With Dynamic Multi-Pathing (DMP) Native Support enabled, LVM global_filter is not updated properly in lvm.conf file to reject the newly added paths. DESCRIPTION: With DMP Native Support enabled, when new paths are added to existing LUNs, LVM global_filter is not updated properly in lvm.conf file to reject the newly added paths. This can lead to duplicate PV (physical volumes) found error reported by LVM commands. RESOLUTION: The code is modified to properly update global_filter field in lvm.conf file when new paths are added to existing disks. INSTALLING THE PATCH -------------------- Run the Installer script to automatically install the patch: ----------------------------------------------------------- Please be noted that the installation of this P-Patch will cause downtime. To install the patch perform the following steps on at least one node in the cluster: 1. Copy the patch infoscale-rhel6.8_x86_64-Patch-7.1.0.100.tar.gz to /tmp 2. Untar infoscale-rhel6.8_x86_64-Patch-7.1.0.100.tar.gz to /tmp/hf # mkdir /tmp/hf # cd /tmp/hf # gunzip /tmp/infoscale-rhel6.8_x86_64-Patch-7.1.0.100.tar.gz # tar xf /tmp/infoscale-rhel6.8_x86_64-Patch-7.1.0.100.tar 3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.) # pwd /tmp/hf # ./installVRTSinfoscale710P100 [ ...] You can also install this patch together with 7.1 base release using Install Bundles 1. Download this patch and extract it to a directory 2. Change to the Veritas InfoScale 7.1 directory and invoke the installer script with -patch_path option where -patch_path should point to the patch directory # ./installer -patch_path [] [ ...] Install the patch manually: -------------------------- Perform the following steps on the node on which this patch is being applied: 1. Take backup of your configurations 2. Stop VCS 3. Install the patch 4. Restart VCS on the node Stopping VCS on the cluster node -------------------------------- 1. Ensure that the /opt/VRTSvcs/bin directory is included in your PATH environment variable so that you can execute all the VCS commands. Refer to Veritas Cluster Server Installation Guide for more information. 2. Freeze all the service groups persistently. # haconf -makerw # hagrp -freeze [group] -persistent 3. If the cluster is writable, you may close the configuration before stopping the cluster. Stop the cluster on this node: # haconf -dump -makero run the following command: # hastop -local -force Verify that the cluster is stopped by running the ha command: # hasys -state make sure that both had and hashadow processes are stopped. Also, stop the VCS CmdServer: # CmdServer -stop 4. Stop the cluster services in order: - For VxFEN: # /etc/init.d/vxfen stop - For GAB: # /etc/init.d/gab stop - For LLT # /etc/init.d/llt stop Note: Stop any other services depending on GAB Installing the Patch -------------------- 1. Un-compress the downloaded patch and change the directory to the uncompressed patch location. Install the patch using the following command: # rpm -Uvh VRTSllt-7.1.0.100-RHEL6.x86_64.rpm 2. Run the following command to verify if the new patch has been installed: # rpm -q VRTSllt If the proper patch is installed, the following output is displayed: VRTSllt-7.1.0.100-RHEL6.x86_64 Re-starting the cluster services: -------------------------------- 1. To start the cluster services in order run the following command: - For LLT: # /etc/init.d/llt start - For GAB: # /etc/init.d/gab start - For VxFEN: # /etc/init.d/vxfen start - For VCS: # hastart # /opt/VRTSvcs/bin/CmdServer 2. Make VCS cluster writable: # haconf -makerw 3. Unfreeze all the groups: # hagrp -unfreeze [group] -persistent # haconf -dump -makero REMOVING THE PATCH ------------------ Removal of the patch will result in removing the whole package from the system/node. To go back to a previous installed version of the package, you may need to re-install the package. Run the following steps on the node where the patch is being uninstalled: To remove the patch from a cluster node: --------------------------------------------- 1. Freeze all the service groups persistently. # haconf -makerw # hagrp -freeze [group] -persistent 2. Stop VCS by following the stop sequence as mentioned in the PATCH INSTALLATION section. 3. Remove the patch by using the following command: # rpm -e VRTSllt --nodeps 4. Verify that the patch has been removed from the system: # rpm -qa|grep VRTSllt Ensure that the package is not displayed. This confirms that the package is removed. 5. Install the relevant package from the VCS base media. Also refer to SORT for any applicable patches. 6. To start the cluster service, follow the start sequence as mentioned in the PATCH INSTALLATION section. 7. Unfreeze all the groups. # hagrp -unfreeze [group] -persistent # haconf -dump -makero SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE