From owner-freebsd-current@FreeBSD.ORG  Sun Jun 28 23:58:00 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D02431065673
	for <freebsd-current@freebsd.org>; Sun, 28 Jun 2009 23:58:00 +0000 (UTC)
	(envelope-from rmacklem@uoguelph.ca)
Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca
	[131.104.91.36])
	by mx1.freebsd.org (Postfix) with ESMTP id 7305B8FC16
	for <freebsd-current@freebsd.org>; Sun, 28 Jun 2009 23:58:00 +0000 (UTC)
	(envelope-from rmacklem@uoguelph.ca)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AocGAO+fR0qDaFvL/2dsb2JhbACOZQG7aYQNBQ
X-IronPort-AV: E=Sophos;i="4.42,305,1243828800"; d="scan'208";a="37686296"
Received: from nile.cs.uoguelph.ca ([131.104.91.203])
	by esa-annu-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2009 19:57:59 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by nile.cs.uoguelph.ca (Postfix) with ESMTP id 9298B8D40DC;
	Sun, 28 Jun 2009 19:57:59 -0400 (EDT)
X-Virus-Scanned: amavisd-new at nile.cs.uoguelph.ca
Received: from nile.cs.uoguelph.ca ([127.0.0.1])
	by localhost (nile.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jM37aPjy+qfV; Sun, 28 Jun 2009 19:57:58 -0400 (EDT)
Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102])
	by nile.cs.uoguelph.ca (Postfix) with ESMTP id BDF9F8D40A3;
	Sun, 28 Jun 2009 19:57:58 -0400 (EDT)
Received: from localhost (rmacklem@localhost)
	by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id
	n5T00Df05807; Sun, 28 Jun 2009 20:00:14 -0400 (EDT)
X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing
	-bs
Date: Sun, 28 Jun 2009 20:00:13 -0400 (EDT)
From: Rick Macklem <rmacklem@uoguelph.ca>
X-X-Sender: rmacklem@muncher.cs.uoguelph.ca
To: freebsd-current@freebsd.org
Message-ID: <Pine.GSO.4.63.0906281955160.5084@muncher.cs.uoguelph.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: freebsd-fs@freebsd.org
Subject: umount -f implementation
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jun 2009 23:58:01 -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.