From owner-freebsd-current@FreeBSD.ORG  Tue Oct  4 17:08:36 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 965C316A41F;
	Tue,  4 Oct 2005 17:08:36 +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 3B48C43D45;
	Tue,  4 Oct 2005 17:08:36 +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 j94H8JJM022379;
	Tue, 4 Oct 2005 10:08:24 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200510041708.j94H8JJM022379@gw.catspoiler.org>
Date: Tue, 4 Oct 2005 10:08:19 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: mi+mx@aldan.algebra.com
In-Reply-To: <200510041255.55183.mi+mx@aldan.algebra.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
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:08:36 -0000

On  4 Oct, Mikhail Teterin wrote:
>> Is this problem repeatable?
> 
> Yes, as per my original e-mail, it has happened twice already.
> 
> The first time the last command in the build log was very similar, but
> involved a different object file. The perl-process was stuck as "running"
> and I was able to kill it, but the subsequent `rm -rf work' became
> unkillable in "ufs", just like `find' is now.
> 
>> What does "ps lax" say about the hung processes?
> 
>     0 65327  8694   0  -4  0  1432   908 ufs    D+    p2    0:02,05 find work/ -name provider.o

Hung trying to lock a vnode ...

What other processes are in the D state, and what is their wchan info?

Are you using filesystem snapshots?