Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXCLUSIO01_062 VAX V6.2 VMScluster/MOUNT/Shadow ECO Summary
Copyright (c) Digital Equipment Corporation 1997. All rights reserved.
Modification Date: 01-APR-99
Modification Type: DOCUMENTATION:
VAXSYS05_070 is retired and superseded by
VAXSYSA01_062.
VAXDOSD06_062 has been superseded by VAXDOSD08_062
(for OpenVMS VAX V6.2 *ONLY*).
REBOOT WARNING: When this kit is installed, the system *MUST* be
rebooted before any other ECO kit is installed. If
the reboot is not performed, the system will lose
functionality.
Attempts to MOUNT devices before rebooting the system
will fail. This includes implicit MOUNTs from BACKUP
and VMSINSTAL.
WARNING: Any customer with MTI StingRay 2 controllers should check
with MTI to see if their current version of firmware will
support CLUSIO or OpenVMS V7.1. This is *NOT* a problem
with OpenVMS V7.1.
CAUTIONS: To all OpenVMS Volume Shadowing Customers
1. The Volume Shadowing software which was shipped in
OpenVMS Alpha and VAX V7.1 requires additional
non-paged pool to improve synchronization. It uses
approximately 800 bytes additional non-paged pool per
concurrent IO to the virtual unit. 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.
2. This version of the software was back-ported to OpenVMS
V6.2, and is available on the V7.1 media in the V6.2
Compatibility (COMPAT) save sets. OpenVMS Engineering
recommends that V6.2 customers install the TIMA versions
of these Compatibility kits, ALPCLUSIO01_062 and
VAXCLUSIO01_062 and tune their systems appropriately
for non-paged pool expansion.
CAUTION: To all RAID Software Users:
RAID Software for OpenVMS, V2.3 (Host-based Raid) and earlier versions
do not work correctly with the following:
o OpenVMS V7.1
o OpenVMS V6.2 Cluster Compatibility kit on V7.1 media
SOLUTION:
In order to use RAID Software on either OpenVMS V7.1 or the V6.2
Compatibility Kit, the following kits must be installed:
OpenVMS V7.1 OpenVMS V6.2 Cluster
Compatibility Kit
----------------------------- -----------------------------
o RAID Software V2.4 or higher o RAID Software V2.4 or higher
o ECO kit SHAD01_V71 or higher o ECO kit CLUSIO01_062 or higher
REGRESSION NOTE: OpenVMS Engineering has discovered that if this ECO
kit is installed on a system on which the VAXDRIV04_070
ECO has been installed, the following fix that was
contained in the VAXDRIV04_070 ECO kit will be lost:
o A problem exists with HSJ/HSD30, 40 and 50
controllers where, after an event that initiates
Mountverfication, a packet acknowledgment will fail
to complete. The controller will report that it is
making progress on the command, but will never
finish. This causes all IO to the affected devices
to hang.
The latest version of the VAXDRIVxx_062 ECO contains
the fix for this problem and can be installed after
the system is rebooted following the installation of
the VAXCLUSIO01_062 ECO.
OP/SYS: OpenVMS VAX
COMPONENT: VMScluster
MOUNT
Volume Shadowing
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXCLUSIO01_062
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 5742 Blocks
Kit Applies To: OpenVMS VAX V6.2
System/Cluster Reboot Necessary: Yes
Installation Rating: 2 - To be installed on all systems running
the listed version(s) of OpenVMS and
using the following feature(s):
+ Systems running the VAXCOMPAT_062
Compatibility Kit
+ Systems running OpenVMS V6.2 where
the included enhancements to SHADOW
and MOUNT are desired
+ Any system running in an OpenVMS
Cluster. This kit is a baseline
kit for any OpenVMS VAX system
running in a cluster environment.
Future OpenVMS VAX remedial kits
will not install on clustered
systems unless this VAXCLUSIO01_062
kit has been installed first.
NOTES: In order to receive the full fixes listed in this kit,
the following remedial kits also need to be installed:
None
Before installing the VAXCLUSIO01_062 remedial kit you
should review the documentation for the following kits.
If you wish to install these kits they must be installed
before installing the VAXCLUSIO01_062 kit.
VAXCLIU02_070 (This kit has been superseded by
VAXCLIU03_070 which is no longer
applicable to OpenVMS VAX V6.2.
Please see the latest version
of VAXCLIUxx_062 for more DCL
"SET" and "SHOW" fixes for OpenVMS
VAX V6.2.)
VAXMANA03_070 (Superseded by VAXMANA04_070 which
does not include any new fixes.)
VAXSYS05_070 (This kit has been retired and is
superseded by VAXSYSA01_062.)
VAXDOSD06_062 (This kit has been superseded by
VAXDOSD08_062 for OpenVMS VAX
V6.2 *ONLY*.)
The VAXCLUSIO01_062 kit contains all the fixes included
in the following list of remedial kits. Once the
VAXCLUSIO01_062 kit is installed there will no longer
be a need to install the particular remedial kits on
this list to OpenVMS VAX V6.2* systems. However, these
kits may be updated in the future and the updated kits
may need to be installed on your system.
VAXDISM01_062
VAXDRIV04_070 (Please see Regression Note above.)
VAXSYS06_070
VAXF11X03_070
VAXINIT01_070
VAXSYS04_070
VAXSYS01_062
VAXMSCP01_070
VAXSHAD05_062
ECO KIT SUMMARY:
An ECO kit exists for several components on OpenVMS VAX V6.2.
Existing Problems Not Addressed in the VAXCLUSI01_062 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.
o RAXCO's PerfectCache V5.0 and PerfectDisk products are not
compatible with the MOUNT that is included in CLUSIO and
OpenVMS V7.1. If either product is started against a disk,
and then another node in the cluster attempts to MOUNT that
disk, the MOUNT will fail with a "DEVBUSY" failure.
Please note that the SWXNA (the current generation of the
FDDI server) presently ships with V5.0 of PerfectCache,
and, therefore, customers installing this product are
exposed to this problem. The HS1xx and HS2xx did not ship
with PerfectCache and are not subject to this issue.
Storage engineering is aware of the the SWXNA issue and
is taking action.
To workaround this problem, be sure that the disks are
mounted on all nodes in the cluster prior to starting
PerfectCache or PerfectDisk; or turn off PerfectCache or
PerfectDisk prior to mounting the disk on another node.
RAXCO is aware of this problem and has fixed it in
PerfectCache V6. They are working on a solution for
PerfectDisk as well.
o SHADDETINCON crashes if the database uses a high number of
locks (>64K) and Write Logging is in effect on shadow
sets. To fix the problem contact your Customer Support
Center for the latest SHDRIVER image. This image will
be released in a future TIMA kit.
o If one of the shadow set members is not visible at boot
time, and the system is booting off the non-master member,
the system may crash with a SHADDETINCON bugcheck at
SHDRIVER+12124. To work around this problem, the System
disk shadow set must be made a single member set prior to
booting. After all nodes have booted and are up, the
other members can be added to the system disk shadow set.
o In a new cluster (never having been booted as a cluster
before), if the CNID = 0, and a node leaves the cluster,
then all shadow set virtual units in that cluster will go
into a full merge. This problem will be addressed in a
future shadowing TIMA kit.
Problems Addressed in the VAXCLUSIO01_062 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 kit (VAXCOMPAT_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 Kit
(VAXCOMPAT_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.
o Cluster Compatibility Kit Functionality
+ The VAXCLUSIO01_062 remedial kit includes the functionality
shipped with the VAXCOMPAT_062 Cluster Compatibilty Kit. The
OpenVMS Cluster Compatibility Kit provides many OpenVMS
Version 7.1 enhancements for Version 6.2 systems. This kit
is required for Version 6.2 systems if they are included in
a VMScluster with Version 7.1 systems (same system architecture
or a mix of VAX and Alpha systems). Optionally, users can
install it on other OpenVMS Version 6.2 systems to derive the
same benefits.
Cluster Compatibility Kit Features:
- OpenVMS Version 7.1 Volume Shadowing enhancements
The volume shadowing enhancements include significant
quality improvements and an increase in supported shadow
set members from 400 to 500. Note that the Version 7.1
volume shadowing system disk minimerge feature is not
included in the Cluster Compatibility Kit nor is the
Dump file off the system disk for OpenVMS Alpha. (The
Dump file off the system disk has been available for
OpenVMS VAX systems since Version 6.2.)
_______________________ Note _______________________________
If you use volume shadowing, be sure to read the volume
shadowing release notes.
____________________________________________________________
- OpenVMS Version 7.1 Mount Enhancements
The Mount utility has been completely rewritten, resulting
in a faster, more robust utility.
- Correction to an OpenVMS Version 6.2 Lock Manager problem
The Lock Manager changes correct a problem in OpenVMS
Version 6.2 that could corrupt some internal states in
lock information used by fork lock routines, notably the
I/O cache subsystem. This problem was corrected in OpenVMS
Version 7.0, and also in the limited hardware releases for
OpenVMS Alpha Version 6.2-1H2 and Version 6.2-1H3.
- Limited support for new port allocation classes for SCSI
Devices
Port allocation classes are a new naming option for SCSI
devices on systems running OpenVMS Alpha Version 7.1. If
you have installed the Cluster Compatibility Kit (on a VAX
or Alpha system ), you can access SCSI disks on an OpenVMS
Alpha Version 7.1 system that use port allocation classes
in their names, but you cannot name SCSI disks on a Version
6.2 system with port allocation classes.
- Snapshot Facility Disabled
Installing the Cluster Compatibility Kit on a Version 6.2
system disables the Snapshot facility, which has been
removed from OpenVMS VAX Version 7.1.
- System Dump Analyzer Utility (SDA)
A special version of the OpenVMS Version 6.2 System Dump
Analyzer (SDA) utility is included in the Cluster
Compatibility Kit. It recognizes the new volume shadowing
data structures.
When you install the Cluster Compatibility Kit, the
existing OpenVMS Version 6.2 SDA is renamed SDA_OLD.EXE
and the Cluster Compatibility Kit version is named
SDA.EXE. Use SDA_OLD.EXE to analyze crash dumps from
OpenVMS Version 6.2 systems on which the Cluster
Compatibility Kit has not been installed. Use SDA.EXE
to analyze crash dumps from OpenVMS Version 6.2 systems
on which the Cluster Compatibility Kit has been installed.
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: 'VAXCLUSIO01_062', 'VAXCLUSIO' or 'VAXCLUS'.
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:
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.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| DEBUG_SHDRIVER.EXE |%XCA5B38F7| SRP-26P4 | 13-FEB-1997 |
| | | 13:41:04.14 |
+----------------------------+----------+-----------------+--------------+
| DISMNTSHR.EXE |%X9BD89429| X-2 | 6-FEB-1997 |
| | | 11:26:51.27 |
+----------------------------+----------+-----------------+--------------+
| DISMOUNT.EXE |%X2C7BC00E| X-4 | 6-FEB-1997 |
| | | 12:03:46.02 |
+----------------------------+----------+-----------------+--------------+
| DUDRIVER.EXE |%X3D8FECE7| X-96 | 6-FEB-1997 |
| | | 12:08:23.32 |
+----------------------------+----------+-----------------+--------------+
| ERRORLOG.EXE |%XF68E873A| X-24 | 6-FEB-1997 |
| | | 12:18:19.08 |
+----------------------------+----------+-----------------+--------------+
| EXEC_INIT.EXE |%XD641BC4F| X-24 | 6-FEB-1997 |
| | | 12:11:42.18 |
+----------------------------+----------+-----------------+--------------+
| F11BXQP.EXE |%X91DCB6FD| XQP V6.2R-0003 | 6-FEB-1997 |
| | | 12:10:11.76 |
+----------------------------+----------+-----------------+--------------+
| IMAGE_MANAGEMENT.EXE |%X580DA801| X-24 | 6-FEB-1997 |
| | | 12:04:44.29 |
+----------------------------+----------+-----------------+--------------+
| INIT$SHR.EXE |%X2FEAAA49| X-2 | 6-FEB-1997 |
| | | 11:27:01.99 |
+----------------------------+----------+-----------------+--------------+
| IO_ROUTINES.EXE |%XA41E2F62| X-24 | 6-FEB-1997 |
| | | 12:13:35.57 |
+----------------------------+----------+-----------------+--------------+
| LOCKING.EXE |%X1AB138B5| X-24 | 6-FEB-1997 |
| | | 12:15:57.99 |
+----------------------------+----------+-----------------+--------------+
| MOUNTSHR.EXE |%X52B2A57D| X-1 | 18-FEB-1997 |
| | | 16:18:52.68 |
+----------------------------+----------+-----------------+--------------+
| MSCP.EXE |%X9BABFC4A| X-65 | 6-FEB-1997 |
| | | 12:15:10.12 |
+----------------------------+----------+-----------------+--------------+
| NISCS_LOAD.EXE |%XCA93672F| X-19 | 6-FEB-1997 |
| | | 12:11:21.92 |
+----------------------------+----------+-----------------+--------------+
| PAGE_MANAGEMENT.EXE |%XB0BE011E| X-24 | 6-FEB-1997 |
| | | 12:06:35.02 |
+----------------------------+----------+-----------------+--------------+
| SDA.EXE |%X1CBF1B07| X-10 | 6-FEB-1997 |
| | | 12:22:43.29 |
+----------------------------+----------+-----------------+--------------+
| SHADOW_SERVER.EXE |%XB9BD2C7A| X-9P2 | 13-FEB-1997 |
| | | 13:40:42.02 |
+----------------------------+----------+-----------------+--------------+
| SHADOW_SERVER_DEBUG.EXE |%X0D934872| X-9P2 | 13-FEB-1997 |
| | | 13:40:46.74 |
+----------------------------+----------+-----------------+--------------+
| SHDRIVER.EXE |%XA6B8719F| SRP-26P4 | 13-FEB-1997 |
| | | 13:40:52.55 |
+----------------------------+----------+-----------------+--------------+
| SHOW.EXE |%X98F76770| X-1 | 6-FEB-1997 |
| | | 12:09:14.37 |
+----------------------------+----------+-----------------+--------------+
| SMI$OBJSHR.EXE |%XF85BFF2B| 0 | 6-FEB-1997 |
| | | 12:04:24.89 |
+----------------------------+----------+-----------------+--------------+
| SMISERVER.EXE |%XD61F6A86| X-13 | 6-FEB-1997 |
| | | 12:08:03.19 |
+----------------------------+----------+-----------------+--------------+
|
