ECO NUMBER: ALPF11X05_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPF11X05_062 2 KITS SUPERSEDED BY THIS KIT: ALPF11X04_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: ALPCLUSIO01_061, ALPY2K01_062 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: ALPSYSA02_062 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 4.2 Files patched or replaced: o [SYS$LDR]F11BXQP.EXE (new image) o [SYS$LDR]FILESERV.EXE (new image) o [SYS$LDR]F11BXQP.STB o [SYS$STARTUP]VMS$CONFIG-050_CACHE_SERVER.COM (new file) 5 PROBLEMS ADDRESSED IN ALPF11X05_062 KIT o When two processes are accessing a file via the MOVEFILE and READATTR/FID_TO_SPEC mechanism, such as a data collector process running on the same volume as a defragger competing for the same data, both processes try to delete the 'primary_fcb' -- COVER LETTER -- Page 2 9 November 1999 used to get the information in question. In both of these circumstances, the reference count on the FCB has not been bumped up so both accesses appear to allow the deletion. This results in a NOTFCBFCB Bugcheck. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 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. However, the blocking lock (F11B$b) is left with the process. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB o An XQPERR Bugcheck occurs in LOCKERS when the retry limit on F11B$x lock is reached. This happens when the owner of the $x lock is running at a high process priority and there are a number of processes in a clustered system that are also trying to validate this lock but at a lower process priority. The high priority process never really gives up the locks long enough to let the low process priority processes to continue and either validate or release the $v lock. To avoid this situation, after (every) 256 attempts, the process with the most retry iterations is stalled for a short period to allow other processes to complete their accesses to the lock. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB o In the process of finding an FCB chain, the XQP switches serialization to the primary FCB of the chain. In this process, the FCB chain an be rebuilt or destroyed while the process is stalled. If this FCB now points to another FCB chain or a deleted FCB the XQP will bugcheck with either an XQPERR bugcheck or a UNXSIGNAL (ACCVIO). Images Affected: -- COVER LETTER -- Page 3 9 November 1999 - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB o A system would crash with an SPLACQERR bugcheck after the releasing of the current processes IPL/Fork lock. The SCH$QAST routine sets R4 to be the address of the target PCB when it returns. The XQP$UNLOCK_CACHE routine expects R4 to be the address of a UCB. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 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." Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 6 PROBLEMS ADDRESSED IN ALPF11X04_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 Note: [SYS$STARTUP]VMS$CONFIG-050_CACHE_SERVER.COM also is needed to run the FILESERV.EXE image. 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). -- COVER LETTER -- Page 4 9 November 1999 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 misplaced SYS_UNLOCK call can cause a SMPRELEASE bugcheck (crash). Image Affected: - [SYS$LDR]F11BXQP.EXE o A dismount on a shadowed device results in an unnecessary copy. 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 -- COVER LETTER -- Page 5 9 November 1999 o A XQPERR Bugcheck (crash) in XQP can occur during an 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 in an 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 An 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 -- COVER LETTER -- Page 6 9 November 1999 is still in memory. Image Affected: - [SYS$LDR]F11BXQP.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 7 PROBLEMS ADDRESSED IN ALPF11X03_062 KIT o A XQPERR bugcheck occurred with a "all the index buffers are active" error message. The problem typically happens when running with a reduced cache or during a BACKUP. o When creating files with ACLs on a full volume, a XQPERR bugcheck 'wrong lock basis with FCB present' occurred. This ACL creation on full volumes was fixed. o One can serialize on the wrong volume in a volume set. o If more than one process queues for a volume's activity blocking lock, the XQP can deadlock. -- COVER LETTER -- Page 7 9 November 1999 o Various XQPERR bugchecks occur in directory scanning/shuffling. o The problem only shows up when creating a file with a version limit of 1 and SYSTEM_CHECK is on or bit 5 or 6 of ACP_DATACHECK is 1. A XQPERR bugcheck occurred due to a corrupted directory. o The NOTIFY_USER for final status of an XQP request occurs too early in XQP request completion to report any errors produced in cleanup or auditing. This problem is normally all right, since USER_STATUS is not expected to change during cleanup. However, if it does change, then the output of SET WATCH FILE is misleading. o XQP requests to create a new file with version limits set can fail with an SS$_NOSUCHFILE error. o Deleting a stale alias on a directory with extension headers can bugcheck with XQPERR "Lock index has shifted". This problem occurs when: 1. an alias to an existing file is created 2. the original file is deleted 3. the original file's file header is reused as an extension header of the alias's parent directory (when ACEs are added to the directory). o Prevent access to file headers beyond index file highwater-marking (HWM). One can possibly ACCESS by FID a file header beyond the current end of the index file on a freshly-initialized volume. Creating a new file accessed in this way can bug-check the system with the XQPERR error. 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 filesystem. In the best case, this problem can lead to bad information being returned. In the worst case, if the filesystem was rebuilding the ORB's ACL chain at the time, a kernel mode ACCVIO can occur. *** Note *** : To get this fix, you must also install kit ALPSYSA02_062. -- COVER LETTER -- Page 8 9 November 1999 8 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_1 : To be installed by all customers. 9 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPF11X05_062 [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. Copyright (c) Compaq Computer Corporation, 1999 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer Corporation. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.