In VxVM 6.2, vxconfigd appears to have a memory leak.
Article ID: 100015098
Updated On:
Description
Error Message
There is no error message, but vxconfigd processes appear to slowly increase memory usage.
On Solaris, findleaks shows as following, memory leaks after getvoldmsg() calls strdup().
# echo "::findleaks -dv" | mdb core.4263
：
：
umem_alloc_16 leak: 40 buffers, 16 bytes each, 640 bytes total
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
eb9a40 eb4e40 184a54a8fb3a98 576
51f088 4b012c 0
libumem.so.1`umem_cache_alloc+0x21c
libumem.so.1`umem_alloc+0xb8
libumem.so.1`malloc+0x28
libc.so.1`strdup+0xc --> !!
getvoldmsg+0x30
msghead+0x258
msg+0x14
array_da_to_disk+0x32c
array_restrict_devices+4
da_online+0x20
da_thread_online_disk1+4
vold_thread_exec+0xa8
libc.so.1`_lwp_start
umem_alloc_16 leak: 1 buffer, 16 bytes
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
eb2708 eb4260 184a52e92af1f0 1
51f088 4bbb58 0
libumem.so.1`umem_cache_alloc+0x21c
libumem.so.1`umem_alloc+0xb8
libumem.so.1`malloc+0x28
libc.so.1`strdup+0xc --> !!
getvoldmsg+0x30
msghead+0x278
msg+0x14
dg_import_start+0x918
dg_reimport+0x1c4
dg_recover_all+0x1d0
mode_set+0x7ac
setup_mode+0x20
startup+0x2dc
main+0xe74
_start+0x108
umem_alloc_16 leak: 7 buffers, 16 bytes each, 112 bytes total
ADDR BUFADDR TIMESTAMP THREAD
CACHE LASTLOG CONTENTS
b7fa40 b74880 184a61b2bfc438 1
51f088 4f1388 0
libumem.so.1`umem_cache_alloc+0x21c
libumem.so.1`umem_alloc+0xb8
libumem.so.1`malloc+0x28
libc.so.1`strdup+0xc --> !!
getvoldmsg+0x30
msghead+0x278
msg+0x14
req_dg_deport+0x2fc
request_loop+0xb74
main+0xec0
_start+0x108
Cause
In 6.2, we replaced dynamic strings in gettxt at e3588012, and that is cause memory leak in strdup().
Resolution
Veritas will address in 6.2.1.
If you need private hotfix for 6.2 , please contact Veritas Technical Support Team.
Applies To
VxVM 6.2 on all platforms
Issue/Introduction
