Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!ncar!ames!zodiac!spark!mliverig
From: mliverig@Verity.COM (Mike Liveright x7627)
Newsgroups: comp.unix.questions
Subject: Robust Mounts
Summary: How does one make an NFS system failure resistant?
Keywords: NFS MOUNT HARD SOFT AUTOMOUNT LOCKUP
Message-ID: <10284@zodiac.ADS.COM>
Date: 4 Jan 90 17:50:54 GMT
References: <21956@adm.BRL.MIL>
Sender: news@zodiac.ADS.COM
Reply-To: mliverig@spark.UUCP (Mike Liveright x7627)
Organization: Verity, Inc., Mtn. View, CA  94043, (415) 960-7600
Lines: 22

A few months back there was a discussion about making "nfs" networks
robust. It was my impression that there was a consensus that:

1) Soft mounts of read-write file systems would increase the risk of
corrupting the file systems.

2) Automounting was a good idea that was not yet safe.

3) Hard mounts should be done at points such that when a "get current
directory" was done it would not "run" into dead mount points, e.g. if the
user was in directory = /a/b/c, then it was important not to mount another
disk at location /a/aa as this would lead to a lockup as the "get current
directory" tried to find "b" in /a, and ran into the dead "/a/aa".

Question:
  a) Is this a correct summary of the situation today relative to sun 4.0.1,3
  b) Are there other thoughts as to increasing the robustness of networked 
         CPU's

I will summarize the responses if there seems to be interest. Thanks...
    Mike Liveright, VERITY, mliverig@verity.com
---------------------------------------------