From owner-freebsd-stable@FreeBSD.ORG  Mon Feb 13 16:45:26 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 422981065673;
	Mon, 13 Feb 2012 16:45:26 +0000 (UTC) (envelope-from bsd@kobyla.org)
Received: from kobyla.org (out.kobyla.org [109.206.180.180])
	by mx1.freebsd.org (Postfix) with ESMTP id 842D78FC1A;
	Mon, 13 Feb 2012 16:45:24 +0000 (UTC)
Received: from pp ([172.29.3.120])
	by kobyla.org (8.14.5/8.14.5) with ESMTP id q1D9FRfS058479;
	Mon, 13 Feb 2012 11:15:45 +0200 (EET) (envelope-from bsd@kobyla.org)
Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes
To: stable@freebsd.org
Date: Mon, 13 Feb 2012 11:15:24 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Pavel Polyakov" <bsd@kobyla.org>
Message-ID: <op.v9l1byf89gyv16@pp>
User-Agent: Opera Mail/11.61 (FreeBSD)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6
	(kobyla.org [172.29.0.117]); Mon, 13 Feb 2012 11:15:47 +0200 (EET)
Cc: daichi@freebsd.org, bsd@kobyla.org
Subject: lock violation in unionfs (9.0-STABLE r230270)
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: Mon, 13 Feb 2012 16:45:26 -0000

http://www.freebsd.org/cgi/query-pr.cgi?pr=165087

Occurs simply trying to use unionfs:
mount -t unionfs -o noatime /usr /mnt

insmntque: mp-safe fs and non-locked vp: 0xfffffe01d96704f0 is not  
exclusive locked but should be
KDB: enter: lock violation

Its possible to continue tho.
Then locks encounter on every file/dir access under mounted path.
It can be resumed from KDB, but sometimes leads to deadlock and system  
freezes at "db> " prompt.