From owner-freebsd-hackers@freebsd.org Thu Dec 24 07:41:09 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B880AA50173 for ; Thu, 24 Dec 2015 07:41:09 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id A51BC1367 for ; Thu, 24 Dec 2015 07:41:09 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id tBO7ewLX097012 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 23 Dec 2015 23:40:59 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be yuri.doctorlan.com Subject: Re: Should DEBUG_VFS_LOCKS messages be reported as bugs? To: Daniel Braniss References: <567791E9.50207@rawbw.com> <56779542.8020205@rawbw.com> <1331010544.139156804.1450706805234.JavaMail.zimbra@uoguelph.ca> <567B4E08.1000204@rawbw.com> <2B571D55-0B24-4E75-AA5B-4CCF9D3B8CD5@cs.huji.ac.il> Cc: Freebsd hackers list , Rick Macklem From: Yuri Message-ID: <567BA189.8080405@rawbw.com> Date: Wed, 23 Dec 2015 23:40:57 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <2B571D55-0B24-4E75-AA5B-4CCF9D3B8CD5@cs.huji.ac.il> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2015 07:41:09 -0000 On 12/23/2015 23:10, Daniel Braniss wrote: > I just turned off WITNESS/INVARIANTS:-) > the only complain I get is when I do a mountd restart, but it’s harmless. Which OS version? I get the messages on 10.2-STABLE with options from my OP. Endless messages like this: Dec 23 17:59:36 yuri kernel: KDB: stack backtrace: Dec 23 17:59:36 yuri kernel: #0 0xffffffff8097c810 at kdb_backtrace+0x60 Dec 23 17:59:36 yuri kernel: #1 0xffffffff809eae7e at assert_vop_elocked+0x6e Dec 23 17:59:36 yuri kernel: #2 0xffffffff809ea6b1 at insmntque1+0x41 Dec 23 17:59:36 yuri kernel: #3 0xffffffff82e202a1 at unionfs_nodeget+0x281 Dec 23 17:59:36 yuri kernel: #4 0xffffffff82e23b06 at unionfs_lookup+0x726 Dec 23 17:59:36 yuri kernel: #5 0xffffffff80e7776f at VOP_CACHEDLOOKUP_APV+0x10f Dec 23 17:59:36 yuri kernel: #6 0xffffffff809d92b6 at vfs_cache_lookup+0xd6 Dec 23 17:59:36 yuri kernel: #7 0xffffffff80e775af at VOP_LOOKUP_APV+0x10f Dec 23 17:59:36 yuri kernel: #8 0xffffffff809e1892 at lookup+0x5c2 Dec 23 17:59:36 yuri kernel: #9 0xffffffff809e0fb4 at namei+0x4e4 Dec 23 17:59:36 yuri kernel: #10 0xffffffff809f683e at kern_statat_vnhook+0xae Dec 23 17:59:36 yuri kernel: #11 0xffffffff809f66cd at sys_stat+0x2d Dec 23 17:59:36 yuri kernel: #12 0xffffffff80d4fff4 at amd64_syscall+0x2c4 Dec 23 17:59:36 yuri kernel: #13 0xffffffff80d339db at Xfast_syscall+0xfb Dec 23 17:59:36 yuri kernel: insmntque: non-locked vp: 0xfffff80046d233b0 is not exclusive locked but should be Yuri