From owner-freebsd-fs@FreeBSD.ORG Tue Nov 14 15:10:25 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 A38CB16A4E7 for ; Tue, 14 Nov 2006 15:10:25 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33F4243D5F for ; Tue, 14 Nov 2006 15:10:24 +0000 (GMT) (envelope-from dudu@dudu.ro) Received: by nz-out-0102.google.com with SMTP id i11so998257nzh for ; Tue, 14 Nov 2006 07:10:24 -0800 (PST) Received: by 10.65.100.14 with SMTP id c14mr811621qbm.1163517023889; Tue, 14 Nov 2006 07:10:23 -0800 (PST) Received: by 10.65.112.4 with HTTP; Tue, 14 Nov 2006 07:10:23 -0800 (PST) Message-ID: Date: Tue, 14 Nov 2006 17:10:23 +0200 From: "Vlad Galu" To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: 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: 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, 14 Nov 2006 15:10:25 -0000 On 11/1/06, Vlad Galu wrote: > 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. Upon Tor Egge's suggestion, I removed ZERO_COPY_SOCKETS from my kernel and the machine has been running nicely ever since. -- 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.