Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_XFC-V0200 Alpha V7.3 XFC ECO Summary
TITLE: OpenVMS VMS73_XFC-V0200 Alpha V7.3 XFC ECO Summary
 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
 
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
 
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.
 

New Kit Date:       13-AUG-2002
Modification Date:  Not Applicable
Modification Type:  NEW KIT

Copyright (c) Compaq Computer Corporation 2001,2002.  All rights reserved.

OP/SYS:     OpenVMS Alpha

COMPONENT:  XFC

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VMS73_XFC-V0200
                    DEC-AXPVMS-VMS73_XFC-V0200--4.PCSI
     ECO Kits Superseded by This ECO Kit:  VMS73_XFC-V0100 
     ECO Kit Approximate Size:  13056 Blocks
     Kit Applies To: OpenVMS Alpha V7.3
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_2
                             2 : To  be  installed  by   all  customers  using  the  following
     			         feature(s):XFC
     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:

         VMS73_UPDATE-V0100 

       In order to receive all the corrections listed in this
       kit, the following remedial kits should also be installed:

         None 


ECO KIT SUMMARY:

An ECO kit exists for XFC components on OpenVMS Alpha V7.3.  
This kit addresses the following problems:


PROBLEMS ADDRESSED IN VMS73_XFC-V0200 KIT

     o  Because of numerous problems reported  against  XFC  in  V7.3,
        customers  were instructed to disable XFC for V7.3 until these
        issues could be addressed.  This kit fixes all  problems  with
        XFC  reported  by customers as of 16 July 2002.  Once this kit
        is installed XFC can be  safely  re-enabled.   Note  that  all
        these issues were corrected for OpenVMS V7.3-1.

          Specific issues addressed are:

          1.  Process or System hangs

               o  XFC internal structures describing cached files  could
                  be deleted while an active operation for that file was
                  stalled.   The  stalled  operation  would   never   be
                  restarted.   This would result in processes being left
                  in RWAST with other processes waiting for  release  of
                  file system locks.

               o  If a blocking  AST  was  processed  on  the  XFC  File
                  Arbitration  lock  while  a readahead was in progress,
                  the readahead would be dismissed, but the blocking AST
                  was  not  restarted.   This would result in subsequent
                  I/Os to this file stalling.

               o  In a cluster with both VIOC and XFC nodes, XFC  queues
                  a  NL  (null) to CW (concurrent write) lock conversion
                  without specifying a lock conversion  priority.   This
                  results  in  a  deadlock.  This is often seen with the
                  file  arbitration  lock  for  SYSUAF.DAT,  making   it
                  impossible to log into the cluster.

               o  Under some conditions, a readahead I/O is not properly
                  cleaned  up  after  an I/O completes with an error.  A
                  subsequent close of the file will  hang,  waiting  for
                  the readahead to complete.

               o  If a file lock transition is in progress at the time a
                  deaccess  was started, it is possible for the deaccess
                  not to  be  restarted.   This  results  in  a  process
                  hanging in RWAST state.

               o  Under very low memory conditions, XFC could get into a
                  state in which there was not enough memory to make any
                  progress on I/Os.   This  fix  increases  the  default
                  amount  of  memory allocated to XFC at boot time to be
                  sufficient to make progress regardless of  how  little
                  free memory is available at any time.

               o  The server process for host-based  RAID  can  hang  in
                  mutex  wait  state.  This is caused by the logical I/O
                  processing of XFC not recognizing that it is  safe  to
                  allow the logical I/O to proceed.


          2.  Stale data in files

              In a cluster, there are several situations under which XFC
              could  leave  stale  data  in  the  cache for a file.  The
              symptom  would  be  that  a  file  would  appear  to  have
              different  data  when  viewed  from  different  nodes in a
              cluster.

               o  File truncate processing would leave data in the cache
                  for  a  file, and the file arbitration lock in a state
                  only appropriate for no valid data.

               o  Under some conditions, QIO write updates to files read
                  using paging I/O would not be seen on other nodes in a
                  cluster.


          3.  File corruption

               o  Large  files  copied  from  IDE  CD  drives  could  be
                  corrupt.   This  is the result of XFC not honoring the
                  maximum I/O size specified by the driver.

               o  Updates to files on a DFS-served device are not  being
                  seen.   The  DFS  server  bypasses the cache for write
                  I/Os.  XFC was  missing  these  writes  and  therefore
                  leaves stale data in the cache for these files.

               o  An example program that uses fastio to implement  file
                  copy  fails  to  copy  the last block of a file copied
                  from a device that did not support fastio  (e.g.   IDE
                  CD or a RAM disk).


          4.  System Crashes

               o  Under heavy loads, XFC would use a  fork  block  twice
                  resulting  in  a corrupt fork queue and a system crash
                  (typically a system service exception).

               o  If a blocking AST for a file arbitration lock fired at
                  exactly  the  same time as that file was being deposed
                  for dismount, then XFC would eventually bugcheck  with
                  either  an XFC ASSERTFAIL bugcheck or a system service
                  exception.

               o  In a cluster, XFC could retain data for a  file  on  a
                  node  that  was  caching  the  file  when the file was
                  deleted on a node not caching the file.  This resulted
                  in  stale  data  in  cache after the file was deleted.
                  Under some conditions, XFC would call the file  system
                  with  the  old,  incorrect  highwater mark information
                  resulting in an XQPERR bugcheck.

               o  Readahead I/Os are sometimes issued after a  file  has
                  been  deaccessed.   If the readahead requires either a
                  file system mapping operation or a window  turn,  then
                  the  system  could  crash  with  either a NOTWCBIRP or
                  STRNOTWCB bugcheck.

               o  XFC uses an uninitialized variable as the saved IPL to
                  a  spinlock  release  routine.   On  some  systems (in
                  particular AS400),  this  results  in  a  machinecheck
                  bugcheck.

               o  XFC would crash attempting to do reads  or  writes  to
                  devices not supporting fastio.


          5.  Halt during boot.

              If XFC detects system configurations that will  not  allow
              XFC   to  run  properly,  XFC  will  halt  the  CPU  [with
              PAL_HALT()].  This causes  CPUSPINWAIT  bugchecks  on  SMP
              systems  that  take  extra  effort  to  diagnose.  XFC now
              prints a message on the console and adjusts the parameters
              MPW_HILIMIT and FREEGOAL to allow booting.

          6.  Set time flushes cache for system disk.

              The $settime() system service would result in XFC flushing
              all cached data for the system disk.

          7.  RAM disk caching state incorrect.

              By default, XFC mounts RAM disks NOCACHE.   However,  this
              was not happening in some circumstances.  XFC now disables
              XFC caching for locally mounted RAM disks.

          8.  RAM disk performance enhancement.

              I/O to a RAM disk is noticeably slowed when XFC is  turned
              on  for  a  system even if the disk were mounted /NOCACHE.
              This has now been corrected.

          9.  File sharing performance enhancement.

              If an application writes to a file open on multiple  nodes
              in  a  cluster,  XFC  stops caching for that file.  In the
              past, XFC would not resume caching for that file  even  if
              all  the  write  accessors  closed the file.  XFC will now
              move a file back to caching when write accessors close the
              file.

         10.  Cache hit performance improvement.

              The performance of cache hits has been improved.

         11.  Spurious XFCACHE-W-DATALOSS messages to OPCOM.

              XFC incorrectly assumes that reads  beginning  beyond  the
              file  high  water  mark  are an integral number of blocks.
              This results in the following problems:

               o  XFCACHE-W-DATALOSS messages to OPCOM when the XFC  I/O
                  completion  code  discovered  that the number of bytes
                  copied did not equal the number of bytes requested.

               o  Potential corruption in user program  space  when  the
                  bytes beyond the end of the user buffer were zeroed.


         12.  The system can crash with an  ASSERTFAIL,  "System  ASSERT
              failure detected" bugcheck.

              Crashdump Summary Information:
              ------------------------------
              Bugcheck Type:     ASSERTFAIL, System ASSERT failure detected
              Current Process:   CTM$_0005000C
              Current Image:     $3$DKC203:[SYS1.SYSCOMMON.][SYSEXE]COPY.EXE
              Failing PC:        FFFFFFFF.802EC6E0    XFCLOCKISFALHELD_C+00D60
              Failing PS:        30000000.00000804
              Module:            SYS$XFCACHE    (Link Date/Time: 11-JUN-2002 20:07:42.49)
              Offset:            000086E0

              The bugcheck might be seen doing a backup  copy  operation
              on  large,  busy systems.  It might also be seen on memory
              tight systems doing DCL copies.


          Images Affected:

           -  [SYS$LDR]SYS$XFCACHE.EXE

           -  [SYS$LDR]SYS$XFCACHE.DSF

           -  [SYS$LDR]SYS$XFCACHE.STB

           -  [SYS$LDR]SYS$XFCACHE_MON.EXE

           -  [SYS$LDR]SYS$XFCACHE_MON.DSF

           -  [SYS$LDR]SYS$XFCACHE_MON.STB

           -  [SYSLIB]XFC$SDA.EXE


PROBLEMS ADDRESSED IN VMS73_XFC-V0100 KIT:

  o  Within a cluster, processes may  seem  to  hang  in  an  RWAST
     state, as seen by the SHOW SYSTEM command.  Using SDA, and the
     SHOW PROC/LOCK command, the process will  be  seen  to  own  a
     F11B$xxx  type  resource  - or be waiting for one.  On the XFC
     node that has the originating problem,  repeated  use  of  the
     command:

          SDA> XFC SHOW CONTEXT/BRIEF

     will display a Close File CTX that never disappears:

     Extract from Sample SDA Output:

     OpenVMS (TM) Alpha Operating System, Version V7.3  
     -- System Dump Analysis ---

     Address          I/O Type               I/O Stall reason
     FFFFFFFF858AA310 eiotFALUpConversio ... estrLockUpConvRequ
     FFFFFFFF84F45F50 eiotFALUpConversio ... estrLockUpConvRequ
     FFFFFFFF86C269D0 eiotFALUpConversio ... estrLockUpConvRequ
     FFFFFFF8595CA50 eiotFALUpConversio ... estrLockUpConvRequ
                                .
                                .
                                .
                                .

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  Incorrect readahead operations can cause  data  corruption  on
     bound volume sets.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB

  o  An incorrectly selected UCB on segmented reads and writes  can
     cause data corruption on bound volumes.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB

  o  During  a  cluster  transition,  an  INVEXCEPTION   crash   at
     SYS$XFCACHE + 8240 can occur.

     Crashdump Summary Information:
     ------------------------------
       Crash Time:         2-MAY-2001 04:02:30.51
       Bugcheck Type:     INVPTEFMT, Invalid page table entry
                          format
       Node:              RM763B  (Cluster)
       CPU Type:          AlphaServer 4100 5/600 8MB
       VMS Version:       V7.3
       Current Process:   NULL
       Current Image:     
       Failing PC:        FFFFFFFF.800CD6DC
                          IOC_STD$PTETOPFN_C+0008C
       Failing PS:        28000000.00000804
       Module:            IO_ROUTINES    (Link Date/Time:
                          17-MAR-2001 03:30:01.24)
       Offset:            000056DC


        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                           [SYS$LDR]SYS$XFCACHE_MON.EXE
                           [SYS$LDR]SYS$XFCACHE.STB
                           [SYS$LDR]SYS$XFCACHE_MON.STB


  o  The system may hang or experience an INCONSTATE crash  due  to
     memory leaks.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYSLIB]XFC$SDA.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  When modifying the  SYSGEN  parameter  VCC_MAX_CACHE,  writing
     ACTIVE  and issuing the SET CACHE/RESET command, XFC would not
     quickly react to a reduction in  size.   Even  though  all  of
     memory  is  in use and processes are pagefaulting, the size of
     the XFC does  not  shrink  dynamically  as  documented.   This
     causes  a  lot  of  processes  to  hang  in  RWMPB  due to the
     inability to allocate out to their WSEXTENT.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYSLIB]XFC$SDA.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  An RESEXH bugcheck occurs with repeated use of FASTIO.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.SDA
                          [SYS$LDR]SYS$XFCACHE_MON.SDA

  o  When using XFC on a system using Software RAID to bind mounted
     Shadowsets,  the  RAID$SERVER process can hang in a MUTEX wait
     state.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  When XFC is called back to release memory, it  can  eventually
     get  locked up in a recursive call to itself trying to release
     memory it doesn't have.  This would usually lead to  a  system
     wide hang, but could possibly lead to CPUSPINWAITs also.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  The dynamic growth of XFC could not be set to larger than  50%
     of physical memory.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB
INSTALLATION NOTES:

This kit requires a system reboot.  Compaq strongly recommends that
a  reboot  is performed immediately after kit installation to avoid
system instability

If you have other nodes in your OpenVMS cluster, they must also  be
rebooted  in  order  to make use of the new image(s).  If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.

INSTALLATION INSTRUCTIONS:

Install this kit with the POLYCENTER Software installation  utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:

PRODUCT INSTALL VMS73_XFC /SOURCE=[location of Kit]

The kit location may be a tape drive, CD, or a disk directory that
contains the kit.

Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt

Special Installation Instructions:

     o  Scripting of Answers to Installation Questions

        During installation,  this  kit  will  ask  and  require  user
        response  to  several  questions.  If you wish to automate the
        installation of this kit and avoid having to provide responses
        to  these  questions,  you must create a DCL command procedure
        that includes the following definitions and commands:

           -  $ DEFINE/SYS NO_ASK$BACKUP TRUE

           -  $ DEFINE/SYS NO_ASK$REBOOT TRUE

           -  Add  the  following  qualifiers  to  the  PRODUCT  INSTALL
              command and add that command to the DCL procedure.

                /PROD=DEC/BASE=AXPVMS/VER=V2.0


           -  De-assign the logicals assigned

        For  example,  a  sample   command   file   to   install   the
        VMS73_XFC-V0200 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $!
          $ PROD INSTALL VMS73_XFC/PROD=DEC/BASE=AXPVMS/VER=V2.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $ DEASSIGN/SYS NO_ASK$REBOOT
          $!
          $ exit

All trademarks are the property of their respective owners.




Copyright (c) Compaq Computer Corporation 2001.  All rights reserved.

New Kit Date     :  20-AUG-2001
Modification Date:  13-AUG-2002
Modification Type:  This kit has been archived 

This kit has been placed on hold by OpenVMS Engineering.  

Problem Statement:

Several customer sites have reported problems with the use of XFC.
Although it is not yet clear that these problems are due to installation
of the VMS73_XFC-V0100 kit, it is being put on hold as a precautionary
measure.

Problem Symptom:

The primary visible symptom is that a file appears to have different
data when viewed from different nodes in a cluster. There are also
reports that updates to files (specifically changes to the license
database) do not seem to remain after a reboot.

Workaround:

Users should disable XFC whether they have installed the VMS73_XFC-V0100
kit or not.  XFC is disabled by setting the SYSGEN parameter VCC_FLAGS
to 1 (this enables the older cluster cache, VIOC) and rebooting.  To
disable XFC perform the following commands:

  $MCR SYSGEN
  SYSGEN>  USE CURRENT
  SYSGEN>  SET VCC_FLAGS 1
  SYSGEN>  WRITE CURRENT
  SYSGEN>  EXIT

After the above commands are entered,enter the following command to reboot
the system:

  @sys$system:shutdown

Alternative Kit:

There is no alternative kit at this time.  A new XFC kit that solves this
problem will be issued at a later time.

OP/SYS:     OpenVMS Alpha

COMPONENT:  XFC

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VMS73_XFC-V0100
                    DEC-AXPVMS-VMS73_XFC-V0100--4.PCSI
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  1968 Blocks
     Kit Applies To: OpenVMS Alpha V7.3
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_1
                            1 - To be installed on all systems running
                                the listed version(s) of OpenVMS.

     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:

         None

       In order to receive all the corrections listed in this
       kit, the following remedial kits should also be installed:

         None


ECO KIT SUMMARY:

An ECO kit exists for XFC components on OpenVMS Alpha V7.3.
This kit addresses the following problems:

PROBLEMS ADDRESSED IN VMS73_XFC-V0100 KIT:

  o  Within a cluster, processes may  seem  to  hang  in  an  RWAST
     state, as seen by the SHOW SYSTEM command.  Using SDA, and the
     SHOW PROC/LOCK command, the process will  be  seen  to  own  a
     F11B$xxx  type  resource  - or be waiting for one.  On the XFC
     node that has the originating problem,  repeated  use  of  the
     command:

          SDA> XFC SHOW CONTEXT/BRIEF

     will display a Close File CTX that never disappears:

     Extract from Sample SDA Output:

     OpenVMS (TM) Alpha Operating System, Version V7.3
     -- System Dump Analysis ---

     Address          I/O Type               I/O Stall reason
     FFFFFFFF858AA310 eiotFALUpConversio ... estrLockUpConvRequ
     FFFFFFFF84F45F50 eiotFALUpConversio ... estrLockUpConvRequ
     FFFFFFFF86C269D0 eiotFALUpConversio ... estrLockUpConvRequ
     FFFFFFF8595CA50 eiotFALUpConversio ... estrLockUpConvRequ
                                .
                                .
                                .
                                .

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  Incorrect readahead operations can cause  data  corruption  on
     bound volume sets.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB

  o  An incorrectly selected UCB on segmented reads and writes  can
     cause data corruption on bound volumes.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB

  o  During  a  cluster  transition,  an  INVEXCEPTION   crash   at
     SYS$XFCACHE + 8240 can occur.

     Crashdump Summary Information:
     ------------------------------
       Crash Time:         2-MAY-2001 04:02:30.51
       Bugcheck Type:     INVPTEFMT, Invalid page table entry
                          format
       Node:              RM763B  (Cluster)
       CPU Type:          AlphaServer 4100 5/600 8MB
       VMS Version:       V7.3
       Current Process:   NULL
       Current Image:     
       Failing PC:        FFFFFFFF.800CD6DC
                          IOC_STD$PTETOPFN_C+0008C
       Failing PS:        28000000.00000804
       Module:            IO_ROUTINES    (Link Date/Time:
                          17-MAR-2001 03:30:01.24)
       Offset:            000056DC


        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                           [SYS$LDR]SYS$XFCACHE_MON.EXE
                           [SYS$LDR]SYS$XFCACHE.STB
                           [SYS$LDR]SYS$XFCACHE_MON.STB


  o  The system may hang or experience an INCONSTATE crash  due  to
     memory leaks.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYSLIB]XFC$SDA.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  When modifying the  SYSGEN  parameter  VCC_MAX_CACHE,  writing
     ACTIVE  and issuing the SET CACHE/RESET command, XFC would not
     quickly react to a reduction in  size.   Even  though  all  of
     memory  is  in use and processes are pagefaulting, the size of
     the XFC does  not  shrink  dynamically  as  documented.   This
     causes  a  lot  of  processes  to  hang  in  RWMPB  due to the
     inability to allocate out to their WSEXTENT.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYSLIB]XFC$SDA.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  An RESEXH bugcheck occurs with repeated use of FASTIO.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.SDA
                          [SYS$LDR]SYS$XFCACHE_MON.SDA

  o  When using XFC on a system using Software RAID to bind mounted
     Shadowsets,  the  RAID$SERVER process can hang in a MUTEX wait
     state.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  When XFC is called back to release memory, it  can  eventually
     get  locked up in a recursive call to itself trying to release
     memory it doesn't have.  This would usually lead to  a  system
     wide hang, but could possibly lead to CPUSPINWAITs also.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB


  o  The dynamic growth of XFC could not be set to larger than  50%
     of physical memory.

        Images Affected:  [SYS$LDR]SYS$XFCACHE.EXE
                          [SYS$LDR]SYS$XFCACHE_MON.EXE
                          [SYS$LDR]SYS$XFCACHE.STB
                          [SYS$LDR]SYS$XFCACHE_MON.STB
INSTALLATION NOTES:

This kit requires a system reboot.  Compaq strongly recommends that
a  reboot  is performed immediately after kit installation to avoid
system instability

If you have other nodes in your OpenVMS cluster, they must also  be
rebooted  in  order  to make use of the new image(s).  If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.

INSTALLATION INSTRUCTIONS:

Install this kit with the POLYCENTER Software installation  utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:

PRODUCT INSTALL VMS73_XFC /SOURCE=[location of Kit]

The kit location may be a tape drive, CD, or a disk directory that
contains the kit.

Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt


All trademarks are the property of their respective owners.


Files on this server are as follows:
»dec-axpvms-vms73_xfc-v0200--4.README
»dec-axpvms-vms73_xfc-v0200--4.CHKSUM
»dec-axpvms-vms73_xfc-v0200--4.pcsi-dcx_axpexe
»vms73_xfc-v0200.CVRLET_TXT
privacy statement using this site means you accept its terms