After installing Volume Manager patch 7.4.2.5400/8.0.2.1504, vxio "took longer to complete" messages seen

book

Article ID: 100073042

calendar_today

Updated On:

Description

Error Message

Example errors seen in /var/log/messages:

Nov  7 03:47:26 server101 kernel: VxVM vxio V-5-0-0 read on disk: ibm_shark0_7 took longer to complete (off: 41280 len: 2048 error: 0 latency: 18445017469126 threshold: 240)
Nov  7 03:47:26 server101 kernel: VxVM vxio V-5-0-0 read on disk: ibm_shark0_7 took longer to complete (off: 43328 len: 2048 error: 0 latency: 18445017469126 threshold: 240)

 

Cause

When the vol_ioship_stats_enable tunable is disabled, the start time of volume IO is reset by Dynamic Multipathing (DMP) in a different format, causing a large discrepancy when comparing the two time formats, which leads to the issue.

 

Resolution

There are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time.  However, the issue has been addressed in the revision of the product specified at the end of this article. 
 
Please contact your Sales representative or the Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.

 

A hot-fix has been made available for this issue. Please contact Technical Support to obtain this fix. The issue is fixed in 8.0.2 Update 5 and also in 7.4.2 on the https://www.veritas.com/content/support/en_US/downloads/update.UPD516448 public patch.

Once the fix is applied, the vxio messages should not be seen in the system log file, regardless of the vol_ioship_stats_enable tunable.

 

Issue/Introduction

After installing Volume Manager patch 7.4.2.5400/8.0.2.1504, vxio "took longer to complete" messages seen

Additional Information

JIRA: STESC-9306