From owner-freebsd-stable@FreeBSD.ORG Mon Feb 6 19:01:06 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AC0E1065674 for ; Mon, 6 Feb 2012 19:01:06 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norman-vivat.ru [89.250.210.68]) by mx1.freebsd.org (Postfix) with ESMTP id 119918FC14 for ; Mon, 6 Feb 2012 19:01:05 +0000 (UTC) Received: from [192.168.248.34] ([192.168.248.34]) by elf.hq.norma.perm.ru (8.14.4/8.14.4) with ESMTP id q16IlBKu029925 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 6 Feb 2012 23:47:11 +0500 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <4F30202C.5040304@norma.perm.ru> Date: Tue, 07 Feb 2012 00:47:08 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: freebsd-stable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [192.168.3.10]); Mon, 06 Feb 2012 23:47:11 +0500 (YEKT) X-Spam-Status: No hits=-101.0 bayes=0.5 testhits ALL_TRUSTED=-1, USER_IN_WHITELIST=-100 autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru Subject: VOP_WRITE is not exclusive locked but should be X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2012 19:01:06 -0000 Hi. I have a server with an 8.2-RELEASE/amd64. It's primary use for routing/ipsec+gre tunneling. It's also running zfs. Sometimes it's locking up: it stops to respond to the network, but the console is still alive, though it doesn't log me in - the 'password:' prompt never comes up (I only can type my username or enter key). I've built a kernel with DEBUG_LOCKS/DEBUG_VFS_LOCKS, KDB/DDB, INVARIANTS, WITNESS and stuff. The only problem is that when booting such a new kernel and DEBUG_LOCKS/DEBUG_VFS_LOCKS are present, I get VOP_PUTPAGES: is not exclusive locked but should be and the kernel immidiately enters ddb. This happens on a daemons startup after the kernel is boot up and filesystems are mounted. Is this something that is safe to ignore (then how do I ignore that ? 'continue' only makes a new VOP_PUTPAGES message appear) ? Is it something that can lock up my server later on and should I report that ? I saw similar message (only it was about VOP_WRITE) in this maillist about 7-STABLE, someone said to try a memtest. I did one pass of a memtest (I know this isn't enough, but I cannot run it there for a day, and, furthermore, I got this message in subject immidiately on multiuser boot sequence so my guess is - the errors should appear immidiately too) and it didn't find any errors. Thanks. Eugene.