From owner-freebsd-stable@FreeBSD.ORG  Thu Jan  5 19:53:33 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: 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 A047A16A41F
	for <freebsd-stable@FreeBSD.org>; Thu,  5 Jan 2006 19:53:33 +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 B813D43D6A
	for <freebsd-stable@FreeBSD.org>; Thu,  5 Jan 2006 19:53:32 +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 k05JrOmx015661;
	Thu, 5 Jan 2006 11:53:28 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200601051953.k05JrOmx015661@gw.catspoiler.org>
Date: Thu, 5 Jan 2006 11:53:24 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: dsh@vlink.ru
In-Reply-To: <87bqyqa2dn.fsf@neva.vlink.ru>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: freebsd-stable@FreeBSD.org
Subject: Re: Recurring problem: processes block accessing UFS file system
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Jan 2006 19:53:33 -0000

On  5 Jan, Denis Shaposhnikov wrote:
>>>>>> "Don" == Don Lewis <truckman@FreeBSD.org> writes:
> 
>  Don> pid 519 wants to lock this vnode but some other thread is
>  Don> holding the vnode lock.  Unfortunately we don't know who the
>  Don> lock holder is because the message is truncated.
> 
> Is it possible to find out the answer from the crashdump?

It's possible if you have the matching debug kernel, though it is more
painful.  In kgdb:
	print *(struct vnode *)0xc691f318
	print (struct vnode *)0xc691f318->v_vnlock->lk_lockholder->td_proc->p_pid)
or something like that.

>  Don> This might just be a vnode lock leak.  Build a debug kernel with
>  Don> the DEBUG_VFS_LOCKS and DEBUG_LOCKS options and see if anything
>  Don> shows up.
> 
> I'll try, thank you.

Are you using any unusual file systems, such as nullfs or unionfs?