* * * READ ME * * * * * * Veritas I/O Fencing 6.0.5 * * * * * * Patch 6.0.5.100 * * * Patch Date: 2014-06-24 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 I/O Fencing 6.0.5 Patch 6.0.5.100 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- RHEL5 x86-64 PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSvxfen BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Symantec VirtualStore 6.0.1 * Veritas Cluster Server 6.0.1 * Veritas Storage Foundation Cluster File System HA 6.0.1 * Veritas Storage Foundation for Oracle RAC 6.0.1 * Veritas Storage Foundation HA 6.0.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: VRTSvxfen-6.0.500.100 * 3387018 (3471571) Cluster nodes may panic if you stop the HAD process by force on a node and reboot that node. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: VRTSvxfen-6.0.500.100 * 3387018 (Tracking ID: 3471571) SYMPTOM: Cluster nodes may panic if you stop the HAD process by force on a node and reboot or shutdown that node. DESCRIPTION: When you execute the following steps on any of the nodes in a cluster, the kernel may panic on any of the nodes in the cluster: 1. Stop the HAD process with the force flag: # hastop -local -force or # hastop -all -force 2. Reboot or shut down the node. Cluster nodes may panic because forcefully stopping VCS on a node leaves all the applications, file systems, CVM, and other processes on that node online. If you reboot the node with applications and processes in online state, VCS triggers a fencing race to avoid data corruption. The sub-cluster that loses the race panics. To ensure that rebooted node loses the race, increase LLT peerinact timeout on that node by running the lltconfig command. RESOLUTION: Symantec has fixed this issue such that rebooted node loses the fencing race and panics. The fix prevents the case where the rebooted node can win the fencing race and therefore cause other nodes in the cluster to panic. 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 vxfen-rhel5_x86_64-6.0.5.100-rpms.tar.gz to /tmp 2. Untar vxfen-rhel5_x86_64-6.0.5.100-rpms.tar.gz to /tmp/hf # mkdir /tmp/hf # cd /tmp/hf # gunzip /tmp/vxfen-rhel5_x86_64-6.0.5.100-rpms.tar.gz # tar xf /tmp/vxfen-rhel5_x86_64-6.0.5.100-rpms.tar 3. Install the hotfix # pwd /tmp/hf # ./installFEN605P1 [ ...] Install the patch manually: -------------------------- Perform the following steps on each cluster node, one node at a time: 1. Stop VCS: # /opt/VRTSvcs/bin/hastop -local 2. Stop vxfen: # /etc/init.d/vxfen stop 3. Apply the patch: # rpm -Uvh VRTSvxfen-6.0.500.100-GA_RHEL5.x86_64.rpm Verify that proper VRTSvxfen is installed: # rpm -qi VRTSvxfen Name : VRTSvxfen Relocations: (not relocatable) Version : 6.0.500.100 Vendor: Symantec Corporation Release : GA_RHEL5 Build Date: Tue 17 Jun 2014 04:50:33 PM IST Install Date: (not installed) Build Host: snapper53-64.engba.symantec.com Group : Applications/System Source RPM: VRTSvxfen-6.0.500.100-GA_RHEL5.src.rpm Size : 1745997 License: Symantec Proprietary Signature : (none) Packager : Enterprise_Support@symantec.com URL : http://www.symantec.com/business/support Summary : Veritas I/O Fencing by Symantec Description : Supported kernel(s): 2.6.18-128.el5 Build Stamp : Veritas-6.0.500.100-GA-2014-06-17_01.08.45 4. Start vxfen: # /etc/init.d/vxfen start 5. Start VCS: # /opt/VRTSvcs/bin/hastart REMOVING THE PATCH ------------------ Perform the following steps on each cluster node, one node at a time: 1. Stop VCS: # /opt/VRTSvcs/bin/hastop -local 2. Stop vxfen: # /etc/init.d/vxfen stop 3. Uninstall VRTSvxfen package: # rpm -ev VRTSvxfen 4. Install previous version of VRTSvxfen package. 5. Start vxfen: # /etc/init.d/vxfen start 6. Start VCS: # /opt/VRTSvcs/bin/hastart SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE