OpenVMS VAXDRIV07_062 VAX V6.2 TUDRIVER/DUDRIVER ECO Summary
TITLE: OpenVMS VAXDRIV07_062 VAX V6.2 TUDRIVER/DUDRIVER ECO Summary
Modification Date: 05-MAY-1999
Modification Type: Updated Kit: Supersedes VAXDRIV06_062
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
Copyright (c) Compaq Computer Corporation 1997, 1999. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENTS: DUDRIVER
TUDRIVER
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXDRIV07_062
ECO Kits Superseded by This ECO Kit: VAXDRIV06_062
VAXDRIV05_062
VAXDRIV04_062
VAXDRIV02_062
VAXDRIV01_062
VAXDRIV04_070 (V6.2 Only)
VAXDRIV03_070 (V6.2 Only)
VAXDRIV02_070 (V6.2 Only)
VAXDRIV01_070 (V6.2 Only)
ECO Kit Approximate Size: 198 Blocks
Kit Applies To: OpenVMS VAX V6.2
System/Cluster Reboot Necessary: Yes
Rolling Reboot Supported: Yes
Installation Rating: INSTALL_3
3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VAXCLUSIO01_062
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for DUDRIVER and TUDRIVER on OpenVMS VAX V6.2. This
kit addresses the following problems:
The two primary deliverables in this kit are:
1. 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).
2. The ability to mount and use Fibrechannel devices from V6.2 and
V7.1 systems.
Problems addressed in VAXDRIV07_062 kit:
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 The following describes conditions that may cause crashes:
1. During a virtual circuit failover event, DUDRIVER
attempts to use the CDT of another connection, for
example, the SCS$DIRECTORY, and this results 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, a SHADDETINCON crash may ocur and the shadowset
member will be remvoed 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 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/10
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
Problems Addressed in the 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.
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.
Problems Addressed in the 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.
Problems Addressed in the 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.
Problems Addressed in the VAXDRIV02_062 Kit:
o The KITINSTAL.COM file in VAXDRIV01_062 does not check to insure
that the VAXCLUSIO01_062 is installed on the system.
Problems Addressed in the VAXDRIV01_062 Kit for OpenVMS VAX 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. VAXCLUSIO01_062 must be installed
on any VAX V6.2 system before installing this kit.
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 hang. 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 the 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.
Problems Addressed in the VAXDRIV04_070 Kit for OpenVMS VAX V6.2:
o A PGFLIPLHI system crash may occur 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 packet acknowledgment
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 hang.
Problems Addressed in the 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
Re-init Count field under SDA.
Problems Addressed in the VAXDRIV02_070 Kit for OpenVMS VAX V6.2:
o A node may hang due to no quorum after losing its connection to the
quorum disk.
o DUDRIVER does not log IRP information.
Problems Addressed in the VAXDRIV01_070 Kit for OpenVMS VAX V6.2:
o Static load balancing does not work as it designed to.
o System crashes occur in DUDRIVER, usually at FUNCTION_EXIT:.
However, the crashes may also occur in other places.
o The errorlog does not contain any information on the actual
outstanding command that has timed out from a Get Command
Status (GCS) query issued from DUDRIVER to the MSCP Server.
o Host Based Shadowset Virtual Units hang in Mount Verification.
All IO to the device is stalled.
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted.
If you have other nodes in your VMS 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 reboot may be performed.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vaxdriv07_062.README
vaxdriv07_062.CHKSUM
vaxdriv07_062.CVRLET_TXT
vaxdriv07_062.a-dcx_vaxexe
vaxdriv07_062.CVRLET_TXT
|
