The "lsvg" command is unresponsive, which appears to be due to an issue with the LVMVG VCS Agent.

book

Article ID: 100010497

calendar_today

Updated On:

Description

Error Message

No error is presented.

Cause

A trace, truss, or other similar commands to determine the cause of unresponsiveness will appear to indicate that the LVMVG agent opens a file and does not close the file.

The file which appears open is required for successful VG operations.

Example of an open filename is:

 /etc/vg/vg0003A7DA0000D30000000120CEE8994C

Review of agent code and system dump information in conjunction with IBM determined that an issue exists with an AIX OS scheduler function which does not return on TL7 and TL8.

Resolution

Killing and restarting the LVMVG Agent may work as a temporary solution to the issue.

To stop and restart the LVMVG Agent, perform the following steps:

1) Determine the applicable process(es).

# ps -ef | egrep -i 'LVM|lsvg'

2) Kill the process(es)

kill -9 (PID of LVM Agent)

kill -9 (PID of hung lsvg commands) 

3) Restart the LVMVG Agent

# /opt/VRST/bin/haagent -start LVMVG -sys (nodename)

 

To permanently resolve the issue, apply IBM APAR IV17508 onto the cluster nodes running TL8.

Where the cluster node is running TL7, an update to TL8 is necessary.

Please contact IBM Technical Support for any additional information or to acquire any necessary TL or APAR packages to resolve the issue.

 


Applies To

AIX 6.1 TL7
AIX 6.1 TL8

Issue/Introduction

After an uptime of several weeks, any attempt to run the "lsvg" command results in a failure to return output. Other volume group related commands may also be unresponsive. Multiple instances of "lsvg" may be seen in "ps" command output. Multiple instances of the LVMVG Agent may appear in "ps" command output. The issue may affect a specific single volume group (VG) while other VGs appear unaffected, or multiple VGs.