# vxconfigd -k
VxVM vxconfigd NOTICE V-5-1-13788 DataCorruption Protection Activated -
User Corrective Action Needed:
VxVMvxconfigd NOTICE V-5-1-13789 LUN serial number 08AF of oldnode
c4t50060E80042B6455d151 does not match with LUN serial number 08B0of
new node c4t50060E80042B6455d151 even though both have same device
number 118/33952


Here are the messages just before the coredump.
edce203:/var/VRTSvcs/log# vxconfigd -k
VxVM vxconfigd NOTICEV-5-1-13788 Data Corruption Protection Activated -
User Corrective Action Needed:
VxVM vxconfigd NOTICE V-5-1-13789 LUN serial number 08AF of oldnode
c4t50060E80042B6455d151 does not match with LUN serial number 08B0of
new node c4t50060E80042B6455d151 even though both have same device
number 118/33952
VxVM vxconfigd NOTICE V-5-1-13788 Data Corruption Protection Activated -
User Corrective Action Needed:
VxVM vxconfigdNOTICE V-5-1-13789 LUN serial number 08AF of old node
c5t50060E80042B6445d151does not match with LUN serial number 08B0 of
new nodec5t50060E80042B6445d151 even though both have same device
number118/33960
VxVM vxconfigd NOTICE V-5-1-13788 Data Corruption Protection Activated -
User Corrective Action Needed:
VxVM vxconfigd NOTICEV-5-1-13789 LUN serial number 08AF of old node
c3t50060E80042B6441d151 does not match with LUN serial number 08B0 of
new node c3t50060E80042B6441d151even though both have same device
number 118/33944
VxVM vxconfigd NOTICEV-5-1-13788 Data Corruption Protection Activated -
User Corrective Action Needed:
VxVM vxconfigd NOTICE V-5-1-13789 LUN serial number 08AF of old node
c2t50060E80042B6451d151 does not match with LUN serial number 08B0of
new node c2t50060E80042B6451d151 even though both have same device
number 118/33936
VxVM vxconfigd ERROR V-5-1-0 Segmentation violation - core dumped


Form the core we see issue is in ddllayer

# mdb vxconfigd.edca203 core.vxconfgd_edce203
mdb: failed to initialize /lib/libthread_db.so.1: libthread_db call failed unexpectedly
mdb:warning: debugger will only be able to examine raw LWPs
Loading modules: [libc.so.1 libnvpair.so.1 libavl.so.1 libuutil.so.1 ld.so.1 ]
>::stack
ddl_delete_node+0xc(0, a1076c, 7d08b0, 40006805, 80808080,1010101)
ddl_migration_devlist_found+0x10c(dacd70, fffffffe, 2cb56c, 2b8f6c,50000, 6fc310)
ddl_check_migration_of_devices+0xb0(a611d8, a090e8, ffbfed1c,6fc270, 5c00, 0)
ddl_reconfigure_all+0x26c(2bed34, 9d6850, 2b8f6c, 50000,3400, 2cb500)
ddl_find_devices_in_system+0x3f0(10800, 0, 5dd4, 2b8f6c, 0,2bd2c8)
find_devices_in_system+0x28(2, 0, 2738e4, 2c6fa4, 11,273800)
mode_set+0x184(2, ffbffaec, 2c6fa4, 2c6fe0, 0,2bc800)
setup_mode+0x24(2, 271800, 0, 2bd000, a39,271800)
startup+0x284(30080a00, 2d8400, 2bd000, 2bd000, 271800,3965)
main+0xcac(2, ffbffcb4, ffffffff, 0, ffbffd84, 0)
_start+0x108(0, 0,0, 0, 0, 0)
> ddl_delete_node+0xc::dis
ddl_destroy_dmpnode+0x88: ld[%i0 + 0x80], %l7
ddl_destroy_dmpnode+0x8c: call -0x7737c
ddl_destroy_dmpnode+0x90: ld [%i0 + 0x80],%o0
ddl_destroy_dmpnode+0x94: call +0x16bc
ddl_destroy_dmpnode+0x98: mov %i0,%o0
ddl_destroy_dmpnode+0x9c: call -0x7738c
ddl_destroy_dmpnode+0xa0: restore
ddl_delete_node: save %sp,-0x60, %sp
ddl_delete_node+4: mov %i0, %i2
ddl_delete_node+8: ld [%i0 +0x8], %i0
ddl_delete_node+0xc: ld [%i0 + 0x4], %o1
ddl_delete_node+0x10:cmp %o1, 0x1
ddl_delete_node+0x14: bne,pn %icc, +0x18
ddl_delete_node+0x18:nop
ddl_delete_node+0x1c: call +0x16ad8
ddl_delete_node+0x20: mov %i0,%o0
ddl_delete_node+0x24: call -0xc8
ddl_delete_node+0x28:restore
ddl_delete_node+0x2c: call +0x8
ddl_delete_node+0x30: mov %o7,%o7
ddl_delete_node+0x34: sethi %hi(0x161800), %o5
> ::regs
%g0 =0x00000000 %l0 = 0x00050000 vold_change_common+0x21c4
%g1 = 0x00000000 %l1 =0x002b8f6c
%g2 = 0x006fc310 %l2 = 0x01303618
%g3 = 0x00000000 %l3 =0xfffd94c0
%g4 = 0x00000000 %l4 = 0x00026800
%g5 = 0x00000008 %l5 =0x000000ee
%g6 = 0x00000000 %l6 = 0x0000000d
%g7 = 0xff1b2a00 %l7 =0x00002000
%o0 = 0x004af120 %i0 = 0x00000000
%o1 = 0x01d88968 %i1 =0x00a1076c
%o2 = 0x002b8f6c %i2 = 0x007d08b0
%o3 = 0x00622658 %i3 =0x40006805
%o4 = 0x01d88968 %i4 = 0x80808080
%o5 = 0x004af120 %i5 =0x01010101
%o6 = 0xffbfeb78 %i6 = 0xffbfebd8
%o7 = 0x0015c0c4ddl_check_if_exists_in_prop_list+0x58 %i7 = 0x00155e28ddl_migration_devlist_found+0x10c
%psr = 0xfe001003 impl=0xf ver=0xeicc=nzvc
ec=0 ef=4096 pil=0 s=0 ps=0 et=0 cwp=0x3
%y = 0x00000000
%pc =0x00157678 ddl_delete_node+0xc
%npc = 0x0015767c ddl_delete_node+0x10
%sp= 0xffbfeb78
%fp = 0xffbfebd8
%wim = 0x00000000
%tbr =0x00000000
>


This is Similar to e1412512
Abstract: DDL: Data corruption protection activated message should be reported by vxdisk scandisksand vxdctl enable CLI
This is fixed in 5.0MP3RP1 but the documentation of5.0MP3RP1 does not mention this bug because it is classed as an internalbug.


Although it is not the exact problem faced by the customer (for this case vxconfig doesn't even start up and core dumps in the beginning itself), installing the fix for 1412512 (RP1) will allow customer to take following corrective action in case they hit similar issue again.
vxdisk rm

As fix for issue is in RP1 and customer needs to installRP1 reboot, customer also agreed to install HF3 at the time.