From owner-freebsd-current  Mon Jun  1 16:09:55 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA03277
          for freebsd-current-outgoing; Mon, 1 Jun 1998 16:09:55 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03263
          for <current@FreeBSD.ORG>; Mon, 1 Jun 1998 16:09:47 -0700 (PDT)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.8/8.8.5) id SAA17484;
	Mon, 1 Jun 1998 18:09:26 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199806012309.SAA17484@home.dragondata.com>
Subject: Re: NFS discovery
In-Reply-To: <35730F59.510D55FB@tdx.co.uk> from Karl Pielorz at "Jun 1, 98 09:30:17 pm"
To: kpielorz@tdx.co.uk (Karl Pielorz)
Date: Mon, 1 Jun 1998 18:09:26 -0500 (CDT)
Cc: mi@video-collage.com, current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Mikhail Teterin wrote:
> 
> > NFS hung ups are a strange topic, in my experience. People agree
> > that they are "bad", but one is not supposed to complain about
> > them...
> 
> I remember having a long conversation with a friend a few years back (can I
> get any more vague?) - Where he was praising NFS's ability to crash - as it
> assures that say your running a program on a remote system, it will either
> run to completion - or hang if the server dies... 
> This I presume works on the assumption that it helps somehow to have a
> client that's 'hung' in mid-air (i.e. at least you know if failed) rather
> than risking any corruption that might have been caused by the server
> disappearing for a while...
> 
> I think you can change this behaviour - have a look at the man page for
> 'mount_nfs' - in particular things like the '-i' option & 'soft' mounting
> etc...
> 

My two problems are slightly different though.

1) After enough processes get 'hung', the entire box dies.

2) After the server comes back, the client never recovers.

(I'm using both -i and -s)

Kevin

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message