ECO NUMBER: ALPDRIV21_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPDRIV21_062 2 KITS SUPERSEDED BY THIS KIT: ALPDRIV20_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: None. 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 [SYS$LDR]SYS$DUDRIVER.EXE (new image) o [SYS$LDR]SYS$TUDRIVER.EXE (new image) 5 PROBLEMS ADDRESSED IN ALPDRIV21_062 KIT o When the previous ALPDRIV20_062 kit is installed, a regression warning is issued and the SYS$DUDRIVER.EXE image is not installed. Image(s) Affected: 1. [SYS$LDR]SYS$DUDRIVER.EXE -- COVER LETTER -- Page 2 17 June 1999 2. [SYS$LDR]SYS$TUDRIVER.EXE 6 PROBLEMS ADDRESSED IN ALPDRIV20_062 KIT There are two primary deliverables in this kit: a number of backported fixes from the V7.2 stream which keeps V6.2 and V7.1 code consistent with the V7.2 release. This proactively delivers fixes that were found during V7.2 regression testing (some of these problems were also reported by customers). The second feature is the ability to mount and use Fibrechannel devices from V6.2 and V7.1 systems. o When initializing a FIBRECHANNEL (DG) device from a client, one of the two following errors is returned to the user (disk only, not tape): 1. INIT-F_DIAGPACK, disk is a diagnostic pack OR 2. INIT-W-NOBADDATA, bad block data not found on volume Note that an INIT of the same devices succeed on the server. Image(s) affected: - [SYS$LDR]SYS$DUDRIVER.EXE o This kit contains code changes that address a number of system crashes. The following describes the conditions that may cause the crashes: 1. During a virtual circuit failover event, DUDRIVER attempts to use the CDT of another connection for example the SCS$DIRECTORY, and this causes in a crash. 2. DUDRIVER will now detect that a CDRP has a zero CDRP$L_UCB field, thereby preventing a system crash. 3. A failover when a device has two paths (one served and one local) may result in a fatal MSCPCLASS bugcheck error. 4. When an MSCP server loses connection to the local MSCP device, may result in a SHADDETINCON crash and shadowset member removal from the shadow set. Image(s) affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE -- COVER LETTER -- Page 3 17 June 1999 o Potential performance problems may occur (high interrupt stack time) on low end systems in large cluster configurations, when drives go offline. Image(s) affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE o DUDRIVER/TUDRIVER device allocation class processing problems can occur, for example during failover and configuration. 1. Drives may be incorrectly configured multiple times as separate devices with the same name on different paths. 2. Invalid data structures can be seen for DUDRIVER based devices with unusual (32-bit number) ALLOCLASSes, which are not valid for any devices on the system. 3. Systems may crash upon receipt of "Duplicate Unit" MSCP messages from a HSx controller. The foot print will be an inconsistent I/O Database or ACCVIO. Image(s) affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE o The MOUNT and INIT commands can fail with an MEDOFL error. Image(s) affected: - [SYS$LDR]SYS$TUDRIVER.EXE o Incorrect byte count in IRP/IOST may occur when a forced error on a disk is encountered. Image(s) affected: - [SYS$LDR]SYS$DUDRIVER.EXE o A DCL copy command to a tape drive connected to a HSD05/10s can cause a process hang. This problem will not happen with a BACKUP command and will not happen on HSJ/HSC connected tape drives. Image(s) affected: - [SYS$LDR]SYS$TUDRIVER.EXE -- COVER LETTER -- Page 4 17 June 1999 7 PROBLEMS ADDRESSED IN ALPDRIV16_062 KIT o The ALPDRIV15_062 remedial kit required that the ALPCLUSIO01_062 kit be installed. If the user tried to install the ALPDRIV15_062 kit on a system that had both the ALPCLUSIO01_062 and OpenVMS Alpha Y2K remedial kits installed, the ALPDRIV15_062 kit did not recognize that the ALPCLUSIO01_062 kit had been installed. This caused the ALPDRIV15_062 installation to fail. There are no new ECO problem corrections in this kit. If you have installed the ALPDRIV15_062 remedial kit, you do not need to install the ALPDRIV16_062 remedial kit. 8 PROBLEMS ADDRESSED IN ALPDRIV15_062 KIT o Attempting to perform a directory of a mounted tape causes the process to hang and "INVALID COMMAND" MSCP END MSG* errorlog entries to be generated. o Unexpected end messages are logged on client nodes for GUS and AVAILABLE commands. o When SCSI disks connected to a HSxx controller are set transportable, the system crashes with a DISKCLASS bugcheck. o DUDRIVER does not FLUSH the pending queue of SHADOWING, HBR and served IOs when connection failure routines are entered. This causes a system/cluster hang. o System crashes with a KERNEL STACK INVALID Bugcheck. o A DCL copy command to a HSD05/10 based tape drive causes a process hang. o Starting with OpenVMS Alpha V7.1, the BACKUP and COPY utilities will fail with "blank check" and "end of data" errors when these utilities are used with certain newer tape drives (e.g. TLZ10) connected to HSJ or HSD controllers. 9 PROBLEMS ADDRESSED IN ALPDRIV11_062 KIT o If a customer upgraded their system to V6.2 from V6.1, the KITINSTAL.COM procedure in kits that require the ALPCLUSIO01 remedial kit to be installed first, did not properly verify that the ALPCLUSIO01_062 remedial kit had been installed. -- COVER LETTER -- Page 5 17 June 1999 10 PROBLEMS ADDRESSED IN ALPDRIV08_062 KIT o The ALPDRIV07_062 kit contained some incorrect build identifications within the images which could have prevented the images from being installed. This kit ALPDRIV08_062 contains the correct build identifications and fixes that problem. 11 PROBLEMS ADDRESSED IN ALPDRIV07_062 KIT o The following problem was also addressed in the ALPDRIV04_070 kit, but was omitted from the SYS$DUDRIVER.EXE which was shipped in the ALPCLUSIO01_062 kit. Customers must install ALPCLUSIO01_062 on any Alpha V6.2 system before installing the ALPDRIV07_062 kit. A problem exists with HSJ/HSD30,40 and 50 controllers. After some event that initiates Mount Verification, a PACKACK will fail to complete. The controller will report that it is making progress on the command, but will never finish. This causes all IO to the affected devices to be hung. The problem has been seen mostly with the ONLINE component of a PACKACK. One case of a NOP hanging has been seen. It is not known whether other IOs including Data Transfer IOs may be involved. o A 9TRK tape written with a density of 6250 is mounted on a TSZ07 tape drive. The mount completes successfully and this is followed by a DCL directory command. When a PACKACK is issued for the tape unit, the subsequent ONLINE command is issued using "stale" density information. This ONLINE command is then rejected by the controller with "INVALID COMMAND, INVALID FORMAT" errors and the process will hang. The error count then continues to increment as the driver keeps issuing the ONLINE command. In TUDRIVER routine START_PACKACK, a GUS-ONLINE-GUS sequence is issued to the tape unit. The initial GUS is skipped unless the drive is a DLT type or if the UCB$V_TU_DENS_DETERMINED bit is set in DEVSTS in the UCB. If a GUS is issued before the ONLINE command, the density gets updated and the ONLINE succeeds. o The operating system may crash with the following error: "TMSCPSERV, Fatal error detected by TMSCP server" This crash would only be seen if a MSCP served tape device requires mount verification. The actual location of the crash is at SCS$TAPE_MSCP_MV_C+00190. -- COVER LETTER -- Page 6 17 June 1999 12 PROBLEMS ADDRESSED IN ALPDRIV04_070 KIT FOR OPENVMS ALPHA V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 o A problem exists with HSJ/HSD 30, 40 and 50 controllers. After some event that initiates Mount Verification, a Pack-Ack will fail to complete. The controller will report that it is making progress on the command, but will never finish. This causes all IO to the affected devices to be hung. 13 PROBLEMS ADDRESSED IN ALPDRIV03_070 KIT FOR OPENVMS ALPHA V6.2, V6.2-1H1, V6.2-1H2 o The system experiences repetitive Volume Processing Messages on Host Based Volume Shadowing Disks. The CDDB$W_RSTRTCNT field of the member devices will be incrementing as seen in the REINIT Count field under SDA. 14 PROBLEMS ADDRESSED IN ALPDRIV02_070 KIT FOR OPENVMS ALPHA V6.2, V6.2-1H1, V6.2-1H2 o If the connection to the quorum disk is broken it can result in quorum loss for the cluster. In this case, re-establishing the connection to the quorum disk may not restore quorum for all nodes. This could result in nodes being hung waiting for quorum. 15 PROBLEMS ADDRESSED IN ALPDRIV01_070 KIT FOR OPENVMS ALPHA V6.2, V6.2-1H1, V6.2-1H2 o The CDDB$W_LOAD_AVAIL field is loaded with an incorrect value which prevents "static" load balancing working as implemented. o System crash in DUDRIVER. Usually in FUNCTION_EXIT but it may occur at other places. o The errorlog does not contain any information on the actual command that has timed out from a Get Command Status (GCS) command. o Host Based Shadowset Virtual Units hang in Mount Verification all IO to the device is stalled. -- COVER LETTER -- Page 7 17 June 1999 16 PROBLEMS ADDRESSED IN AXPDRIV01_062 KIT o For systems that are members of a VMScluster system, and that have a KFESA/KFESB EISA DSSI controller, failover of I/O traffic using the PEDRIVER (ETHERNET) to the PADRIVER (DSSI) - now works correctly. 17 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. 18 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 ALPDRIV21_062 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. The images in this kit will not take effect until the system is rebooted. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 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 -- COVER LETTER -- Page 8 17 June 1999 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.