From owner-freebsd-current  Mon Jun  1 11:29:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA29596
          for freebsd-current-outgoing; Mon, 1 Jun 1998 11:29:31 -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 LAA29588
          for <current@FreeBSD.ORG>; Mon, 1 Jun 1998 11:29:28 -0700 (PDT)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.8/8.8.5) id NAA20244;
	Mon, 1 Jun 1998 13:29:24 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199806011829.NAA20244@home.dragondata.com>
Subject: Re: NFS discovery
In-Reply-To: <199806011751.NAA29921@xxx.video-collage.com> from Mikhail Teterin at "Jun 1, 98 01:51:03 pm"
To: mi@video-collage.com (Mikhail Teterin)
Date: Mon, 1 Jun 1998 13:29:24 -0500 (CDT)
Cc: 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

> Kevin Day once stated:
> 
> =However entering this on the client machine
> =
> =mount -u -o async /home
> =
> =*while* the client's nfs is hosed will make it recover within 5
> =seconds. It even appears that all the writes that were queued are
> =executed, and no data is lost.
> 
> That's a great thing to know. Those hungups are damn annoying.
> The reason is, probably, a side effect of how `-u'/`async' are
> implemented. AFAIK, the fs is unmounted and then remounted with
> async. Which is just what you wanted.

That's my thought too, but:

umount /home

will freeze, so it's not exactly unmounting things. :)

> 
> =Is there any way of making whatever it was that did this happen
> =automatically every once in a while? :)
> 
> 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...

Don't read my post as a complaint, rather as a 'hey, why does it do this?"
:)

Kevin

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