Error Message

The following warnings or errors are noticed due to this issue.

Example VxVM Command Error:

# vxdmpadm listapm
Filename           APM Name           APM Version  Array Types       State
================================================================================
dmpalua.ko         dmpalua                1        ALUA              Not-Active
dmpsvc.ko          dmpsvc                 1        IBMSVC-ALUA       Not-Active
dmpjbod.ko         dmpjbod                1        Disk              Not-Active
dmpjbod.ko         dmpjbod                1        APdisk            Not-Active
dmpinv.ko          dmpinv                 1        Inv-A/A           Not-Active
dmpinv.ko          dmpinv                 1        VPLEX-A/A         Not-Active
dmpapg.ko          dmpapg                 1        A/PG              Not-Active
dmpapg.ko          dmpapg                 1        A/PG-C            Not-Active
dmpsun7x10alua.ko  dmpsun7x10alua         1        SUN7x10-ALUA      Not-Active
dmpCLARiiON.ko     dmpCLARiiON            1        CLR-A/P           Not-Active
dmpCLARiiON.ko     dmpCLARiiON            1        CLR-A/PF          Not-Active
dmpCLARiiON.ko     dmpCLARiiON            1        CLR-ALUA          Not-Active
dmphuawei.ko       dmphuawei              1        A/A-A-HUAWEI      Not-Active
dmphuawei.ko       dmphuawei              1        A/PF-HUAWEI       Not-Active
dmpaa.ko           dmpaa                  1        A/A               Active
dmpapf.ko          dmpapf                 1        A/PF-VERITAS      Not-Active
dmpapf.ko          dmpapf                 1        A/PF-T3PLUS       Not-Active
dmpap.ko           dmpap                  1        A/P               Not-Active
dmpap.ko           dmpap                  1        A/P-C             Not-Active
dmpaaa.ko          dmpaaa                 1        A/A-A             Not-Active
VxVM ERROR V-5-2-14196 crc_file: open fails for /lib/modules/2.6.32-358.el6.x86_64/veritas/vxvm/dmpKOVE.ko    <<<=== ERROR


OR


While installing OS Patches (Receive warnings)

Installing : kmod-be2net-10.2.340.7-1.rhel6u4.x86_64 1/1
WARNING: /lib/modules/2.6.32-358.el6.x86_64/veritas/vxvm/dm.ko needs unknown symbol kdsa_ext_ioctl            << ==== WARNINGS
WARNING: /lib/modules/2.6.32-358.23.2.el6.x86_64/veritas/vxvm/dm.ko needs unknown symbol kdsa_ext_ioctl    << ==== WARNINGS
WARNING: /lib/modules/2.6.32-358.el6.x86_64/veritas/vxvm/dm.ko needs unknown symbol kdsa_ext_ioctl            << ==== WARNINGS
Verifying : kmod-be2net-10.2.340.7-1.rhel6u4.x86_64 1/1

 

During an upgrade, using either manual RPM commands or using the Stroage Foundation product installation Cross Platform Installer (CPI), if the VRTSvxvm rpm package is installed after the installation of the VRTSaslapm rpm package, then the post installation script of the VRTSvxvm rpm package incorrectly removes the KOVE Module from the ‘/lib/modules/`uname -r`/veritas/vxvm/‘ location.

MANUAL SOLUTION:

Since the problem is related to the post install script belonging to the RPM package of VRTSvxvm, it is not possible to fix it in the form of another RPM because the product version is now already GA released. However, the following manual steps are recommended to fix the missing KOVE module issue.

1.) Re-Install the VRTSaslapm rpm (Does not require an outage and can be performed while  online)
 
Example: (Re-installing VRTSaslapm RPM of version 6.0.5 for SF 6.0.5)

# rpm -Uvh --force VRTSaslapm-6.0.500.000-GA_RHEL6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:VRTSaslapm             ########################################### [100%]
Installing keys for APMs
 
 
2.) Confirm that the KOVE module (dmpkove.ko) is available and the links created correctly
 
# ls -l /etc/vx/kernel/
total 21428
-rw-r--r--. 1 root root   22544 Mar 30  2014 dmpaaa.ko.2.6.32-71.el6.x86_64
…
-rw-r--r--. 1 root root   23032 Mar 30  2014 dmpjbod.ko.2.6.32-71.el6.x86_64
-rw-r--r--. 1 root root   24024 Mar 30  2014 dmpkove.ko.2.6.32-71.el6.x86_64          <<======== This is the location of the KOVE module
-rw-r--r--. 1 root root   24864 Mar 30  2014 dmpnalsi.ko.2.6.32-71.el6.x86_64
…
-rwxr--r--. 1 root root   22512 Feb 28  2013 vxportal.ko.2.6.32-71.el6.x86_64
-rw-r--r--. 1 root root   10720 Mar 30  2014 vxspec.ko.2.6.32-71.el6.x86_64


# ls -l /lib/modules/`uname -r`/veritas/vxvm/
total 24
-rw-r--r--. 1 root root 24024 Mar 30  2014 dm.ko       <<<========= This module gets added after installation of VRTSvxvm rpm but is not required
lrwxrwxrwx. 1 root root    45 Oct 15 03:59 dmpaaa.ko -> /etc/vx/kernel/dmpaaa.ko.2.6.32-71.el6.x86_64
…
lrwxrwxrwx. 1 root root    46 Oct 15 03:59 dmpjbod.ko -> /etc/vx/kernel/dmpjbod.ko.2.6.32-71.el6.x86_64
lrwxrwxrwx. 1 root root    46 Oct 15 03:59 dmpkove.ko -> /etc/vx/kernel/dmpkove.ko.2.6.32-71.el6.x86_64       <<=== Symlink for KOVE module created
lrwxrwxrwx. 1 root root    47 Oct 15 03:59 dmpnalsi.ko -> /etc/vx/kernel/dmpnalsi.ko.2.6.32-71.el6.x86_64
…
lrwxrwxrwx. 1 root root    45 Oct 15 03:34 vxspec.ko -> /etc/vx/kernel/vxspec.ko.2.6.32-71.el6.x86_64
 
 
3.) Manually remove the ‘dm.ko’ file in the modules directory location:
 
# rm /lib/modules/`uname -r`/veritas/vxvm/dm.ko
 
 

PERMANENT SOLUTION:

To fix this issue in the RPM packages, a permanent General Availability (GA) fix will be made available by Veritas in the next release of GA patches on top of 6.0.5 and 6.1.1 when available. Currently there is no ETA for the next GA release for these versions, but customers can refer to the https://docs.infoscale.com/ website and also subscribe for notifications to our patch updates to get more information of the next GA patches when they will be released. The next release of SF 6.2 will include the fix for this issue.

Note: The warnings and/or errors received due to this issue do not affect any product functionality in any way unless the system uses KOVE devices and has the KOVE’s KDSA software installed.


 

Applies To

• The KOVE device support is introduced in Storage Foundation 6.0.5 and 6.1.1 releases and hence this issue does not impact previous versions of the product.
• Any systems on supported Linux platforms upgrading from any earlier release of Storage Foundation to the Storage Foundation version 6.0.5 or 6.1.1 will be vulnerable to this issue.
• This issue impacts only the Linux platform.

Errors relating to the KOVE (kdsa_ext_ioctl) module can be seen reported in the system logs or on the system terminal or console while attempting to execute some VxVM commands or while installing OS related kernel patches on systems running with Storage Foundation version 6.0.5 and later.

ETrack: 3584341