Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!gordius!johnk
From: johnk@gordian.com (John Kalucki)
Newsgroups: comp.protocols.nfs
Subject: Re: perculiar NFS behaviour
Message-ID: <130@gordius.gordian.com>
Date: 16 Apr 91 17:02:23 GMT
References: <1991Apr15.045511.6354@massey.ac.nz>
Sender: news@gordian.com
Reply-To: johnk@gordian.com (John Kalucki)
Organization: Gordian; Costa Mesa, CA
Lines: 22

In article <1991Apr15.045511.6354@massey.ac.nz>, G.Eustace@massey.ac.nz (Glen Eustace) writes:
|> [...]
|> All in all the only way to fix this was to reboot the pyramid.  Not a
|> solution I like but it did work.  I am perplexed with why such a simple
|> command like 'ls' or 'find' on a local file system should cause a
|> 'getattr' call on an entirely different remote file system.
|> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|> Glen Eustace, Systems Software Manager | EMail: G.Eustace@massey.ac.nz
|>  Computer Centre,  Massey University,  Palmerston North,  New Zealand
|> Phone: +64 63 69099 x7440, Fax: +64 63 505 607,       Timezone: GMT-12

What is probably happening is the gettattr is being called on the
nfs mount point as it walks up the tree.  This is the exact same
problem that I posted a few weeks ago about my Mips machines. I've
mounted them as follows and it has helped a bit:

alecto:/n/alecto        /n/alecto       nfs bg,rw,soft,timeo=2,intr 0 0

..but what I'd really like is some method to allow me to umount a
dead nfs filesystem.

		-John Kalucki