lkml.org 
[lkml]   [1999]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: NFS errors.
From
Date
Justin Hahn <jehahn@raven.bu.edu> writes:

> Running knfsd 1.2.2a on kernel 2.2.6. Getting a LOT of these. NFS
> debugging is off. Machine is talking to a heavily patched Solaris
> 2.5.1 machine. Pretty sure the Sun machine is the server (need to
> check with the user on his pattern.) Anyone care to interpret? This
> looks like the error I used to get when we got data corruption.
>
> May 26 13:37:20 pelican kernel: nfs_revalidate_inode: labels/MalePhoneTranscripts.mlf getattr failed, ino=712003, error=-116
> May 26 13:37:20 pelican kernel: NFS: bad fh 0000000000000000000000000000000000000000000000000000000000000000
> May 26 13:37:20 pelican kernel: NFS: lookup failed, error=-116
> May 26 13:37:20 pelican kernel: nfs_revalidate_inode: labels/MalePhoneTranscripts.mlf getattr failed, ino=712003, error=-116
> May 26 13:37:20 pelican kernel: NFS: bad fh 0000000000000000000000000000000000000000000000000000000000000000
> May 26 13:37:20 pelican kernel: NFS: lookup failed, error=-116
>

The file handle is zero, so you're getting 'Stale file handle' (-ESTALE
== -116) messages.
If the client thinks you have a stale inode (i.e. somebody on another
machine has deleted the file, and the file handle has been reused by
the server) it will set the file handle to zero and the above messages
may occur.

Please note that Linux-2.2.9 (well 2.2.8 is first actually) fixes a
few bugs w.r.t. whether an inode is considered to be stale or not.

Cheers,
Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:52    [W:0.027 / U:0.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site