OpenVMS VMS712_MOUNT96-V0200 MOUNT ECO Summary
TITLE: OpenVMS VMS712_MOUNT96-V0200 MOUNT ECO Summary
New Kit Date : 19-FEB-2001
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VMS712_MOUNT96-V0100
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-dcx_axpexe.pcsi, then it can
be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 2001. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: Mount
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS712_MOUNT96-V0200
DEC-AXPVMS-VMS712_MOUNT96-V0200--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS712_MOUNT96-V0100
ECO Kit Approximate Size: 1280 Blocks
Kit Applies To: OpenVMS Alpha V7.1-2
System/Cluster Reboot Necessary: NO
Rolling Re-boot Supported: Information not available
Installation Rating: INSTALL_1
1 - To be installed on all systems running
the listed version(s) of OpenVMS.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
o VMS712_UPDATE-V0300.
o VMS62TO71U2_PCSI-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 the MOUNT utility on OpenVMS Alpha V7.1-2.
This kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS712_MOUNT96-V0200 KIT:
o MOUNT appears to successfully mount a shadow set that is in
"MountVerify Timeout" state, but no members are added and the
set remains in "MountVerify Timeout" state.
A device that is in "MountVerify Timeout" state must be
dismounted before you can successfully re-mount the device.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
o If a batch job issues a SPWAN/NOWAIT MOUNT command, and then
exits while the MOUNT is in operator assist wait, the result is
that the subprocess hangs in MOUNT in LEF and the main process
in RWAST waiting for the subprocess to exit.
Images Affected: [SYSLIB]MOUNTSHR.EXE
o When MOUNTing bound volume sets which are also shadow set
members, MOUNT-F-INCONSET and MOUNT-I-DOVOLSET occur on certain
devices.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
o Initialize VCB$L_BLOCKFACT to be at least 1, so that the XQP
does not incur 'divide by zero' and UNXSIGNAL bugchecks.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
o When mounting a CD that was created from a disk that was larger
than the CD itself, a check that compares the volume size,
cluster factor and block count fails with a %MOUNT-F-FILESTRUCT
error.
Images Affected: [SYSLIB]MOUNTSHR.EXE
[SYSEXE]VMOUNT.EXE
PROBLEMS ADDRESSED IN VMS712_MOUNT96-V0100 KIT:
o OpenVMS V7.2 provided a new check to determine if the disk
that is being MOUNTed was initialized to a size that is larger
than the number of blocks that are now available.
This size discrepancy occurs when a disk is moved from one
controller type to another (for example, from a local SCSI
connection to an HSJ) without the disk being initialized on
the new controller. As a result, some data may be
inaccessible through the new controller. If this condition
was detected, then a fatal MOUNT-F-FILESTRUCT error was
reported and the MOUNT was aborted.
It has been determined that a number of systems are running
with disks which are in this condition. While there may be
data that is inaccessible on the disk, the usefulness of the
disk should be left to the discretion of the system manager.
Therefore, this change makes this condition issue the following
warning message rather than a fatal error:
%MOUNT-W-INCONSIZE, inconsistent number of blocks reported,
some data may not be accessible
It is recommended that the BACKUP utility be used to move
data from a disk on one controller type to a disk on another
controller type, especially if those controllers report a
different number of blocks available for the same disk type.
Once the data has been moved, the physical disk can be moved
and initialized on the new controller.
Images Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
- [SYSMSG]SYSMSG.EXE
o Previously, a fix was included to address a problem in which
SWL disks do not come out of mount verification properly.
The fix insured that the VCB$T_VOLOCKNAM matches the
SCB$_VOLOCKNAME of the volume, even for privately mounted
disks. However, if a member of a shadow set is removed
from the set for BACKUPs, then both the still-mounted
shadow set and the privately mounted former member will
have the same VCB$T_VOLOCKNAMs.
This causes a variety of symptoms, including access conflicts
during BACKUPs of the former member and in at least one case,
an XQPERR, Error detected by file system XQP bugcheck at
F11BXQP_PRO+0BE48. In addition, reports of systems unable
to MOUNT multiple CDROMS have been attributed to this problem.
Due to the problems that it caused, the original fix has been
removed. As a result, the original problem may still occur.
If a disk is write-locked, it will not successfully complete
mount verification. The device will be marked as "wrong volume".
Compaq OpenVMS Engineering continues to research solutions to
this problem.
Images Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
only "scratch" disks can be added to shadow sets.
This is similar to the /CONFIRM switch, except that it
can be used in command procedures as well, without
immediate operator intervention. It is also similar
to the /NOCOPY command, except it allows copies to
occur, as long as the label is "scratch".
Images Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
- [SYSMSG]SYSMSG.EXE
- [SYSLIB]DCLTABLES.EXE
INSTALLATION NOTES:
No reboot is necessary after successful installation of the kit.
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_MOUNT96 /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
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
dec-axpvms-vms712_mount96-v0200--4.README
dec-axpvms-vms712_mount96-v0200--4.CHKSUM
dec-axpvms-vms712_mount96-v0200--4.pcsi-dcx_axpexe
vms712_mount96-v0200.CVRLET_TXT
|
