1    Release Notes

This chapter provides information that you must be aware of when working with Tru64 UNIX 4.0F and TCR 1.6 Patch Kit-0005.

1.1    Required Storage Space

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

Base Operating System

TruCluster Software Products

1.2    New dupatch Features

Beginning with Revision 26-02 of dupatch, this patch tool utility has been enhanced to provide new features, as described in the following sections. For more information, see the Patch Kit Installation Instructions.

1.2.1    Patch Installation from Multiuser Mode

Patches can now be installed when a system is in multiuser mode.

There are no restrictions on performing patch selection and preinstallation checking in multiuser mode.

However, although you can now install patches in multiuser mode, Compaq recommends that you bring down your system to single-user mode when installing patches that affect the operation of the Tru64 UNIX operating system (or the product you are patching). If your system must remain in multiuser mode, it is recommended that you apply the patches when the system is as lightly loaded as possible.

1.2.2    Automatic Kernel Build

If the patches installed indicate that a kernel build is required, dupatch will initiate the kernel build automatically.

Most times a reboot is required to complete the installation and bring the system to a consistent running environment. Certain file types, such as libraries, are not moved into place until you reboot the system.

When installing patches in multiuser mode, you can take one of three options after the kernel build is complete:

1.2.3    Patch Installation from a Pseudo-Terminal

Patches can now be installed on the system from a pseudo-terminal (pty) while in single-user mode. To do this, log into the system as root from a remote location and specify that the patches are to be installed in single-user mode. Once all the patch prerequisites are completed, the system will be taken to single-user mode while maintaining the network connection for the root user. The patches will then be installed by the system.

1.3    Release Notes for Tru64 UNIX Patches 342.00 and 465.00

This release notes contains the new reference page for ttauth.

NAME
 
  ttauth - ToolTalk authority file utility
 
SYNOPSIS
 
  ttauth [[-f] | [authfile] ] [[-vqib] ] [[command arg ...] ]
 
DESCRIPTION
 
  The ttauth program is used to edit and display the authorization
  information used in connecting to ToolTalk.  This program is usually used
  to extract authorization records from one machine and merge them in on
  another (as is the case when using remote logins or granting access to
  other users).  Commands (described below) may be entered interactively, on
  the ttauth command line, or in scripts.  Note that this program does not
  contact the ToolTalk server, ttsession.  Normally ttauth is not used to
  create the authority file entry in the first place; ttsession does that.
 
OPTIONS
 
  The following options may be used with ttauth. They may be given
  individually or may combined.
 
  -f authfile 
             This option specifies the name of the authority file to use.
              By default, ttauth uses the file specified by the TTAUTHORITY
              environment variable or the .TTauthority file in the user's
              home directory.
 
  -q         This option indicates that ttauth should operate quietly and
              not print unsolicited status messages. This is the default if
              an ttauth command is given on the command line or if the
              standard output is not directed to a terminal.
 
  -v         This option indicates that ttauth should operate verbosely and
              print status messages indicating the results of various
              operations (for example, how many records have been read in or
              written out). This is the default if ttauth is reading commands
              from its standard input and its standard output is directed to
              a terminal.
 
  -i          This option indicates that ttauth should ignore any authority
              file locks. Normally, ttauth refuses to read or edit any
              authority files that have been locked by other programs
              (usually ttsession or another ttauth).
 
  -b         This option indicates that ttauth should attempt to break any
              authority file locks before proceeding. Use this option only to
              clean up stale locks.
 
COMMANDS
 
  The following commands may be used to manipulate authority files:
 
  add protoname protodata netid authname authdata
              An authorization entry for the indicated ToolTalk session using
              the given protocol name (protoname), protocol data (protodata),
              ToolTalk session id (netid), authentication name (authname),
              and authentication data (authdata) is added to the
              authorization file. The protocol name should always be the
              string "TT". The protocol data should always be the empty
              string. The ToolTalk session ID is formatted string consisting
              of the ttsession program number, the ttsession authorization
              level, the IP address of the host running ttsession, and the
              RPC version number of the ttsession. See the TTSESSION
              IDENTIFIERS section below for information on constructing
              ToolTalk session ID's for the authority file. The
              authentication name should always be the string "MIT-MAGIC-
              COOKIE-1". The authentication data is specified as an even-
              lengthed string of hexadecimal digits, each pair representing
              one octet. The first digit of each pair gives the most
              significant 4 bits of the octet, and the second digit of the
              pair gives the least significant 4 bits.  For example, a 32
              character hexkey would represent a 128-bit value.
 
  [n]extract filename                  
              Authorization entries which match the specified fields are
              written to the indicated file. If the nextract command is used,
              the entries are written in a numeric format suitable for non-
              binary transmission (such as secure electronic mail). The
              extracted entries can be read back in using the merge and
              nmerge commands.  If the file name consists of just a single
              dash, the entries will be written to the standard output.
 
  [n]list                 
              Authorization entries which match the specified fields (or all
              if nothing is specified) are printed on the standard output.
              If the nlist command is used, entries are shown in the numeric
              format used by the nextract command; otherwise, they are shown
              in a textual format.  Key data is always displayed in the
              hexadecimal format given in the description of the add command.
 
  [n]merge [filename1  ...]
              Authorization entries are read from the specified files and are
              merged into the authorization database, superseding any
              matching existing entries. If the nmerge command is used, the
              numeric format given in the description of the extract command
              is used.  If a file name consists of just a single dash, the
              standard input will be read if it hasn't been read before.
 
  remove                  
              Authorization entries which match the specified fields are
              removed from the authority file.
 
  source filename
              The specified file is treated as a script containing ttauth
              commands to execute. Blank lines and lines beginning with a
              pound sign (#) are ignored. A single dash may be used to
              indicate the standard input, if it has not already been read.
 
  info        
              Information describing the authorization file, whether or not
              any changes have been made, and from where ttauth commands are
              being read is printed on the standard output.
 
  exit       
              If any modifications have been made, the authority file is
              written out (if allowed), and the program exits. An end of file
              is treated as an implicit exit command.
 
  quit       
              The program exits, ignoring any modifications. This may also be
              accomplished by pressing the interrupt character.
 
  help [string]
               A description of all commands that begin with the given string
              (or all commands if no string is given) is printed on the
              standard output.
 
  ?           
              A short list of the valid commands is printed on the standard
              output.
 
TTSESSION IDENTIFIERS
 
  The ToolTalk session identifiers (netid) in the authority file and used by
  the add, [n]extract, [n]list, and remove commands are derived from the
  TT_SESSION identifier constructed by ttsession at startup.  The ttsession
  rendezvous with clients by writing the TT_SESSION identifier as a property
  on the root window or as an environment variable in the client's
  environment (see ttsession -c). In addition, ttsession creates an entry in
  the user's authority file.  The authority file entry has a netid component
  which is derived from the TT_SESSION identifier.
 
  The TT_SESSION(STRING) = "01 1433 1342177279 1 1 2002 130.105.9.22 4"
  identifier is composed of the following elements:
 
    <Dummy Number>                        = 01
    <ttsession Process Id>                = 1433
   <ttsession Program Number>       = 1342177279
   <DummyNumber>                         = 1
   <ttsession Authorization Level>  = 1
   <ttsession UID>                            = 2002           
   <Host IP Address>                       = 130.105.9.22
   <RPC Version Number>               = 4
 
The ToolTalk session identifiers (netid) in the authority file are composed
  of the <ttsession Program Number>,  <ttsession Authorization Level>,  <Host
  IP Address>, and <RPC Version Number> fields of the TT_SESSION identifier
  as follows:
 
  1342177279/1/130.105.9.22/4
 
EXAMPLE
 
  The most common use for ttauth is to extract the entry for the current
  ttsession, copy it to another machine, and merge it into the user's
  authority file on the remote machine:
 
  % xprop -root | grep TT_SESSION
 
  TT_SESSION(STRING) = "01 1433 1342177279 1 1 2002 130.105.9.22 4"
  _SUN_TT_SESSION(STRING) = "01 1433 1342177279 1 1 2002 130.105.9.22 4"
 
  % ttauth extract - netid=1342177279/1/130.105.9.22/4 | rsh otherhost ttauth
  merge -
 
ENVIRONMENT
 
  This ttauth program uses the following environment variables:
 
  TTAUTHORITY 
  Gets the name of the authority file to use if the -f option is not used.
 
FILES
 
  .TTauthority
              Default authority file in the user's home directory if
              TTAUTHORITY is not defined.
 
RESTRICTIONS
 
  Users that have unsecure networks should take care to use encrypted file
  transfer mechanisms to copy authorization entries between machines.
  Similarly, the MIT-MAGIC-COOKIE-1 protocol is not very useful in unsecure
  environments.  Sites that are interested in additional security may need to
  use encrypted authorization mechanisms such as Kerberos.
 
  Spaces are currently not allowed in the protocol name.  Quoting could be
  added for the truly perverse.
 
SEE ALSO
 
  Commands:  ttsession(1)
 
  ToolTalk Reference Manual
 
 
The options section of the ttsession manpage should now look like this:
 
 
  -a level
        Set the server authentication level.  The following level string
        values are supported:
 
        cookie  
        The sender and receiver must share the same cookie.  This
        means that messages which do not specify a handler "ptype"
        are delivered even if the cookies do not match.  This is the
         default authorization scheme.  For "full security" use the -F
          option.  Refer to the ttauth(1) reference page for more
          information.

1.4    Release Notes for Tru64 UNIX Patch 505.00

This section contains release notes for Patch 505.00.

1.4.1    UFS Delayed Metadata mount Option

This new mount option allows for disabling synchronous metadata writes on a specified filesystem. The new mount option name is delayed.

To maintain the file system's consistency, UFS metadata (such as inode, directory, and indirect blocks) is updated synchronously by default.

Metadata updates are typically performed synchronously to prevent filesystem corruption after a crash. The trade-off for this filesystem integrity, however, is performance. In some cases, such as a filesystem serving as a cache, performance (faster metadata update) is more important than preserving data consistency across a system crash; for example, files under /tmp or web proxy servers such as Squid.

This means two things. One is that multiple updates to one block becomes only one block write, as opposed to multiple writes of the same block with traditional synchronous metadata update. The other is that users can experience much better responsiveness when they run metadata intensive applications because metadata writes will not go out to the disk immediately while users get their prompt back as soon as the metadata updates are queued.

This delayed option should not be used on the / or /usr filesystems. It should be used only on filesystems that do not need to survive across a system crash.

To enable the delayed option, run:

mount -o delayed

or

mount -u -o delayed mount -u -o delayed

1.4.2    3DLabs Oxygen VXI Graphics Card

This patch provides the driver support for the 3DLabs Oxygen VX1 graphics card. In order to obtain full support for this graphics card, you must also select Patch 194.00, which is the X server portion of the patch.

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

To reconfigure and rebuild the kernel, 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/update

  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 3DLabs Oxygen VX1 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 3DLabs Oxygen VX1 graphics card as described you will need to rebuild the kernel again to restore generic VGA graphics support. To do this, follow the steps given previously. The doconfig utitlity running on the original, unpatched genvmunix will not recognize the 3DLabs Oxygen VX1 graphics card and will include generic VGA graphics support in the resulting kernel.

1.4.3    PCI To Ethernet/Graphics Combo Adapter (3X-DEPVD-AA)

This patch provides the driver support for the PCI To Ethernet/Graphics Combo Adapter (3X-DEPVD-AA) (also known as the ITI6021E Fast Ethernet NIC 3D Video Combination Adapter, InterServer Combo, or JIB). To obtain full support for the PCI To Ethernet/Graphics Combo Adapter (3X-DEPVD-AA), you must also select Patch 359.00, which is the X server portion of the patch.

1.4.4    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.4.5    Intelligent I/O Disks with mnemonic ri

If Patch 505.00 is installed on a system with Intelligent I/O (I2O) disks that use the device identifier, mnemonic ri, Patch 571.00 should also be installed if the user uses the diskconfig utility. Without Patch 571.00, the diskconfig utility will not recognize or configure the Intelligent I/O (I2O) disks.

1.4.6    Virtual Memory Problem

Installing Patch 505.00 on a system running Tru64 UNIX 4.0D through 4.0F may cause the system to crash if you run an application that maps a large number of file system objects into virtual memory using the mmap(2) function call. This problem may occur with large threaded applications, such as the Netscape Enterprise Web Server, which use this technique to improve performance and scalibility.

To avoid this problem, disable the kernel's virtual memory (vm:) subsystem attribute vm-map-index-enable after installing the patch and before rebooting the system. The attribute is disabled when its value is set to zero at boot time.

Enter the following commands at the shell prompt (when logged in as root) to add or modify the vm-map-index-enable attribute entry in the /etc/sysconfigtab file:

$ su root
$ cat << _EOF_ > /tmp/vm.stanza
> vm:
> vm-map-index-enabled=0
> _EOF_
$ sysconfigdb -m -f /tmp/vm.stanza vm
$rm -f /tmp/vm.stanza
$ reboot

See the sysconfigdb(8) man page for additional information.

This problem will be fixed in the next release of the patch kits.

1.4.7    PCI To Ethernet/Graphics Combo Adapter

This patch provides support for the PCI To Ethernet/Graphics Combo Adapter (3X-DEPVD-AA). If you have a system with this adapter, you will need to reconfigure and rebuild the kernel after installing this patch. To do this:

  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 PCI To Ethernet/Graphics Combo Adapter.

  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 PCI To Ethernet/Graphics Combo Adapter as previously described, you will need to rebuild the kernel again to restore generic VGA graphics support. To do this, follow the steps previously given.

If doconfig is running on the original kernel, the unpatched genvmunix will not recognize the PCI To Ethernet/Graphics Combo Adapter and will include generic VGA graphics support in the resulting kernel.

1.4.8    Pleiades II Switches

To determine if target IDs are being consumed by the switch, look at the contents of the /etc/emx.info file. If a FC Port Name exists that does not start with 0x0050 (a HSG80) or a 0x0010 (a KGPSA), it is most likely a switch entry consuming the target ID (or an unsupported FC device exists on the fabric).

To remove the switch entry from the emx target ID mappings, in addition to installing this patch, the /sys/data/emx_data.c file must be modified to contain the switch entry to be deleted (by setting the target ID to -1). See the reference pages for emx and emx_data.c for instructions on modifying the emx_data.c file. After the emx_data.c file has been modified, the kernel must be regenerated and the resulting kernel booted.

1.4.9    I/O Throttling/Smooth Sync

Note

Smooth Sync is for UNIX File System (UFS) only.

Note

To activate I/O Throttling/Smooth Sync, you must install Patch 299.00.

The new mount options are smsync2 and throttle. The smsync2 option enables an alternate smsync policy in which dirty pages do not get flushed until they have been dirty and idle for the smoothsync age period (the default 30 is seconds). The default policy is to flush dirty pages after being dirty for the smoothsync age period, regardless of continued modifications to the page. Note that mmaped pages always use this default policy, regardless of the smsync2 setting.

For example, change the /etc/fstab entries from:

/dev/rz12e /mnt/test ufs rw 0 2

to:

/dev/rz12e /mnt/test ufs rw,smsync2,throttle 0 2

Note

If you choose not to use smsync2 (which does not affect mmaped buffers), just remove the smsync2 option from the previous string.

Append any tuning changes to /etc/sysconfigtab. See the TUNING notes that follow for a description of the new io-throttle-shift and io-throttle-maxmzthruput tunables. These tunables are configured in the vfs stanza. The following three lines make up an example:

vfs:

io-throttle-shift = 1

io-throttle-maxmzthruput = 1

When removing this patch, follow these steps:

  1. Remove the lines added above to /etc/inittab.

  2. Remove any additions to /etc/fstab you may have made (see previous instructions).

Failure to remove /etc/inittab and /etc/fstab modifications may result in unknown attribute messages, particularly upon system reboot.

TUNING

The purpose of this patch is to minimize system stalls resulting from a heavy system I/O load. This patch introduces a smoothsync approach to writing delayed I/O requests and introduces I/O throttling.

Using smoothsync allows each dirty page to age for a specified time period before getting pushed to disk. This allows more opportunity for frequently modified pages to be found in the cache, which decreases the net I/O load. Also, as pages are enqueued to a device after having aged sufficiently, as opposed to getting flushed by the update daemon, spikes are minimized in which large numbers of dirty pages are locked on the device queue.

I/O throttling further addresses the concern of locking dirty pages on the device queue. It enforces a limit on the number of delayed I/O requests allowed to be on the device queue at any point in time. This allows the system to be more responsive to any synchronous requests added to the device queue, such as a read or the loading of a new program into memory. This may decrease the duration of process stalls for specific dirty buffers, as pages remain available until placed on the device queue.

The relevant tunable variables are:

smoothsync-age

This variable can be adjusted from 0 (off) up to 300. This is the number of seconds a page ages before becoming eligible for being flushed to disk via the smoothsync mechanism. A value of 30 corresponds to the "guarantee" provided by the traditional UNIX update mechanism. Increasing this value increases the exposure of lost data should the system crash, but can decrease net I/O load (to improve performance) by allowing the dirty data to remain in cache longer. In some environments, any data that is not up to date is useless; these are prime candidates for an increased smoothsync-age value. The default value of smoothsync-age is 30.

io-throttle-shift

The greater the number of requests on an I/O device queue, the longer the time required to process those requests and make those pages and device available. The number of concurrent delayed I/O requests on an I/O device queue can be throttled by setting the io-throttle-shift tunable. The throttle value is based on this tunable and the calculated I/O completion rate. The throttle value is proportional to the time required to process the I/O device queue. The correspondences between io-throttle-shift values and the time to process the device queue are:

io-throttle-shift  time to process device queue (sec)
-------------------------------------------------------------------      -2                   0.25
      -1                   0.5
       0                   1
       1                   2
       2                   4

For example, an io-throttle-shift value of 0 corresponds to accommodating 1 second of I/O requests. The valid range for this tunable is [-4..4] (not all values are shown in the previous table; you can extrapolate). The default value of io-throttle-shift is 1. Environments particularly sensitive to delays in accessing the I/O device might consider reducing the io-throttle-shift value.

io-maxmzthruput

This is a toggle that trades off maximizing I/O throughput against maximizing the availability of dirty pages. Maximizing I/O throughput works more aggressively to keep the device busy, but within the constraints of the throttle. Maximizing the availability of dirty pages is more aggressive at decreasing stall time experienced when waiting for dirty pages.

The environment in which you might consider setting io-maxmzthruput off (0) is one in which I/O is confined to a small number of I/O-intensive applications, such that access to a specific set of pages becomes more important for overall performance than does keeping the I/O device busy. The default value of io-maxmzthruput is 1. Environments particularly sensitive to delays in accessing sets of frequently used dirty pages might consider setting io-maxmzthruput to 0.

1.4.10    Granularity Hint Regions Restriction Removal

This patch removes a Granularity Hint Regions (also called GH chunks) restriction which may be encountered on AlphaServerTMTM DS20 and ES40 systems running the Tru64 UNIX Version 4.0F release. This restriction can reduce performance for certain database applications.

The following error message on the system's console terminal (also logged in /var/adm/messages) indicates possible performance loss for applications using GH chunks:

gh_chunks value of # invalid

where # is a number that varies depending on memory size.

To remove the GH chunks restriction, you need to modify your target kernel configuration file (and rebuild the kernel) and change the state of a console firmware environment variable. To make these changes, follow these steps:

  1. Follow the steps in Section 4.5.3 of the Guide to System Adminstration, with the following exceptions:

    In step 4, edit the configuration file and add the following line immediately before the first line starting with makeoptions:

    makeoptions LOADADDR="fffffc0000430000"

    In step 6, instead of /usr/sbin/shutdown -r now, add the following line:

    /usr/sbin/shutdown -h now

  2. Check the console firmware version:

    P00>>>show version

    If the version is not V5.5 or later, you need to upgrade your firmware to V5.5 or later.

  3. Change the value of the console_memory_allocation environment variable from old to new and reset the system:

    P00>>>set console_memory_allocation new

    P00>>>init

  4. Boot the new kernel:

    P00>>>boot

    If the new kernel fails to boot use one of the following procedures:

    P00>>>set console_memory_allocation old

    P00>>>init

    P00>>>boot -fi vmunix.save

    or:

    P00>>>boot -fi genvmunix

    Correct the error and repeat the previous procedure.

Additional Information

Note

If you customized your existing configuration file, doconfig allows you to edit the new configuration file so you can restore your customizations.

1.5    Release Notes for Tru64 UNIX Patches 476.00 and 511.00

The following release notes provide Visual Threads Upgrade information and updated information for the quotacheck(8), fsck(8), and fstab(4) reference pages.

1.5.1    Visual Threads Upgrade Required

Visual Threads users will need to upgrade to the latest version of Visual Threads for the race detection rules to work. The Visual Threads upgrade is available from http://www.tru64unix.compaq.com/visualthreads and will be available in the next Developers' Tooklit Supplement.

1.5.2    quotacheck(8), fsck(8), and fstab(4) Reference Pages

quotacheck(8) Reference Page Update

  SYNOPSIS
 
    /usr/sbin/quotacheck [-guv] filesystem ...
 
  OLD>  /usr/sbin/quotacheck -a [-guv] [-l number]
  NEW>  /usr/sbin/quotacheck -a [-guv] [-l number] [-t [no]type]
 
 
  FLAGS
 
  OLD>  -a    Checks all file systems identified in the /etc/fstab file
              as read/write with disk quotas.
 
  NEW>  -a    Checks all UFS and AdvFS file systems identified in the
              /etc/fstab file as read/write with userquota and/or
              groupquota options specified, and a pass number of 1 or
              greater.  If the -t option is specified, only the file systems
              of the specified type will be checked.  Alternatively, if
              type is prefixed with 'no', then the valid file systems in
              the /etc/fstab file that do not have that type will be
              checked.
 
 
  OLD>  -l    number Specifies the number of times to perform disk quota
              checking.
 
  NEW>  -l    number Specifies the maximum number of parallel quotacheck
              processes to run at one time.
 
  NEW>  -t    [no]type
  NEW>        Specifies the file system type.  The supported file systems are 
              as follows:
 
              advfs - Advanced File System (AdvFS)
 
              ufs - UNIX File System (UFS)
 
              See fstab(4) for a description of file system types.  If
              the 'no'  prefix is used, all of the above file types
              except the one specified are checked.
 
              Note, the -t flag is only valid when used with the -a flag.
 
  DESCRIPTION
 
  OLD>  The quotacheck command examines each specified file system, builds a
        table of current disk usage, and compares this table against that
        stored in the disk quota file for the file system.  If any
        inconsistencies are detected, both the quota file and the current
        system copy of the incorrect quotas are updated.  Each file system
        must be mounted with quotas enabled.
 
  NEW>  The quotacheck command examines each specified file system, builds a
        table of current disk usage, and compares this table against that
        stored in the disk quota file for the file system.  If any
        inconsistencies are detected, both the quota file and the current
        system copy of the incorrect quotas are updated.
 
  OLD>  The quotacheck command runs parallel passes on file systems using
        the number specified in the fsck field of the file system's entry in
        the /etc/fstab file.  The quotacheck command only checks file
        systems with pass number 1 or higher in the fsck field.  A file
        system with no pass number is not checked.
 
  NEW>  The quotacheck -a command runs parallel passes on file systems using
        the number specified in the /etc/fstab pass number field.  The
        quotacheck command only checks file systems with pass number 1 or
        higher in the fsck field.  A file system with no pass number is
        not checked.
 
  OLD>  For both UFS file systems and AdvFS filesets, you should assign the
        root file system a fsck field value of 1, and a value of 2 or
        higher to other file systems.  See fstab(4) for more information.
 
  NEW>  For both UFS file systems and AdvFS filesets, you should assign the
        root file system a pass number of 1, and a value of 2 or higher
        to other file systems.  See fstab(4) for more information.
 
  OLD>  The quotacheck command checks only file systems that have the
        userquota or groupquota option specified in the /etc/fstab file.
 
  NEW>  The quotacheck command checks only file systems that are mounted.
        UFS file systems must also have userquota and/or groupquota options
        specified in the /etc/fstab file.  The userquota and groupquota
        options are only needed for AdvFS file systems if quotas are
        actually going to be enforced or if they are to be selected with the 
        -a option.

fsck(8) Reference Page Update

OLD>  When the system boots, the fsck program is automatically
        run with the -p flag.  The program reads the /etc/fstab file to
        determine which file systems to check.  Only partitions that 
        are specified in the fstab file as being mounted ``rw'' or 
        ``ro'' and that have a non-zero pass number are checked.  
        File systems that have a pass number 1 
        (usually only the root file system) are checked one at a time.  
        When pass 1 completes, all the remaining file systems are
        checked, with one process running per disk drive.
 
  NEW>  When the system boots, the fsck program is automatically
        run with the -p flag.  The program reads the /etc/fstab file to
        determine which file systems to check.  Only partitions that 
        are specified in the fstab file as being mounted ``rw'' or 
        ``ro'' and that have a non-zero pass number are checked.  
        File systems that have a pass number 1
        (usually only the root file system) are checked one at a time.  
        When pass 1 completes, the remaining pass numbers are processed
        with one parallel fsck process running per disk drive in the 
        same pass.
 
  NEW>  The per disk drive logic is based on the /dev/disk/dsk0a
        syntax where different partition letters are treated as being 
        on the samedisk drive.  Partitions layered on top of an LSM 
        device may not follow this naming convention.  In this case 
        unique pass numbers in /etc/fstab may be used to sequence fsck 
        checks.

fstab(4) Reference Page Update

 userquota [=filename] and groupquota [=filename]
 
        If quotas are to be enforced for users or groups,
        one or both of the options must be specified.  If 
        userquota is specified, user quotas are to be enforced.  
        If groupquota is specified, group:
 
  OLD>  quotas are to be enforced.
 
  NEW>  quotas are to be enforced (also see quotaon and quotaoff(8)).
 
 
  OLD>  For UFS  file systems, the sixth field (fsck) is used by 
        the fsck command to determine the order in which file system
        checks are done at reboot time.  For the root file system, 
        specify 1 in the fsck field. For other UFS file systems, 
        specify 2 or higher in the fsck field.  Each UFS file system 
        should have a unique fsck value.
 
  NEW>  For UFS  file systems, the sixth field (pass number) is
        used by the fsck and quotacheck commands to determine the 
        order in which file system checks are done at reboot time.  
        For the root file system, specify 1 in the fsck field.  For 
        other UFS file systems specify 2 or higher in the pass number 
        field.
 
  OLD>  For AdvFS filesets, the sixth field is a pass number
        field that allows the quotacheck command to perform all of the
        consistency checks needed for the fileset.  For the root file 
        system, specify 1 in the fsck field.  Each AdvFS fileset in 
        an AdvFS file domain should have a unique fsck value, which 
        should be 2 or higher.
 
  NEW>  For AdvFS filesets, the  sixth field is a pass number
        field that allows the quotacheck command to perform all of the
        consistency checks needed for the fileset.  For the root file 
        system, specify 1 in the fsck field.  For other AdvFS file 
        systems specify 2 or higher in the pass number field.
 
  OLD>  File systems that are on the same disk are checked
        sequentially, but file systems on different disks are 
        checked at the same time to utilize parallelism available 
        in the hardware.  If the sixth field is not present or zero, 
        a value of 0 is returned and the fsck command
        assumes that the file system does not need to be checked.
 
  NEW>  File systems that are on the same disk or domain are checked
        sequentially, but file systems on different disks or
        domains but with the same or greater than 1 pass number are 
        checked at the same time to utilize parallelism available in 
        the hardware.  When all the file systems in a pass have 
        completed their checks, then the file systems with the 
        numerically next higher pass number will be processed.
 
  NEW>  The UFS per disk drive logic is based on the
        /dev/disk/dsk0a syntax where different partition letters 
        are treated as being on the same disk drive.  Partitions 
        layered on top of an LSM device may not follow this naming 
        convention.  In this case unique pass numbers may be used
        to sequence fsck and quotacheck processing.  If the sixth 
        field is not present or zero, a value of 0 is returned
        and the fsck command assumes that the file system does
        not need to be checked.

1.6    Release Note for Patch 315.00

This is a release note for the Enhanced Round Robin Sequential Read Patch.

If the system configurable parameter lsm:lsm_V_ROUND_enhanced is set (value = 1) the enhanced read round robin policy is activated. This new policy stores the last block accessed by the previous I/O request. When returning for another block in round robin (V_ROUND) mode, that value is compared to the current read. If it is within a predefined, user-configurable value (lsm:lsm_V_ROUND_enhance_proximity), then the same plex is used. Otherwise the next plex is used as for a normal round robin behavior.

The two new additional tunable parameters are lsm_V_ROUND_enhanced set to 1 by default (V_ROUND read is activated) and lsm_V_ROUND_enhance_proximity is set to 512 by default.

Append any tuning changes to/etc/sysconfigtab. See the TUNING notes below for a description of the new lsm_V_ROUND_enhanced and lsm_V_ROUND_enhance_proximity tunables. These tunables are configured in the lsm stanza. For example:

lsm:

lsm_V_ROUND_enhanced = 1

lsm_V_ROUND_enhance_proximity = 1024

Note

If you already have an lsm stanza in your sysconfigtab file, add the two lsm_V_ROUND entries.

TUNING

The purpose of this patch is to increase performance with sequential reads. This patch introduces a new enhanced round robin mode where the last block read is now compared to the next block to read and a check is added to see if last block number-next block number is less than or equal to lsm_V_ROUND_enhance_proximity. If it is, read from the same plex. This is to attempt to hit the disk cache, and so increase performance.

The relevant tunable variables are as follows:

lsm_V_ROUND_enhanced

This variable activates the new enhanced round robin read policy if it is set to TRUE (1). Otherwise the policy is deactivated.

DEFAULT = 1

lsm_V_ROUND_proxmity

This variable provides the proximity in which the last read and new read most lie in an attempt to read data from the disk's cache by reading from the same plex. The variable can be adjusted from 0 to 4096.

DEFAULT = 512

1.7    Release Note for Patch 351.00

For more information about the functionality provided and special installation instructions related to this patch, please refer to the online README file located at:

http://www.service.digital.com/patches/

From this URL directory, click on the following link:

duv40fwlseco2.README

Note

It may be necessary to navigate additional directories below this top level URL to find the specific README file related to this patch.

1.8    Release Notes for Tru64 UNIX Patch 577.00

This patch provides the X server support for the new 3Dlabs OXYGEN VX1 PCI graphics card. In order to obtain full support for this graphic card, you must also select Patch 505.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.9    Release Note for Tru64 UNIX Patch 592.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_v40g.tar.gz, available from:

http://ftp1.support.compaq.com/public/unix/v4.0g

1.10    Release Note for TruCluster DRD Workaround

Adding a new member to an existing cluster will fail under the following conditions:

To work around this problem, you must update the data base using the Enable ASE V1.6 functionality option from the Managing the ASE menu on the existing member prior to attempting to add the new member. Thus, the new member will be added with a V1.6-type ASE data base and will proceed successfully.

A patch will be in released in the near future.