README VERSION : 1.1 README CREATION DATE : 2012-03-14 PATCH-ID : 6.0.1.0 PATCH NAME : VRTScavf 6.0RP1 BASE PACKAGE NAME : VRTScavf BASE PACKAGE VERSION : 6.0.0.0 OBSOLETE PATCHES : NONE SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sles10_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER REBOOT REQUIRED : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to the Release Notes for Installation and Uninstallation Instructions. PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to the Release Notes for Installation and Uninstallation Instructions. SPECIAL INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 2608568 Abrupt messages are seen in engine log after complete storage failure in cvm resiliency scenario. SUMMARY OF KNOWN ISSUES: ----------------------------------------- 2689195 vxfsckd daemon is not getting joined/restarted after manual killing. KNOWN ISSUES : -------------- * INCIDENT NO::2689195 TRACKING ID ::2720034 SYMPTOM:: vxfsckd resource not coming up when reboot a node in cluster/killed vxfsckd, faulted cvm services. WORKAROUND:: Following commands need to be used when above situation arises hastop -local rm /var/adm/cfs/vxfsckd-pid kill all vxfsckd processes fsclustadm cfsdeinit hastart FIXED INCIDENTS: ---------------- PATCH ID:6.0.1.0 * INCIDENT NO:2608568 TRACKING ID:2663750 SYMPTOM: Incorrect remote notifications are given on local disk connectivity lost/restore event for disks with same pattern as that of actual disk for which event has occurred. DESCRIPTION: When local disk connectivity is restored/lost for a disk, in addition to correct notification for a disk cvmvoldg agent will also log wrong notifications in VCS engine log for disks having similar pattern though there is no change in connectivity on those disks. RESOLUTION:In cvmvoldg agent, local disk connectivity events (restore/lost) are now checked with exact match before reporting. INCIDENTS FROM OLD PATCHES: --------------------------- NONE