Error Message

#> vxdctl enable
VxVM vxdctl ERROR V-5-1-14519  Data Corruption Protection Activated - User
Corrective Action Needed
VxVM vxdctl INFO V-5-1-14521  To recover, first ensure that the OS device tree is up to date (requires OS specific commands).
VxVM vxdctl INFO V-5-1-14520  Then, execute 'vxdisk rm' on the following devices before reinitiating device discovery:
tagmastore-usp0_6b1a, tagmastore-usp0_6b2a, tagmastore-usp0_6b4d, tagmastore-usp0_6b4f, tagmastore-usp0_6b59,tagmastore-usp0_6b19, tagmastore-usp0_6b41, tagmastore-usp0_6b30, tagmastore-usp0_6b12, tagmastore-usp0_6b4e, tagmastore-usp0_6b2e, tagmastore-usp0_6b18
 

The /var/adm/messages file reports:

 Aug  6 20:17:02 ftwdscig29 vxvm:vxconfigd: [ID 702911 daemon.notice] V-5-1- 14523 LUN serial number of the OS device path with device number 118/7248  has changed from 6B12 (c3t50060E800544AF7Ed259) to 6BFA  (c3t50060E800544AF7Ed259)
 

DMP information inconsistency causes the reconfiguration to abort and logs the message. This is usually caused when a device is removed from the server without removing it from Volume Manager.

Clean the device tree. i.e. on Solaris or Linux:

# /usr/lib/vxvm/voladm.d/bin/dmpdr -o refresh

If the issue still persists, exclude the device or array library.

 
Verify the ASL support library name:

--------------------------------------------------

Determine the type of storage array and library used. This example uses the tagmastore-usp.
# vxddladm listsupport   
# vxddladm listsupport libname=libvxhdsusp.so  (example) - to show more details about the library
--------------------------------------------------

Re-claim device (ASL)

 --------------------------------------------------
1. Freeze the service group to prevent any failover  (if in a cluster to prevent unwanted failover)

2. Scan new devices
# vxdisk scandisks new

- it may complain about data protection

3. Exclude and include Array Support library to re-claim the device
# vxddladm excludearray libname=libvxhdsusp.so   (tagmastore)
# vxddladm includearray libname=libvxhdsusp.so  (tagmastore)

4. Scan new device
# vxdisk scandisks

If data corruption protection messages still exist, a reconfigure reboot may be required.