Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS72_SHADOWING-V0100 Alpha V7.2 Shadowing ECO Summary
Copyright (c) Compaq Computer Corporation 2000. All rights reserved.
Modification Date: 26-JAN-2000
Modification Type: New Kit VMS72_SHADOWING-V0100
PRODUCT: OpenVMS Alpha
COMPONENT: Shadow Driver and Shadow Server
SYS$SHDRIVER.EXE
SHADOW_SERVER.EXE
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS72_SHADOWING-V0100
DEC-AXPVMS-VMS72_SHADOWING-V0100--4.PCSI
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 1968 Blocks
Kit Applies To: OpenVMS Alpha V7.2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_2
2 - To be installed on all systems running
the listed version(s) of OpenVMS and
using the following feature(s):
SHADOWING
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VMS72_UPDATE-V0200
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 Volume Shadowing on OpenVMS Alpha V7.2
This kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS72_SHADOWING-V0100 KIT
o There is An XQP crash in MOVEFILE when a compare error occurs
on a file header, while a disk that is shadow copying is also
being defragged with DFO.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
o When a copy operation that interrupts a merge operation is
terminating, it finds that there are no members marked for the
merge and the thread crashes the system with a SHADDETINCON bug
check.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
o SHOW DEVICES shows zero percent merged status although the
shadow set status does not indicate that a merge is required.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
o Bit 16 in SHADOW_SYS_DISK can be set by the user to eliminate
using remote members of the shadowset for reads. Occasionally,
use of bit 16 fails to eliminate remote members from being
used.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
o A CPUSPINWAIT bug check can occur, if the read of the SCB, of a
shadow set member, cannot pass the checksum test.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
o DCD (Disk Copy Data) will not always be initiated properly.
During an assisted copy operation, if the source member was
dismounted or otherwise removed from the shadow set, the
connection to the controller would not clean up correctly.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
o A full copy operation that is interrupted for a mini-merge will
not complete the full copy operation correctly.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
o Typing incorrect commands results in a system crash
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
o When two disks are added to a shadowset in the same mount
command, the copies are done sequentially instead of in
parallel. This causes the copies to take twice as long as they
should.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
- [SYSEXE]SHADOW_SERVER.EXE
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database(s). To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'SHADOWING' or 'VMS72_SHADOWING-V0100'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, 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.
All trademarks are the property of their respective owners.
|