* * * READ ME * * *
                 * * * Veritas Volume Manager 8.0 * * *
                         * * * Patch 1200 * * *
                         Patch Date: 2022-02-10


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Volume Manager 8.0 Patch 1200


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
RHEL8 x86-64


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvxvm


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Enterprise 8.0
   * InfoScale Foundation 8.0
   * InfoScale Storage 8.0


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 8.0.0.1200
* 4066259 (4062576) hastop -local never finishes on Rhel8.4 and RHEL8.5 servers with latest minor kernels due to hang in vxdg deport command.
Patch ID: 8.0.0.1100
* 4064786 (4053230) VxVM support for RHEL 8.5
* 4065628 (4065627) VxVM Modules failed to load after OS upgrade .


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:

Patch ID: 8.0.0.1200

* 4066259 (Tracking ID: 4062576)

SYMPTOM:
When hastop -local is used to stop the cluster, dg deport command hangs. Below stack trace is observed in system logs :

#0 [ffffa53683bf7b30] __schedule at ffffffffa834a38d
 #1 [ffffa53683bf7bc0] schedule at ffffffffa834a868
 #2 [ffffa53683bf7bd0] blk_mq_freeze_queue_wait at ffffffffa7e4d4e6
 #3 [ffffa53683bf7c18] blk_cleanup_queue at ffffffffa7e433b8
 #4 [ffffa53683bf7c30] vxvm_put_gendisk at ffffffffc3450c6b [vxio]   
 #5 [ffffa53683bf7c50] volsys_unset_device at ffffffffc3450e9d [vxio]
 #6 [ffffa53683bf7c60] vol_rmgroup_devices at ffffffffc3491a6b [vxio]
 #7 [ffffa53683bf7c98] voldg_delete at ffffffffc34932fc [vxio]
 #8 [ffffa53683bf7cd8] vol_delete_group at ffffffffc3494d0d [vxio]
 #9 [ffffa53683bf7d18] volconfig_ioctl at ffffffffc3555b8e [vxio]
#10 [ffffa53683bf7d90] volsioctl_real at ffffffffc355fc8a [vxio]
#11 [ffffa53683bf7e60] vols_ioctl at ffffffffc124542d [vxspec]
#12 [ffffa53683bf7e78] vols_unlocked_ioctl at ffffffffc124547d [vxspec]
#13 [ffffa53683bf7e80] do_vfs_ioctl at ffffffffa7d2deb4
#14 [ffffa53683bf7ef8] ksys_ioctl at ffffffffa7d2e4f0
#15 [ffffa53683bf7f30] __x64_sys_ioctl at ffffffffa7d2e536

DESCRIPTION:
This issue is seen due to some updation from kernel side w.r.t to handling request queue.Existing VxVM code set the request handling area (make_request_fn) as vxvm_gen_strategy, this functionality is getting impacted.

RESOLUTION:
Code changes are added to handle the request queues using blk_mq_init_allocated_queue.

Patch ID: 8.0.0.1100

* 4064786 (Tracking ID: 4053230)

SYMPTOM:
RHEL 8.5 support is to be provided with IS 8.0

DESCRIPTION:
RHEL 8.5 ZDS support is being provided with IS 8.0

RESOLUTION:
VxVM packages are available with RHEL 8.5 compatibility

* 4065628 (Tracking ID: 4065627)

SYMPTOM:
VxVM modules are not loaded after OS upgrade followed by a reboot .

DESCRIPTION:
Once the stack installation is completed with configuration , after OS upgrade vxvm directory is not formed under /lib/modules/<upgraded_kernel>veritas/ .

RESOLUTION:
VxVM code is updated with the required changes .



INSTALLING THE PATCH
--------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
Please be noted that the installation of this P-Patch will cause downtime.

To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch vm-rhel8_x86_64-Patch-8.0.0.1200.tar.gz to /tmp
2. Untar vm-rhel8_x86_64-Patch-8.0.0.1200.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/vm-rhel8_x86_64-Patch-8.0.0.1200.tar.gz
    # tar xf /tmp/vm-rhel8_x86_64-Patch-8.0.0.1200.tar
3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.)
    # pwd /tmp/hf
    # ./installVRTSvxvm800P1200 [<host1> <host2>...]

You can also install this patch together with 8.0 base release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 8.0 directory and invoke the installer script
   with -patch_path option where -patch_path should point to the patch directory
    # ./installer -patch_path [<path to this patch>] [<host1> <host2>...]

Install the patch manually:
--------------------------
Please be noted that the installation of this P-Patch will cause downtime.

To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch vm-rhel8_x86_64-Patch-8.0.0.1200.tar.gz to /tmp
2. Untar vm-rhel8_x86_64-Patch-8.0.0.1200.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/vm-rhel8_x86_64-Patch-8.0.0.1200.tar.gz
    # tar xf /tmp/vm-rhel8_x86_64-Patch-8.0.0.1200.tar
3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.)
    # pwd /tmp/hf
    # ./installVRTSvxvm800P1200 [<host1>     <host2>    ...]

You can also install this patch together with 8.0 base release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 8.0 directory and invoke the installer script
   with -patch_path option where -patch_path should point to the patch directory
    # ./installer -patch_path [<path to this patch>     ] [<host1>      <host2>     ...]

Install the patch manually:
--------------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
Please be noted that the installation of this P-Patch will cause downtime.

To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch vm-rhel8_x86_64-Patch-8.0.0.1200.tar.gz to /tmp
2. Untar vm-rhel8_x86_64-Patch-8.0.0.1100.tar.gz to /tmp/hf
# mkdir /tmp/hf
# cd /tmp/hf
# gunzip /tmp/vm-rhel8_x86_64-Patch-8.0.0.1200.tar.gz
# tar xf /tmp/vm-rhel8_x86_64-Patch-8.0.0.1200.tar
3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.)
# pwd /tmp/hf
# ./installVRTSvxvm80P1100 [<host1>          <host2>          ...]

You can also install this patch together with 8.0 maintenance release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 8.0 directory and invoke the installmr script
with -patch_path option where -patch_path should point to the patch directory
# ./installmr -patch_path [<path to this patch>         ] [<host1>          <host2>          ...]

1.Before-the-upgrade:-
(a) Stop I/Os to all the VxVM volumes.
(b) Umount any filesystems with VxVM volumes.
(c) Stop applications using any VxVM volumes.
2.Check whether root support or DMP native support is enabled or not:
# vxdmpadm gettune dmp_native_support
If the current value is "on", DMP native support is enabled on this machine.
If disabled: goto step 4.
If enabled: goto step 3.
3.If DMP native support is enabled:
a.It is essential to disable DMP native support.
Run the following command to disable DMP native support
# vxdmpadm settune dmp_native_support=off
b.Reboot the system
# reboot
4.Select the appropriate RPMs for your system, and upgrade to the new patch.
# rpm -Uvh VRTSvxvm-8.0.0.1200-RHEL8.x86_64.rpm

5.Run vxinstall to get VxVM configured
# vxinstall
6.If DMP Native Support was enabled before patch upgrade, enable it back.
a. Run the following command to enable DMP native support
# vxdmpadm settune dmp_native_support=on
b. Reboot the system
# reboot


REMOVING THE PATCH
------------------
#rpm -e <rpm_name> 

Please note: Uninstall VRTSaslapm package before uninstalling VRTSvxvm or use --nodeps option .


SPECIAL INSTRUCTIONS
--------------------
This patch addresses the issue of 'hastop' hang observed with below mentioned kernels :
RHEL 8.4 EUS kernel >= kernel-4.18.0-305.30.1.el8_4.x86_64
RHEL 8.5 kernel >= kernel-4.18.0-348.7.1.el8_5.x86_64

This patch may cause slight performance drop with SSD devices .


OTHERS
------
NONE