Skip to main content
NetApp Knowledge Base

NFS data serving disruption after a Node panic or halt

Views:
270
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9.7P8
  • FlexGroup
  • AFF-A800
  • 4 or more nodes in the Cluster

Issue

  • NFS data serving disruption after a Node panic or halt
  • FlexGroup operations stalled or appear stuck for several minutes when one or more of the nodes are halted
  • EMS log: 
[cluster01-n05: FgGroupListTimer: fg.stateChange:notice]: FlexGroup workspace01 (fg-uuid 96f2562a-xxxx-xxxx-xxxx-00a098f3e4e7) has changed state from online to not online.
 
[cluster01-n05: CsmMpAgentThread: csm.createSessionFailed:debug]: Cluster Session Manager (CSM) failed to create session (req=cluster01-n05:dblade, rsp=custer01-n07:dblade, uniquifier=1105xxxxxxxxa0c3) with record state STARTING, CSM error CSM_CONNABORTED, low-level error UNKNOWN, socket error 0, and TLS error 0.
 
[cluster01-n05: client_common_RPC: csm.invalidDSID:debug]: params: {'dsid': '1968-0', 'lineno': '1359', 'filename': 'src/Csm/BladeLocationService.cc'}

[cluster01-n05: kernel: Nblade.dBladeNoResponse.NFS:error]: File operation timed out because there was no response from the data-serving node. Node UUID: ee6c434e-xxxx-xxxx-xxxx-00a098f3e4e7, file operation protocol: NFS, client IP address: x.x.x.x, RPC procedure: 17.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support