README VERSION : 1.1 README CREATION DATE : 2013-08-20 PATCH-ID : 5.1.134.000 PATCH NAME : VRTScavf 5.1.134.000 BASE PACKAGE NAME : VRTScavf BASE PACKAGE VERSION : 5.1.000.000 SUPERSEDED PATCHES : 5.1.133.000 REQUIRED PATCHES : 5.1.100.000 INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sles11_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : RECOMMENDED HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : Yes PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Release Notes for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Release Notes for uninstall instructions SPECIAL INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:5.1.134.000 2930184 (2720034) The vxfsckd(1M) daemon does not restart after being killed manually. PATCH ID:5.1.133.000 2922688 (2392571) cvm service group fails to come online after phased upgrade. PATCH ID:5.1.132.000 SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:5.1.134.000 * INCIDENT NO:2930184 TRACKING ID:2720034 SYMPTOM: The vxfsckd(1M) daemon does not restart after being killed manually. DESCRIPTION: When the vxfsck process is killed manually, all the processes may not be killed and there might be some process still running. Starting of the new vxfscd fails since the cleanup of these processes is not done correctly. RESOLUTION: The script is modified to clean-up/kill existing vxfsckd daemons correctly before re-starting them. PATCH ID:5.1.133.000 * INCIDENT NO:2922688 TRACKING ID:2392571 SYMPTOM: After Phased Upgrade cvm service group fails to come online on the nodes unless they are rebooted. DESCRIPTION: After Phased Upgrade cvm resource does not come up because VRTScavf patch overwrite /etc/VRTSvcs/conf/config/CVMTypes.cf and makes it an empty file. Because of this empty CVMTypes.cf file, installer cannot be used to start the processes but have to reboot the node to start the sub cluster. RESOLUTION: Code changes are made in the script such that cvm resource comes online successfully on the nodes without reboot. PATCH ID:5.1.132.000 INCIDENTS FROM OLD PATCHES: --------------------------- NONE