Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: richard%aiai.edinburgh.ac.uk@nsfnet-relay.ac.uk (Richard Tobin)
Newsgroups: comp.sys.sun
Subject: Bizarre nfs problem
Keywords: SunOS
Message-ID: <3645@kalliope.rice.edu>
Date: 1 Jun 89 17:34:43 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 27
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 13, message 8 of 17

Bute is a 4/260 running 4.0.1.  Skye is a 3/280 running 3.5.  Staffa is a
3/260 running 3.2.  Bute and staffa mount /usr/skye2 (rw, hard, intr)
from skye.

User rt has a file thesis.tex in /usr/skye2, which he edits with gnu emacs
on staffa.  However, the new version of the file isn't visible on bute
where he runs latex on it.  Indeed, it looks very strange:

 34906 -rw-r--r--  1 rt           1865 May 31 14:46 thesis.tex
 34906 -rw-r--r--  1 rt           1865 May 31 14:46 thesis.tex.~38~

Two files, each with the same inode number, with but a single link each!

If user richard (me) looks at it (on bute):

 34889 -rw-r--r--  1 rt           1811 Jun  1 18:06 thesis.tex
 34906 -rw-r--r--  1 rt           1865 May 31 14:46 thesis.tex.~38~

If rt looks at it from a different machine he see the right thing (ie
the same as me).

Fsck on skye says that the filesystem is fine.  So it seems to be a
problem with nfs on bute.  This seems very strange (especially that it
depends on the user - does nfs do per-user cacheing?).  Is there a known
bug that could account for it?

Richard