We have a solaris 2.6 server with MANY users, that is getting regular "NFS stale file handle" errors. We have the file handle from /var/adm/messages but we do not know which process is generating the error.
Is there anything we can do to get a file name from the file handle, to help identify which process is the source? Rebooting this machine is a last resort option since it is a primary user server (meaning we'd have to do it in the wee hours)
thanks Betsy (new to the list, hello all!)
We have discovered that if a user has ksh processes running on two different NFS clients and the ksh processes are using the same NFS mounted history file, that this usually results in "stale NFS handle" messages when one of the ksh processes exits.
This is a fairly common occurrence for us because we have a cluster of unix servers mounting home directories from a netapp. If a user logs in to two different unix boxes he usually gets the same history file in both login sessions. So we have two ksh processes on two different NFS clients banging on the same history file.
We've only seen this behavior with ksh. It also happens when the NFS server is not a netapp.
Steve Losen scl@virginia.edu phone: 804-924-0640
University of Virginia ITC Unix Support