1    Release Notes

This chapter provides important information that you need in order to work with the Tru64 UNIX 5.1 and TruCluster 5.1 Patch Kit-0003.

1.1    Patch Process Resources

Compaq provides Web sites to help you with the patching process:

1.2    Required Storage Space

The following storage space is required to successfully install this patch kit:

Base Operating System

TruCluster Server

Note

A rolling upgrade has specific disk space requirements. Be sure to check your disk space before starting a rolling upgrade. Make sure that your system contains the required space in all file systems before you begin the setup stage of the roll. If any file system fails to meet the minimum space requirements, the program will fail and generate an error message similar to the following: 

***Error***
The tar commands used to create tagged files in the '/' file system have
reported the following errors and warnings:
NOTE: CFS: File system full: /
 
        tar: sbin/lsm.d/raid5/volsd : No space left on device
        tar: sbin/lsm.d/raid5/volume : No space left on device
NOTE: CFS: File system full: /
 
.NOTE: CFS: File system full: /

If you receive this message, run the clu_upgrade -undo setup command, free up or add the required amount of space on the affected file systems, and then rerun the clu_upgrade setup command.

Rolling upgrade disk space requirements are described in Section 7.4.1 of the TruCluster Server Software Installation manual.

1.3    Difference Between the First and Second Release Version 5.1 Kits

The Version 5.1 Patch Kit-0003 was re-issued to correct a problem with the baselining operation of the patch installation utility, dupatch. The patches themselves are exactly the same in both kits. You can tell the difference between these kits as follows:

To install this patch kit, use one of the following procedures.

1.3.1    Installing Kit-0003 for the First Time

If you are installing the second release of Patch Kit-0003 and did not install the initial release of Patch Kit-0003, you need only follow the instructions in the Patch Kit Installation Instructions document provided with your kit. No special action is needed.

1.3.2    Installing the Second Release of Kit-0003 over the First Release of Kit-0003

If you previously installed the initial release of Patch Kit-0003 on a system, the steps you take with the second release kit depend on whether or not your system contains manually installed customer-specific patches (CSPs):

The following sections describe these procedures. Compaq recommends that you have the Patch Kit Installation Instructions available.

Common Steps

The following steps are common to all stand-alone and clustered systems:

  1. From root, extract the T64V51AS0003-20010521.tar file to a locally mounted file system. For example: 

    # script untar.log
# tar -xpvf T64V51AS0003-20010521.tar
 
 

  2. From the directory containing the extracted files run dupatch: 

    # ./dupatch

    Note

    Do not run the version of dupatch in /usr/sbin.

  3. When the dupatch menu is displayed, verify that the revision is listed as Rev. 29-02.

If your system has no customer-specific patches installed, type q to exit dupatch; you have done all you need to do. For systems containing CSPs, see the next section.

Note

If you want to install the new installation tools without invoking the dupatch menu (for example, if you are using a script), use the following command. You will, however, need to invoke the dupatch menu if you want to verify the dupatch revision. 

dupatch -track -kit patch_kit -type kit

Additional Steps for Manually Installed CSPs

If your system contains manually installed customer-specific patches, perform the previous steps, and then do the following:

  1. Review your session logs from the installation of the initial Patch Kit-0003 to determine if any critical patches failed to install. If you find none, you do not have to do anything else. If you find critical patches that failed to install, continue with the following steps.

  2. Run the baseline option. See the Patch Kit Installation Instructions for step-by-step instructions on baselining.

  3. Install the patch kit.

    Note

    If you are installing the patch kit on a cluster using the Rolling Upgrade procedure, perform steps 1 through 5 before beginning the Rolling Upgrade.

    Perform step 6 during the Install Stage of the Rolling Upgrade procedure. See the Patch Kit Installation Instructions for step-by-step instructions on performing a Rolling Upgrade.

1.4    Release Note for Tru64 UNIX Patch 399.00

1.4.1    AdvFS and Direct I/O

In laboratory testing, Compaq has observed that under certain circumstances, a possibility exists that inconsistent data may be written to disk on some Tru64 UNIX V5.0A and V5.1 systems running AdvFS and direct I/O.

Compaq became aware of this possibility only during laboratory testing. To our knowledge, no customer has experienced this problem. Compaq is alerting customers to this potential problem as a precautionary measure.

The conditions under which this potential problem may occur are as follows:

Invalid data could occur when a single direct I/O write spans multiple AdvFS pages, and some, but not all, of the pages are still in the UBC. If the file has been opened only for direct I/O and remains open for direct I/O, the problem does not exist.

Applications that use direct I/O, such as Oracle, could be affected.

Configurations Affected

The potential problem may affect the following systems:

Only V5.0A and V5.1 systems running an application that uses direct I/O could experience this potential problem. Any application using direct I/O must request this feature explicitly.

The following Oracle versions use direct I/O and may therefore be affected:

In addition, the AdvFS file system that is used for any of the following Oracle files:

An Oracle environment meeting the above criteria could experience this potential problem.

Oracle running on raw partitions exclusively or running LSM on raw partitions exclusively are not affected.

Some customers write their own applications that use direct I/O. These customers should be aware of the detailed circumstances under which this problem could occur. The problem could occur as follows:

Under these circumstances, the data written at the start of the total write is the original data, offset by the amount of data written to the last page.

Tru64 UNIX versions V4.* and V5.0 are NOT affected.

The potential problem is fixed in future Tru64 UNIX versions and in V5.0 Patch Kit 3 and V5.1 Patch Kit 3.

Problem

If Oracle customers are running one of the affected Oracle configurations, Oracle may have already detected an inconsistency in the database and reported errors similar to the following in the alert log and trace file: 

ORA-01578: ORACLE data block corrupted (file # 1, block # 100)
ORA-01119: data file 1: '/scratch/820/qa/dbs/t_db1.f'
 
 


ORA-00368: checksum error in redo block
ORA-00354: Log corruption near block #231
 
 

Oracle customers that have run the dbverify (dbv) utility may have encountered an error message similar to the following: 

***
  Corrupt block relative dba: 0x0040900b (file 0, block 36875)
  Bad header found during dbv:
  Data in bad block -
   type: 27 format: 2 rdba: 0x0040900d
   last change scn: 0x0000.0001349a seq: 0x2 flg: 0x04
   consistency value in tail: 0x349a1b02
   check value in block header: 0xa377, computed block checksum: 0x0
   spare1: 0x0, spare2: 0x0, spare3: 0x0
  ***
 
 

1.4.2    Technical Update for KZPCC products

This patch provides support for KZPCC products.

For more information see Tru64 UNIX technical updates provided at the following URL:

http://www.tru64unix.compaq.com/faqs/publications/patch/

Select the option for Operating System Technical Updates and choose the following document:

Tru64 UNIX Version 5.1 Technical Update

This technical update will also contain information for valid upgrade paths to Tru64 UNIX Version 5.1 from the Version 4.0x releases that currently support I2O.

1.4.3    Release Note for KZPCC Products

In a TruCluster environment, the deletion and re-creation of any logical drive on a KZPCC controller using the SWCC utility can result in the drive becoming inaccessable. Even though the hwmgr sees the drive being deleted and added back, it can not be disklabeled nor can any read/write operation be performed to the drive. Rebooting the system will restore the drive to a usable state.

This will be fixed in the next patch kit.

1.4.4    Problem with Multi-user Mode Application

Warning

When applying this patch in multi-user mode, an inconsistency problem results between the updated /shlib/libpthread.so and the existing kernel. The problem manifests itself when you install the patch in multi-user mode and you elect to reboot at a later time. The scheduled reboot will not occur. This problem can be avoided by installing Patch 399.00 in single user mode, or selecting the option to reboot now (rather than scheduling later).

To correct this situation, if you have installed the patch and have not rebooted the system, execute the following commands:

  1. Set DUPATCH_SESLOG to location of session log, by default:

    /var/adm/patch/log/session.log

  2. Get the name of newly-built kernel:

    # NEW_KERNEL=`grep "The new kernel is" $DUPATCH_SESLOG | awk ' { print $5 }' `

  3. Copy the new kernel:

    # cp <NEW_KERNEL> /vmunix

  4. Reboot the system at a specified time:

    # shutdown -r <TIME_OF_REBOOT>

After rebooting with the new kernel, your system will once again be consistent.

1.4.5    New Graphics Card

This patch provides the driver support for a new graphics card. In order to obtain full support for this graphics card, you must also select Patch 287.00, which is the X server portion of the patch.

A list of supported platforms is available on the following web page:

http://www.compaq.com/alphaserver/products/options.html

If you have a system with this new graphics card, you will need to reconfigure and rebuild the kernel after installing this patch.

To do this, follow these steps:

  1. Shut down the system:

    # /usr/sbin/shutdown -h now

  2. Boot genvmunix to single-user mode:

    >>> boot -fi genvmunix -fl s

  3. After the system boots to single-user mode, mount the file systems, run the update command, and activate the swap partition:

    # /sbin/bcheckrc

    # /sbin/update

    # /sbin/swapon -a

  4. Run doconfig to create a new kernel configuration file and rebuild the kernel:

    # /usr/sbin/doconfig

    Note

    Do not specify the -c option to doconfig. If you do, doconfig will use the existing kernel configuration file which will not have the appropriate controller entry for the new graphics card.

  5. Save the old /vmunix file and move the new kernel to /vmunix.

  6. Shut down the system:

    # /usr/sbin/shutdown -h now

  7. Boot the new kernel:

    >>> boot

If you remove this patch from your system after you have rebuilt the kernel to incorporate support for the new graphics card as described previously, you will need to rebuild the kernel again to restore generic VGA graphics support. To do this, follow the steps given previously. The doconfig running on the original, unpatched genvmunix will not recognize the new graphics card and will include generic VGA graphics support in the resulting kernel.

1.4.6    DEGPA-TA Gigabit Ethernet Device

This patch provides support for DEGPA-TA (1000BaseT) Gigabit Ethernet device. If you have a system with this new Ethernet device, you will need to reconfigure and rebuild the kernel after installing this patch.

To do this, follow these steps:

  1. Shut down the system:

    # /usr/sbin/shutdown -h now

  2. Boot genvmunix to single-user mode:

    >>> boot -fi genvmunix -fl s

  3. After the system boots to single-user mode, mount the file systems, run the update command, and activate the swap partition:

    # /sbin/bcheckrc

    # /sbin/update

    # /sbin/swapon -a

  4. Run doconfig to create a new kernel configuration file and rebuild the kernel:

    # /usr/sbin/doconfig

    Note

    Do not specify the -c option to doconfig. If you do, doconfig will use the existing kernel configuration file which will not have the appropriate controller entry for the new graphics card.

  5. Save the old /vmunix file and move the new kernel to /vmunix.

  6. Shut down the system:

    # /usr/sbin/shutdown -h now

  7. Boot the new kernel:

    >>> boot

If you remove this patch from your system after you have rebuilt the kernel to incorporate support for the new Ethernet card as described previously, you will need to rebuild the kernel. To do this, follow the steps given previously. The doconfig running on the original, unpatched genvmunix will not recognize the new Ethernet driver.

1.5    Release Note for Tru64 UNIX Patch 287.00

This patch provides the X server support for a new graphics card. In order to obtain full support for this graphic card, you must also select Patch 399.00, which is the driver portion of the patch.

A list of supported platforms is available on the following web page:

http://www.compaq.com/alphaserver/products/options.html

1.6    Release Note for Tru64 UNIX Patch 371.00

This patch contains a solution for the following issue:

Compaq has advised owners of DS10, DS10L, ES40 AlphaServers, and XP900 AlphaStations that Compaq has determined in laboratory testing that there is a theoretical possibility that during read and write operations to the floppy disk on these systems, a single byte of data may be inaccurately read or written without notice to the user or system. The potential for this anomaly exists only if floppy disk read or write operations are attempted while there is extremely heavy traffic on these Alpha systems' internal input/output busses.

Although Compaq has observed the anomaly only in laboratory tests designed to create atypical system stresses, including almost constant use of the floppy disk drive, Compaq has informed owners of the remote possibility that the anomaly could occur so that they may take precautions to prevent it.

Compaq recommends that the solution be installed by all DS10, DS10L, ES40 AlphaServers, and XP900 AlphaStation customers.

The solution to this issue is also available as an individual, manually installed patch kit named floppy_CSP_v51.tar.gz, available from:

http://ftp1.support.compaq.com/public/unix/v5.1

1.7    Release Note for TruCluster Server Software

During the switch stage of a rolling upgrade from TruCluster Server Version 5.1 to TruCluster 5.1 Patch Kit-0003, you may see the following message: 

Initiating version switch on cluster members
.Switch already switched

You can safely ignore this message. The switch stage will complete successfully.

1.8    Release Note for Broken Link Problem

When performing a baseline analysis with the dupatch utility on Tru64 UNIX 5.1 systems, the baseline error log files may report that a number of files have broken hard links to the /usr/share/man/man3 directory.

The presence of these broken links will not affect your system operation, the installation of dupatch or dupatch tools, the successful installation of patches, or the rebuilding of kernels on the system. The problem will be addressed in a future version of the operating system.

You can determine if these broken links exist on your system by performing the following steps:

  1. Change directories as follows: 

    # cd /usr/share/man/man3

  2. Check to see that the inodes are the same for all the files: 

    # ls -il slk*.3.gz curs_slk.3.gz

An example of a correct hard link would look as follows. Note the same inodes. 

14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 curs_slk.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_attr_off.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_attr_on.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_attr_set.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_attroff.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_attron.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_attrset.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_clear.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_color.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_init.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_label.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_noutrefresh.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_refresh.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_restore.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_set.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_touch.3.gz
14648 -rw-r--r--  17 root     system      2086 Mar  9  2000 slk_wset.3.gz
 
 

An example of an incorrect hardlink would look as follows. Note the different inodes. 

54891 -rw-r--r--   2 root     system      2086 Aug 11 17:32 curs_slk.3.gz
54891 -rw-r--r--   2 root     system      2086 Aug 11 17:32 slk_attr_off.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_attr_on.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_attr_set.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_attroff.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_attron.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_attrset.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_clear.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_color.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_init.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_label.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_noutrefresh.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_refresh.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_restore.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32  slk_set.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_touch.3.gz
55583 -rw-r--r--  15 root     system      2086 Aug 11 17:32 slk_wset.3.gz
 
 

1.9    Release Note for Potential Rolling Upgrade Problem

When patching a clustered Tru64 UNIX 5.1 system using the rolling upgrade procedure, the operation may fail if your system has been upgraded from a patched Tru64 UNIX 5.0A version.

In such cases, the lead member is successfully patched, but the patching operation fails for subsequent members. The problem occurs because the file var/adm/patch/roll/installed_patches contains the old OSFPAT*505 entries, which no longer exist in ./usr/.smdb. As a result, the rolling upgrade generates error messages such as the following when subsequent members are rolled: 

Backing up member-specific data for member: 2
 .......
 grep: can't open ./usr/.smdb./OSFPAT00018600505.inv
 grep: can't open ./usr/.smdb./OSFPAT00019200505.inv
 grep: can't open ./usr/.smdb./OSFPAT00020500505.inv
 grep: can't open ./usr/.smdb./OSFPAT00021100505.inv
 grep: can't open ./usr/.smdb./OSFPAT00016500505.inv
 grep: can't open ./usr/.smdb./OSFPAT00020000505.inv
 
 
 

The following procedures describe how to solve the problem if you discover it during a rolling upgrade or if you have not yet begun the rolling upgrade.

Rolling Upgrade Started

Perform the following steps if you issued the clu_upgrade command and discovered the error during the roll of the second member (designated here as member 2):

  1. Halt the failing member: 

    # halt

  2. On the lead member, undo the roll: 

    # clu_upgrade undo roll 2

  3. Remove the old OSFPAT*505 entries from /var/adm/patch/roll/installed_patches. Because this is a cluster-common file, you need only do this once. The remaining members can be rolled as documented in the Patch Kit Installation Instructions.

    1. Change to the /var/adm/patch/roll directory: 

      # cd /var/adm/patch/roll

    2. Invoke an editor such as vi and remove any lines that contain the string OSFPAT*505 from the file installed_patches: 

      # vi ./installed_patches

  4. Boot member 2 to multiuser mode and then shut down to single-user mode: 

    >>> boot
 
# shutdown now

  5. Roll member 2: 

    # bckeckrc
 
# clu_upgrade roll

  6. Complete the procedure as documented in the Patch Kit Installation Instructions.

Rolling Upgrade Not Started

Perform the following steps if you have not started a rolling upgrade:

  1. Rename the installed_patches file and re-create it. 

    # cd /var/adm/patch/roll/ 
# mv ./installed_patches ./installed_patches.V50A
# touch ./installed_patches

  2. Complete the procedure as documented in the Patch Kit Installation Instructions.

For information on patching your clustered system using the rolling upgrade procedure, see the Patch Kit Installation Instructions and the clu_upgrade(8) reference page.

1.10    Release Note for Tru64 UNIX Patch 169.00

In cases where the bttape or btcreate command is used to back up and restore UFS file systems, btextract leaves behind a symboltable file in the restored file system. This file, if present, will cause btextract to hang the next time a bootable tape is created using btcreate or bttape. The btextract command hangs while trying to restore the UFS file system.

To work around this problem, ensure that the file restoresymtab? (where ? refers to the cluster member ID, 0 by default) is removed. Every UFS file system that was restored using btextract will have this file, and this file needs to be removed on each file system before running the bttape or btcreate command the next time. For example, if / and /usr are backed up, then the file will be found at /restoresymtable0 and /usr/restoresymtable0, and both instances of the file need to be removed before proceeding with btcreate or bttape.

1.11    Release Note for Tru64 UNIX Patch 270.00

This patch fixes a security vulnerability (called the Brown Orifice) in Netscape Communicator Version 4.72 by updating Netscape Communicator to Version 4.75.

To determine which version of Netscape Communicator you are running, click on the Help button in the toolbar at the top of the Navigator component window, then choose the About Communicator option from the drop down menu.

You can download the latest version of Netscape Communicator for Tru64 UNIX from the Netscape Download World Wide Web site:

http://home.netscape.com/download/index.html

Or, from the Compaq Tru64 UNIX World Wide Web site:

http://www.tru64unix.compaq.com/internet/download.htm

If you are unable to upgrade to Netscape Communicator 4.75 or later, you can avoid this security vulnerability by disabling the browser's ability to run Java by following these steps:

  1. Start Netscape Communicator:

    $/usr/bin/X11/netscape

  2. Click on the Edit button in the toolbar at the top of the Navigator component window.

  3. Click on the Preferences... option on the drop down menu that appears when the Edit button is selected. This displays the Netscape: Preferences dialog box.

  4. In the window pane on the left of the Netscape: Preferences dialog box, click on the Advanced tab. This displays the advanced Communicator preferences in the dialog box.

  5. If the box next to the Enable Java preference has a check mark in it, click on the box to remove the check mark. This will disable the Java programming language. Then, click on the Okay button in the Advanced preferences dialog box. (Note: If there is no check mark in the box, you do not need to take any action.)

  6. Exit Netscape Communicator by clicking on the Exit option in the drop down menu that appears when you click on the File button on the toolbar at the top of the Navigator window.

Disabling Java ensures Netscape Communicator is not vulnerable to the Brown Orifice vulnerability. You do not have to disable JavaScript.

Note

If you use the Japanese or Chinese interfaces provided in the Worldwide Language Support software, you must update the Communicator version numbers in the /usr/lib/X11/*/app-defaults/Netscape file if you choose to upgrade to Netscape Communicator Version 4.75 or later.

If the version numbers in these files do not match the version of Netscape Communicator installed, it will not run in the Japanese or Chinese locales.

You can download the updated files from the Compaq Tru64 UNIX World Wide Web site:

http://www.tru64unix.compaq.com/internet/download.htm