ECO NUMBER: ALPMOUN04_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPMOUN04_062 2 KITS SUPERSEDED BY THIS KIT: ALPMOUN03_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: ALPCLUSIO01_062 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: These following kits are only required if you are running MME-based applications: ALPSYSA02_062 ALPBACK02_062 ALPDISM02_062 ALPINIT01_062 ALPMTAA02_062 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 4.2 Files patched or replaced: o [SYSLIB]MOUNTSHR.EXE (new image) o [SYSEXE]VMOUNT.EXE (new image) o [SYSLIB]DCLTABLES.EXE (updated with a new MOUNT.CLD) -- COVER LETTER -- Page 2 24 February 1999 5 PROBLEMS ADDRESSED IN ALPMOUN04_062 KIT o This kit provides a new check to determine if the disk that being MOUNTed is initialized to a size that is larger than the number of blocks that are currently available. This condition is a result of a disk that is moved from one controller type to another (for example, from a local SCSI connection to an HSJ) without the disk being initialized on the new controller. o Mount Verification fails incorrectly with a "wrong volume" error if the device is mounted /NOWRITE. This failure also occurs when former shadow set members are MOUNTed without /OVERRIDE=SHADOW, which causes the device to be mounted write-locked. o MOUNT/SYSTEM fails with an %MOUNT-F-IVBUFLEN error when an attempt is made to MOUNT an ISO 9660 CDROM with a volume label of more than 27 characters. The ISO 9660 specification allows volume labels of 32 characters. o A MOUNT/POLICY=(REQUIRE_MEMBERS,VERIFY_LABELS) switch was added to the MOUNT command. This change is an enhancement, not a fix. The following switch and options were added to MOUNT: 1. /POLICY=REQUIRE_MEMBERS - force all specified members to be available for MOUNT to occur The /POLICY=REQUIRE_MEMBERS option is used in disaster-tolerant configurations where another site may have a more recent disk that is not available. In effect, this option will force more human decision making. 2. /POLICY=VERIFY_LABELS - all copy targets must have label "SCRATCH_DISK" or they will not be added to the set The volume must be ODS2 and have a valid file structure. The new option will force users to use alternate volume labels. One of the biggest causes of "a wrong disk being added to a shadow set" is mis-typed commands. If users are given a way to be sure that they only added "scratch" disks to shadow sets, then they will be less likely to lose data. This option is similar to /CONFIRM, except that it can be used in command procedures as well, without immediate operator intervention. It is also similar to the /NOCOPY command, except it allows copies to occur, as long as the label is "scratch". NOTE: -- COVER LETTER -- Page 3 24 February 1999 Related to the above two qualifiers, the following new error messages were added to MOUNT. However, these messages will not display correctly until an updated SYSMSG.EXE has been installed on your system. Although MOUNT will still operate correctly, it will report these errors as: %NONAME-F-NOMSG, Message number 00728xxx The message numbers and their corresponding messages are as follows: 007283C4 is "NOTALLMEM, one or more specified members not available for mounting" 007283CC is "BADPOLICY, invalid syntax on /POLICY" A TIMA kit with a new SYSMSG.EXE will be available at a future date. o A process using MME could potentially "miss" the VOL1 label on a tape. Also, a process could "hang" trying to send a message to the MME process. o A possible system crash occurs during Host Based RAID Unbinds with MME code enabled. A mailbox read synchronization problem causes the crash. This problem only occurs when a host-based RAID UNBIND command is done while an MME-based application is running. This problem may occur in several different code areas of the operating system. In order to eliminate all instances of this problem, the following remedial kits (or their supersedants) will also need to be installed: o ALPSYSA02_062 o ALPBACK02_062 o ALPDISM02_062 o ALPINIT01_062 o ALPMTAA02_062 o $MOUNT DSAn/SHAD=$n$ddcu (shadow set), with a media manager running, causes a "no such device error" and then mount fails. o MME (MME_MNTREQ) broke the RAID BIND command with shadow sets. MME passes a fatal error to Host-Based Shadowing or Host-Based Raid on a mount request, if the shadow set virtual unit has not been created. -- COVER LETTER -- Page 4 24 February 1999 o A media management application can crash the system with an invalid exception bugcheck. The reason for the crash is due to an access violation. The crashing image is [SYSLIB]MMESHR.EXE 6 PROBLEMS ADDRESSED IN ALPMOUN03_062 KIT o If the target disk of a shadow copy has been initialized, such that the SCB is in a different location than that of the master node (i.e. INIT/INDEX=END), and the shadow copy has not yet started, then validation during a second MOUNT of this disk would fail with an ISAMBR error. However, this error message was incorrect; the actual error was a WRONGVU error. 7 PROBLEMS ADDRESSED IN ALPMOUN02_062 KIT o There have been a number of reports of "MOUNT-F-ISAMBR" error messages on MOUNT/SHADOW. Most of them were not reproducible and most of them were on shadow sets that were already mounted elsewhere in the cluster. This error message does not give the user any idea why the MOUNT failed. The failure message is now clearer. o A device could be mounted /NOSHARE on one system and as the member of a shadow system disk on another system. This could result in Disk Corruption. No "Alloc. lock ID" is setup on the booting system. o A MOUNT of a former shadow set member will fail on all nodes in a cluster, except the first mounting node, with a "%MOUNT-F-DIFVOLMNT" failure. o A MOUNT of multiple tape devices with one command will cause inconsistent "write lock" attributes. For example: $ mount/write mkb400,mkb500 MKB400,TZ000 %MOUNT-I-MOUNTED, MKB400 mounted on _N24005$MKB400: %MOUNT-I-MOUNTED, TZ000 mounted on _N24005$MKB500: $ sho dev mkb Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt MKB400: Mounted alloc 0 MKB400 0 1 1 MKB500: Mounted alloc 0 TZ000 0 1 1 wrtlck MKB500 should not be "wrtlck". o MOUNT messages obtained through OPCOM with MOUNT/ASSIST are often less helpful than the error code returned when /NOASSIST is specified. For example: -- COVER LETTER -- Page 5 24 February 1999 $ MOUNT/ASSIST /OVER=ID mua0: %MOUNT-I-OPRQST, device _SCSI3$MUA0: contains the wrong volume %MOUNT-I-OPRQST, Please mount device _SCSI3$MUA0: MOUNT/NOASSIST /OVER=ID mua0: %MOUNT-F-NOTLABELMT, tape is not labeled The "NOTLABELMT" is a more accurate message than "wrong volume". o MOUNT/FOREIGN/CLUSTER DUnxx will mount the disk locally, but fails to mount the device on other nodes in the cluster. The error message is: %MOUNT-W-RMTMNTFAIL, _$4$DUA216: failed to mount on node BEAR -MOUNT-F-CONFQUAL, conflicting qualifiers o Failure of a tape MOUNT would cause MOUNT to retry the MOUNT for 2 minutes before reporting the error to the user and OPCOM. This time is wasted under many circumstances as the drive status will not change without operator intervention. o If the /SYSTEM qualifier was not used when adding a member to an existing shadow set, that was mounted with /SYSTEM, the add appeared to be successful. It was not. The resulting behavior ranges from member copies that never happen ("0% copies") to system crashes. o Since the MOUNT96 rewrite some customers have had an issue with the extended period of time MOUNT attempts retries. When one or more members of a shadowset are offline/unavailable for mounting, a mount of that shadowset is observed to take approximately 2 minutes to complete. This leads to unacceptably long delays in system and application startup completion. o Attempting to MOUNT/SYSTEM two ISO-9660 volumes, whose volume labels are not unique in the first 12 characters, results in an "another volume of the same label already mounted" error. 8 PROBLEMS ADDRESSED IN ALPMOUN01_062 KIT o If per-disk licensing is used, MOUNT may end up in an infinite loop if this is the first mount of any shadow set and the system disk is unit 0. This problem is corrected in OpenVMS Alpha V7.0. -- COVER LETTER -- Page 6 24 February 1999 9 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_3 : To be installed by customers experiencing the problems corrected. 10 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPMOUN04_062 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. No reboot is necessary after successful installation of the kit. NOTE: After the installation, any process that attempts to do a MOUNT will fail unless a the following command is issued: $ SET COMMAND/TABLE=SYS$LIBRARY:DCLTABLES.EXE Otherwise the user should log out and then log back in. Copyright (c) Compaq Computer Corporation, 1999 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer Corporation. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.