Messages in this thread | | | Date | Mon, 19 Oct 1998 11:36:48 -0500 (CDT) | From | "Robert M. Hyatt" <> | Subject | Re: NFS error (Maybe off topic) |
| |
I also think that this can happen normally... without there being any kind of problem on either end, other than the client end holding on to a handle for a long period of time, while on the server end the file, the directory or whatever has been totally removed. I've seen this several times on my notebook where I suspend and then resume later and get a couple of such errors right off the bat...
"Stateless" doesn't mean "glitchless"... :)
Robert Hyatt Computer and Information Sciences hyatt@cis.uab.edu University of Alabama at Birmingham (205) 934-2213 115A Campbell Hall, UAB Station (205) 934-5473 FAX Birmingham, AL 35294-1170
On Mon, 19 Oct 1998, Anders Hammarquist wrote:
> > Has anyone received this error before or have any idea what it means. > > > > Oct 16 01:17:00 comm6 kernel: nfs_statfs: statfs error = 116 > > 116 is ESTALE 'Stale NFS handle' - it means that the filehandle your machine > tried to use to access the file on the NFS server is no longer valid. It is > perfectly normal to see these after a reboot of the NFS server (the client > will attempt to look up a new filehandle for the file). If accessing a file > results in this and then fails with Stale NFS handle something is likely wrong > at the server, but I need more information to know for sure. > > Regards, > /Anders > -- > -- Of course I'm crazy, but that doesn't mean I'm wrong. > Anders Hammarquist | iko@cd.chalmers.se > Not system administrator at DjungelData | Hem: +46 31 47 69 27 > Chalmers University of Technology, G|teborg, Sweden | Mob: +46 707 27 86 87 > >
- 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/
| |