Core dump issue after restoration of disk group backup (3909046)

Last published : Sep 18, 2026
After you restore a disk group backup using the vxconfigrestore command, it is possible that some configuration copies remain in a disabled state. As a result, VxVM generates a core dump when you view the list of disk groups after the restore operation.
Stack Trace:
\#0  0x00000033a3432625 in raise () from /lib64/libc.so.6
\#1  0x00000033a3433e05 in abort () from /lib64/libc.so.6
\#2  0x00000033a342b74e in __assert_fail_base () from /lib64/libc.so.6
\#3  0x00000033a342b810 in __assert_fail () from /lib64/libc.so.6
\#4  0x00000000005060f1 in req_dg_get_info_common (clnt=0x1af1750,
dg=0x7fc330004bb0) at
dg.c:3261
\#5  0x00000000005059f5 in req_dg_get_info_name (clnt=0x1af1750,
req=0x1b03f78)
at dg.c:3057
\#6  0x00000000005b2e2d in vold_process_request (arg=0x18f5f20) at
request.c:1997
\#7  0x00000033a3807a51 in start_thread () from /lib64/libpthread.so.0
\#8  0x00000033a34e896d in clone () from /lib64/libc.so.6
Workaround: Restart the VxVM configuration daemon.
\# vxconfigd -kr reset