vxconfigd is creating core file on ddl_add_lun, and unable to satrt

Issue

vxconfigd is dumping core file, and the stack looks similar ro below:

# pstack core | more
core 'core_ares_vxconfigd_0_0_1290401318_5362' of 5362: vxconfigd -m disable
-----------------  lwp# 1 / thread# 1  --------------------
 0017b8ac ddl_parse_entity_list (481010, fffdb314, ffbfe9e2, 44b8e0, 0, 29ae00) + 8b8
 0017bf34 ddl_build_entity_list (fffdb534, 0, 0, 2c5988, 5ea8, 5c00) + 1d4
 0013993c ddl_find_devices_in_system (5400, 0, fffca308, 2bfae0, 0, 2c3e30) + 1b4
 000e7ac8 find_devices_in_system (3, 0, 27963c, 2ce574, 11, 279800) + 28
 000e70b0 mode_set (3, ffbffa74, 2ce574, 2ce5b8, 0, 2c3400) + 184
 000df47c setup_mode (3, 277400, 0, 4d414e, a39, 277400) + 24
 000df3a0 startup  (9d3ec4c0, 2e0000, 2c3c00, 2c3c00, 277400, 14f1) + 258
 000dedbc main     (3, ffbffc3c, ffffffff, 0, ffbffd18, 0) + cf0
 00036820 _start   (0, 0, 0, 0, 0, 0) + 108


Environment

The issue was discovered on Volume Manager 5.0MP3RP4 and Solaris 10, but the issue could be occurred on any 5.XX and all platform.

Cause
/etc/vx/ddlconfig.info file has invalid LUN id or corrupted.

 To verify the issue, you can collect vxconfigd debug log:

# vxconfigd -x log -x 9 >> vxconfigd.log 2>&1

# tail vxconfigd.log

...

11/21 21:05:23.515: VxVM vxconfigd DEBUG V-5-1-21566 ddl_add_lun: Found lun QLogic Corp.
11/21 21:05:23.515: VxVM vxconfigd DEBUG 11/21 21:05:25.160: VxVM vxconfigd ERROR V-5-1-0 Segmentation violation - core dumped


You can see the vxcofnigd was crashed right after trying to add a lun, but the device name was "QLogic Corp."

The wrong device name comes from /etc/vx/ddlconfig.info, and it caused the issue:

/etc/vx/ddlconfig.info
....
                       LUN c2t50060482D531401Dd294s2
                        LUN c2troot  <-------------------------------------------------  LUN name is incorrect!!

Solution

The issue can be resolved by rename the file and restart vxconfigd:

# mv /etc/vx/ddlconfig.info /etc/vx/ddlconfig.old

# vxconfigd -k