Installation of Veritas Volume Manager (VxVM) 5.1SP1RP3 patch and above in Alternate Boot Environment (ABE) are susceptible to corruption when used with Third Party Drivers (TPD) like MPxIO

Article:TECH204238  |  Created: 2013-03-24  |  Updated: 2013-04-03  |  Article URL http://www.symantec.com/docs/TECH204238
Article Type
Technical Solution

Product(s)

Environment

Issue



Installation of Veritas Volume Manager (VxVM) 5.1SP1RP3 patch and above in Alternate Boot Environment (ABE) are susceptible to corruption when used with Third Party Drivers (TPD) like MPxIO.
 

Corruption can occur in Volume Manager (VxVM) configurations involving TPD like MPxIO or Powerpath upon executing commands like  "vxddladm assign names" and/or "vxddladm set namingscheme=osn". VxVM patches when installed in ABE calls 'vxddladm assign names' command from postinstall script which may cause the issue.


Error




Feb 19 15:03:18 system1 vxio: [ID 914260 kern.notice] NOTICE: VxVM vxio V-5-0-1046 changing UDID for disk emc2_66
Feb 19 15:03:18 system1 vxio: [ID 300316 kern.notice] NOTICE: VxVM vxio V-5-0-1135 change disk emc2_66 has a non-unique UDID
Feb 19 15:03:18 system1 vxio: [ID 914260 kern.notice] NOTICE: VxVM vxio V-5-0-1046 changing UDID for disk emc2_74
Feb 19 15:03:18 system1 vxio: [ID 300316 kern.notice] NOTICE: VxVM vxio V-5-0-1135 change disk emc2_74 has a non-unique UDID
[...]
Feb 19 15:03:25 system1 vxio: [ID 914260 kern.notice] NOTICE: VxVM vxio V-5-0-1046 changing UDID for disk emc2_63
Feb 19 15:03:25 system1 vxio: [ID 914260 kern.notice] NOTICE: VxVM vxio V-5-0-1046 changing UDID for disk emc2_84
 


Environment



This issue is applicable only when all of the below conditions are met:

- VxVM 5.1SP1 and above

- Solaris 9, 10 (SPARC) or Solaris 10 (x64)

- MPxIO is configured

- Patch upgrade is performed in ABE

 


Cause



When installing VxVM 5.1SP1RP3 (142629-16) patch or above, 'vxddladm assign names' gets called from postinstall script which may result in corruption when MPxIO is enabled, hitting e2674465. The problem with running '/usr/sbin/vxddladm assign names' in this case is that the command is run on the primary boot environment whereas the patch is only installed on the alternate boot environment. The issue occurs only when installing the patch in ABE and when MPxIO is configured.
 

Please see TECH180703 (in Related Articles section) for additional details on the root cause.

 


Solution



The permanent fix will be included via e3131071 in upcoming:

- VxVM 5.1SP1RP3P3 and VxVM 5.1SP1RP4 patches (on SPARC platform)

- VxVM 5.1SP1RP4 (on x64 platform)

 


Workaround

SPARC: For 5.1SP1RP3 (142629-16) Patch:

The workaround is to use a newer version of VxVM 5.1SP1RP3 patch available as 142629-16.tar.gz.e3131073. Two files have been modified since the original patch release.


./142629-16/VRTSvxvm/install/postinstall
- Removed calling 'vxddladm assign names' command when MPxIO is configured as the command is no longer needed to be run as part of postinstall script post VxVM 5.1SP1.


./142629-16/VRTSvxvm/pkgmap
- Modified the checksum and size values of postinstall to correspond to the change.


1) Download 142629-16.tar.gz.e3131073 from Symantec support


2) Extract SFHA RP3 patch in local directory


3) Replace the original 142629-16.tar.gz file with the modified 142629-16.tar.gz.e3131073 file.

# cp 142629-16.tar.gz.e3131073 <patch_dir>/sol_sparc/patches/142629-16.tar.gz
#

4) Ensure the checksum output matches with below output:

# cksum <patch_dir>/sol_sparc/patches/142629-16.tar.gz
3105734690      46997561        sol_sparc/patches/142629-16.tar.gz
#

Now the patch could be installed using installrp or patchadd commands. 

 

SPARC: For 5.1SP1RP3P2 (142629-18) Patch:

The workaround is to use a newer version of VxVM 5.1SP1RP3P2 patch available as 142629-18.tar.e3131073.gz. Two files have been modified since the original patch release.


./142629-18/VRTSvxvm/install/postinstall
- Removed calling 'vxddladm assign names' command when MPxIO is configured as the command is no longer needed to be run as part of postinstall script post VxVM 5.1SP1.


./142629-18/VRTSvxvm/pkgmap
- Modified the checksum and size values of postinstall to correspond to the change.


1) Download 142629-18.tar.e3131073.gz from Symantec support.

2) Use this new patch to install VxVM 5.1SP1RP3P2 patch.

3) Ensure the checksum output matches with below output:

# cksum vm-sol_sparc-5.1SP1RP3P2-patches.tar.e3131073.gz
1640914671      47116346        vm-sol_sparc-5.1SP1RP3P2-patches.tar.e3131073.gz
#

Now the patch could be installed using patchadd commands. 

 

x64: For 5.1SP1RP3 (142630-16) Patch:

The workaround is to use a newer version of postinstall and pkgmap files for VxVM 5.1SP1RP3 patch available in the attachments. Two files have been modified since the original patch release.


./142630-16/VRTSvxvm/install/postinstall
- Removed calling 'vxddladm assign names' command when MPxIO is configured as the command is no longer needed to be run as part of postinstall script post VxVM 5.1SP1.


./142630-16/VRTSvxvm/pkgmap
- Modified the checksum and size values of postinstall to correspond to the change.


1) Download postinstall.RP3-x64.e3131073 and pkgmap.RP3-x64.e3131073 from Symantec support (attachments in this article).


2) Extract SFHA RP3 patch in local directory


3) Replace the original ./142630-16/VRTSvxvm/install/postinstall file with the modified postinstall.RP3-x64.e3131073 file.

# cp postinstall.RP3-x64.e3131073 <patch_dir>/patches/142630-16/VRTSvxvm/install/postinstall
#

4) Ensure the checksum output matches with below output:

# cksum <patch_dir>/patches/142630-16/VRTSvxvm/install/postinstall
1041231953      45556   patches/142630-16/VRTSvxvm/install/postinstall
#

5) Replace the original ./142630-16/VRTSvxvm/pkgmap file with the modified pkgmap.RP3-x64.e3131073 file.

# cp pkgmap.RP3-x64.e3131073 <patch_dir>/patches/142630-16/VRTSvxvm/pkgmap
#

6) Ensure the checksum output matches with below output:

# cksum <patch_dir>/patches/142630-16/VRTSvxvm/pkgmap
4245464270      49447   patches/142630-16/VRTSvxvm/pkgmap
#

Now the patch could be installed using installrp or patchadd commands. 

 

x64: For 5.1SP1RP3P2 (142630-18) Patch:

The workaround is to use a newer version of postinstall and pkgmap files for VxVM 5.1SP1RP3P2 patch available in the attachments. Two files have been modified since the original patch release.


./142630-18/VRTSvxvm/install/postinstall
- Removed calling 'vxddladm assign names' command when MPxIO is configured as the command is no longer needed to be run as part of postinstall script post VxVM 5.1SP1.


./142630-18/VRTSvxvm/pkgmap
- Modified the checksum and size values of postinstall to correspond to the change.


1) Download postinstall.RP3P2-x64.e3131073 and pkgmap.RP3P2-x64.e3131073 from Symantec support (attachments in this article).


2) Extract VxVM 5.1SP1RP3P2 (142630-18) patch in local directory


3) Replace the original ./142630-18/VRTSvxvm/install/postinstall file with the modified postinstall.RP3P2-x64.e3131073 file.

# cp postinstall.RP3P2-x64.e3131073 <patch_dir>/patches/142630-18/VRTSvxvm/install/postinstall
#

4) Ensure the checksum output matches with below output:

# cksum <patch_dir>/patches/142630-18/VRTSvxvm/install/postinstall
1715451269      46888   patches/142630-18/VRTSvxvm/install/postinstall
#

5) Replace the original ./142630-18/VRTSvxvm/pkgmap file with the modified pkgmap.RP3P2-x64.e3131073 file.

# cp pkgmap.RP3P2-x64.e3131073 <patch_dir>/patches/142630-18/VRTSvxvm/pkgmap
#

6) Ensure the checksum output matches with below output:

# cksum <patch_dir>/patches/142630-18/VRTSvxvm/pkgmap
70220237        49407   patches/142630-18/VRTSvxvm/pkgmap
#

Now the patch could be installed using patchadd commands. 

 


Attachments

Modified VxVM 5.1SP1RP3 (142629-16) patch
142629-16.tar.gz.e3131073 (45.9 MBytes)
Modified VxVM 5.1SP1RP3P2 (142629-18) patch
vm-sol_sparc-5.1SP1RP3P2-patches.tar.e3131073.gz (46 MBytes)


Modified postinstall script for VxVM 5.1SP1RP3 (142630-16) x64 patch
postinstall.RP3-x64.e3131073 (44 kBytes)
Modified pkgmap file for VxVM 5.1SP1RP3 (142630-16) x64 patch
pkgmap.RP3-x64.e3131073 (48 kBytes)
Modified postinstall script for VxVM 5.1SP1RP3P2 (142630-18) x64 patch
postinstall.RP3P2-x64.e3131073 (46 kBytes)
Modified pkgmap file for VxVM 5.1SP1RP3P2 (142630-18) x64 patch
pkgmap.RP2P2-x64.e3131073 (48 kBytes)

Supplemental Materials

SourceETrack
Value2674465
Description

Data Corruption while adding/removing LUNs


SourceETrack
Value3131071
Description

Installation of 5.1SP1RP3 (142629-16) patch in ABE ends up in data corruption hitting e2674465





Article URL http://www.symantec.com/docs/TECH204238


Terms of use for this information are found in Legal Notices