Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!labrea!rutgers!mailrus!ncar!noao!amethyst!spock!chris From: chris@spock (Chris Ott) Newsgroups: comp.unix.questions Subject: Re: WHat is "Stale NFS handle"? Message-ID: <877@amethyst.ma.arizona.edu> Date: 20 Jan 89 14:39:19 GMT Sender: news@amethyst.ma.arizona.edu Reply-To: chris@spock.ame.arizona.edu (Chris Ott) Distribution: na Organization: Computer-Aided Engr. Lab (CAEL), University of Arizona, Tucson Lines: 35 >I have a VAXstation 2000 running Ultrix 2.2, using NFS >to use the /usr/local of a MicroVAX II, also running Ultrix. >Yesterday, I could no longer access some files, and got the >message "stale NFS handle". What circumstances cause this? I've seen this message once myself. Unfortunately, my experience was on a Sun. I'm not sure it will apply to your Vax. It was the following situation: On a server, there was a directory mounted from the root filesystem, say "dir1". Then, somewhere inside "dir1" was mounted another filesystem, say "dir2". So, if you wanted to get to "dir2" on the server, you would use the path "/dir1/dir2". For clients, the first thing that came to my mind is that, if you can get to "dir2" with "/dir1/dir2" on the server, you should be able to do the same on the clients, but only have to mount "dir1". I was wrong. Any attempt to get to "dir2", such as "cd /dir1/dir2" would give the message "stale NFS handle". Both "dir1" and "dir2" have to be mounted on the clients as well as the server. Hope that helps. Chris ------------------------------------------------------------------------------- Chris Ott Computational Fluid Mechanics Lab Infatuation is blind, not love. A University of Arizona person in love can see the other's faults, but loves them anyway. Internet: chris@spock.ame.arizona.edu UUCP: {allegra,cmcl2,hao!noao}!arizona!amethyst!spock!chris -------------------------------------------------------------------------------