[1425] in linux-net channel archive
Re: Strange behaviour with NFS
daemon@ATHENA.MIT.EDU (Kurt Watkins)
Sat Nov 25 06:00:00 1995
Date: Fri, 24 Nov 1995 22:20:00 -0600 (CST)
From: Kurt Watkins <watkins@chop.swmed.edu>
Reply-To: Kurt Watkins <Watkins@chop.swmed.edu>
To: Juha Virtanen <jiivee@hut.fi>
cc: "Ed Carp [khijol SysAdmin]" <khijol!erc@vger.rutgers.edu>,
linux-net@vger.rutgers.edu
In-Reply-To: <Pine.A32.3.91.951124194509.142914D-100000@vipunen.hut.fi>
On Fri, 24 Nov 1995, Juha Virtanen wrote:
> On Thu, 23 Nov 1995, Ed Carp [khijol SysAdmin] wrote:
>
> > Um, this isn't limited to Linux - Solaris also exhibits this behavior. When one of our NFS
> > servers dumps the big one, we often have to reboot the clients. Someone suggested that the
> > mounts be changed from 'hard' to 'soft', but I don't think this would make any difference.
> >
> > Suggestions welcome...
>
> Make NFS mounts both soft and interruptible. I use likes like the
> one below to do NFS mounts. Then machines can go up'n'down as
> they will and users can interrupt requests to NFS partitions easily.
>
> iguana.hut.fi:/u1 /u1 nfs bg,soft,intr,rsize=8192,wsize=8192 0 0
>
>
> Juha
FWIW, my habit is to *always* hard mount read/write filesystems and file
systems which supply executables. About the only thing I soft mount are
non-critical read-only filesystems. (This has worked particularly well
for me with some troublesome VMS boxes pretending to do NFS:)
K.
____________________________________________________________________
Kurt Watkins Watkins@chop.swmed.EDU
Howard Hughes Medical Institute Phone: (214) 648-5034
UT Southwestern Medical Center Fax: (214) 648-5066
5323 Harry Hines Blvd. Y4.106
Dallas, TX 75235-9050
