* * * READ ME * * * * * * Veritas Group Lock Manager 6.0.1 * * * * * * Patch 6.0.1.200 * * * Patch Date: 2016-03-03 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 ---------- Veritas Group Lock Manager 6.0.1 Patch 6.0.1.200 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- HP-UX 11i v3 (11.31) PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSglm BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * 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: PVKL_04071 * 3845273 (2850818) GLM thread got panic with null pointer de-reference. Patch ID: PVKL_04035 * 3364311 (3364309) Internal stress test on cluster file system hit debug assert in Group Lock Manager (GLM). DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: PVKL_04071 * 3845273 (Tracking ID: 2850818) SYMPTOM: GLM thread may get panic if cache pointer remains null. DESCRIPTION: When GLM cache pointer is de-refrenced, thread got panicked. This is due to the reason that there can be a case where memory is not allocated to the cache and pointer remained null but we missed the check for null pointer and later we de-referenced that resulting into the panic. RESOLUTION: Code has been modified to handle the situation where memory is not allocated for the cache. Patch ID: PVKL_04035 * 3364311 (Tracking ID: 3364309) SYMPTOM: Internal stress test on cluster file system hit debug assert in Group Lock Manager (GLM). DESCRIPTION: In GLM, the code to handle last revoke for a lock may cause a deadlock which is caught upfront by debug assert. RESOLUTION: The code is modified to avoid deadlock while handling last revoke for a lock. 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 glm-hpux1131-Patch-6.0.1.200.tar.gz to /tmp 2. Untar glm-hpux1131-Patch-6.0.1.200.tar.gz to /tmp/hf # mkdir /tmp/hf # cd /tmp/hf # gunzip /tmp/glm-hpux1131-Patch-6.0.1.200.tar.gz # tar xf /tmp/glm-hpux1131-Patch-6.0.1.200.tar 3. Install the hotfix # pwd /tmp/hf # ./installGLM601P2 [ ...] You can also install this patch together with 6.0.1 GA release and 6.0.5 Patch release # ./installGLM601P2 -base_path [<601 path>] -mr_path [<605 path>] [ ...] 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: -------------------------- a)If you install this patch on a CVM cluster, install it one system at a time so that all the nodes are not brought down simultaneously. b)GLM 6.0.1(GA) must be installed before applying these patches. c)To verify the VERITAS file system level, enter: # swlist -l product | egrep -i "VRTSglm" d)All prerequisite/corequisite patches have to be installed.The Kernel patch requires a system reboot for both installation and removal. e)To install the patch, enter the following command: # swinstall -x autoreboot=true -s PVKL_04071 REMOVING THE PATCH ------------------ a)To remove the patch, enter the following command: # swremove -x autoreboot=true PVKL_04071 SPECIAL INSTRUCTIONS -------------------- Manually install this patch by the native OS command such as "patchadd" if it's installed on stacks other than 6.0.5. OTHERS ------ NONE