OOh, I went through this headache. Hard to get info. If you check the archives for two or three months ago I might of explained how I finally figured it out (I don't remember now). You have to take the 4th or 5th number from the error number I think and convert it from hex to decimal, and that'll give you the inode. Now one is a 16 bit file inode which you can't ever find that inode on the system because that's a netapps inode, but what you CAN find in that string of numbers is the inode for the directory where the file was, which would be on an mounted partition. That's the closest I got, but it was enough.
I know the docs off of netapps were wrong and I had a discussion here with someone from netapps about that (helpful people), and I had also tried reading sunworld online's "errno libretto" document, both which were wrong but gave me leads of where to persue this. Search the archives at :
http://teaparty.mathworks.com:1999/toasters/
Sorry can't be much more helpful...
On Fri, 23 Jul 1999, Elizabeth Schwartz wrote:
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!)
----------- Fujitsu - Nexion, St. Louis, MO Jay Orr (314) 579-6517