> I'm still experiencing _many_ NFS errors.
> T have a NFS mounted home directory and in this home dir is the MH
> mailbox area. I'm using exmh and other MH tools for e-mail, so the NFS
> code is stress tested with this setup. The server is running unfsd
> 2.2beta4 and kernel 2.0.33
> for example stat'ing the ~/Mail/inbox dir gives the following kernel
> loki kernel: nfs_revalidate_inode: Mail/inbox getattr failed, ino=554541071, error=-116
> Aug 6 12:20:26 loki kernel: NFS: bad fh 210da00f6160230500001b540000000000000000000000000000000000000000
> Aug 6 12:20:26 loki kernel: 210da00f6160230500001b540000000000000000000000000000000000000000
> ls -lid ~/Mail/inbox gives the following output:
> 554541071 drwx------ 2 xxxx xxxx 24576 Aug 6 13:15 /users/mla/Mail/inbox/
> The application gets an ESTALE error.
Error 116 is ESTALE, though from the diagnostic messages it's not clear why the server thinks the filehandle
is stale. The first hex dump is the current NFS fh the client is using, and the second line is the fh the
server thinks would be correct (i.e. the result of a lookup.) Unless I've misread the lines above, the two
values are identical.
You might see if there's some way to log errors on the server to find out why the fh is being declared
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html