README VERSION : 1.1 README CREATION DATE : 2012-09-20 PATCH-ID : 5.1.133.000 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 : rhel5_x86_64,rhel6_x86_64,sles10_x86_64,sles11_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : HANG , 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 INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 2636875 (2636874) AMF calls VxFS API with spinlock held. 2813781 (2813773) AMF driver panics the box with the message "AMF ASSERT panic: FAILED(dev_name)" 2907691 (2907684) AMF driver interaction with SLES-10 kernel should not break because of the changes in SLES-10 kernel. SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:5.1.133.000 * 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:2813781 TRACKING ID:2813773 SYMPTOM: AMF driver panics the box with the message "AMF ASSERT panic: FAILED(dev_name)" DESCRIPTION: When multipathd is run after AMF driver has started, multipathd calls an unmount operation. AMF driver does not get sufficient information about this unmount operation. As a result, AMF driver panics the machine. RESOLUTION: When AMF driver fails to get sufficient information about a mount or unmount operation, AMF driver notifies all mount and unmount events. * INCIDENT NO:2907691 TRACKING ID:2907684 SYMPTOM: AMF causes process inquiring programs like ps to hang. VCS agents also hang. DESCRIPTION: AMF driver interacts with the Linux kernel to get event notifications. A kernel change in SLES10 caused this interaction to break. RESOLUTION: Symantec changed the AMF driver to be able to work with the changed kernel. INCIDENTS FROM OLD PATCHES: --------------------------- Patch Id::5.1.132.000 * Incident no::2287061 Tracking ID ::2348721 Symptom::The basic event registration with AMF fails. Subsequently basic commands on the system hang. Description::This issue is observed only on SLES10 SP4. The AMF implementation running on SLES10 SP3 needed some changes to work on SLES10 SP4. Resolution::Symantec has enhanced the AMF driver so that it now supports SLES10 SP4. * 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::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. * Incident no::2439310 Tracking ID ::2483712 Symptom::Kernel panics when you mount a file system that is registered for mount offline monitoring. Description::The driver was sleeping on a semaphore in an atomic context and thus panicked by giving the error message "BUG: Scheduling while atomic". Resolution::Symantec modified the code to hold the semaphore in a non-atomic context.