|
|
HP Services Software Patches - alpshad01_070
|
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) Digital Equipment Corporation 1996. All rights reserved.
******************** WARNING! ********************
* *
* Engineering has discovered a problem with this *
* ECO kit and has requested that it be placed on *
* hold. They are currently researching the *
* problem. *
* *
****************************************************
PRODUCT: Volume Shadowing for OpenVMS (Phase II)
OP/SYS: OpenVMS Alpha V7.0
COMPONENT: Shadow Driver
Bugcheck
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ALPSHAD01_070
ECO Kits Superseded by This ECO Kit: None.
ECO Kit Approximate Size: 882 Blocks
Kit Applies To: OpenVMS Alpha V7.0
System/Cluster Reboot Necessary: Yes
ECO KIT SUMMARY:
An ECO kit exists for Volume Shadowing on OpenVMS Alpha V7.0.
This kit addresses the following problems:
o Failures occur during attempts to start copies or restart
copies, usually after a node halt, shutdown or reboot.
Additional symptoms observed include inconsistent values for
HBS_CIP when compared to SHADOW_MAX_COPY, negative values for
HBS_CIP and copies that should continue start over from the
beginning.
o If a DCD copy is interrupted by a mini-merge, the copy will
restart at 0% copied (LBN 0) rather than continuing from where
it left off. DCD copies should restart at the last copied LBN
after it was interrupted by mini-merge.
o System hangs may occur when I/Os pending to a shadow set do
not complete.
o A two member shadowset with member index 0 a copy target and
index 1 the only source member experiences a node failure on a
node serving the disks. The source member goes "available".
The source index is never packacked and the system remains with
the set hung in mount verification forever.
o UCB$L_MAXBCNT is not set up for system disks before the first
writes are enabled for that device. The attempt to issue a
write without having this field initialized results in a
SHADDETINCON bug check.
INSTALLATION NOTES:
In order for the corrections in this kit to take effect, the system
must be rebooted. If the system is a member of a VMScluster, the
entire cluster should be rebooted.
Files on this server are as follows:
|
»alpshad01_070.README
»alpshad01_070.CHKSUM
»alpshad01_070.a-dcx_axpexe
»alpshad01_070.CVRLET_CVRLET_TXT
|