PROBLEM: (82505, SSRT0691U) (PATCH ID: TCR510-004) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Compaq has corrected this potential vulnerability. PROBLEM: (82592) (PATCH ID: TCR510-006) ******** This is a small TPC-C performance optimization to cfsspec_read. This is required to be reporting TPC-C single node cluster numbers based on this change. PROBLEM: (82650, 81082, 82110, 81915, 80967, 80006) (PATCH ID: TCR510-026) ******** This patch fixes the following clu_upgrade command problems: - When attempting to roll a patch kit on a single member cluster, without this patch, the following error messages will be seen when running the postinstall stage: This is cluster upgrade program. You have indicated that you want to perform the 'postinstall' stage of the upgrade. Do you want to continue the upgrade of the cluster? [yes]: yes *** Error*** Members '2' is NOT at the new base software version. *** Error*** Members '2' is NOT at the new TruCluster software version. - During backup stage of "clu_upgrade setup 1", clu_upgrade is unable to determine the name of the kernel configuration file. The following error message is displayed: Message from backup stage of "clu_upgrade setup 1": *** Error *** The cluster upgrade command was unable to determine the name of the kernel configuration file. Do you want to continue the cluster upgrade without backing up this file? [no] - clu_upgrade does not check the availabilty of space in / and /usr and /usr/i18n. - During the preinstalled phase, clu_upgrade will ignore a "no" answer when user is prompted, during an error condition, if wish to continue. - clu_upgrade incorrectly assumes that if the directory /usr/i18n exists, then it is in its own file system. If the user sets up the cluster with i18n in /usr, which is a valid configuration permitted by installation, the attempt to run clu_upgrade setup to perform a rolling upgrade will fail in the following manner: # clu_upgrade -c setup 1 *** Error *** There is no space available in the root (/), /usr, or /var file systems to back up member ''???'' member-specific files. Increase the available disk space on one of these file systems and rerun this stage of the upgrade. - After the "clu_upgrade clean" phase, the final step of clu_upgrade, no message is displayed that leads the user to believe they have completed the upgrade. Only the prompt is returned and the "clu _upgrade -completed clean" command reports that the clean had not completed. - clu_upgrade can display the following "Could not get property..." and "...does not exist" error messages during the undo install phase: Could not get property for file /usr/.smdb./.Old..OSFACCT505.inv Could not get property for file /usr/.smdb./.Old..OSFACCT505.lk Could not get property for file /usr/.smdb./.Old..OSFACCT505.scp and /usr/var/cluster/members/member0/im/webagent/.Old..IMAGES does not exist /usr/var/cluster/members/member0/im/webagent/.Old..WEBAGENT.INI does not exist - The "clu_upgrade undo switch" command after completing a "clu_upgrade switch" command should display an error message instead of claiming it has succeeded. PROBLEM: (DMO13809, N/A) (PATCH ID: TCR510-020) ******** This patch fixes a problem with disaster recovery whereby the node being restored will hang on boot. This hang will usually occur after a SCSI bus reset or 'waiting for cluster mount to complete.' It corresponds to step 11 in section 11.1.6 of the v5.1 Cluster Administration documentation. PROBLEM: (83724, GOZ14663B) (PATCH ID: TCR510-013) ******** This patch corrects a problem in which a cluster may panic with a "cfsdb_assert" message when restoring files from backup while simultaneously relocating the CFS server for that file system. PROBLEM: (83952, SOO12306A) (PATCH ID: TCR510-015) ******** This patch corrects a problem in which a cluster member can panic with the panic string "cfsdb_assert" when a NFS v3 TCP client attempts to create a socket using mknod(2). PROBLEM: (83749, VNO76936A, MGO38615A) (PATCH ID: TCR510-017) ******** This patch corrects a problem in which a cluster member will panic with the patch string "lock_terminate: lock held" from cinactive(). PROBLEM: (BCGM919P3, EVT376821B, EVT376821, 82934) (PATCH ID: TCR510-014) ******** This patch fixes a hang seen while running collect and the vdump utility. This patch prevents the hang in tok_wait from occurring. This also prevents a cfsdb_assert panic that contains the following message: "Assert Failed: (tcbp->tcb_flags & TOK_GIVEBACK) == 0" PROBLEM: (84176, TKTBB0088, HPAQC0DRG, EVT0576031, HPAQ1093P) (PATCH ID: TCR510-025) ******** This patch prevents a cfsdb_assert panic from occurring in the cfs block reserve code. The system is most likely running process accounting that will receive this type of panic. Panics seen: Assert Failed: brp->br_allocated >= 0 file: ../../../../src/kernel/tnc_common/tnc_cfe/cfs_blkrsrv.c line: 1508 caller: 0xfffffc0000861f4c panic (cpu 2): cfsdb_assert and Assert Failed: bdp->bd_svr_out >= blkreturn file: ../../../../src/kernel/tnc_common/tnc_cfe/cfs_blkrsrv.c line: 2591 caller: 0xfffffc00008d8294 panic (cpu 0): cfsdb_assert PROBLEM: (BCGM90MM9) (PATCH ID: TCR510-008) ******** This patch is to provide performance enhancements for copying large (These are files smaller than the total size of client's physical memory.) files between a CFS client and server within the cluster.