From owner-freebsd-stable@FreeBSD.ORG  Thu May 19 22:02:29 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 86B1C16A4CF
	for <stable@freebsd.org>; Thu, 19 May 2005 22:02:29 +0000 (GMT)
Received: from philemon.caltech.edu (philemon.caltech.edu [131.215.158.74])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 165E543DB8
	for <stable@freebsd.org>; Thu, 19 May 2005 22:02:29 +0000 (GMT)
	(envelope-from jd@philemon.caltech.edu)
Received: from philemon.caltech.edu (localhost.caltech.edu [127.0.0.1])
	by philemon.caltech.edu (8.13.1/8.12.9) with ESMTP id j4JM00OM094130
	for <stable@freebsd.org>; Thu, 19 May 2005 15:00:00 -0700 (PDT)
	(envelope-from jd@philemon.caltech.edu)
Received: (from jd@localhost)
	by philemon.caltech.edu (8.13.1/8.12.9/Submit) id j4JM00BH094129
	for stable@freebsd.org; Thu, 19 May 2005 15:00:00 -0700 (PDT)
Date: Thu, 19 May 2005 15:00:00 -0700
From: pallen@donut.ugcs.caltech.edu
To: stable@freebsd.org
Message-ID: <20050519220000.GE88799@philemon.caltech.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: Status of kern/79700, nfs lockups
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2005 22:02:29 -0000

I notice that this pr hasn't gotten any attention.
"Suspending process that is actively writing to a file on an
nfs mount causes future access to that file by other
processes to hang until the first process is resumed."

I didn't care much before, but recently I've started having
enough load on my machines to see this problem as well (and
routinely... i.e., not synthetically).

Is this something I should expect to live with for a while?

    -Paul