* * * READ ME * * * * * * Veritas Group Lock Manager 5.1 SP1 RP1 * * * * * * P-patch 1 * * * Patch Date: 2015-04-22 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 5.1 SP1 RP1 P-patch 1 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 5.1 SP1 * Veritas Storage Foundation for Oracle RAC 5.1 SP1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: PHKL_44216 * 3661441 (3364309) Internal stress test on the cluster file system, hit a debug assert in the Group Lock Manager (GLM). Patch ID: PHKL_42342 DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: PHKL_44216 * 3661441 (Tracking ID: 3364309) SYMPTOM: Internal stress test on the cluster file system, hit a debug assert in the Group Lock Manager (GLM). DESCRIPTION: In GLM, the code to handle the last revoke for a lock may cause a deadlock. This deadlock is caught upfront by the debug assert. RESOLUTION: The code is modified to avoid the deadlock when the last revoke for the lock is in progress. Patch ID: PHKL_42342 * 2241125 (Tracking ID: 2241123) SYMPTOM: glmdmp specific tests fail on 4-node cluster in internal testing. DESCRIPTION: /bin/sh interpreter does not understand variable declaration using 'typeset' RESOLUTION: Removed 'typeset' in variable declaration * 2406572 (Tracking ID: 2146573) SYMPTOM: Customer reported this as performance issue. The application was running slower when this problem happens. The SAR utility on HP-UX was showing some processes in PRI state. DESCRIPTION: (1) Complexity: This is an extremely complex performance concern in an environment where different applications are in great competition for the same system-wide resources. (2) Performance overheads: Competition for system resources is expected. However intense competition can create large overheads due to increased repetitive initialization. We approached this issue in multiple ways. Provided customer some tuning and application changes. RESOLUTION: No product bug was identified from Symantec side. However a GLM patch was provided to customer which does two things. 1. Different names given to different GLM spin locks. So that we can identify various locks from spin watcher output. 2. We take avoiding a spinlock which keeps accounting if how many times allocation did in GLM. Removing this lock will not cause any regression. Also, we have not said that it will solve this performance problem. INSTALLING THE PATCH -------------------- To install the GLM 5.1-11.31 SP1RP1P1 patch: a) The GLM 11.31 pkg with revision 5.1.100.000 b) To verify the VERITAS file system level, execute: # swlist -l product | egrep -i 'VRTSglm' VRTSglm 5.1.100.000 Veritas Group Lock Manager c)All prerequisite/corequisite patches have to be installed. d) To install the patch, execute the following command: # swinstall -x autoreboot=true -s PHKL_44216 If the patch is not registered, you can register it using the following command: # swreg -l depot The is the absolute path where the patch resides. REMOVING THE PATCH ------------------ Removing GLM 5.1-11.31 SP1RP1P1 patches: a)To remove the patch, enter the following command: # swremove -x autoreboot=true PHKL_44216 SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE