|
|
 |
VAXF11X06_062 VAX V6.2 F11/File Serve ECO Summary
|
TITLE: VAXF11X06_062 VAX V6.2 F11/File Serve ECO Summary
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.
*OpenVMS] VAXF11X06_062 VAX V6.2 F11/File Serve ECO Summary
Copyright (c) Compaq Computer Corporation 1998, 1999. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENT: F11BXQP
F11AACP
FILESERV
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXF11X06_062
ECO Kits Superseded by This ECO Kit: VAXF11X05_062
NOTE: The fixes contained in the previous versions
of this ECO (VAXF11X03_062, VAXF11X02_062 and
VAXF11X01_062) are included in the
VAXY2K02_062 ECO kit.
ECO Kit Approximate Size: 432 Blocks
Kit Applies To: OpenVMS VAX V6.2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
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:
VAXCLUSIO01_062, VAXY2K02_062
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
VAXSYSA02_062 for a $GET_SECURITY fix when reading the ORB
on a file that had no synchronization with the file system.
ECO KIT SUMMARY:
An ECO kit exists for F11BXQP on OpenVMS VAX V6.2. This kit addresses
the following problems:
Problems Addressed in the VAXF11X05_062 kit:
o A NOTFCBFCB bugcheck on the simultaneous dereference of a file
occurred.
Image(s) Affected: [SYS$LDR]F11BXQP.EXE
o If a process attempts to mount a bound volume set (BVS) and
all the members of the BVS are not present, an attempt to lock
the volume for REBUILDing the meta-data on the volume will
fail, but the blocking lock (F11B$b) is left with the process.
Image(s) Affected: [SYS$LDR]F11BXQP.EXE
o An XQPERR bugcheck in LOCKERS can occur when the retry limit
on the F11B$x lock is reached.
This problem can occur when the owner of the $x lock is
running at a high process process priority and a number of
processes are in a clustered system are also trying to
validate this lock, but at a lower process priority.
Image(s) Affected: [SYS$LDR]F11BXQP.EXE
o When a directory with multiple headers, e.g., a large ACL, is
deleted on one mode in a cluster (Node A), if that directory
had previously been accessed on another node in the cluster
(Node B), the files created with the previously deleted
headers would show up on Node B with a NOSUCHFILE error."
o Fix the internal GETTIM function so that it properly formats
the 64 bit internal time to an RSX-11 compatible ASCII string.
RSX date strings contain only a 2 character year field (ASCII).
In order to accommodate the year 2000, this ASCII encoding
will now include the value of decades (since 1900) into the
string. This means that for the years 1900 through 1999, the
date string will appear as 00 to 99. For the years 2000 into
the years 39xx, the string will show as ':0', ';0', etc.
For years prior to the year 1900, dates are encoded as binary
zeros, which is interpreted as 'no date'.
Image(s) Affected: [SYS$LDR]F11BXQP.EXE
Problems Addressed in the VAXF11X05_062 kit:
o During the mounting of the system disk, the error message that
the disk is mounted with a reduced cache is suppressed. Hence,
the System Manager may be unaware that the performance of the
system disk and all others attached to the same cache block is
questionable.
Image Affected: [SYSEXE]FILESERV.EXE
o When deleting a large file (such as a system dump file), a
UNXSIGNAL Bugcheck may occur. This particular bugcheck occurs
because a variable in the code causes a reference to memory
data that the file system does not own and an internal access
violation occurs (ACCVIO).
Image Affected: [SYS$LDR]F11BXQP.EXE
o On some systems with higher rates of system paging or with
WSDEC set to a non-standard value, a system can crash with a
PGFLIPLHI (Page Fault IPL too High) bugcheck. This problem
happened when the system returns from a SMP$ACQUIRE call.
Image Affected: [SYS$LDR]F11BXQP.EXE
o An XQPERR can occur in the RDBLOK module during disk cleanup
using DCL.
Image Affected: [SYS$LDR]F11BXQP.EXE
o When storing the value of a directory index buffer, the system
may crash with a PGFLIPLHI, SSRVEXCPTN error.
Image Affected: [SYS$LDR]F11BXQP.EXE
o A dismount on a shadowded device results in an unnecessary
copy.
Image Affected: [SYS$LDR]F11BXQP.EXE
o If a process is created with a termination mailbox unit
assigned, the files are not properly audited.
Image Affected: [SYS$LDR]F11BXQP.EXE
o An XQPERR bugcheck (crash) in the RETURN_CREDITS module can
occur during DISMOUNT.
Image Affected: [SYS$LDR]F11BXQP.EXE
o An XQPERR Bugcheck (crash) in XQP can occur during a SET ACL
(SET FILE/ACL) operation.
Image Affected: [SYS$LDR]F11BXQP.EXE
o When two processes are competing to dismount a volume, one
process may be just a bit faster than the other and delete the
VCB and other structures before the second process has time to
finish up its processing. The result is a UNXSIGNAL/ACCVIO
crash.
Image Affected: [SYS$LDR]F11BXQP.EXE
o A device reporting a read error (SS$_PARITY) during read/write
processing in the XQP will attempt to record the bad blocks
and FID in the BADLOG.SYS file. When the internal close
operation occurs (on BADLOG), the system XQPERR bugchecks
when it finds the process's dirty buffers have not been
written out.
Image Affected: [SYS$LDR]F11BXQP.EXE
o A UNXSIGNAL/ACCVIO error can occur at module F11BXQP. This
problem occurs during mount, when the primary volume is not
yet mounted.
Image Affected: [SYS$LDR]F11BXQP.EXE
o Processes can hang (deadlock) when dismounting a device.
Image Affected: [SYS$LDR]F11BXQP.EXE
o A 'no such file' error can occur on directory extension FCBs.
This problem can occur in at least two ways:
1. A file appears normal on one node but has an 'no such
file' error from another node.
2. BACKUP or DUMP /HEADER encounters a read attributes
error of NOSUCHFILE. This error occurs when an attempt
is made to read a file header, for which the FCB for the
old header is still in memory.
Image Affected: [SYS$LDR]F11BXQP.EXE
o Alternate file access checking does not provide the correct
information for files on ODS-1 disks. That is, an ODS-1 disk
access does not process the alternate file access checking
parameters FIB$L_ALT_ACCESS and FIB$L_STATUS.
Image Affected: [SYSEXE]F11AACP.EXE
o The F11A routine ACPCONTROL only understands the control
function REMAP_FILE. Hence, for illegal function codes, all
other control functions return NORMAL, when ILLIOFUNC should
be returned instead.
Image Affected: [SYSEXE]F11AACP.EXE
o Occasional false end-of-file (EOF) errors can occur on a read
operation.
Image Affected: [SYS$LDR]F11BXQP.EXE
o The XQP fails after an IO$_DEACCESS call with an SS$_BADPARAM
error. One cannot determine whether a file is still open or
not due to the failed IO$_DEACCESS call.
Image Affected: [SYS$LDR]F11BXQP.EXE
o Non-privileged users can change the revision date (and count)
of a file for which they should have only READ access. For
example, if a non-privileged user with READ-only file access
tries to set the file protection, a failure occurs with an
SS$_NOPRIV error as expected. However, the revision date (and
count) are modified.
Image Affected: [SYS$LDR]F11BXQP.EXE
Problems Addressed in the VAXF11X04_062 kit:
o An XQPERR bugcheck error, "all the index buffers are active",
occurs when running with a reduced cache or during a BACKUP.
o An XQPERR bugcheck error, 'wrong lock basis with FCB present',
occurred when creating files with ACLs on a full volume.
o One can serialize on the wrong volume in a volume set.
o Fix a reserved operand fault bugcheck on $QIO exit. The $QIO
failed on return because the IPL was set to zero but was
entered at IPL 2.
o $GET_SECURITY was reading the ORB on a file without any
synchronization with the file system. In the best case, this
problem can lead to bad information being returned. In the
worst case, if the file system was rebuilding the ORB's ACL
chain at the time, a kernel mode ACCVIO can occur.
*** Note: In order to get this fix, you must also install the
kit VAXSYSA01_062.
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, they must
also be rebooted in order to make use of the new images.
If it is not possible or convenient to reboot the entire cluster at
this time, a rolling re-boot may be performed.
All trademarks are the property of their respective owners.
|
Files on this server are as follows:
|
»vaxf11x06_062.README
»vaxf11x06_062.CHKSUM
»vaxf11x06_062.CVRLET_TXT
»vaxf11x06_062.a-dcx_vaxexe
»vaxf11x06_062.CVRLET_TXT
|
