|
|
 |
HP Services Software Patches - vaxf11x04_070
|
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
Copyright (c) Digital Equipment Corporation 1994, 1997. All rights reserved.
PRODUCT: OpenVMS VAX, Version 7.0
COMPONENTS: File System - F11BXQP (XQP)
ACL
BACKUP
SLS
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXF11X04_070
ECO Kits Superseded by This ECO Kit: VAXF11X01_071 (V7.0 Only)
VAXF11X03_070 (V7.0 Only)
VAXF11X02_070 (V7.0 Only)
VAXF11X01_070 (V7.0 Only)
ECO Kit Approximate Size: 325 Blocks
Kit Applies To: OpenVMS VAX V7.0
System/Cluster Reboot Necessary: Yes
Installation Rating: 1 - To be installed on all systems running
the listed version(s) of OpenVMS.
NOTE: In order to receive the full fixes listed in this kit,
the following remedial kits also need to be installed:
VAXSYS06_070 for V7.0 (or its supersedant kit)
Due to a remedial change in the XQP, systems running
V7.0 may be at a greater risk of encountering a memory
management problem that may lead to system crashes.
When this VAXF11X remedial kit is installed on a system,
the VAXSYS06_070 kit for V7.0 should also be installed
to ensure that this problem does not occur. A
description of the memory management problem can be
found in the VAXSYS06_070 remedial kit.
ECO KIT SUMMARY:
An ECO kit exists for F11BXQP.EXE on OpenVMS VAX V7.0. This kit
addresses the following problems:
Problems Addressed in the VAXF11X04_070 Kit:
o An XQPERR bugcheck occurs when trying to create a file.
o A bad FID bugcheck occurs when trying to mark a file header free in
the index file bitmap.
o There are multiply allocated blocks and file headers on the disk.
o Processes hang in an RWAST state while trying to deaccess a file
during channel deassignment.
o The system hangs during cluster wide cache flushes.
o The contents of a header or bitmap block could be corrupted within
the block buffer cache.
o Failure to take an allocation lock could be ignored.
o If a DEACCESS request failed with a SS$_DEADLOCK error, a process
could be left in an RWAST state indefinitely.
o If a large file is created on a fragmented disk that has quotas
enabled and the user needs to use EXQUOTA privilege to allocate the
necessary disk space, an internal XQP table can become corrupted.
This leads to the following bugcheck:
SECAUDERR, Fatal error attempting to perform a security audit
o Superseding a file with a version limit set can remove the oldest
version of a file even if that version is undeletable by the user
according to its protection mask or ACL. The file is removed but
not deleted, and can be recovered by ANALYZE/DISK/REPAIR.
o Attempting to queue a maximal length (39.39;5) filename to the XQP
for spooling to a symbiont would cause either an infinite CPU loop
or the following bugcheck:
FILCNTNONZ, Open file count nonzero after process rundown
Problems Addressed in the VAXF11X01_071 Kit for OpenVMS VAX V7.0:
o The problem occurs when a file is deleted while still being accessed
by someone. This produces an XQPERR bugcheck when an attempt is
made to access the deleted file.
o The problem may result in an XQPERR bugcheck which claims that: "all
the index buffers are active" during the processing of a directory
file.
o The fault occurs as a UNXSIGNAL Bugcheck after running AUTOGEN, and
rebooting with very large SYSGEN ACP cache parameters.
Problems Addressed in the VAXF11X03_070 Kit for OpenVMS VAX V7.0:
o A system might crash with a SECAUD bugcheck if "ANAL/DISK/ . . ."
is run on a corrupted disk with auditing turned on.
o An XQP bugcheck occurs when a file is accessed for the first time
with cathedral windows, and the accessing process runs out of BYTLM
quota.
o Window mapping code might incorrectly concatenate extents which run
from one volume to another in a volume set.
o An XQPERR bugcheck may occur in [F11X]DIRSCNuPDATE_INDEX() during an
attempt to insert an index entry into a directory index block with
DIR$W_TOTALCELLS equal to zero.
o Directory FCBs can become stale but invisible to the XQP. The File
IDs can then be reused. If the FCB in question is an extension FCB,
the next time the new file is accessed on that node, the XQP will
bugcheck with the fatal XQPERR 'wrong lockbasis with FCB present'.
o If a file is opened for exclusive access on one node in a cluster
and a 'BACKUP/IGNORE=INTERLOCK' command is issued to backup the file
on that node, after the BACKUP completes the file can be
successfully accessed from the other node(s) of the cluster. The
BACKUP destroys the exclusive access.
o BACKUP and SLS can cause WCBFCBMNG bugchecks when operating on some
files. These files are legal, uncorrupted files so they should not
repeatedly cause a crash whenever BACKUP or SLS tries to back them up.
Problems Addressed in the VAXF11X02_070 Kit for OpenVMS VAX V7.0:
o The VAXF11X01_070 remedial kit placed the OpenVMS VAX V7.0
F11BXQP.EXE image in the SYS$SYSTEM directory. For V7.0 the
location of this file changed. The file should now be placed in the
SYS$LOADABLE_IMAGES images directory.
Problems Addressed in the VAXF11X01_070 Kit for OpenVMS VAX V7.0:
o When enabling quotas on the system disk, the system occasionally
crashes with an ACCVIO.
o Due to an XQP error in the directory handling cleanup code, a
file may appear twice in the same directory block.
o Incorrect timing in blocking AST code may cause a system
crash with a BADDALRQSZ bugcheck.
o It is possible for the sequence numbers which protect the
index file bitmap and storage bitmaps to wrap while another
node is holding an obsolete buffer. If that node then decides
to use that buffer, there is a small window during which the
invalid buffer could be seen as valid, and used to allocate
blocks on the disk. This is reported by the system as
multiple allocated blocks after a disk has been defragmented.
o UNXSIGNAL crash due to a corrupt Window Control Block (WCB).
o When disk quota is exceeded, an extension File Control Block is not
allocated, causing corruption of File Access Control Lists.
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.
|
Files on this server are as follows:
|
»vaxf11x04_070.README
»vaxf11x04_070.CHKSUM
»vaxf11x04_070.CVRLET_TXT
»vaxf11x04_070.a-dcx_vaxexe
|
