Oracle ZFS Storage Appliance: NFS client reports NFS4ERR

Asset ID:	1-72-2135382.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 2135382.1 : Oracle ZFS Storage Appliance: NFS client reports NFS4ERR_STALE error while accessing a file

Applies to:

Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-2 - Version All Versions to All Versions [Release All Releases]
Sun Storage 7410 Unified Storage System - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

Clients using NFS shares from a ZFS Storage Appliance report NFS4ERR_STALE error in the messages file.

example :

Apr 1 21:47:03 ps-hial-wls2 nfs: [ID 236337 kern.info] NOTICE: [NFS4][Server: ehrps0-storIB][Mntpt: /zfs/zones/ps-hial-wls2/root/u01/oracle/config]NFS op OP_CLOSE got error NFS4ERR_STALE causing recovery action NR_STALE.
Apr 1 21:47:03 ps-hial-wls2 nfs: [ID 286389 kern.info] NOTICE: [NFS4][Server: ehrps0-storIB][Mntpt: /zfs/zones/ps-hial-wls2/root/u01/oracle/config]File ./iehr/hial/logs/alert-wls_soa21-wls_soa22-2016-04-01-21-47.txt (rnode_pt: c40773a0c7d8) was closed due to NFS recovery error on server ehrps0-storIB(failed to recover from NFS4ERR_STALE NFS4ERR_STALE)
Apr 1 21:47:03 ps-hial-wls2 nfs: [ID 941083 kern.info] NOTICE: NFS4 FACT SHEET: #012 Action: NR_STALE #012 NFS4 error: NFS4ERR_STALE

Cause

In case of a shared filesystem, like NFS, if the file does not exist then this type of error reported at the client side is normal.

When an application tries to access a non-existent file, these errors are reported indicating a stale file handle.

A client application will log an NFS4ERR_STALE error when the 'file handle' is not accessible or is removed (by some other process).

Solution

When you get this error, check whether the file given in the message exists or not ?

Who (which application) is responsible for creating and deleting this file ?

NOTE: This is not an issue from the storage side, but it simply means the file being accessed does not exist.

(If the same error occurs and the file does exist - investigate the reason why it is not accessible.)

Attachments

This solution has no attachment