NFSv4 fails with error NFS4ERR_STALE errors on the client
Applies to
- ONTAP 9 and later
- NFSv4.x
Issue
- Failure is seen on the Client kernel logs:
Jul 25 10:42:54.598 host nfs: [ID 698999 kern.notice] NOTICE: [NFS4][Server: 10.xx.xx.1][Mntpt: /mountpoint]NFS op OP_LOOKUP got error NFS4ERR_STALE(70) causing recovery action NR_STALE.
Jul 25 10:42:54.598 host nfs: [ID 698999 kern.notice] NOTICE: [NFS4][Server: 10.xx.xx.1][Mntpt: /mountpoint]NFS op OP_GETATTR got error NFS4ERR_STALE(70) causing recovery action NR_STALE.
Jul 25 10:42:54.598 host nfs: [ID 698999 kern.notice] NOTICE: [NFS4][Server: 10.xx.xx.1][Mntpt: /mountpoint]NFS op OP_LOOKUP got error NFS4ERR_STALE(70) causing recovery action NR_STALE.
Jul 25 10:42:54.598 host nfs: [ID 698999 kern.notice] NOTICE: [NFS4][Server: 10.xx.xx.1][Mntpt: /mountpoint]NFS op OP_GETATTR got error NFS4ERR_STALE(70) causing recovery action NR_STALE.
Jul 25 10:42:54.598 host nfs: [ID 286389 kern.notice] NOTICE: [NFS4][Server: 10.xx.xx.1][Mntpt: /mountpoint]File ././directory1/directory2/folder/file (rnode_pt: 18401939e87d8) was closed due to NFS recovery error on server 10.xx.xx.1(failed to recover stale file handle NFS4ERR_STALE)
Jul 25 10:42:54.598 host nfs: [ID 941083 kern.notice] NOTICE: NFS4 FACT SHEET:
Jul 25 10:42:54.598 host Action: NR_STALE
Jul 25 10:42:54.598 host NFS4 error: NFS4ERR_STALE
- The Error "NFS4ERR_STALE" indicates that the file system object referred to by that filehandle no longer exists, or access to which has been revoked
- File does not exist in Ontap when verified using command:
cluster::> file-directory show -vserver svm1 -path /directory1/directory2/folder/file
Error: show failed: The specified path "directory1/directory2/folder/file" cannot be used. Reason: No such file or directory