From owner-freebsd-current@FreeBSD.ORG  Tue Oct  4 17:43:58 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 95F4D16A41F;
	Tue,  4 Oct 2005 17:43:58 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 414ED43D48;
	Tue,  4 Oct 2005 17:43:58 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id j94HhfRW023403;
	Tue, 4 Oct 2005 10:43:45 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200510041743.j94HhfRW023403@gw.catspoiler.org>
Date: Tue, 4 Oct 2005 10:43:41 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: mi+mx@aldan.algebra.com
In-Reply-To: <200510041328.05637.mi+mx@aldan.algebra.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=iso-8859-5
Content-Transfer-Encoding: 8BIT
Cc: re@FreeBSD.org, current@FreeBSD.org, openoffice@FreeBSD.org
Subject: Re: 6.0 hangs (while building OOo)
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: Tue, 04 Oct 2005 17:43:58 -0000

On  4 Oct, Mikhail Teterin wrote:
> вівторок 04 жовтень 2005 13:08, Don Lewis Ви написали:
>> Hung trying to lock a vnode ...
>>
>> What other processes are in the D state, and what is their wchan info?


>     0 45773 45771   0  -4  0  1740  1208 ufs    D     p1    0:00,32 dmake
>     0 45806 45788 350  -4  0  1548   632 ufs    D     p1    0:00,00 /bin/tcsh -fc zipdep.pl -u -j  ../../../
>     0 65072 64985 271  -4  0  1248   480 ufs    D     p1    0:00,00 /bin/tcsh -fc if ( -e ../../../unxfbsd.p
>     0 65327  8694   0  -4  0  1432   908 ufs    D+    p2    0:02,05 find work/ -name provider.o

Looks like some sort of vnode locking bug.  All the other processes are
system processes in their usual idle state.

> The two tcsh and the dmake process are remnants of the interrupted OOo build.
> What's a "wchan"?

wchan is the column labeled MWCHAN in the ps lax output.  The wchan info
for the processes above is "ufs".

>> Are you using filesystem snapshots?
> 
> Not "on purpose". This is the /var partition, BTW, nothing fancy:
> 
> 	/dev/da0s2e on /var (ufs, local, soft-updates)
> 
> The only suspect thing about it, that I can say, is that "a few reboots ago"
> I used growfs to extend it. Thanks for your help,

I'm hoping that something will show up on my HEAD box because it has
vnode lock debugging enabled.  If not, it will require some time in the
kernel debugger.