release: /re/vm/bin/aix/patch/5.0mp1/RP-50mp1rp2/patchesVolume Manager 5.0.1.20 (Rolling-Patch_2) ======================================== Patch Information: ================== Date: 08 Aug 2007 AIX Release: AIX 5.2 /AIX 5.3 Product: VERITAS Volume Manager Release: VxVM 5.0 Fileset: VRTSvxvm Fileset level: VxVM 5.0.1.20 Description: VERITAS Volume Manager (VxVM) 5.0MP1 + Rolling-Patch_2 Pre-requisites: =============== 1. VxVM release level 5.0.1.0 (minimum) 2. AIX release level 5.2 TL8 and above (minimum) 3. AIX release level 5.3 TL5 Plus Service Pack 1 and above (minimum) Support for AIX 5.1 is not available for this release. Software patch for the VERITAS volume Manager(VxVM) to install over the VRTSvxvm fileset. Binaries included in this Rolling patch: ====================================== x ./usr/lib/drivers/vxdmp.5.1 x ./usr/lib/drivers/vxdmp.5.2 x ./usr/lib/drivers/vxdmp.5.3 x ./usr/lib/drivers/vxio.5.1 x ./usr/lib/drivers/vxio.5.2 x ./usr/lib/drivers/vxio.5.3 x ./opt/VRTS/bin/vxsnap x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/sbin/vxconfigd x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/sbin/vxconfigd.5.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/sbin/vxconfigd.5.2 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/sbin/vxconfigd.5.3 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/sbin/vxsnap x ./usr/lib/libvxscsi.so x ./usr/lib/vxvm/voladm.d/lib/vxadm_lvmlib.sh x ./usr/lib/vxvm/voladm.d/bin/disk.ckinit x ./usr/lib/vxvm/bin/vxnewdmname x ./usr/lib/vxvm/voladm.d/help/inst.dmname.help x ./usr/lib/libvxddl.a x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/kernel/dmpsvc.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/apmkey.d/dmpsvc.key.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/opt/VRTSvxms/lib/map/libvxdmp.so x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/opt/VRTSvxms/lib/map/libvxvm.sox ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/opt/VRTSvxms/lib/map/aix64/libvxvm.so x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/lib/discovery.d/libvxCLARiiON.so.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/aslkey.d/libvxCLARiiON.key.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/kernel/dmpCLARiiON.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/apmkey.d/dmpCLARiiON.key.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/aslkey.d/libvxhdsusp.key.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/lib/discovery.d/libvxhdsusp.so.1 x ./usr/lib/vxvm/bin/vxdevlist x ./usr/lib/vxvm/voladm.d/lib/vxadm_syslib.sh x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/lib/discovery.d/libvxhdsalua.so.1 x ./usr/lpp/VRTSvxvm/VRTSvxvm/5.0.1.20/inst_root/etc/vx/aslkey.d/libvxhdsalua.key.1 x ./usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh x ./usr/lib/vxvm/voladm.d/bin/vdisk.lvm.ckinit x ./usr/lib/vxvm/voladm.d/bin/vdisk.anal.ckinit Installation Procedure: ======================= If the currently installed VRTSvxvm is below 5.0.1.0 level, you must upgrade VRTSvxvm to 5.0.1.0 level before installing this patch. AIX maintenance levels and APARs can be downloaded from the IBM web site: http://techsupport.services.ibm.com 1. Since the patch process will configure the new kernel extensions, ensure that no VxVM volumes are in use or open or mounted before starting the installation procedure 2. Use the installp or Smit to install the patch image. Using installp: 0. Before applying this patch, please kill the vxsvc process: /opt/VRTSob/bin/vxsvcctrl stop 1. To apply this patch, use following command. installp -ag -d ./VRTSvxvm.05.00.0001.0020.bff VRTSvxvm 2. To apply and commit this patch, use following command installp -acg -d ./VRTSvxvm.05.00.0001.0020.bff VRTSvxvm NOTE: Please refer installp(1M) man page for clear understanding on APPLY & COMMIT state of the package/patch. Using Smit: Software Installation and Maintenance -> Install and Update Software -> Update Installed Software to Latest Level 3. Reboot the system after the installation is complete. Deinstallation Procedure: ========================= If patch installation is in "APPLY" state, patch image can be rejected or deinstalled. For rejecting the patch image, please use following command installp -r VRTSvxvm 5.0.1.20 This command will reject/deinstall the VRTSvxvm 5.0.1.20(MP1 RP2) patch. Patch contents cannot be rejected/deinstalled if it is in COMMITed state. Note that rejecting the patch will stop the vxconfigd(1M) (VxVM configuration Daemon). Please start vxconfigd manually or reboot the system. NOTE: Please refer SF 5.0 Installation Guide for AIX minimum level requirements. Incidents fixed in 5.0mp1rp2 patch: =================================== 1) Incident e1034736 Need to change dmp_get_path_state() to only check for write protection for Symmetrix arrays 2) Incident e1034737 Corrected PID in Clariion ASL NOTE: When you install this patch on machine with EMC-CLARION arrays which use libvxCLARiiON.so ASL, the disks state will be displayed as online udid_mismatch. This is occurring due to a PID change for this ASL. To move the disks to online state, you have to run the command, vxdisk 鈥揼 updateudid for disks with disk group or vxdisk updateudid for disks without a disk group 3) Incident e1064376 AIX: Disable ecopy probing in Hitachi Tagmastore ASL. 4) Incident e1066526 4042 : ./scripts/admin/voldg/cds/init.tc#1 failed 5) Incident e1072760 IO Errors during SVC node add/remove test sequence 6) Incident e1080971 vxvm commands take unexpected amount of time with clariion 7) Incident e1080973 vxvm gives same dmpnode for 2 netapp luns 8) Incident e1080991 VXMS: Escalation: Memory Leak in VM & DMP plugin of VxMS 9) Incident e1080993 VXMS: VM plugin of VxMS fails to initialise the private data of log plex and it results in buildmapdomain to fail 10) Incident e1080997 VXMS: VxDMP provider for VxMS does not return all the paths on Linux 11) Incident e1081000 VXMS: Adding support passive path - Adding VF_OID_DUMMY flag 12) Incident e1081003 VXMS: Escalation: Titan Case 290-543-757 -"Storage Extensions doesn"t work" - dg_set_current fails for bootdg 13) Incident e1081005 VXMS: Customer Escalation: Open Failing on Passive Paths 14) Incident e1101658 5012:CVMTC: drl_rec_dbg.tc hung causing node to reebots 15) Incident e1110211 5012 : vxconvert needs a correct default "Disk_Access_Name" 16) Incident e1112840 5012 : vxconvert : Vxconvert repeatedly asks for disk names when default disk layout is changed. 17) Incident e1082148 vxconvert command fails to convert for VPATH devices NOTE: vxconvert works with vpath devices. 18) Incident e1083610 VVR:hang on primary with heavy io load because of unprotected setting and resetting ru state flag 19) Incident e1084341 AIX : lex/yacc parser error due to compiler change 20) Incident e1085640 AIX: No need to say fencing ioctl succeeded 21) Incident e1087620 AIX:SVC: svc disk are very slow during online, if the disk is not registered. 22) Incident e1092024 AIX : DMP : RDAC devices panic due to invalid file pointer 23) Incident e1092300 AIX : DMP : IO"s to DMP devices are broken into 128 MB instead of 256 24) Incident e1094138 VXMS: Escalation: Storage Extensions doesn"t work - VM plugin of VxMS tries to claim "/" 25) Incident e1097611 Willow 5.0: Hazard read data corruption 26) Incident e1097729 AIX: VOL_TIMEOUT*() macros can hang the system 27) Incident e1098768 5012 :vxconfigd core dumped Incidents fixed in 5.0mp1rp1 patch: =================================== 1) Incident e973100 vxsnap refresh failed with volume names longer than 24 characters 2) Incident e989870 CVM Reboot Resources Fault - (RETEST)Qualification AxRT SFOR 4.0mp4 DMP AIX 5.3 DS4300a0a 3) Incident e989872 AxRT 5.0MP1; cdmedia; vxconvert removed LVM and failed to convert 4) Incident e989880 Window exists in vxreconfd thread during vold signal that can lead to reconfiguration hang 5) Incident e989881 AxRT5.0: CVM: nodes remain in "master selection" after updown using "shutdown - r now" on 16 nodes 6) Incident e994862 panic in dbf_fmt_tbl dg disabled 7) Incident e994867 system panic in function voliod_iohandle as it tries to use previously freed sio 8) Incident e1013534 : QA-GENERATED: vxdiskadm: not able to add a disk to a new disk group 9) Incident e1019740: 5011 vxconvert : default disk naming logic is incorrect 10) Incident e 1030723 : vxdisk updateudid after udid_mismatch could lead to dg config mess up 11) Incident e1067642: AIX: Detection of SAS disks under VxVM control