Workaround for error message "v-5-1-13788 Data Corruption Protection Activated - User Corrective Action Needed:" reported following vxconfigd restart or 'vxdctl enable' execution

Article:TECH128862  |  Created: 2010-01-15  |  Updated: 2012-10-24  |  Article URL http://www.symantec.com/docs/TECH128862
Article Type
Technical Solution

Product(s)

Issue



Workaround for error message "v-5-1-13788 Data Corruption Protection Activated - User Corrective Action Needed:" reported following vxconfigd restart or 'vxdctl enable' execution


Error



LUN Serial Number Change Detection Messages (found in system log):

 

VxVM vxconfigd NOTICE V-5-1-0 LUN serial number of the OS device path with device number 118/52 has changed from 5000C50007EE9D03 (c5t50060E80104EF3F0d8) to 3000D60AA8CC187 (c5t50060E80104EF3F0d8)
VxVM vxconfigd NOTICE V-5-1-0 LUN serial number of the OS device path with device number 118/94 has changed from 5000C50007EE9D03 (c5t50060E80104EF3F1d8) to 3000D60AA8CC187 (c5t50060E80104EF3F1d8)
 

Error Reported following "vxdctl enable", also logged in syslog:

 

VxVM vxconfigd NOTICE V-5-1-13788 Data Corruption Protection Activated - User Corrective Action Needed:
VxVM vxconfigd NOTICE V-5-1-0 To recover, first ensure that the OS device tree is up to date (requires OS specific commands). Then, execute 'vxdisk rm' on the following devices before reinitializing device discovery using 'vxdisk scandisks'
VxVM vxconfigd NOTICE V-5-1-0 ams_wms0_0952
VxVM vxconfigd ERROR V-5-1-13790 No device configuration changes have been applied to DMP kernel database.
VxVM vxconfigd ERROR V-5-1-13791 Please consult the documentation for correct procedure to replace disk/path.

Cause



This issue indicates that DMP contains multiple device registrations for the indicated Major/Minor number(s) with conflicting serial numbers. 

 

This is typically the result of LUN ID reuse, or incomplete removal of internal disk devices.  When reattaching internal devices or reusing the same LUN ID, the new device will be presented at the same Major/Minor device number but with a new serial number.

 

The Data Corruption Protection (DCP) mechanism was introduced in VXVM 5.0 MP3 to detect this condition and stop all device discovery.  The condition has traditionally resulted in corruption of in-core DMP device information, which would necessitate high-impact system reboots to clear.

 

DCP detects and warns the administrator that a conflict situation has occurred and provides the administrator the opportunity to resolve the situation before discovery can take place.  Note that because discovery is halted, VM will not discover/present new devices until the situation is resolved.


Solution



The error message provides the correct and expected method to correct the situation.  Executing the "vxdisk rm <dmpnode>" command is intended to clear all registrations in the in-core DMP device tree for associated paths, clearing the way for fresh discovery.

 

EG:
# vxdisk rm ams_wms0_0952

where ams_wms0_0952 is the lun device access name 

This additional command activity was not implemented correctly in the 5.0 MP3, and 5.0 MP3 RP1, RP2, and RP3 patch levels, as well as 5.1 GA, and executing the "vxdisk rm" command does not resolve this situation.

 

This issue can be resolved using the following workaround by utilizing the path exclusion system in VxVM.  The path exclusion subsystem was properly implemented to clear all in-core DMP registrations for the excluded path.

 

WORKAROUND

 

Identify the paths associated with the impacted DMP node:

# vxdisk list <dmpnode> | grep state

 

EG:
# vxdisk list ams_wms0_0952 | grep state
c5t50060E80104EF3F0d8s2 state=enabled 
c5t50060E80104EF3F1d8s2 state=enabled
 

 In the above command output, c5t50060E80104EF3F0d8s2 and  c5t50060E80104EF3F1d8s2 are the two dmp paths of the lun ams_wms0_0952.

Use vxdmpadm to exclude the associated paths:

  # vxdmpadm exclude vxvm path=<path>
 
EG:
# vxdmpadm exclude vxvm path=c5t50060E80104EF3F0d8s2
# vxdmpadm exclude vxvm path=c5t50060E80104EF3F1d8s2

After excluding associated paths, initiate a VxVM device scan:

# vxdctl enable

 

If additional devices are reported as having conflict, repeat the above steps.  If no further conflict conditions are reported, reverse the exclusion process:

 

# vxdmpadm include vxvm path=<path>
 
EG:
# vxdmpadm include vxvm path=c5t50060E80104EF3F0d8s2
# vxdmpadm include vxvm path=c5t50060E80104EF3F1d8s2

 

Complete the process by performing one more device scan:

  # vxdctl enable      

 

SUMMARY OF WORKAROUND:

 

- Exclude impacted paths via "vxdmpadm exclude vxvm path=<path>"
- Scan device tree via "vxdctl enable"
- Include the excluded paths "vxdmpadm include vxvm path=<path>"
- Scan the device tree again: "vxdctl enable"

 


The correct functionality of using "vxdisk rm <device>" works correctly in the following product versions:

 

  • Volume Manager 5.0 MP3 RP4 (and above)
  • Storage Foundation 5.1 SP1 (and above)
  • Storage Foundation 6.0


Legacy ID



350387


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


Terms of use for this information are found in Legal Notices