From owner-freebsd-fs@FreeBSD.ORG  Mon Jun 29 04:53:05 2009
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id BABA4106564A;
	Mon, 29 Jun 2009 04:53:05 +0000 (UTC)
	(envelope-from dg@dglawrence.com)
Received: from dglawrence.com (75-148-92-17-Oregon.hfc.comcastbusiness.net
	[75.148.92.17])
	by mx1.freebsd.org (Postfix) with ESMTP id 936088FC0C;
	Mon, 29 Jun 2009 04:53:05 +0000 (UTC)
	(envelope-from dg@dglawrence.com)
Received: from tnn.dglawrence.com (localhost [127.0.0.1])
	by dglawrence.com (8.14.1/8.14.1) with ESMTP id n5T4r5K7093361;
	Sun, 28 Jun 2009 21:53:05 -0700 (PDT)
	(envelope-from dg@dglawrence.com)
Received: (from dg@localhost)
	by tnn.dglawrence.com (8.14.1/8.14.1/Submit) id n5T4r4AK093302;
	Sun, 28 Jun 2009 21:53:04 -0700 (PDT)
	(envelope-from dg@dglawrence.com)
X-Authentication-Warning: tnn.dglawrence.com: dg set sender to
	dg@dglawrence.com using -f
Date: Sun, 28 Jun 2009 21:53:04 -0700
From: David G Lawrence <dg@dglawrence.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Message-ID: <20090629045304.GI39302@tnn.dglawrence.com>
References: <Pine.GSO.4.63.0906281955160.5084@muncher.cs.uoguelph.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.63.0906281955160.5084@muncher.cs.uoguelph.ca>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0
	(dglawrence.com [127.0.0.1]); Sun, 28 Jun 2009 21:53:05 -0700 (PDT)
Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org
Subject: Re: umount -f implementation
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2009 04:53:06 -0000

> I just noticed that when I do the following:
> - start a large write to an NFS mounted fs
> - network partition the server (unplug a net cable)
> - do a "umount -f <mntpoint>" on the machine
> 
> that it gets stuck trying to write dirty blocks to the server.
> 
> I had, in the past, assumed that a "umount -f" of an NFS mount would be
> used to get rid of an NFS mount on an unresponsive server and that loss
> of "writes in progress" would be expected to happen.
> 
> Does that sound correct? (In other words, an I seeing a bug or a 
> feature?)
> 
> Thanks in advance for any info, rick
> ps: I have a simple "fix" if this is a bug, but I wanted to check before
>     submitting a patch.

   I would say that you are seeing a bug. -f is supposed to mean "force",
of course. Any buffers or outstanding transactions should be terminated
immediately.
   Oh, and most of us know that you, as one of the NFS developers in the
past, well-know the difference between hard and soft NFS mounts. ;-)

-DG

David G. Lawrence
President
Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500
Pave the road of life with opportunities.