From owner-freebsd-current@FreeBSD.ORG  Thu Aug 28 13:25:18 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 410F916A4BF; Thu, 28 Aug 2003 13:25:18 -0700 (PDT)
Received: from mail.allcaps.org (allcaps.org [216.240.173.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0D5E243FAF; Thu, 28 Aug 2003 13:25:17 -0700 (PDT)
	(envelope-from bsder@allcaps.org)
Received: from mail.allcaps.org (localhost [127.0.0.1])
	by mail.allcaps.org (Postfix) with ESMTP
	id DFCA692FAF; Thu, 28 Aug 2003 16:25:16 -0400 (EDT)
Received: from localhost (bsder@localhost)h7SKPG6F019253;
	Thu, 28 Aug 2003 13:25:16 -0700
X-Authentication-Warning: mail.allcaps.org: bsder owned process doing -bs
Date: Thu, 28 Aug 2003 13:25:16 -0700 (PDT)
From: "Andrew P. Lentvorski, Jr." <bsder@allcaps.org>
To: Alexander Leidinger <Alexander@Leidinger.net>
In-Reply-To: <20030828193342.3cb6a927.Alexander@Leidinger.net>
Message-ID: <Pine.LNX.4.44.0308281322320.19092-100000@mail.allcaps.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
cc: rwatson@freebsd.org
Subject: Re: nfs tranfers hang in state getblck or nfsread
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Thu, 28 Aug 2003 20:25:18 -0000

On Thu, 28 Aug 2003, Alexander Leidinger wrote:

> There's no lockd running, only the statd on the server, so we already
> can rule out the lockd.

You probably want to shut down statd on the server as well.  Since statd
is only used to recover locks on reboots, it is of no use without lockd,
and it can only get it the way.

-a