VERITAS VOLUME MANAGER 2.7 FOR WINDOWS 2000
HOTFIX 2 README FILE
English Version
December 19, 2001

This Readme file has the following topics:

I.   INSTALLING THE HOTFIX
II.  UNINSTALLING THE HOTFIX
III. ISSUES RESOLVED IN THIS HOTFIX

I. INSTALLING THE HOTFIX

If you have a cluster, install the hotfix on each
node of the cluster. See the note below for details.

Use the following steps to install this hotfix:

1. On the VERITAS Support web site, access the product
  listing for Volume Manager for Windows 2000.
   
2. Under "Recently Published Patches and Updates,"
   click to select the appropriate link for this
   hot fix.  The file name starts with "VM2K27HF"
  and the number of the hotfix.

3. When prompted, select "Save This Program To Disk"
   and click OK.

4. When the download completes, extract the contents by
  double-clicking the downloaded package. The hotfix
   package contains three files--a package ID, this Readme
  file, and the hotfix executable file, VMW2K27HF02.EXE.    

5. Copy the hotfix executable file to any directory
   on the computer where Volume Manager is installed.

6. Double-click the hotfix executable file to start the
  installation.

  The install utility's welcome screen appears.

7. Click Next to continue.

8. Click Install to proceed with the installation. The hotfix
  install runs automatically and will install the files modified
   by the hotfix to the appropriate directories.

9. In the final screen, click Finish. A message appears,
   prompting you to restart your system.

10. Click Yes to restart the computer now or No if you plan
    to restart later. You must reboot to have the changes take
    effect.

Note: A cluster does not have to be brought down to install
the hotfix. A rolling upgrade can be done so that the cluster
resources remain available during the installation (see steps
a through d below).

  a. Before installing the hotfix to a cluster node,
     move all cluster resources to another cluster node.

  b. Install the hotfix as directed above.

  c. Move the cluster resources back to the original
     node.

  d. Repeat steps a through c for each remaining node
     of the cluster.


II. UNINSTALLING THE HOTFIX

Normally you would not need to uninstall the hotfix;
but if it becomes necessary to do so, here are the steps:

1. Open the Control Panel and select Add/Remove Programs.

2. Click to select the VERITAS Volume Manager
  Hot Fix VMW2K27HF02 and then click Remove.

3. Click Yes to respond to the confirmation box that
   appears.

  After the process for uninstalling is complete,
  a message appears, prompting you to restart
  your system.

4. Click Yes to restart the computer now or No if
  you plan to restart later. You must reboot to have
   the changes take effect.
 
  The process for uninstalling is now complete.

Note: If you want to repair the hotfix, use steps 1
and 2 above but select Change instead of Remove. A
dialog box comes up with two options--Repair and Remove.
The hotfix repair option runs automatically.  It will
uninstall the hotfix files and restore the previous
files to the appropriate directories.


III. ISSUES RESOLVED IN THIS HOTFIX

This hotfix was created to address one current issue.  
Because it is a cumulative hotfix, it also contains fixes
for problems in all previous hot fixes. This Issues section
is divided into two topics:

- Current Issue for This Hotfix
- Past Issues from Previous Hotfixes

A. Current Issue for This Hotfix

  Bugcheck with stop code "0X50 PAGE_FAULT_IN_NONPAGED_
   AREA" (Incident 85793)

  Occasionally, a system running VM 5.27 under heavy
   I/O may fail to load a driver correctly and results
  in a bugcheck with stop code 0x50, "PAGE_FAULT_IN_
  NONPAGED_AREA."

  This problem has been resolved with the hotfix.


B. Past Issues from Previous Hotfixes

  VM 5.27 Hotfix 1


  1. Optimized the Rescan function to improve performance
     when hot plugging disks (Incident 71196).

     Improved the rescanning process so that it rescans
     only for the disks that were removed or replaced
     rather than all the disks on the system.

  2. The hot fix resolves a number of problems that caused HCT
     MSCS Validate 2 Node tests to fail when Volume Manager
     cluster disk group resources were in use. These problems
     might also affect normal operations or occur during
     certain failure scenarios. The following issues
     were resolved:

     - Improvements were made to the processes for locking
       and dismounting volumes on cluster disk groups during
       an offline operation (Incident 53844).

      NOTE: For cluster disk groups, Volume Manager makes
      several attempts to lock and dismount volumes
      before deporting the group, but eventually will
      force deport a group with active I/O. The cluster
      administrator should structure cluster group
      dependencies to ensure that applications that
      depend on a Volume Manager disk group resource
      are offlined before the cluster disk group is
      offlined.

      - Performance for offlining cluster disk groups
      was improved (Incidents 73365, 73370).

      - When the MSCS cluster service was stopped on a
      node with an online Volume Manager Disk Group
      resource, the resource could not be brought
      online again on that node until the node had
      been rebooted (Incident 73368).

      This problem has been resolved with the hotfix.

   3. In a system with MSCS and DMP installed, disabling both
      paths to a disk that is a part of a cluster resource
      causes the Cluster Administrator to freeze and not
      failover to the the other node (Incident 72343).

      This problem has been resolved with the hotfix.

   4. After Volume Manager and DMP have been installed,
      adding or removing a SCSI adapter card may result
      in a blue screen with the error "Bugcheck 0x1e"
      (Incident 71033).

      This problem has been resolved with the hotfix.

   5. In a system that has Volume Manager with DMP and a
      Compaq Smart Array controller installed, the message
      "Driver Power_State_Failure STOP" may occur when there
      is a second shutdown after the PNP driver discovers
      new hardware (Incident 72454).

      This problem has been resolved with the hotfix.