README VERSION : 1.1 README CREATION DATE : 2012-09-20 PATCH-ID : 145472-03 PATCH NAME : VRTSamf 5.1 SP1RP3 BASE PACKAGE NAME : Veritas Asynchronous Monitoring Framework by Symantec BASE PACKAGE VERSION : VRTSamf 5.1SP1 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol10_x86 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : PANIC PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer the release notes for installation instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer the release notes for un-installation instructions. SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 2621819 (2632569) Unable to stop to load amf driver even if amf in SMF is disabled 2636875 (2636874) AMF calls VxFS API with spinlock held. 2779958 (2779951) AMF event registration failure on Solaris. SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:145472-03 * INCIDENT NO:2621819 TRACKING ID:2632569 SYMPTOM: Even after AMF module is stopped, it gets loaded automatically when accessed. DESCRIPTION: Stopping AMF module does not completely remove the module from the system. Thus, if an operation is attempted on the module, the module gets loaded in the system. After stopping the AMF module, this is undesirable behavior. RESOLUTION: Symantec has changed code such that as part of stopping the AMF module, the AMF module gets completely removed from the system. * INCIDENT NO:2636875 TRACKING ID:2636874 SYMPTOM: The system panics when monitoring Veritas File System (VxFS) resources. DESCRIPTION: Asynchronous Monitoring Framework (AMF) calls the VxFS API when holding a spinlock. RESOLUTION: Symantec has fixed the code. Now the VxFS API is called outside of a spinlock. * INCIDENT NO:2779958 TRACKING ID:2779951 SYMPTOM: AMF event registration failure on Solaris. DESCRIPTION: Under certain conditions an AMF event remains in an inconsistent state in the AMF data structures. As a result, future AMF event registrations for the same event fail. RESOLUTION: Symantec changed the AMF driver to ensure that the event does not enter an inconsistent state. INCIDENTS FROM OLD PATCHES: --------------------------- Patch Id::145472-02 * Incident no::2301731 Tracking ID ::2301709 Symptom::Kernel panics when you unconfigure the AMF driver. Description::There was a race condition between a system call and the AMF driver unconfiguration which caused this issue. Resolution::Symantec modified the code to address this race condition. * Incident no::2403851 Tracking ID ::2403846 Symptom::System cannot unload the AMF driver. Description::An error in the code prevented the AMF module from being unloaded though the module was not being used. Resolution::Symantec has modified the code. AMF module can be unloaded when it is not in use. * Incident no::2406748 Tracking ID ::2406746 Symptom::Offline registration for a process with AMF succeeds even when the process is running. Description::When AMF processes the offline registration request, stale data from earlier cycles causes an online process to be reported as offline. Resolution::Symantec had modified the code to remove the stale data. The correct status is passed on to registration requests. * Incident no::2407612 Tracking ID ::2364959 Symptom::1. After installing 5.1sp1 without configuring when node is rebooted, LLT, GAB, FENCING and AMF goes in maintenance state. 2. After upgrade to 5.1SP1, local zones SMF dependencies complain about missing services and "svcs -x" is not clean Description::Install of 5.1SP1 or upgrade from 5.0 in a global zone only temporarily disables llt/gab/fencing/amf services. So after reboot they are re-enabled and SMF dependencies fail. Resolution::Changed the LLT, GAB, FENCING and AMF postinstall scripts to permanently disable services. Added a check not to create SMF service for non-global zones. * Incident no::2407653 Tracking ID ::2407652 Symptom::The module reference count on the filesystem registered with AMF for mount offline monitoring or mount online monitoring is not released when you forcefully unconfigure AMF using the "amfconfig -Uof" command. Description::When forcefully unconfiguring AMF, it was not releasing its reference from the filesystem modules. This caused extra reference counts on these modules to remain even after AMF driver was unloaded. Resolution::Symantec modified the code for proper reference counting on these filesystem modules during forceful unconfiguration of AMF.