Skip to main content
NetApp Knowledge Base

NFS gets hung after issued command volume flexcache config-refresh

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

Applies to

  • ONTAP 9
  • FlexCache

Issue

NFS gets hung after issued command volume flexcache config-refresh:

[?] Fri Oct 29 13:47:13 +0800 [node1: kernel: Nblade.dBladeNoResponse.NFS:error]: File operation timed out because there was no response from the data-serving node. Node UUID: b13937a2-375c-11ea-94a4-xxxxx, file operation protocol: NFS, client IP address: xxx, RPC procedure: 3.
Fri Oct 29 13:55:18 +0800 [node1: nblade1: Nblade.JunctionRootLookup2:error]: Junction root lookup of a volume in Vserver 3 with MSID xxxxx has failed for reason "CSM_TIMEOUT".

[?] Fri Oct 29 17:03:45 +0800 [node1: CSM BTLS:csm.createSessionFailed:debug]: Cluster Session Manager (CSM) failed to create session (req=node2:dblade,rsp=node1:dblade, uniquifier=0205cf7a13axxxxx) with transport type CT, record state ACTIVE, CSM error CSM_CONNABORTED,low-level error UNKNOWN, socket error 0, and TLS error 0

 

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.