Skip to main content
NetApp Knowledge Base

Nblade.dBladeNoResponse.NFS Errors when accessing FlexCache cached volumes

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

Applies to

  • ONTAP 9
  • FlexCache
  • NFS

Issue

  • Customers observe persistent EMS log errors similar to:
  • Nblade.dBladeNoResponse.NFS: File operation timed out because there was no response from the data-serving node.
  • NodeUUID: 0df1a59c-16f1-11f0-a67e-d039eac2418a, file operation protocol: NFS, client IP address: 2620:10d:c086:a::403, Opcode/Procedure: NFS3_ACCESS(4)
  • And in debug logs:
  • CfVldbDebug_ERROR: VldbRpcJunctionLookupResponse: vldbrpcresult 162, junction 0x0|2149489380.0|655954|476220248
  • CfVldbDebug_ERROR: VldbRpcJunctionLookupResponse: vldbrpcresult 162, junction 0x0|2149489380.0|13457134|798661158
  • Clients accessing FlexCache volumes experience NFS3_EJUKEBOX errors, and monitoring systems are spammed with Nblade.dBladeNoResponse.NFS events. NFS access to the FlexCache cache volume may hang

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.