3    Summary of TruCluster Software Patches

This chapter summarizes the TruCluster software patches included in Patch Kit-0002.

Table 3-1 lists patches that have been updated.

Table 3-2 provides a summary of patches in Patch Kit-0002.

Table 3-1:  Updated TruCluster Software Patches

Patch IDs Change Summary
Patch 23.00 New
Patches 2.00, 4.00, 12.00 Superseded by Patch 21.00
Patches 6.00, 7.00, 9.00, 10.00, 11.00, 24.00, 5.00, 1.00, 14.00, 15.00, 16.00, 17.00, 19.00 Superseded by Patch 26.00

Table 3-2:  Summary of TruCluster Patches

Patch IDs Abstract

Patch 8.00

TCR505-008

Patch: Fix for MC2 vhub cluster panic

State: New

If lockmode has been set to 4, booting an MC2 vhub cluster generates the following panic on the second node booting:

simple_lock: uninitialized lock
....
panic (cpu 0): simple_lock: uninitialized lock

Patch 13.00

TCR505-018

Patch: Problem seen when running clu_upgrade preinstall cmds

State: Supersedes patch TCR505-009 (3.00)

This patch fixes the following:

Delivers a new stripped clu_genvmunix and several fixes to the cluster rolling upgrade procedure.

Problem seen when running clu_upgrade preinstall commands on certain multi-cpu systems. Numerous error messages similar to the following are seen:

*** Error ***
Could not create: ocolsocols/.Old..ocols

If you see this problem enter a Ctrl/C and rerun the clu-upgrade preinstall command.

Patch 21.00

TCR505-021

Patch: Corrects problem with cluster member

State: Supersedes patches TCR505-006 (2.00), TCR505-002 (4.00), TCR505-014 (12.00)

This patch corrects the following problems:

  • Fixes a system panic that can be caused by Memory Channel errors occurring when the system is under heavy load.

  • Improves cluster communication performance including file system mount times.

  • Corrects problems seen when both a member is leaving and joining the cluster at the same time.

  • Corrects problems with loss of quorum in a cluster. Once the quorun is lost, the member may panic with the panic string:

    QNX DISK: yeilding to foreign owner with quorum.

Patch 23.00

TCR505-019

Patch: Fixes a problem with the Memory Channel API

State: New

This patch fixes a problem with the Memory Channel API, whereby a node crashes holding an mc-api lock. Under certain circumstances the lock will not be released after the node crashes.

Patch 26.00

TCR505-011

Patch: Fixes problem on cluster nodes

State: Supersedes patches TCR505-003 (6.00), TCR505-007 (7.00), TCR505-010 (9.00), TCR505-012 (10.00), TCR505-013 (11.00), TCR505-023 (24.00), TCR505-004 (5.00), TCR505-005 (1.00), TCR505-015 (14.00), TCR505-024 (15.00), TCR505-020 (16.00), TCR505-016 (17.00), TCR505-017 (19.00)

This patch corrects the following problems:

  • Fixes a situation which has caused a node panic with the following message:

    SIMPLE_LOCK: TIME LIMIT EXCEEDED PANIC ON SHARED TAPE

  • Solves a problem with booting and shutting down cluster nodes while using a tape (or changer) device in a V5.0A cluster.

  • Fixes a problem where a mount command will hang after DRM has restored the path to an HSG80 storage volume.

  • Fixes a problem where a path will fail after DRM has restored the path to an HSG80 storage volume.

  • Fixes a problem where on a cluster node, if a new device is detected by a HW scan while the cluster is up running, one of the following situations can occur:

    • Only one node will be able to use the device; if the device is Fiber Channel.

    • There is a small risk for data corruption on parallel SCSI device on a shared bus if the node subsequently loses quorum.

  • Provides the DRD portion of a fix to prevent an AdvFS Domain Panic from occurring during the boot process following a clu_add_member.

  • Fixes a problem where on a cluster node, if a SCSI bus reset occurs, when there is a loss of quorum, the drd will be blocked on tape devices.

  • Fixes a kernel memory fault panic in routines cfstok_find_held_tok. This is caused when the very first action of a new alloocated thread is a lookup in an NFS filesystem of ".".

  • Fixes a problem where mounts that return "ESTALE" may loop forever. This patch prevent a KMF panic from occurring when an AdvFS mount is attempted without a fileset being specified.

  • Provides the CFS/CMS portion of a fix to prevent an AdvFS Domain Panic from occurring during the boot process following a clu_add_member.

  • Corrects a problem with cluster members panic with a "kernel memory fault" when either running sys_check or mulitple cfsmgr commmands.

  • Provides performance enhancements for CFS.

  • Prevents an "request_internal: client already had token" panic from occurring when nodes are leaving and joining the cluster.