Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS73_SHADOWING-v0300 ALPHA V7.3 SHADOWING ECO Summary
*OpenVMS] VMS73_SHADOWING-v0300 ALPHA V7.3 SHADOWING ECO Summary
Copyright (c) Compaq Computer Corporation 2001, 2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: Volume Shadowing
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS73_SHADOWING-v0300
DEC-AXPVMS-VMS73_SHADOWING-v0300--4.PCSI
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 2096 Blocks
Kit Applies To: OpenVMS Alpha V7.3
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_2
To be installed by all customers using the following feature(s):
- SHADOWING
This 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)
Kit Dependencies:
The following remedial kit(s), or later, must be installed BEFORE
installation of this , or any required kit:
VMS73_PCSI-V0100
VMS73_UPDATE-V0200
In order to receive all the corrections listed in this
kit, the following remedial kits, or later, should also be installed:
None
FILES PATCHED OR REPLACED:
o [SYSEXE]SHADOW_SERVER.EXE (new image)
Image Identification Information
image name: "SHADOW_SERVER"
image file identification: "X-13"
image file build identification: "X9UH-0060010021"
link date/time: 4-AUG-2003 15:22:15.04
linker identification: "A11-50"
o [SYS$LDR]SYS$SHDRIVER.EXE (new image)
Image Identification Information
image name: "SYS$SHDRIVER"
image file identification: "X-3"
image file build identification: "X9UH-0060010021"
link date/time: 4-AUG-2003 15:22:27.66
linker identification: "A11-50"
PROBLEMS ADDRESSED IN THIS KIT
New problems addressed in the VMS73_SHADOWING-V0300 kit
o System hang during the mounting of a shadowset.
During the mounting of a shadowset, a series of protocols
can collide such that a thread is left waiting to be
resumed and there is no thread to resume it. This can
result in a system hang.
Images Affected:[SYS$LDR]SYS$SHDRIVER.EXE
o Multi-site cluster shadowset member is returned to the
shadwoset incorrectly
In a multisite cluster with all timeouts set to the
maximum, a shadowset member is returned to the shadwoset
incorrectly. Manual removal of a member from one site,
followed by manual aborting of the virtual unit at a
second site, allowed a third site to return the member to
the shadowset without either a copy or a merge.
Images Affected:[SYS$LDR]SYS$SHDRIVER.EXE
o Ensure shadow copies handle bad blocks correctly
If a bad block is detected on the source disk during a
full copy operation, the copy will abort with the
following OPCOM message :
%%%%%%%%%%% OPCOM 10-MAY-2002 09:41:23.94 %%%%%%%%%%%
(from node UKVMS3 at 10-MAY-2002 09:41:22.46)
Message from user SYSTEM on UKVMS3
%SHADOW_SERVER-E-SSRVTRMSTS, reason for termination
of operation on device _DSA1: IVADDR, invalid media
address
The virtual unit will look like this afterwards:
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA1: Mounted 0 ALPHAE731_CD 15330438 1 1
$7$DKA100:(UKVMS3) ShadowSetMember 2 (member of DSA1:)
$7$DKA1000:(UKVMS3) ShadowCopying 0 (copy trgt DSA1:11% copied)
Note that the virtual unit will still be accessible in
this state.
Images Affected:[SYS$LDR]SYS$SHDRIVER.EXE
o Shadowset Aborts after node is shutdown
Shadowsets on the remaining node of a multi-site cluster
abort after the serving node of one member is shutdown.
Images Affected:[SYS$LDR]SYS$SHDRIVER.EXE
o Host Based Volume Shadowing (HBVS) Mini Copy Problem
When using HBVS, if Mini Copy is used to return a former
Shadow Set Member (SSM) to a virtual unit, and that SSM
is removed from the shadow set before the copy can
complete, the user must execute the following commands
before adding that SSM is added back into the shadow set:
$ SHOW DEVICE/BITMAP/FULL DSAnnnn:
$ DELETE /BITMAP x
"DSAnnnn:" is the virtual unit and "x" is the BitMap ID
displayed by the SHOW DEVICE/BITMAP/FULL command. If
multiple BitMap IDs are displayed, delete the one that
has the SSM in the Bitmap Name portion of the display.
If these steps are not taken, data integrity could be
affected.
Images Affected:[SYS$LDR]SYS$SHDRIVER.EXE
o Repair read bias calculation for multipath devices
The read performance for a multiple member shadow set,
that has multipath enabled members, has been using only
the primary UCB, not the current UCB.
Images Affected:[SYS$LDR]SYS$SHDRIVER.EXE
o Default read cost for locally remote device set to high
Default read cost for locally remote device is set to
high
Images Affected:[SYS$LDR]SYS$SHDRIVER.EXE
o INVEXCPTN Crash during shadow copy
When doing a controller assisted copy, available with HSC
and HSJ controllers, if the source member gets an error
an incorrect index is set up that results in a crash.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while
above ASTDEL
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF 80268D60
Failing PS: 30000000 00000804
Module: SYS$SHDRIVER
Offset: 0004AD60
:
Exception Frame:
R2 = FFFFFFFF 837A6380 R3 = 00000000 00000000
R4 = FFFFFFFF 839CB3C0 R5 = FFFFFFFF 83689D80
R6 = FFFFFFFF 839CB680 R7 = 00000000 00000000
PC = FFFFFFFF 80268D60 PS = 30000000 00000804
Images Affected:[SYS$LDR]SYS$SHDRIVER.EXE
INSTALLATION INSTRUCTIONS:
Installation Command
Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:
PRODUCT INSTALL VMS73_SHADOWING /SOURCE=[location of Kit]
The kit location may be a tape drive, CD, or a disk directory that
contains the kit.
Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt
Scripting of Answers to Installation Questions
During installation, this kit will ask and require user response to
several questions. If you wish to automate the installation of
this kit and avoid having to provide responses to these questions,
you must create a DCL command procedure that includes the following
definitions and commands:
- $ DEFINE/SYS NO_ASK$BACKUP TRUE
- $ DEFINE/SYS NO_ASK$REBOOT TRUE
- Add the following qualifiers to the PRODUCT INSTALL command and
add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V3.0
- De-assign the logicals assigned
For example, a sample command file to install the VMS73_SHADOWING
kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$!
$ PROD INSTALL VMS73_SHADOWING/PROD=DEC/BASE=AXPVMS/VER=V3.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
COPYRIGHT AND DISCLAIMER:
(C) Copyright 2003 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP and/or its
subsidiaries required for possession, use, or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer
Software, Computer Software Documentation, and Technical Data for
Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
Neither HP nor any of its subsidiaries shall be liable for
technical or editorial errors or omissions contained herein. The
information in this document is provided "as is" without warranty
of any kind and is subject to change without notice. The
warranties for HP products are set forth in the express limited
warranty statements accompanying such products. Nothing herein
should be construed as constituting an additional warranty.
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.
All trademarks are the property of their respective owners.
|
