Skip to main content
NetApp Knowledge Base

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

Views:
97
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
nfs
Last Updated:

Applies to

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

Issue

  • Clients receive "nfs server not responding" messages.
    • Aug 23 13:08:29 linux kernel: [1966881.247069] nfs: server fileserver.domain.com 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 10.10.10.22:691. The local IP address:port is 10.10.10.23:2049. 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.

 

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