Patch-ID# 102403-04 Keywords: topography, displays, 112, ssa, view, vxva Synopsis: Volume Manager 2.1: Volume Manager Jumbo Patch Date: Feb/01/96 Solaris Release: 2.3, 2.4 SunOS Release: 5.3, 5.4 Unbundled Product: SSA Volume Manager Unbundled Release: 2.1 Relevant Architectures: sparc BugId's fixed with this patch: 1210650 1203974 1201533 1189407 1189672 1208862 1209105 1212551 1212558 1214112 1215264 1218489 1226216 1229647 Changes incorporated in this version: 1226216 1218489 1229647 Patches accumulated and obsoleted by this patch: 102403-03 Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /etc/init.d/vxvm-reconfig /kernel/drv/vxio /kernel/drv/vxspec /sbin/vxconfigd /usr/lib/vxvm/bin/vxbootsetup /usr/lib/vxvm/bin/vxencap /usr/lib/vxvm/bin/vxevac /usr/lib/vxvm/bin/vxmirror /usr/lib/vxvm/bin/vxprtvtoc /usr/lib/vxvm/bin/vxslicer /usr/lib/vxvm/bin/vxunroot /usr/lib/vxvm/diag.d/vxconfigdump /usr/lib/vxvm/diag.d/vxkprint /usr/lib/vxvm/diag.d/vxprivutil /usr/lib/vxvm/type/fsgen/vxplex /usr/lib/vxvm/type/gen/vxmake /usr/lib/vxvm/type/gen/vxplex /usr/lib/vxvm/type/gen/vxsd /usr/lib/vxvm/type/gen/vxvol /usr/lib/vxvm/type/raid5/vxmake /usr/lib/vxvm/type/raid5/vxplex /usr/lib/vxvm/type/raid5/vxsd /usr/lib/vxvm/type/raid5/vxvol /usr/lib/vxvm/voladm.d/bin/disk.ckinit /usr/lib/vxvm/voladm.d/bin/disk.encap /usr/lib/vxvm/voladm.d/bin/disk.mirror /usr/lib/vxvm/voladm.d/help/disk.init.help /usr/lib/vxvm/voladm.d/help/disk.offline.help /usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh /usr/sbin/vxassist /usr/sbin/vxprint /usr/sbin/vxrecover /usr/sbin/vxstat /usr/sbin/vxtrace /opt/vxva/app-defaults/Vxva /opt/vxva/app-defaults/Vxva-color /opt/vxva/bin/vxva /opt/vxva/bin/vxva.dl /opt/SUNWvxvm/man/man1m/vxencap.1m /opt/SUNWvxvm/man/man1m/vxrootmir.1m /opt/SUNWvxvm/man/man1m/vxvol.1m /opt/SUNWvxvm/man/man7/vxevent.7 Problem Description: 1210650 The patch 102403-01 for Volume Manager 2.1 does not have the correct path for the files of the package SUNWvxva. 1203974 After a system panic the boot process cannot recover the raid 5 volumes. The system tries to swap out the entire vxvol one by one and do recovery. If swap + memo is equal to vxvol size or larger its ok If not you get"not enough memory" and you have to boot -s and encrease swap space. 1208862 vxvm error during vxrecover - Invalid magic number in log 1209105 vxvm: panic in vol_drlsio_done 1212551 A system panic occurs after forcing a raid5 volume into degraded mode. 1212558 Heavy I/o to mix of volumes results in a system panic 1214112 vxvm:vxassist: ERROR: diskgroup-name: Disk group is ambiguous 1215264 solaris 2.3, VM 2.1, VolumeManager suddenly goes hang during mirror sync. 1218489 Threads are hung on a rw lock owned by fsflush which is blocked on a semaphore 1226216 VM 2.1, patch 102403-03, ld.so.1: vxconfigd: fatal: libc.so.1: can't open file: 1229647 vxio panics in voliomem_more_memory at mutex_exit 1201533 System running load and stress tests on various volumes locks up system 1189407 vxva leaves zombie processes around after executing cli commands 1189672 recovery of RAID5 vol w/ DRL after simultaneous sys crash and disk failure broke Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- Backout obsolete patches 102403-01 and 102403-02.