|
|
OpenVMS VMS712_SHADOWING-V0500 Alpha V7.1-2 Shadowing ECO Summary
|
TITLE: OpenVMS VMS712_SHADOWING-V0500 Alpha V7.1-2 Shadowing ECO Summary
New Kit Date: 25-JAN-2002
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VMS712_SHADOWING-V0400
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
For OpenVMS savesets, the name of the compressed saveset
file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
saveset is copied to your system, expand the compressed
saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
For PCSI files, once the PCSI file is copied to your system,
rename the PCSI file to kitname.pcsi-dcx_axpexe, then it can
be expanded by typing RUN kitname.pcsi-dcx_axpexe. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 2000, 2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: Volume Shadowing
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS712_SHADOWING-V0500
DEC-AXPVMS-VMS712_SHADOWING-V0500--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS712_SHADOWING-V0400
ECO Kit Approximate Size: 2048 Blocks
Kit Applies To: OpenVMS Alpha V7.1-2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
1 - To be installed by all customers.
Kit Dependencies:
The following remedial kit(s), or later, must be installed BEFORE
installation of this, or any required kit:
VMS712_UPDATE-V0300
VMS62TO71U2_PCSI-V0200
In order to receive all the corrections listed in this
kit, the following remedial kits, or later, should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for Shadowing on OpenVMS Alpha V7.1-2. This kit
addresses the following problems:
PROBLEMS ADDRESSED IN VMS712_SHADOWING-V0500 KIT:
o An 'Operation incomplete" error can cause a host-based raidset
to hang.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o A SHADDETINCON bugcheck occurs in routine SHLK$MERGE_SIGNAL.
Crashdump Summary Information:
------------------------------
Bugcheck Type: SHADDETINCON, SHADOWING detects inconsistent
state
Current Process: CTM$_00060006
Current Image: [CTM_HAMMER]CTM_HAMMER_ALPHA_32.EXE
Failing PC: FFFFFFFF.804A1CD4
SYS$SHDRIVER+93CD4
Failing PS: 14000000.00000804
Module: SYS$SHDRIVER
(Link Date/Time: 15-DEC-2000 15:08:57.95)
Offset: 00093CD4
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o The mini copy operation will occasionally abort with an
%SYSTEM-F-IVADDR.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o A crash occurs with SHADDETINCON in SYS$SHDRIVER + 000762A0.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o Two nodes in the cluster each remove a different member of a
shadowset at the same time. Node A removes member 1 and
thinks it has a single member set with member 2. At the same
time, Node B removes member 2 and thinks it has a single
member set with member 1. The removals actually occur one
after the other, but Node A and Node B are unaware that that
is happening simultaneously. As a result, Node A thinks there
is a single member in the set and it is member 1, but node A
no longer has member 1, so it crashes.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o If the device is unable to perform a read SCB, the
/POLICY=MINICOPY command will fail.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o Multiple systems may hang on cluster shutdown because a
deadlock occurs when the WATCHER node closes.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o A SHADDETINCON bugcheck occurs in EXPEL_DEVICE.
Crashdump Summary Information:
------------------------------
Bugcheck Type: SHADDETINCON, SHADOWING detects inconsistent state
Current Process: NULL
Current Image:
Failing PC: FFFFFFFF.8047BC38 SYS$SHDRIVER+83C38
Failing PS: 34000000.00000804
Module: SYS$SHDRIVER
(Link Date/Time: 30-MAR-2001 09:09:47.85)
Offset: 00083C38
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o If system check is enabled, the first MOUNT of the system disk
or a shadow set will crash the system.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o The first MOUNT of a system disk will crash, if SYSGEN
system_check is enabled.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o A system can experience many MountVerifcation messages occur
with no apparent cause and no errors reported. There is no
way to identify what is causing these messages
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o In a multi-node cluster, some cluster members may hang when
accessing a shadowset if:
o The shadowset being accessed has multiple members.
o All the shadowset members are local to one of the cluster
nodes.
o All the shadowset members are being MSCP-served by the
local node to the other cluster members.
o The local node goes down and remains down for at least
MVTIMEOUT seconds.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o On multiple member shadow sets greater than 18 Gigabyte in
size, if the port driver returns an SS$_DATACHECK for a
IO$_WRITEPBLK, the wrong LBNs will be written by the shadowing
driver. This could lead to data corruption.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o On a stand alone system, when a virtual unit aborts, the
system could crash with an INVEXCEPTN bugcheck.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o OPCOM will frequently display a virtual unit device, or the
member device string, without any other message. This can be
seen during startup if you are using a shadowed system disk,
or even during the dismount of the virtual unit or the
dismount of members.
This has been corrected so that you now will receive a
complete VMS message, such as:
%SHADOW-I-VOLPROC, DSA719: shadow master has changed.
Dump file WILL be written if system crashes.
rather than just displaying:
DSA719:
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
Problems Addressed VMS712_SHADOWING-V0400:
o Increase the merge factor for shadowing from 1,000 to 10,000.
This change also displays the merge factor only during an
actual merge operation.
Images Affected: [SYSEXE]SHADOW_SERVER.EXE
o An INVEXCPETN crash occurs in SHIN$RESTORE_WLE_ENTRY when a
write completes to a multi-member shadow set.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o An "Incompatible Shadow Set Member" (SS$_INCSHAMEM) error
message displays.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o A SHADDETICON error occurs after removing or adding a shadow
set member.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o Removal of the master shadow set member may cause data
corruption.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o When a path to a device is lost during a write operation, the
SCB (system control block) can contain a stale master member
index value. This will cause the system to crash.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o A system crash occurs on a cluster node when a SS$_VALNOTVALID
error occurs in MERGE_SIGNAL on another cluster.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o Add changes to SHADDEF.SDL to support per member FibreChannel
features.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
Problems addressed in VMS712_SHADOWING-V0300:
o The VMS712_SHADOWING-V0200 kit documentation contained an
incorrect kit name for the dependent PCSI kit. This
incorrect name also appeared in kit installation messages.
This lead to user confusion regarding what dependent kits
needed to be installed prior to installing the VMS712_SHADOWING
kit.
This kit corrects the above documentation error. Functionally,
it is the same as the previous SHADOWING kit, VMS712_SHADOWING-V0200.
If you have installed the VMS712_SHADOWING-V0200 kit, you do not
need to install the VMS712_SHADOWING-V0300 kit.
Problems addressed in VMS712_SHADOWING-V0200:
o Multipath secondary UCBs cannot be shadow set members. The
multipath disk would be immediately removed from the shadow
set and an OPCOM message would be issued. Since MOUNT retries
this operation a number of times, even with /NOASSIST, the
failure would be repeated a number of times.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o Disabling a FibreChannel cascade connection corrupts a
shadowset member. When the cascade connection is broken,
two nodes can only see their local FC device. They enter
Mountverifaction. One node will throw out its remote member
and continue using the last member. The other node will then
throw out its remote member, i.e., the disk that has just been
used by the first node. This causes the first node to have
zero members and the second node continues with a member that
did not get the last set of writes.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o Disabling a FibreChannel cascade connection results in an
INVEXCPTN crash.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o SHADOWSET goes MOUNTVERIFYTIMEOUT and cannot be remounted.
The process attempting the remount hangs.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
o The Master Member SCB hangs until MVTIMEOUT expires.
Images Affected: [SYS$LDR]SYS$SHDRIVER.EXE
Problems addressed in VMS712_SHADOWING-V0100:
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
INSTALLATION NOTES:
This kit requires a system reboot. Compaq strongly recommends that
a reboot is performed immediately after kit installation to avoid
system instability
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.
INSTALLATION INSTRUCTIONS:
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 VMS712_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
SPECIAL INSTALLATION INSTRUCTIONS:
o 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=V5.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS712_SHADOWING-V0500 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$!
$ PROD INSTALL VMS712_SHADOWING/PROD=DEC/BASE=AXPVMS/VER=V5.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
All trademarks are the property of their respective owners.
Files on this server are as follows:
|
»dec-axpvms-vms712_shadowing-v0500--4.README
»dec-axpvms-vms712_shadowing-v0500--4.CHKSUM
»dec-axpvms-vms712_shadowing-v0500--4.pcsi-dcx_axpexe
»vms712_shadowing-v0500.CVRLET_TXT
|