Skip to main content
NetApp Stage KB

NFS server not responding or NVRAM takes more time than normal on CVO instance

Last Updated:

Applies to

  • ONTAP 9
  • Cloud Volumes ONTAP for AWS
  • Cloud Volumes ONTAP for Azure


  • Clients receive "nfs server not responding" messages.
    • Aug 23 13:08:29 linux kernel: [1966881.247069] nfs: server not responding, still trying
  • EMS indicates a long operation
    • Mon Aug 23 12:02:23 +0100 [ONTAP-01: wafl_exempt13: vnvram.dma.long.wait:alert]: vNVRAM flush taking over 10 seconds.
    • Mon Aug 23 12:02:38 +0100 [ONTAP-01: kernel: Nblade.nfsLongRunningOp:debug]: Detected a long running network process operation. The client IP address:port is The local IP address:port is The protocol requesting the operation is NFS3. The RPC program number for the operation is 100003. The protocol procedure for the operation is Write (7). The disk process UUID is 210137455afd11eb9a0e000d3ad879a8. The Vserver associated with the operation is SVM01. The UID of the user is 769. The MSID for the volume is 2163530000. The inode number of the file is 350.


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.