From owner-freebsd-fs@FreeBSD.ORG  Thu Nov  4 14:45:29 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D3DEC106564A;
	Thu,  4 Nov 2010 14:45:29 +0000 (UTC) (envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id CCD3E8FC1A;
	Thu,  4 Nov 2010 14:45:28 +0000 (UTC)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
	[212.40.38.101])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA27911;
	Thu, 04 Nov 2010 16:45:26 +0200 (EET) (envelope-from avg@icyb.net.ua)
Message-ID: <4CD2C706.6000100@icyb.net.ua>
Date: Thu, 04 Nov 2010 16:45:26 +0200
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.11) Gecko/20101021 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG
References: <4CD2656D.8050701@icyb.net.ua>
In-Reply-To: <4CD2656D.8050701@icyb.net.ua>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=x-viet-vps
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Re: processes stuck on a vnode lock
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 14:45:29 -0000

on 04/11/2010 09:49 Andriy Gapon said the following:
> 
> I see a few processes stuck on the same vnode, trying to take or to upgrade to
> an exclusive lock on it, while the lock data suggests that it is already
> shared-locked.  The vnode is a root vnode of one of ZFS filesystems (it's not a
> global root).
> 
> I couldn't find any (other) threads that could actually hold the vnode lock, but
> lock shared count is suspiciously or coincidentally the same as number of
> threads in zfs_root call.

BTW, I still have the system alive and online, so if anyone has ideas I can try them.

-- 
Andriy Gapon