Skip to main content
NetApp Knowledge Base

NFS stale file handle errors on creating new files or directories after hardware issue

Last Updated:

Applies to

  • ONTAP 9
  • NFSv3


  • Files can be listed and browsed by an NFS client, but new files or directories can't be created
  • Creating a new file fails with error
[root@hostname nfsmount]# touch filetest
touch: cannot touch `filetest': Stale file handle
  • ONTAP EMS log has error that the volume is marked nvfailed

Tue Aug 24 23:04:21 +0200 [node1: wafl_exempt08:]: Volume vol1@vserver:0a1f9157-e57b-11e3-b6f3-123478561223 is marked as in-nvfailed-state: NVRAM not in sync.
Wed Aug 25 00:00:06 +0200 [node1: statd: wafl.vol.nvfail.recovery.needed:notice]: Volume vol1@vserver:0a1f9157-e57b-11e3-b6f3-123478561223 is marked as in-nvfailed-state. The recovery process needs to be initiated on the volume to recover from the NVFAIL event

  • Nvfailed state is set to true for the volume

cluster::> set advanced

cluster::*> vol show -vserver vs1 -volume vol1 -fields in-nvfailed-state
vserver volume in-nvfailed-state
------- ------ -----------------
vs1    vol1   true


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.