Skip to main content
NetApp Knowledge Base

Early signs of latency on Flexgroups

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

Applies to

  • ONTAP 9
  • Flexgroups

Issue

  • No access to flexgroups across the entire cluster
  • EMS messages found in all nodes in the cluster:
Wed Oct 05 08:49:06 -0500 [Node: wafl_exempt04: wafl.xmem.nomemory:debug]: Unable to allocate memory through the xxxx.lng_strings.lns_freelist freelist. Allocation size: 5280 bytes.
Wed Oct 05 08:56:57 -0500 [Node: wafl_exempt22: ems.engine.suppressed:debug]: Event 'wafl.xmem.nomemory' suppressed 421 times in last 470 seconds

Wed Oct 05 00:23:23 -0500 [Node: kernel: Nblade.dBladeNoResponse.NFS:error]: File operation timed out because there was no response from the data-serving node. Node UUID: xxxx, file operation protocol: NFS, client IP address: xx.xx.xxx.xxx, RPC procedure: 1.

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.