From owner-freebsd-fs@FreeBSD.ORG Tue Oct 31 22:26:59 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFF3316A4CE for ; Tue, 31 Oct 2006 22:26:59 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9C2F43D5A for ; Tue, 31 Oct 2006 22:26:58 +0000 (GMT) (envelope-from dudu@dudu.ro) Received: by nz-out-0102.google.com with SMTP id o37so1581730nzf for ; Tue, 31 Oct 2006 14:26:58 -0800 (PST) Received: by 10.65.160.7 with SMTP id m7mr7671704qbo; Tue, 31 Oct 2006 14:26:57 -0800 (PST) Received: by 10.65.112.4 with HTTP; Tue, 31 Oct 2006 14:26:57 -0800 (PST) Message-ID: Date: Wed, 1 Nov 2006 00:26:57 +0200 From: "Vlad Galu" To: "Kris Kennaway" In-Reply-To: <20061031193139.GA27951@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200610010015.k910F6Ba001594@cwsys.cwsent.com> <45475DEA.2030506@centtech.com> <20061031193139.GA27951@xor.obsecurity.org> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Frequent VFS crashes with RELENG_6 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2006 22:27:00 -0000 On 10/31/06, Kris Kennaway wrote: > On Tue, Oct 31, 2006 at 04:34:59PM +0200, Vlad Galu wrote: > > > Yes, but for objective reasons I can't publish it :( > > The only > > debugging option that I didn't use was INVARIANTS. > > Which is coincidentally the most useful one ;-) > > Also turn on DEBUG_LOCKS and DEBUG_VFS_LOCKS then report the output of > 'show lockedvnods' at the time of crash, as well. I've applied a patch suggested by Eric and I'll see how it goes with it. If it crashes again, I'll add the things you mentioned to my kernel configuration and get back to the list with further details. -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.