VxVM commands such as "vxdctl enable", “vxdisk scan disks” and "vxdisk -o alldgs list" and vxconfigd startup sometime consume all the CPUs on the host having many LUNs attached to it.
Article ID: 100014919
Updated On:
Description
Error Message
This issue is seen in HPUX 11.31 platform and VxVM versions starting 5.0.
Cause
VxVM needs information about the devices and paths attached to the system from Operating System (HPUX) and it uses HPUX's API’s to query the device tree from OS's I/O subsystem. Since VxVM is a multithreaded application, it sends multiple requests in parallel to I/O subsystem. I/O subsystem API’s internally use global spin lock (GIO lock).When one thread has acquired the GIO lock other threads have to wait till the thread has released the lock. Thus, there is GIO lock contention in the OS due to multiple I/O subsystem requests from parallel applications like VxVM. Hence we see majority of the CPUs are busy only with VxVM threads.
Resolution
Veritas and HP are discussing this issue to come up with a solution. Till that time please reach out to Veritas support to know the latest progress and also temporary workaround if any.
Issue/Introduction
