[721] in Hotline Meeting
"rs1.new"
daemon@ATHENA.MIT.EDU (David Krikorian)
Fri Jun 8 05:07:58 1990
Date: Fri, 8 Jun 90 05:07:38 -0400
From: David Krikorian <dkk@ATHENA.MIT.EDU>
To: kevles@ATHENA.MIT.EDU
Cc: hotline@ATHENA.MIT.EDU, rita@ATHENA.MIT.EDU, op@ATHENA.MIT.EDU,
Reply-To: dkk@ATHENA.MIT.EDU
You wrote:
------------
> The user at m36-878-1 tried to attach rs1.new, but first got a
> timeout on talos (no mention of odysseus!) and then started getting
> kerberos errors.
The rs1.new locker is a filesystem group containing two filesystems:
tisiphone% hes rs1.new filsys
NFS /u3/lockers/rs1.new.2 odysseus r /mit/rs1.new
NFS /u4/lockers/rs1.new talos r /mit/rs1.new
When the first one fails, attach tries the second without displaying
the error from the first. Since both failed for the user, only the
Talos error appeared in the window.
Here's a test to see if the individual filesystems work:
------------
tisiphone% attach -e odyss:/u3/lockers/rs1.new.2
odyss:/u3/lockers/rs1.new.2: Error message returned from server ODYSSEUS.MIT.EDU: No such file or directory
tisiphone% attach -e talos:/u4/lockers/rs1.new
talos:/u4/lockers/rs1.new: NFS mounted talos.MIT.EDU:/u4/lockers/rs1.new...
------------
The attach from Talos worked fine, but note the error from the first
attach (from Odysseus). Also:
tisiphone# rsh odyss ls -d /u3/lockers/rs1\*
/u3/lockers/rs1.old
This would imply that maybe "rs1.old" on Odysseus should be rs1.new
(that seems unlikely), or perhaps that the proper locker was moved
elsewhere, and the Hesiod entry wasn't corrected. In either case, the
User Accounts staff should be able to fix it.
