Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXSHAD10_071 OpenVMS VAX V7.1 Volume Shadowing ECO Summary
*OpenVMS] VAXSHAD10_071 OpenVMS VAX V7.1 Volume Shadowing ECO Summary
New Kit Date: 14-NOV-2002
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2001,2002. All rights reserved.
PRODUCT: Volume Shadowing for OpenVMS
OP/SYS: OpenVMS VAX
COMPONENT: Shadow Driver
Shadow Server
DCL
Show
System Dump Analyzer (SDA)
Initialize
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXSHAD10_071
ECO Kits Superseded by This ECO Kit: VAXSHAD09_071
ECO Kit Approximate Size: 2322 Blocks
Kit Applies To: OpenVMS VAX V7.1
System/Cluster Reboot Necessary: Yes
Rolling Reboot Supported: Yes
Installation Rating: INSTALL_2
2 - To be installed by all customers using the following
feature(s):
SHADOWING
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
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 VAX V7.1.This kit addresses the following
problems:
PROBLEMS ADDRESSED IN VAXSHAD10_071 KIT
o The VAXSHAD09_071 ECO kit contained a SYSINIT.EXE image that
was from an earlier build then the image in the VAXSHAD08_071
kit. This caused installation warning messages during
installation of the VAXSHAD09_071 kit. The VAXSHAD09_071 kit
should have contained the same image as the VAXSHAD08_071 kit.
Images Affected:[SYSEXE]SYSINIT.EXE
PROBLEMS ADDRESSED IN VAXSHAD09_071 KIT
o A Host Based Raidset can hang when one member of a shadowset
encounters an Operation Incomplete error.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o A system can crash with a SHADDETINCON bugcheck at
SHDRIVER+93CD4
Crashdump Summary Information:
------------------------------
Bugcheck Type: SHADDETINCON, SHADOWING detects
inconsistent state
Current Process: CTM$_00060006
Current Image: $1$DGA5014:[CTM$TMROOT.]
[CTM_HAMMER]CTM_HAMMER_ALPHA_32.EXE;1
Failing PC: FFFFFFFF.804A1CD4 SHDRIVER+93CD4
Failing PS: 14000000.00000804
Module: SHDRIVER
(Link Date/Time: 15-DEC-2000 15:08:57.95)
Offset: 00093CD4
Images Affected:[SYS$LDR]SHDRIVER.EXE
o A mini copy operation aborts with a %SYSTEM-F-IVADDR error
message.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o A system crash occurs with SHADDETINCON in SHDRIVER +
000762A0.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o A system crash can occur with SHADDETINCON in the WATCHER node
when a master member identifies that an IN_SET lock value
block is not a member of the set on the WATCHER node.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o A mini copy /POLICY=MINICOPY operation can occasionally fail.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o Multiple systems can hang on cluster shutdown.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o A system disk MVTIMEOUT is not managed correctly.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o A system crash occurs with SHADDETINCON in EXPEL_DEVICE when
membership event status cannot be determined in
end_mbr_change_vp.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o If SYSGEN system check is enabled, the first MOUNT of a system
disk will crash the system.
Images Affected:[SYS$LDR]SHDRIVER.EXE
o Mount verification messages can occur with no apparent cause.
There is no way to identify what is causing these messages
Images Affected:[SYS$LDR]SHDRIVER.EXE
PROBLEMS ADDRESSED IN VAXSHAD08_071 KIT:
o Correction for DCL SHOW display errors.
After the VAXSHAD07_071 kit has been installed, a user-mode
ACCVIO or formatting display errors may occur with various DCL
SHOWs (e.g., SHOW DEVICE, SHOW MEMORY,SHOW TERMINAL, SHOW WORK,
SHOW NET).
Images Affected: [SYSMSG]CLIUTLMSG.EXE
Problems Addressed in the VAXSHAD07_071:
o The Master Member SCB hangs until MVTIMEOUT expires.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o If one of the existing members of the system disk shadow set
cannot be found, a lock status race condition could occur.
Images Affected: [SYS$LDR]SHDRIVER.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]SHDRIVER.EXE
o An "Incompatible shadow set member" (SS$_INCSHAMEM) error
message displays.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o A SHADDETICON error displays after removing or adding a
shadowset member.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o Under certain circumstances during a full copy operation, the
removal of the master member can cause data corruption.
Images Affected: [SYS$LDR]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]SHDRIVER.EXE
o A system crash occurs on a cluster node in SHLK$MERGE_SIGNAL
when another cluster node holding MRGVAL lock either crashes
or is shut down.
Images Affected: [SYS$LDR]SHDRIVER.EXE
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
Problems Addressed in VAXSHAD06_071:
o SHADOWSET goes MOUNTVERIFYTIMEOUT and cannot be remounted.
The process attempting the mount hangs.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o After entering an incorrect command involving a shadowset, the
system crashes with SHADDETINCON.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o Disabling a FibreChannel cascade connection results in a
system crash.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o Disabling a FibreChannel cascade connection results a
corruption of a shadowset member.
Images Affected: [SYS$LDR]SHDRIVER.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]SHDRIVER.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]SHDRIVER.EXE
o DCD (Disk Copy Data) will not always be initiated properly.
During an assisted 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]SHDRIVER.EXE
o A full copy operation that is interrupted by a mini merge may
not be completed correctly.
Images Affected: [SYS$LDR]SHDRIVER.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]SHDRIVER.EXE
o SHOW DEVICES shows zero percent merged status, even though the
shadow set status does not indicate that a merge is required.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o INCSHAMEM tracing is not enabled.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o Use of bit 16 in SHADOW_SYS_DISK bias reads of the local
source shadow set member does not always work.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o When all members of the system disk shadowset are configured,
if the boot device has gone off line, SCB reads fail with dev
off line errors. This causes the system to crash with
SHADBOOTFAIL.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o When one or more shadowset members is in a copy state, the
system may with an INVEXCPTN bugcheck.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o System crash in XQP when an IO gets a SS$_DATACHECK during a
Shadowset copy operation.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o System can crash with a SHADDETINCON bugcheck.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o Incomplete SDA displays for DSA devices.
Images Affected: [SYSEXE]SDA.EXE
o While trying to form a multimember shadowed system disk, if
something happens which causes the boot device to go offline,
then during re-boot, the system times out as though the second
shadow set member can not be found and the crashes with a
SHADBOOTFAIL bugcheck.
Images Affected: [SYS$LDR]SHDRIVER.EXE
o There may be an inconsistent display of the output from a SHOW
DEVICE/SERVED command if a SET DEVICE/SERVED command is issued
at the same time. Also a system crash could occur if queues
are updated while SHOW DEVICE/SERVED code is traversing the
queues at an elevated IPL and the update causes an access
violation or pagefault.
Images Affected: [CLIUTL]SHOW.EXE
Problems Addressed in the VAXSHAD05_071 Kit:
o Functionality was added to enable customers to shadow devices
that report an identical number of "Total Blocks".
In the past, Sectors per track, Tracks per cylinder, and Total
cylinders had to be identical, but the requirement is no
longer needed.
For example:
$ SHOW DEVICES/FULL $84$DKC200:
Disk $84$DKC200: (CSG84), device type RZ74, is online,
mounted, file-oriented device, shareable, served to a cluster
via MSCP Server, error logging enabled.
Error count 1 Operations completed 28293
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 137 Default buffer size 512
Total blocks 6976375 Sectors per track 91
Total cylinders 3067 Tracks per cylinder 25
$ SHOW DEVICES/FULL $84$MDA1200:
Disk $84$MDA1200: (CSG84), device type RAM Disk, is online,
allocated, deallocate on dismount, mounted, file-oriented
device, shareable, served to cluster via MSCP Server.
Error count 0 Operations completed 420
Owner process "username" Owner UIC [SYSTEM]
Owner process ID 4260041B Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 2 Default buffer size 512
Total blocks 6976375 Sectors per track 64
Total cylinders 3407 Tracks per cylinder 32
Allocation class 84
These two devices can be members of the same shadow set.
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA8400: Mounted 0 CSG84_V71 56308 319 1
$84$DKC200:(CSG84) ShadowSetMember 0 (member of DSA8400:)
$84$MDA1200:(CSG84) ShadowCopying 0 (copy trgt DSA8400: 2% copied)
USERNAME_CSG84 ...
o Faster I/O subsystems, for example the HSZ50 and the HSZ70,
were taking longer to perform full merges than some older and
slower subsystems.
Changes were made to allow the System Manager to adjust
thresholds. Two new logicals were adjusted to vary the merge
multiplication factor used for a virtual unit, on a per node
basis.
The logicals used must be defined in the system table and
therefore should be defined on each node in the cluster. The
valid range for a threshold is 100 to 1000. Any value outside
of this range causes a factor to default to 200. This value
of 200 is displayed at the start of a shadow set merge, in the
'%SHADOW_SERVER-I-SSRVINIMRG' message, following the word
'Factor'.
CAUTION:
Increasing the values excessively may cause application
performance problems when merges are occurring. When setting
values, System Managers must balance the site specific
application needs with their merge requirements.
Since two logical names are evaluated every one thousand I/Os,
the factor can possibly be adjusted while a merge is in
progress.
The first logical name is:
SHAD$MERGE_DELAY_FACTOR_DSAnnnn
^^^^
||||
vvvv
This logical name is virtual unit specific, with 'nnnn'
representing the virtual unit number. This delay factor will
be applied to the virtual unit only. If any important disks
need to be merged with minimal disruption, values as high
as 1,000% (threshold = 10 times best time) may be defined. By
the same token, if a particular disk's merge operation is
interfering with application I/O, it can cause the disk to
delay more frequently by reducing the value as low as:
100 (threshold = 1 times the best time)
If the above logical is not defined, then the following
logical is evaluated:
SHAD$MERGE_DELAY_FACTOR
Like the virtual unit specific logical, this value will adjust
the threshold, but only for all shadow sets that do not have a
virtual unit specific logical defined.
o Additional tracing code was added to help diagnose why mini
merge operations were converted to full merge.
o If a VMScluster that has more than 96 nodes crashes, then
write logging is never used to recover the virtual unit. The
result is unnecessary full merge operations.
o If a shadow set exists on multiple nodes in a qcluster and one
cluster member adds a device which cannot be accessed by
other nodes in the cluster, then those nodes will crash with
an INVEXCEPTN in the SHDriver within SHSB$MATCH_MASTER_SCB.
When calling SHSB$AVAILABLE_SHADOW_SET, the call to log an
error packet resulted in an overwritten register (R0) and then
a system crash occurred.
An example of a crash footprint is:
Crash Time: 28-OCT-1998 12:47:46.03
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Node: ATOZ (Clustered)
CPU Type: AlphaServer 8400 Model EV56/440
VMS Version: V6.2-1H3
Current Process: ATOZ_1
Current Image: DSA1111:<GBASE.>[RUN]GEM.EXE
Failing PC: FFFFFFF8026E454
Failing PS: 34000000 00000804
Module: SYS$SHDRIVER
Offset: 0003E454
Boot Time: 25-OCT-1998 18:51:50.00
o A Virtual Unit can hang and then no further use of the virtual
unit is possible. If the System Dump Analyzer (SDA) is used
to examine the virtual unit, then a negative value will be
found in UCB$W_RWAITCNT.
o Repeating mini merges or full merges can occur immediately
after the successful completion of a previous mini merge or
full merge on a virtual unit.
o During a system shutdown, two possible scenarios could occur:
1. Other nodes that have the system disk virtual unit MOUNTed
may suspend use of that virtual unit, until the node
running shutdown is stopped.
2. When a system disk that is disabled for write logging is
mounted on several nodes in a cluster, a non-system disk
volume aCCESS qto that virtual unit in the cluster may
suspend, until the node running shutdown is stopped.
o During a system reboot, the rebooting node may intermittently
hang if write logging is concurrently enabled on the system
disk and on other nodes in the cluster.
o Since a virtual unit can be aborted for several reasons,
additional tracing is needed to differentiate why the virtual
units abort.
Problems Addressed in the VAXSHAD04_071 Kit:
o When shutting down a node in a VMScluster, the system that is
being used to perform the shutdown will crash.
o Shadowsets intermittently hang.
o A new informational message has been added that will result in
a Mount verify message if the IO$_DIAGNOSE function is
executed by the SHDRIVER.
o Additional code changes to improve the error log reporting for
Volume Shadowing.
o The Volume Shadowing code in OpenVMS V7.1 (and V6.2, with the
CLUSIO kit installed) included a new algorithm that did not
always guarantee that read requests would be serviced by a
locally connected disk in preference to a disk that was MSCP
served by another OpenVMS system. Prior to V7.1 (and V6.2
with the CLUSIO kit installed), if there were local and MSCP
served disks to choose from, all read requests were always
queued to a local disk, unless the queue depth exceeded
twenty, on the local member.
Some customers, especially those who shadow over FDDI reported
that this new algorithm was not preferable, and therefore
requested the ability to choose the previous behavior.
The ability to prefer that read requests be performed by local
shadow set members, over those served by an OpenVMS system has
been added to this version of the driver. To select that mode
of operation another bit(16) in SHADOW_SYS_DISK has been used.
$ MC SYSGEN
SYSGEN> SHOW SHADOW_SYS_DISK
Parameter Name Current Default Min. Max.
-------------- ------- ------- ------- -------
SHADOW_SYS_DISK 1 0 0 -1
SYSGEN> SET SHADOW_SYS_DISK %X10001
SYSGEN> WRITE CURRENT
SYSGEN> WRITE ACTIVE
SYSGEN> EXIT
Problems Addressed in the VAXSHAD02_071 Kit:
o A system crash may occur with SHADDETINCON bugcheck at
SHDRIVER+12124 during boot from a multi-member shadow set.
This occurs if the booting member is not the first in the
member array, and the other member is not yet visible.
o SHADDETINCON bugchecks occur on multiple nodes in cluster
during a merge operation.
System crash information
------------------------
Time of system crash: 13-APR-1997 13:21:05.59
Version of system: OpenVMS (TM) VAX Version V6.2
System Version Major ID/Minor ID: 1/0
VAXcluster node: CYV7KE, a VAX 7000-760
Crash CPU ID/Primary CPU ID: 00/00
Bitmask of CPUs active/available: 0000003F/0000003F
CPU 00 reason for Bugcheck: SHADDETINCON, SHADOWING detects
inconsistent state
Process currently executing on this CPU: None
Current IPL: 8 (decimal)
CPU database address: C9212000
MPB address: B29B09C0
CPU 00 Processor stack
General registers:
R0 = 00000000 R1 = B67D258C R2 = B67D2180 R3 = B6544600
R4 = B35992C0 R5 = B624A340 R6 = B65447C8 R7 = 00000000
R8 = B67D2180 R9 = B6544730 R10 = 00000000 R11 = B6544600
AP = B65446B8 FP = 7FE2534C SP = C9213DAC PC = B82E42B3
PSL = 04080000
Processor registers:
P0BR = C9946800 SBR = 1EF80400 ASTLVL = 00000004
P0LR = 0000018B SLR = 003FFF00 SISR = 00000010
P1BR = C9216400 PCBB = 7F7B0020 ICCS = 00000000
P1LR = 001FF116 SCBB = 1EF5F000 SID = 17000201
LDEV = 00018002 LBER = 00000000 LCNR = 00000001
LCON0 = DF0007ED LCON1 = 00000000 TODR = 44D09B64
LBECR0 = 0040003A LBECR1 = 00008060 LMODE = 000332A4
LMERR = 00000000 BIU_STAT = F00E1070 BIU_ADDR = 00000298
MMESTS = 10004005 TBSTS = 800001D0 PCSTS = FFFFF800
ISP = C9213DAC
KSP = 7FFE7800
ESP = 7FFE9800
SSP = 7FFED800
USP = 7FE2534C
o System crashes may occur in SHADDETINCON SYS$SHDRIVER+3D3C0.
Bugcheck Type: SHADDETINCON, SHA RBADC2 (Clustered)
CPU Type: AlphaServer 2100 4/233
VMS Version: V6.2-1H2
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF 8025B3C0
Failing PS: 08000000 00000804
Module: SYS$SHDRIVER
Offset: 0003D3C0
Boot Time: 15-APR-1997 08:39:31.00
System Uptime: 5 22:23
Crash/Primary CPU: 00/00
Saved Processes: 22
Pagesize: 8 KByte (8192 bytes)
Physical Memory: 256 MByte (32768 PFNs)
Dumpfile Pagelets: 184518 blocks
Dump Flags: olddump,writecomp,errlogcomp,dump_style
EXE$GL_FLAGS: poolpging,init,bugdump
Stack Pointers:
KSP = FFFFFFFF 8A731D88 ESP = FFFFFFFF 8A733000 SSP = FFFFFFFF
8A72D000
USP = FFFFFFFF 8A72D000
General Registers:
R0 = 00000000 00000001 R1 = FFFFFFFF 8162F7E0 R2 = FFFFFFFF
8162F7C0
R3 = FFFFFFFF 8186EBC0 R4 = 00000000 00000003 R5 = FFFFFFFF
8162F890
R6 = FFFFFFFF 8186EE80 R7 = 00000000 00000000 R8 = FFFFFFFF
8162F7C0
R9 = FFFFFFFF 8186EDE8 R10 = 00000000 00000000 R11 = FFFFFFFF
8186EBC0
R12 = FFFFFFFF 8186ED38 R13 = FFFFFFFF 8710A270 R14 = FFFFFFFF
87084200
R15 = 00000000 003C60E0 R16 = 00000000 000008B4 R17 = 00000000
00000501
R18 = 00000000 00000000 R19 = FFFFFFFF 87084200 R20 = 00000000
00000000
R21 = FFFFFFFF 8162F808 R22 = FFFFFFFF 8710FB20 R23 = 00000000
00000000
R24 = 00000000 00000001 AI = 00000000 00000001 RA = FFFFFFFF
80288928
PV = FFFFFFFF 8710A698 R28 = 00000000 00000000 FP = FFFFFFFF
8A731DE0
PC = FFFFFFFF 8025B3C4 PS = 08000000 00000804
System Registers:
Page Table Base Register (PTBR) 00000000
00007FF8
Processor Base Register (PRBR) FFFFFFFF
8110A000
Privileged Context Block Base (PCBB) 00000000
0110A080
System Control Block Base (SCBB) 00000000
000001B3
Software Interrupt Summary Register (SISR) 00000000
00000000
Address Space Number (ASN) 00000000
00000000
AST Summary / AST Enable (ASTSR_ASTEN) 00000000
00000000
Floating-Point Enable (FEN) 00000000
00000000
Interrupt Priority Level (IPL) 00000000
00000008
Machine Check Error Summary (MCES) 00000000
00000000
Virtual Page Table Base Register (VPTB) 00000002
00000000
Failing Instruction:
SYS$SHDRIVER_NPRO+393C0: BUGCHK
Instruction Stream (last 20 instructions):
SYS$SHDRIVER_NPRO+39370: RET R31,(R28)
SYS$SHDRIVER_NPRO+39374: LDQ_U R31,(SP)
SYS$SHDRIVER_NPRO+39378: SUBQ SP,#X10,SP
SYS$SHDRIVER_NPRO+3937C: STQ R16,#X0008(SP)
SYS$SHDRIVER_NPRO+39380: STQ R17,(SP)
SYS$SHDRIVER_NPRO+39384: LDQ R17,#XF8E0(R13)
SYS$SHDRIVER_NPRO+39388: BIS R17,#X04,R17
SYS$SHDRIVER_NPRO+3938C: BIS R31,R17,R16
SYS$SHDRIVER_NPRO+39390: LDQ R17,(SP)
SYS$SHDRIVER_NPRO+39394: ADDQ SP,#X08,SP
SYS$SHDRIVER_NPRO+39398: BUGCHK
SYS$SHDRIVER_NPRO+3939C: HALT
SYS$SHDRIVER_NPRO+393A0: SUBQ SP,#X10,SP
SYS$SHDRIVER_NPRO+393A4: STQ R16,#X0008(SP)
SYS$SHDRIVER_NPRO+393A8: STQ R17,(SP)
SYS$SHDRIVER_NPRO+393AC: LDQ R17,#XF8E0(R13)
SYS$SHDRIVER_NPRO+393B0: BIS R17,#X04,R17
SYS$SHDRIVER_NPRO+393B4: BIS R31,R17,R16
SYS$SHDRIVER_NPRO+393B8: LDQ R17,(SP)
SYS$SHDRIVER_NPRO+393BC: ADDQ SP,#X08,SP
SYS$SHDRIVER_NPRO+393C0: BUGCHK
SYS$SHDRIVER_NPRO+393C4: HALT
SYS$SHDRIVER_NPRO+393C8: BIS R31,R31,R31
SYS$SHDRIVER_NPRO+393CC: BIS R31,R31,R31
SYS$SHDRIVER_NPRO+393D0: SUBQ SP,#X50,SP
o The Volume Shadowing software which was shipped in OpenVMS
Alpha and VAX V7.1 and the CLUSIO remedial kits, requires
additional non-paged pool to improve synchronization.
Customers should take this into account when they are tuning
their systems, and be aware that Volume Shadowing is now more
sensitive to resource problems with the possibility that
systems may crash if non-paged pool is exhausted.
Shadowing uses approximately 800 bytes of additional non-paged
pool per concurrent IO to the virtual unit. This remedial kit
includes codes which avoids system crashes if a system exhausts
non-paged pool.
Please be aware that there are still cases under which
Non-Paged Pool exhaustion will result in a SHADDETINCON
bugcheck. This modification reduces the probability but
does not completely eliminate them.
o During internal testing, a system crash occurred which indicated
that IOs were left outstanding in DUDRIVER after a virtual unit
had been removed.
o There is a missing index on a check for member valid in the
BBR_READ_RECOVERY routine.
o There is an "infinite" loop condition at SHCP$START_QUED, and
the code has been modified so that the persistent thread will
be "killed" if the VU it has spawned fails.
o This remedial kit includes additional error logging
capabilities to collect additional information when a virtual
unit is made available.
The new LOG_IT macro code has the following input parameters:
o R0 - value of P4
o R1 - value of P5
o R2 - address of LW in SHAD containing P6
o R3 - VU UCB
o R5 - SHAD IRP address with:
- CDRP$L_BCNT = P1
- CDRP$L_MEDIA = P2
- CDRP$L_PID = P3
The implementation makes use of the following cells in the
errorlog record.
o EMB$W_SP_BOFF - set to %xBADE as TAG
o EMB$W_SP_FUNC - reason code
o EMB$L_SP_BCNT - LW for information
o EMB$L_SP_MEDIA - LW for information
o EMB$L_SP_RQPID - LW for information
o EMB$Q_SP_IOSB - 2 LW for information
o EMB$L_SP_CMDREF - LW for Information
o A process may intermittently hang during the dismount of a
shadow-set while waiting for completion of the QIOW in DO_IO
routine.
o A KRNLSTAKNV halt may occur during MOUNT/CLUSTER DSAx:
Bugcheck Type: CPUSANITY, CPU sanity timer expired
Node: AI84 (Clustered)
CPU Type: AlphaServer 8400 Model EV56/440
VMS Version: V6.2-1H3
Current Process: PM2SKZ
Current Image: DSA40:[ZENT410.][EXE]BUS.EXE
Failing PC: FFFFFFFF 8001F8D0
Failing PS: 18000000 00001604
Module: SYSTEM_PRIMITIVES_MIN
Offset: 0000B8D0
Boot Time: 26-JUN-1997 08:34:37.00
System Uptime: 1 00:46:34.07
Crash/Primary CPU: 01/00
Saved Processes: 26
Pagesize: 8 KByte (8192 bytes)
Physical Memory: 2048 MByte (262144 PFNs)
Dumpfile Pagelets: 999974 blocks
Dump Flags: writecomp,errlogcomp,dump_style
EXE$GL_FLAGS: poolpging,init,bugdump,pgflfrag
Stack Pointers:
KSP = 00000000 7FF91C98 ESP = 00000000 7FF96000 SSP = 00000000
7FF9C100
USP = 00000000 7EDE4030
General Registers:
R0 = 00000000 00000000 R1 = FFFFFFFF 814EA180 R2 = FFFFFFFF
81410000
R3 = FFFFFFFF 9DE268F8 R4 = 00000000 0000012C R5 = 00000000
7FF91D40
R6 = 00000000 7FF445A0 R7 = 08000000 00000200 R8 = FFFFFFFF
F7710250
R9 = 00000000 00000030 R10 = 00000000 00000031 R11 = 00000000
00000001
R12 = 00000000 00008001 R13 = FFFFFFFF 9DE268F8 R14 = FFFFFFFF
9DE25640
R15 = FFFFFFFF 9DE04200 R16 = 00000000 00000774 R17 = 00000000
7FF91C38
R18 = FFFFFFFF 9DE32CE0 R19 = FFFFFFFF 9DE04200 R20 = 00000000
00000000
R21 = 00000000 272007F0 R22 = FFFFFFFF 9DE04200 R23 = 00000000
00000000
R24 = FFFFFFFF 9DE04AC0 AI = 00000000 00000000 RA = FFFFFFFF
00000000
PV = FFFFFFFF FFFFFFFF R28 = FFFFFFFF 8001F83C FP = 00000000
7FF91E10
PC = FFFFFFFF 8001F8D4 PS = 18000000 00001604
Failing Instruction:
EXE$HWCLKINT_C+00510: BUGCHK
o A system may crash when a second node attempts to boot a system
disk shadow set with two members. The following SHADDETINCON
bugcheck at SHDRIVER+12124 or SYS$SHDRIVER_NPRO+449B4 occurs:
SHADDETINCON, SHADOWING detects inconsistent state
o The mount of a shadow set fails. The failure report says that
the set is already mounted or that there is a duplicate unit
number.
Existing Problems Not Addressed in the VAXSHAD01_071 Kit:
o The following three MOUNT problems were discovered at a late
stage in the release of this kit. OpenVMS Engineering is
working on solutions to these problems which will be available
in a future MOUNT ECO kit.
If a user, either manually or by a command procedure, executes
one of the following errors, MOUNT may incorrectly add members
to existing shadow sets.
- A MOUNT/SHAD with an incorrect volume label will succeed
in adding the member to the shadow set, for example:
$ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1
$! The shadow set DSA1 is now available with DUA1 as
$! the only member
$ MOUNT/SYSTEM DSA1/SHAD=$4$DUA5 TST5
$! The device $4$DUA5 is wrongly added as a full copy
$! target.
- Similarly, a MOUNT/SHAD with an incorrect volume label of
a shadow set that is MOUNTed elsewhere in the VMScluster
will succeed in adding the member to the set on the other
nodes in the VMScluster, but the MOUNT will fail on the
local node, for example:
NODE_1> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1
NODE_1> $ ! The shadow set DSA1 is now available on NODE_1
NODE_2> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA5 TST5
NODE_2> $ ! The MOUNT correctly fails on NODE_2 with an
$ ! INCVOLLABEL error
NODE_1> $ ! However, the member $4$DUA5 is incorrectly added
NODE_1> $ ! to the set DSA1 as a full copy target.
- MOUNT will incorrectly allow a non-shareable MOUNT/SHADOW of a
disk that is already mounted on another node as "shareable" to
succeed. As a result, corruption of the disk(s) will occur,
for example:
NODE_1> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1
NODE_1> $ ! The shadowset DSA1 is now available on NODE_1
NODE_2> $ MOUNT /NOSHARE DSA5/SHAD=$4$DUA1 TST1
NODE_2> $ ! The shadowset DSA5 is now incorrectly available
$ ! on NODE_2
NODE_1> $ ! The shadowset DSA1 is also available on NODE_1
Corruption of the disk will occur when write operations are
performed by either node.
Problems Addressed in the VAXSHAD01_071 ECO Kit:
o A SHADDETINCON BUGCHECK may occur in SHD_THREADS when an
attempt is made to terminate a thread that is still a
Significant Event.
o The Volume Shadowing driver delivered in OpenVMS V7.1 and
the V6.2 Cluster Compatibility kits (xxxCOMPAT_062) does not
contain the full solution for the 'Bad Block Repair' (BBR)
problem. As a result, a disk may not be expelled from a shadow
set when necessary.
o An incompatibility exists between the StorageWorks Host Based
RAID Software and the enhanced volume shadowing provided in
both OpenVMS 7.1 and in the Cluster Compatibility Kits
(xxxCOMPAT_62). Because of this incompatibility, RAID
software can no longer detect that a shadow set state change
has occurred.
o Write protecting a shadow set member which is being added to
an existing shadowset causes the virtual unit to hang.
o A system may crash with an INVEXCEPTN bugcheck in SHSB$SEND_MESSAGE
because the UCB address in R5 is zero. It may also crash in
IOC_STD$CVT_DEVNAM in IO_ROUTINES when an attempt is made to get
a DDB out of a UCB that is corrupt.
The problem occurs when the IRP$L_ARB field is not correctly set
up with the clone error index. In the SH$VP_DEV_DRVERR routine,
this byte is used as an index to fetch the longword UCB of the
erring device which is set to FF and is incorrect.
The bad value occurs when volume processing begins to initiate
mount verification after a device error occurs.
o A shadowset may hang in mountverify for an extended period of
time after it encounters a DRAB_INT controller failure on an
HSJ50 which is followed by many 'forced error flagged in last
sector read' error messages on multiple shadowset member disks.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database. To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'VAXSHAD' or 'VAXSHAD10_071'.
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:
Install this kit with the {Installation Utility} utility by logging
into the SYSTEM account, and typing the following at the DCL
prompt:
@SYS$UPDATE:VMSINSTAL VAXSHAD10_071 [location of the saveset]
The saveset location may be a tape drive, CD, or a disk directory
that contains the kit saveset.
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.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| CLIUTLMSG.EXE |%X62A831ED| X-3 | 8-DEC-2000 |
| | | 08:57:34.16 |
+----------------------------+----------+-----------------+--------------+
| SDA.EXE |%XE1C0E09F| X-10A1 | 9-MAY-2001 |
| | | 06:07:14.41 |
+----------------------------+----------+-----------------+--------------+
| SHADOW_SERVER.EXE |%XCDD00B08| X-13 | 16-AUG-2001 |
| | | 12:54:29.59 |
+----------------------------+----------+-----------------+--------------+
| SHDRIVER.EXE |%XF22761B4| SHADOW01 | 16-AUG-2001 |
| | | 12:54:38.51 |
+----------------------------+----------+-----------------+--------------+
| SHOW.EXE |%XD9E44D1A| X-1 | 16-AUG-2001 |
| | | 12:55:37.40 |
+----------------------------+----------+-----------------+--------------+
| SYSINIT.EXE |%X010B201B| X-31 | 22-OCT-2000 |
| | | 23:09:23.47 |
+----------------------------+----------+-----------------+--------------+
All trademarks are the property of their respective owners.
|
