lkml.org 
[lkml]   [1998]   [May]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: nfs v2.1.103 alpha staleness
Pete Wyckoff wrote:
>
> I repeatedly see console messages of the form:
>
> nfs_revalidate_inode: lib/ld-2.0.5.so getattr failed, ino=151011339, error=-70
> NFS: bad fh 0900400b48470b04000000dc0000000000000000000000000000000000000000
> 0900400b48470b04000000dc0000000000000000000000000000000000000000
>
> on an NFS client which mounts its / filesystem. Both server and client are
> linux-alpha v2.1.103. When the server is v2.0.30, same problem. When the
> client is v2.0.30, no such problems. 70 is ESTALE on the alpha.

Hi Pete,

The stale filehandle message was added to try to track down the cause of
these sporadic failures. The first line shows the filehandle the client
is currently using, and the second line shows the result of a new lookup
-- i.e., what the server thinks the fh _should_ be. What's really
puzzling is that in your case the two are identical, making it appear
that the failure is spurious.

I would have expected the two fh values to differ in some way, or for a
lookup error to occur when trying to get the current fh (e.g. if someone
else deleted the file on the server.)

Are you using the knfs server or the unfsd? Any pattern to the messages?

Regards,
Bill

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

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