Patch-ID# 104172-05 Keywords: i18n metatool diskset mirror stripe RAID HA Synopsis: Solstice DiskSuite 4.1: Jumbo patch Date: May/12/97 Solaris Release: 2.4 or later SunOS Release: 5.4 or later Unbundled Product: Solstice DiskSuite Unbundled Release: 4.1 Relevant Architectures: sparc BugId's fixed with this patch: 4007392 4007398 4007403 4007037 4010514 4013935 4014398 4004412 4004551 4005380 4004668 4005880 4006305 1247309 4012852 4012858 4013095 4015009 4016074 4013260 4016847 4016077 1204367 1265579 4004441 1250238 4022285 4023536 4028959 4019273 4041484 4043506 4045398 1258389 1242214 Changes incorporated in this version: 4043506 4045398 1258389 1242214 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /kernel/drv/md /kernel/misc/md_mirror /kernel/misc/md_stripe /kernel/misc/md_hotspares /kernel/misc/md_trans /kernel/misc/md_raid /kernel/misc/md_notify /usr/lib/drv/config_md.so.1 /usr/lib/drv/preen_md.so.1 /usr/opt/SUNWmd/sbin/metaclear /usr/opt/SUNWmd/sbin/metadb /usr/opt/SUNWmd/sbin/metadetach /usr/opt/SUNWmd/sbin/metahs /usr/opt/SUNWmd/sbin/metainit /usr/opt/SUNWmd/sbin/metaoffline /usr/opt/SUNWmd/sbin/metaonline /usr/opt/SUNWmd/sbin/metaparam /usr/opt/SUNWmd/sbin/metarename /usr/opt/SUNWmd/sbin/metareplace /usr/opt/SUNWmd/sbin/metastat /usr/opt/SUNWmd/sbin/metasync /usr/opt/SUNWmd/sbin/metattach /usr/opt/SUNWmd/sbin/metaroot /usr/opt/SUNWmd/sbin/metaset /usr/opt/SUNWmd/sbin/rpc.metad /usr/opt/SUNWmd/sbin/rpc.metamhd /usr/opt/SUNWmd/sbin/metatool /usr/opt/SUNWmd/lib/X11/uid/Metatool/PerfMonWindow.uid Problem Description: Bugs corrected in revision 05: 4043506 - mirror_map_write() overwrites label on x86 during metareplace of mirror component 4045398 - ODS syncing devices will cause a read to hang 1258389 - on metasync -p failure, EQ_REGEN_DONE event returned instead of EQ_REGEN_FAILED 1242214 - TSmd/setup sometimes fails if test suite temp directory contains files Bugs corrected in revision 04: 4041484 - system panics during ha-switch due to mirror_mark_resync_region Bugs corrected in revision 03: 4019273 - mirror not synchronizing properly with ODS 3.0 or ODS 4.0 In some circumstances, when an application is modifying pages as they are being written, submirrors may momentarily contain different copies of data. This fix narrows this window to a much smaller time. 4023536 - RAID5 needs to set 4 bytes alignment for write buffer 4028959 - Incorrect size indicators are shown on Disk Information window. Bugs corrected in revision 02: 4004412 - add disk to diskset w/ stale dbases wipes out any existing configuration 4004551 - taking set with 2 of 3 replicas bad & mediators, returns 50/50 instead of stale 4005380 - loading a module when dbase is stale panics the machine 4004668 - release then take of diskset with mediators and tagged replicas clears replicas 4005880 - metaset -q shows and metaset -t -u accepts tags that are no longer available 4006305 - fully qualified non-existant slice results in core dump, eg. /dev/dsk/c0t0d0s44 1247309 - metaset takes a long time to take a set when a disk in an ssa is down 4012852 - inability to update at least 50% of mediators results in a panic on take owner 4012858 - SUNWmdm cannot be upgraded using standard pkgrm/pkgadd procedures 4013095 - metaset(1M) does not always balance replicas properly on dual string configs 4015009 - cannot forcible delete of a host and of a mediator host (host repair procedure) 4016074 - metaset take ownership takes too long w/ unreachable mediator host 4013260 - specifying diskset name prefix with device name stopped working; must use -s 4016847 - metadb -s-a fails when mediators are installed and second cluster host is down 4016077 - medstat(1M) takes too long w/ an unreachable mediator 1204367 - Customers request ability to perform resync at disk speed 1265579 - RAID-5 under extreme loads hangs for 10,000 seconds 4004441 - Mirror and Stripe xcall performance slower on 2.6 than on 2.51 1250238 - libconfig doesn't return storage descriptors for all disks in a set 4022285 - metaset -s -t -f will allow takeover of string with stale data with no error Bugs corrected in revision 01: 4007392 - (i18n) metatool hangs when select Exit on the File menu. 1) launch metatool under ja locale with both metatool.cat and Metatool for ja. 2) select File -> Exit 3) metatool hangs 4007398 - (i18n) Some items for Statistics Graph does not shown properly in ja locale. "Wait Queue", "15 Minute History (5 second intervals", "Totals", "Reads", "Writes" and "Load" are not shown properly in ja locale. The value for the divisions of the right scale of the graph does not show properly. It seems that the value is 0.0001, but it could not be shown. The value for the divisions of the left scale of the graph might have same problem as above. 4007403 - (i18n) "Size" of "Disk Information" is not correctly i18ned. The "Size" option menu in the Disk Information window is not i18n'ed correctly. 4007037 - (i18n) missing messages for metatool. "Tools" and it's menu items of metatool of SDS4.1 are not i18n'ed. 4010514 - (i18n) some OK seems to be hard coded. The OK button labels are hard coded in some places. 4013935 - "On Help..." does not show correct help messages The Help window, which comes up when selecting the "On help..." from the "Help" of DiskSuite tools (metatool, and so on), does not show the correct help message. 4014398 - %s shows up in several error dialogs The error dialogs for some SSA operations have a %s in them that's not filled in by the object that the error occurs upon. Patch Installation Instructions: -------------------------------- Refer to the Install.info file for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below as special instructions. Special Install Instructions: ----------------------------- A bug in backoutpatch has been discovered during the generation of this patch. The problem is seen when this patch is installed after previously backing it out, a syntax error will be seen while running the subsequent installpatch. The patch will install correctly, however, and can be successfully backed out.