ECO NUMBER: VAXDRIV07_062 PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: VAXDRIV07_062 2 KITS SUPERSEDED BY THIS KIT: VAXDRIV06_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: VAXCLUSIO01_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 VAX V6.2 4.2 Files patched or replaced: o [SYS$LDR]DUDRIVER.EXE (new image) o [SYS$LDR]TUDRIVER.EXE (new image) 5 PROBLEMS ADDRESSED IN VAXDRIV07_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. -- COVER LETTER -- Page 2 4 May 1999 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 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. -- COVER LETTER -- Page 3 4 May 1999 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 inconsistant 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 6 PROBLEMS ADDRESSED IN VAXDRIV06_062 KIT o The VAXDRIV05_062 remedial kit required that the VAXCLUSIO01_062 kit be installed. If the user tried to install the VAXDRIV05_062 kit on a system that had both the VAXCLUSIO01_062 and OpenVMS VAX Y2K remedial kits installed, the VAXDRIV05_062 kit did not recognize that the VAXCLUSIO01_062 kit had been installed. This caused the VAXDRIV05_062 installation to fail. -- COVER LETTER -- Page 4 4 May 1999 There are no new ECO problem corrections in this kit. If you have installed the VAXDRIV05_062 remedial kit, you do not need to install the VAXDRIV06_062 remedial kit. 7 PROBLEMS ADDRESSED IN VAXDRIV05_062 KIT 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 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. 8 PROBLEMS ADDRESSED IN VAXDRIV04_062 KIT o If a customer upgraded their system to V6.2 from V6.1, the KITINSTAL.COM procedure, in kits that require the VAXCLUSIO01 remedial kit to be installed first, did not properly verify that the VAXCLUSIO01_062 remedial kit had been installed. 9 PROBLEMS ADDRESSED IN VAXDRIV02_062 KIT o Kitinstal missing check for VAXCLUSIO01_062 for OpenVMS VAX V6.2 systems only. 10 PROBLEMS ADDRESSED IN VAXDRIV01_062 KIT FOR OPENVMS V6.2 o The following problem was also addressed in the VAXDRIV04_070 kit, but was omitted from the DUDRIVER.EXE which was shipped in the VAXCLUSIO01_062 kit. Customers must install VAXCLUSIO01_062 on any VAX V6.2 system before installing this kit. -- COVER LETTER -- Page 5 4 May 1999 A problem exists with HSJ/HSD30,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. The problem has been seen mostly with the ONLINE component of a Pack-Ack. 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 Pack-Ack 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. 11 PROBLEMS ADDRESSED IN VAXDRIV04_070 KIT FOR OPENVMS VAX V6.2 o PGFIPLHI crash when the controller is rebooted. o A problem exists with HSJ/HSD30,40 and 50 controllers where, after an 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. 12 PROBLEMS ADDRESSED IN VAXDRIV03_070 KIT FOR OPENVMS VAX V6.2 o The system will get 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. -- COVER LETTER -- Page 6 4 May 1999 13 PROBLEMS ADDRESSED IN VAXDRIV02_070 KIT FOR OPENVMS VAX V6.2 o A node hangs because of no quorum after losing connection to the quorum disk. o DUDRIVER does not log IRP information. 14 PROBLEMS ADDRESSED IN VAXDRIV01_070 KIT FOR OPENVMS VAX V6.2 o The CDDB$W_LOAD_AVAIL field is loaded with an incorrect value which prevents "static" load balancing from working as implemented. o System crash in DUDRIVER usually in FUNCTION_EXIT: but 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. 15 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. 16 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 VAXDRIV07_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. -- COVER LETTER -- Page 7 4 May 1999 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 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.