Skip to main content
NetApp Knowledge Base

Extremely latency on volume from CPU N-blade

  1. Last updated
  2. Save as PDF
Views:
335
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

ONTAP 9

Issue

  • Extremely latency on volume from CPU N-blade
  • The VLDB lookups failure in ASUP SKTRACE.GZ
2022-10-24T02:34:02Z 113535092315613186   [12:0] SPINVFS_COMMON_RPC:  spin_msid_vol_lookup: tid=(101000:mgwd) attempt=24, ttl=4971 ms error=35, last_error=60
2022-10-24T02:34:02Z 113535092315615356   [12:0] SPINVFS_COMMON_RPC:  spin_msid_vol_lookup: tid=(101000:mgwd) attempts=25, ttl=972 ms error=5
  • The VLDB time-out from ASUP EMS-LOG-FILE.GZ
Mon Oct 24 10:34:00  0800 [cluster-01: nblade2: Nblade.vldb.Timeout:error]: Request from the network module to the volume location database (VLDB) timed out.
  • Failed to get volume information for volume in ASUP MGWD.GZ
Mon Oct 24 2022 10:31:52  08:00 [kern_mgwd:error:2177] Failed to get volume information for volume with uuid 00000000-0000-0000-0000-000000000000. Reason: entry doesn't exist [at src/tables/rest/volume_rest_util.cc:31 in 'get_vserver_and_volume_from_uuid']
 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.