======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS722_SHADOWING-V0200 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 1 KIT NAME: VMS722_SHADOWING-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 INSTALL_2 : To be installed by all customers using the following feature(s): - SHADOWING This 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) 2.2 Reboot Requirement: Reboot Required. HP 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. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-2 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: Page 2 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS722_UPDATE-V0100 - VMS722_PCSI-V0100 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 FILES PATCHED OR REPLACED: o [SYSEXE]SHADOW_SERVER.EXE (new image) Image Identification Information image name: "SHADOW_SERVER" image file identification: "X-13" image file build identification: "X71Z-0050170015" link date/time: 6-AUG-2003 11:20:45.58 linker identification: "A11-39" o [SYS$LDR]SYS$SHDRIVER.EXE (new image) Image Identification Information image name: "SYS$SHDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170015" link date/time: 6-AUG-2003 11:20:58.11 linker identification: "A11-39" 6 PROBLEMS ADDRESSED IN THIS KIT 6.1 New problems addressed in the VMS722_SHADOWING-V0200 kit 6.1.1 System hang during the mounting of a shadowset. Page 3 6.1.1.1 Problem Description: During the mounting of a shadowset, a series of protocols can collide such that a thread is left waiting to be resumed and there is no thread to resume it. This can result in a system hang. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 6.1.1.2 CLDs, and QARs reporting this problem: 6.1.1.3 CLD(s) 75-13-829,CFS.90085 6.1.1.4 QAR(s) None. 6.1.1.5 Problem Analysis: The START_MBR_CHANGE_VP macro used in the START_PROTOCOL_END macro will exit with an error when it detects PASSIVE_MV. This causes either a loop in the START_PROTOCOL_END macro or two NL enques in a row which causes the STALL mechanism in the GRANT_LOCK code to fail to resume a stalled thread. The check for PASSIVE was added to prevent incorrect member removal during volume processing. To fix this problem the original START_MBR_CHANGE_VP has been restored and called START_MBR_CHANGE_MNT to be used in the START_PROTOCOL_END macro. This allows MOUNTS to do the right thing. The error loop has been taken out of START_PROTOCOL_END. 6.1.1.6 Work-arounds: None. 6.1.2 Multi-site cluster shadowset member is returned to the shadowset incorrectly Page 4 6.1.2.1 Problem Description: In a multisite cluster with all timeouts set to the maximum, a shadowset member is returned to the shadwoset incorrectly. Manual removal of a member from one site, followed by manual aborting of the virtual unit at a second site, allowed a third site to return the member to the shadowset without either a copy or a merge. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 6.1.2.2 CLDs, and QARs reporting this problem: 6.1.2.3 CLD(s) 70-3-5465,CFS.88963 6.1.2.4 QAR(s) None. 6.1.2.5 Problem Analysis: When the virtual unit is aborted, if there is an outstanding write a merge is triggered. Although the member has been removed from the first site, the third site still thinks it can do a merge. As soon as it can access the removed member it starts the merge. The update of the merge being started causes the member to be added back into the set on the first site. The fix is to not allow NODE_FAILURE to proceed untill PASSIVE_MV has completed. 6.1.2.6 Work-arounds: None. 6.1.3 Ensure shadow copies handle bad blocks correctly 6.1.3.1 Problem Description: If a bad block is detected on the source disk during a full copy operation, the copy will abort with the following OPCOM message : %%%%%%%%%%% OPCOM 10-MAY-2002 09:41:23.94 %%%%%%%%%%% (from node UKVMS3 at 10-MAY-2002 09:41:22.46) Message from user SYSTEM on UKVMS3 %SHADOW_SERVER-E-SSRVTRMSTS, reason for termination Page 5 of operation on device _DSA1: IVADDR, invalid media address The virtual unit will look like this afterwards: Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DSA1: Mounted 0 ALPHAE722_CD 15330438 1 1 $7$DKA100:(UKVMS3) ShadowSetMember 2 (member of DSA1:) $7$DKA1000:(UKVMS3) ShadowCopying 0 (copy trgt DSA1:11% copied) Note that the virtual unit will still be accessible in this state. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 6.1.3.2 CLDs, and QARs reporting this problem: 6.1.3.3 CLD(s) 75-66-1156 6.1.3.4 QAR(s) None. 6.1.3.5 Problem Analysis: When the SHADOW_SERVER is asked to do a shadow copy, it "steps" through the disk processing one 127-block chunk after another (the SCB is handled differently), and it does this by sending IO$_COPYSHAD $QIOs to the shadowing driver. There are three pieces of information that the driver sends back to SHADOW_SERVER in response to a IO$_COPYSHAD, which are: 1. Status code 2. Byte transfer count 3. LBN copy fence, ie the last LBN successfully copied. If the LBN copy fence does not agree with what SHADOW_SERVER thinks it should be, then it adjusts its value before moving onto the next LBN range. Page 6 The problem occurs when a bad block is detected on the source volume. In this case, a zero is returned erroneously as the "LBN copy fence". The SHADOW_SERVER then attempts to start copying at LBN 1 again. It encouners a consistency check in SHDRIVER which aborts the COPYSHAD with an SS$_IVADDR error status. 6.1.3.6 Work-arounds: None. 6.1.4 Shadowset Aborts after node is shutdown 6.1.4.1 Problem Description: Shadowsets on the remaining node of a multi site cluster abort after the serving node of one member is shutdown. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 6.1.4.2 CLDs, and QARs reporting this problem: 6.1.4.3 CLD(s) CFS.90313,CFS.91498,CFS.93820 6.1.4.4 QAR(s) None. 6.1.4.5 Problem Analysis: An attempt was made to keep a shadowset together when a cluster interconnect is intermittent. This allowed the behaviour of hanging the set until MVTIMOUT then aborting it. 6.1.4.6 Work-arounds: None. Page 7 6.1.5 Host Based Volume Shadowing (HBVS) Mini Copy Problem 6.1.5.1 Problem Description: When using HBVS, if Mini Copy is used to return a former Shadow Set Member (SSM) to a virtual unit, and that SSM is removed from the shadow set before the copy can complete, the user must execute the following commands before adding that SSM is added back into the shadow set: $ SHOW DEVICE/BITMAP/FULL DSAnnnn: $ DELETE /BITMAP x "DSAnnnn:" is the virtual unit and "x" is the BitMap ID displayed by the SHOW DEVICE/BITMAP/FULL command. If multiple BitMap IDs are displayed, delete the one that has the SSM in the Bitmap Name portion of the display. If these steps are not taken, data integrity could be affected. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 6.1.5.2 CLDs, and QARs reporting this problem: 6.1.5.3 CLD(s) CFS.100146 6.1.5.4 QAR(s) None. 6.1.5.5 Problem Analysis: See problem description 6.1.5.6 Work-arounds: None. 6.1.6 Repair read bias calculation for multipath devices Page 8 6.1.6.1 Problem Description: The read performance for a multiple member shadow set, that has multipath enabled members, has been using only the primary UCB, not the current UCB. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 6.1.6.2 CLDs, and QARs reporting this problem: 6.1.6.3 CLD(s) None. 6.1.6.4 QAR(s) None. 6.1.6.5 Problem Analysis: Use the correct primary UCB number 6.1.6.6 Work-arounds: None. 6.1.7 Default read cost for locally remote device set to high 6.1.7.1 Problem Description: Default read cost for locally remote device is set to high. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 6.1.7.2 CLDs, and QARs reporting this problem: Page 9 6.1.7.3 CLD(s) None. 6.1.7.4 QAR(s) None. 6.1.7.5 Problem Analysis: Change to a more reasonable value. The user is able to modify the value. 6.1.7.6 Work-arounds: None. 6.1.8 INVEXCPTN Crash during shadow copy 6.1.8.1 Problem Description: When doing a controller assisted copy, available with HSC and HSJ controllers, if the source member gets an error an incorrect index is set up that results in a crash. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF 80268D60 Failing PS: 30000000 00000804 Module: SYS$SHDRIVER Offset: 0004AD60 : exception Frame: R2 = FFFFFFFF 837A6380 R3 = 00000000 00000000 R4 = FFFFFFFF 839CB3C0 R5 = FFFFFFFF 83689D80 R6 = FFFFFFFF 839CB680 R7 = 00000000 00000000 PC = FFFFFFFF 80268D60 PS = 30000000 0000080 Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE Page 10 6.1.8.2 CLDs, and QARs reporting this problem: 6.1.8.3 CLD(s) CFS.99512 6.1.8.4 QAR(s) None. 6.1.8.5 Problem Analysis: Ensure all users of shad$ca_target_index use a longword to move in and out of this field. 6.1.8.6 Work-arounds: None. !.lm +5 7 INSTALLATION INSTRUCTIONS: 7.1 Installation Command 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 VMS722_SHADOWING /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 7.2 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE Page 11 - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V2.0 - De-assign the logicals assigned For example, a sample command file to install the VMS722_SHADOWING kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS722_SHADOWING/PROD=DEC/BASE=AXPVMS/VER=V2.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2003 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. 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.