Operating System - Tru64 Unix
1827474 Members
2061 Online
109965 Solutions
New Discussion

Re: nfs error in messages file

 
AKSHAY.DANAK
Occasional Contributor

nfs error in messages file

Mar 11 11:11:26 ALPHAEH5 vmunix: NFS server: stale file handle fs(3614,468006) file 24880 gen 32770
Mar 11 11:11:26 ALPHAEH5 vmunix: RFS3_READ, client address = 150.0.150.3, errno 22

The server is ES40 with 5.1tru-64.
Doubting that only nfs mount was attemted from other server with ip 150.0.150.3

Has anybody faced this errorno 22.

Regards,
Akshay.Danak
3 REPLIES 3
Ralf Puchner
Honored Contributor

Re: nfs error in messages file

use "search" and enter "stale" "nfs".
You will get suitable answers for your problem.
Help() { FirstReadManual(urgently); Go_to_it;; }
Al Licause
Trusted Contributor

Re: nfs error in messages file

A stale file handle can occur under many different circumstances. It is most often seen when a client attempts to access a file or files on an nfs server which may have rebooted in which case, the file handles
are no longer valid, which may account for the errno=22 which equates to an invalid argument.

I would start by looking through other log files on both the client and the server for events that might have occured around the time of the error listed.

Check to see if anything has changed recently in the network configuration or host environments for either client or server.

Check for errors on both client and server (netstat -i).

Check to see if the server has spiked in terms of cpu utilization.

Check to see if there is a difference in network interface speeds between
the client and the server and if so, see if this is a recent change.

Check to see if these are new errors or something that has been occuring
for some time.

If you can supply more information, perhaps we can be of further assistance.
Radouan Bouzite
Advisor

Re: nfs error in messages file

If you are using ADVFS, you can usr /sbin/advfs/tag2name /mountpoint/.tags/24880 to convert a tag 24880 to a filename,

I have some messages, and I found that some files in shared directory are being accessing by two process in the same time .
(ie , one is copying the file and the other try to move it to another direcory)