Patch IDs |
Abstract |
Patch 4.00
TCR510DX-001
|
Patch:
Fix for Cluster Alias Manager system management tool
State:
Existing
This patch fixes the
Cluster Alias Manager system management tool from crashing and displaying
errors. |
Patch 9.00
TCR510-001 |
Patch:
Initializing the MC-API results in system crash
State:
Existing
This patch fixes a problem where on
the AlphaServer GS160 systems, initializing the MC-API results in the system
crashing with a "kernel memory fault" message. |
Patch 45.00
TCR510-043
|
Patch:
Prevents ics_mct error panic on clusters
State:
Supersedes patches TCR510-018 (17.00), TCR510-028 (42.00),
TCR510-052 (43.00)
This patch corrects the following:
Eliminates unnecessary rail failovers in vhub configurations
and removes rmerror_int diagnostic messages.
Fixes an issue which causes all cluster nodes to hang or panic
if a Wildfire is halted via the halt button.
Fixes a panic that is caused in a clustered environment that
has the following error message:
rm_request_on_bad_prail
Prevents an "ics_mct: Error from establish_RM_notification_channel"
panic on clusters.
|
Patch 49.00
TCR510-037
|
Patch:
Fixes networking issues within cluster environment
State:
Supersedes patches TCR510-019 (28.00), TCR510-029 (41.00),
TCR510-041 (46.00), TCR510-048 (47.00)
This patch corrects the
following:
Fixes the cluamgr command where it will display the alias
status even if no cluster member has joined the alias.
Fixes a problem in which RPC requests to the cluster alias
may fail with "RPC timeout" message.
Fixes a cluster node hang from in_pcbnotify.
Fixes a problem that a rebooted node not able of sending messages
to the cluster alias.
Fixes multiple networking issues within a cluster environment:
Cluster member loses connectivity with clients on remote subnets.
aliasd not handling multiple virtual aliases in a subnet and/or
IP aliases.
Allows cluster members to route for an alias without joining
it.
aliasd writing illegal configurations into gated.conf.memebrX.
Default route not being restored after network connectivity
issues.
Fixes a race condition between aliasd and gated.
Fixes a problem with a hang caused by an incorrect /etc/hosts
entry.
|
Patch 66.00
TCR510-027
|
Patch:
CAA unable to update the state of devices
State:
New
This patch is for systems running TruCluster
Server V5.1 with the following configurations:
Tapes and/or media changer devices used as CAA resources.
A combination of tapes, media changers, and network interfaces
used as CAA resources.
The patch fixes a problem that prevents CAA from updating
the state of any of the above resources when connectivity to the corresponding
device (tape, media changer, or network) is lost or restored. |
Patch 69.00
TCR510-049
|
Patch:
Fix for KMF with RDG autowiring mechanism
State:
Supersedes patches TCR510-007 (11.00), TCR510-024 (30.00),
TCR510-036 (67.00)
This patch corrects the following:
Corrects a problem in which the RDG subsystem will stop sending
messages even though there are messages which are deliverable.
Fixes an incorrect display of the following warning message
at boot time:
rdg: failed to start context rcvq scan thread
Fixes a kernel memory fault with the RDG autowiring mechanism,
also seen as a "pte not valid" crash.
Adds a multichannel wait flag to pid_unblock.
Contains performance enhancements.
Fixes a problem with RDG whereby broadcast packets can interact
with the context receive queue.
|
Patch 72.00
TCR510-039
|
Patch:
Fixes a panic that causes a CNX QDISK error message
State:
Supersedes patches TCR510-002 (5.00), TCR510-003
(7.00), TCR510-023 (32.00), TCR510-042 (70.00)
This patch corrects
the following:
Fixes an occasional cluster hang which can occur after a Memory
Channel error.
Fixes a kernel memory fault which occurs in the ics_mct_ring_recv()
routine.
The kernel memory fault is seen when a node is booting into the
cluster, and can occur on the booting node or on another node.
Fixes a problem in ICS where ring_recv() does not properly
handle a change in channel numbers.
The fix will, in turn, improve validation
of the connection structure on node joins.
Fixes the way communication errors occur on clusters such
that a down node will not declare all other nodes dead.
Fixes the problem that causes a panic with error message "CNX
QDISK: Yielding to foreign owner with quorum" caused by a long running thread,
ICS/MCT receive thread, which defers other kernel threads from accessing
the CPU.
|
Patch 77.00
TCR510-034
|
Patch:
Fixes KZPCC controller problem
State:
Supersedes patches TCR510-005 (15.00), TCR510-021 (33.00), TCR510-009
(34.00), TCR510-016 (35.00), TCR510-011 (36.00), TCR510-022 (37.00), TCR510-012
(39.00), TCR510-035 (73.00), TCR510-038 (74.00), TCR510-030 (75.00)
This patch corrects the following:
Fixes two TruCluster problems:
If a Quorum disk is manually added by the command
clu_quorum -d add, the disk becomes inaccessible because
the PR flag is not being cleaned up.
The same command will work in
the next reboot.
A cluster member cannot boot under a specific hardware setup.
The CFS mount fails because of the PR flag is not cleaned up.
Addresses the need for IOCTL for remote DRD, adds clean up
for failed remote closes for non-disks, fixes error returns on failed tape/changer
closes, and fixes tape deadlock experienced in netbackups.
Fixes an issue with a tape/changer failing to correctly report
a close failure of a device in a cluster environment.
Fixes a problem which results in a system panic while doing
tape failovers.
Fixes a node panic during fiber port disables.
Fixes an issue with a tape/changer giving back "busy
on open" if a close from a remote node failed.
Provides the TCR portion of the functionality to support EMC
storage boxes that support Persistent Reserves (SCSI command set) as defined
by the final SCSI specification.
Fixes an issue with requests being stuck on a failed disk
in a cluster.
Allows high density tape drives to use the high density compression
setting in a cluster environment.
Fixes a kernel memory fault panic that can occur within a
cluster member during failover while using shared served devices.
Aixes an issue with the hwmgr -delete command that causes
a panic in a cluster.
Fixes the KZPCC controller problem seen when deleting a Virtual
Drive using SWCC and adding the same drive back can result in the disk being
unaccessible.
|
Patch 80.00
TCR510-047
|
Patch:
Fixes an Oracle process hang
State:
Supersedes patch TCR510-033 (78.00)
This patch corrects the following:
|
Patch 82.00
TCR510-064
|
Patch:
TCR510-058
State:
Supersedes
patches TCR510-004 (2.00), TCR510-006 (13.00), TCR510-026 (18.00), TCR510-020
(19.00), TCR510-013 (20.00), TCR510-015 (21.00), TCR510-017 (22.00), TCR510-014
(23.00), TCR510-025 (24.00), TCR510-008 (26.00), TCR510-056 (50.00), TCR510-050
(51.00), TCR510-054 (52.00), TCR510-057 (53.00), TCR510-046 (54.00), TCR510-040
(55.00), TCR510-031 (56.00), TCR510-032 (57.00), TCR510-051 (58.00), TCR510-060
(59.00), TCR510-044 (60.00), TCR510-053 (61.00), TCR510-045 (62.00), TCR510-058
(64.00)
This patch corrects the following:
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.
Provides a small TPC-C performance optimization to cfsspec_read
for reporting TPC-C single node cluster numbers.
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:
*** 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.
clu_upgrade does not check the availabilty of space in /,
/usr, and /usr/i18n.
During the preinstalled phase, clu_upgrade will ignore a no
answer when the user is prompted, during an error condition, whether
they wish to continue.
clu_upgrade incorrectly assumes that if the directory /usr/i18n
exists, then it is in its own file system.
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 "Could not get property..." and
"...does not exist" type of error messages during the undo install
phase.
The clu_upgrade undo switch command, after completing a clu_upgrade
switch command, should display an error message instead of claiming it
has succeeded.
Fixes a problem with disaster recovery whereby the node being
restored will hang on boot.
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.
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).
Corrects a problem in which a cluster member will panic with
the patch string "lock_terminate: lock held" from cinactive().
|
Patch 82.00
continued |
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
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.
Provides performance enhancements for copying large files
(files smaller than the total size of client's physical memory) between
a CFS client and server within the cluster.
Corrects a token hang situation by comparing against the
correct revision mode.
Fixes a bug in the cluster filesytem that can cause a kernel
memory fault.
Eliminates superfluous AutoFS auto-mount attempts during rolling
upgrade.
These attempted auto-mounts slow down certain operations and leave
the AutoFS namespace polluted with directories prefexed with ".Old..".
Fixes memory leak in cfscall_ioctl().
Fixes a panic with the following error message:
panic: cfsdb_assert
Contains corrections required for proper operation of Oracle
9i with Tru64 UNIX/TruCluster 5.1.
The problems corrected include:
Processes hanging when using Cluster File System/Direct I/O
feature.
Improper handling of direct I/O to an AdvFS fileset if a clone
fileset was already in use, potentially resulting in an inconsistent
backup.
Using ls -l, the Cluster File System file attribute could
be seen inconsistently from the server and client members.
For example,
a file's mode could be seen differently from the server and the client.
A file opened for Direct I/O on the Cluster File System server
may inappropriately be opened in non-direct I/O mode by a client.
Oracle processes hanging due to shutting down one cluster
member.
A problem with the Cluster File System which could cause a
cluster system to panic with the panic string "kernel memory fault" in
the routine mc_bcopy().
A problem with Cluster File System which could cause a cluster
member to panic with the panic string "uiomove: mode." This problem
could cause Oracle multi-instance data bases to crash with the message
similar to the following:
ORA-27063: skgfospo: number of bytes read/written is incorrect
|
Patch 82.00
continued |
Fixes data inconsistency problems that can be seen on clusters
that are NFS clients.
Frevents a cfsdb_assert panic from occurring in cfs_reclaim.
This panic has been seen while running ensight7.
Prevents a potential hang due to external NFS servers.
Provides a warning to users installing a patch kit that includes
a patch which requires a version switch.
The warning informs the user that
the installed patches include a version switch which cannot be removed using
the normal patch removal procedure.
The warning allows the user to continue
with the switch stage or exit clu_upgrade.
Prevents a potential hang that can occur on a CFS failover.
Allows POSIX semaphores/msg queues to operate properly on
a CFS client.
Allows the command cfsstat -i to execute properly.
Corrects a problem which can cause cluster members to hang,
waiting for the update daemon to flush /var/adm/pacct.
Fixes a potential CFS hang on defragment.
|
|
|