Skip to main content

This Site will be down for up to 3 hours on December 2, 2023 from 8 PM - 11 PM PST, to deploy an infrastructure update.

NetApp Knowledge Base

What data should I collect for NFSv4 StorePool issues?

Last Updated:

Applies to

  • ONTAP 9
  • NFSv4.x


  1. EMS Messages provide a significant amount of information to help narrow down your troubleshooting
    • Trigger an AutoSupport to provide this to support
    • Take note of the Node Management lif for the node reporting the error
  2. Statistics provide guidance to see if any buckets are full and what instance they are associated with
    • What are performance archives and how are they triggered?
    • statistics start can be used to collect a sample over a period of time that can be referenced many times.
    • Use the REST API call to check for storePool_* counters:
      • curl -siku "admin:PASSWORD" https://Cluster-Mgmt-IP/api/cluster/counter/tables/nfs_v4_diag/rows/
        NOTE:  use the response from above to run the second call per node to get the storePool counters like in example below.


        curl -siku "admin: PASSWORD " https://Cluster-Mgmt-IP/api/cluster/counter/tables/nfs_v4_diag/rows/Cluster-01%3Cluster-01%3A67261b3
    • Objects that can be relevant to storepool
      • nfsv4
      • nfsv4_diag
      • nfsv4_error
      • nfsv4_1_error
      • nfsv4_1_diag
      • nfsv4_1
      • spinnp_error
      • spinnp
      • spinhi
      • lmgr_ng
  3. Collect Locks from the node to see current utilization, vserver locks nfs4 is node scoped
  4. If a top client was identified previously, collect a packet-trace filtered for that client for 5 minutes while the issue is occurring
  5. Collect this data again if LIF migration is done to mitigate the issue.
  6. Be sure to substitute in the node management IP for the node where the LIF now resides.


Additional Information

  • NFSv4 Storepool - Resolution guide 
  • A bash script has been provided to facilitate easier collection of this data

    #Set the IP address of the node management server
    #Set the username to user during authentication (Ideal to use pubkey auth)
    #Create a directory to store the statistics
    mkdir -p statistics/$NODE_MANAGEMENT
    #Collect the statistics for NFSv4 and NFSv4_1
    for version in nfsv4 nfsv4_1
        for TYPE in "" "_diag" "_error"
            ssh $USERNAME@$NODE_MANAGEMENT "set d -c off; rows 0; date; statistics show -object $version$TYPE -raw" >> statistics/$NODE_MANAGEMENT/nfs.txt
    #Collect the statistics for spinnp
    for TYPE in spinnp_error spinhi spinnp
        ssh $USERNAME@$NODE_MANAGEMENT "set d -c off; rows 0; date; statistics show -object $TYPE -raw" >> statistics/$NODE_MANAGEMENT/spin.txt
    #Collect the statistics for lmgr_ng
    ssh $USERNAME@$NODE_MANAGEMENT "set d -c off; rows 0; date; statistics show -object lmgr_ng -counter files|hosts|owners|locks|*max -raw" >> statistics/$NODE_MANAGEMENT/locks.txt
    #Collect the statistics for vserver locks nfsv4
    ssh $USERNAME@$NODE_MANAGEMENT "set d -c off; rows 0; date; vserver locks nfsv4 show -inst" >> statistics/$NODE_MANAGEMENT/locks.txt
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.
Scan to view the article on your device