From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 07:12:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41FA316A4CE for ; Thu, 2 Dec 2004 07:12:30 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id A1E8D43D5C for ; Thu, 2 Dec 2004 07:12:29 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 39776 invoked from network); 2 Dec 2004 06:58:20 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 2 Dec 2004 06:58:20 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB26wJ4C082472; Thu, 2 Dec 2004 07:58:19 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB26wJCp082471; Thu, 2 Dec 2004 07:58:19 +0100 (CET) (envelope-from pho) Date: Thu, 2 Dec 2004 07:58:19 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041202065819.GA82433@peter.osted.lan> References: <20041201055115.I18185@mail.chesapeake.net> <20041201160351.V18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> <20041201184238.K18185@mail.chesapeake.net> <20041201185146.W18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201185146.W18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 07:12:30 -0000 On Wed, Dec 01, 2004 at 06:52:19PM -0500, Jeff Roberson wrote: > On Wed, 1 Dec 2004, Jeff Roberson wrote: > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > On Wed, Dec 01, 2004 at 04:11:50PM -0500, Jeff Roberson wrote: > > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > > > > > On Wed, Dec 01, 2004 at 05:54:49AM -0500, Jeff Roberson wrote: > > > > > > I have updated the patch at: > > > > > > > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > > > > > > > > > > > > I got a page fault in kern/vfs_vnops.c:542 due to vp->v_mount == NULL. > > > > > > > > > > More info at http://www.holm.cc/stress/log/jeff03.html > > > > > > > > The v_mount should only be NULL very briefly for the rootdevvp. What is > > > > your setup here? Any filesystems other than devfs and ffs? > > > $ mount > > > /dev/ad0s1a on / (ufs, local) > > > devfs on /dev (devfs, local) > > > /dev/ad0s1e on /tmp (ufs, NFS exported, local, soft-updates) > > > /dev/ad0s1f on /usr (ufs, local, soft-updates) > > > /dev/ad0s1d on /var (ufs, local, soft-updates) > > > procfs on /proc (procfs, local) > > > linprocfs on /usr/compat/linux/proc (linprocfs, local) > > > > > > >I think that > > > > deadfs might not set a mountpoint either.. DId you do a forced unmount? > > > No. > > > > I think I know how I'm going to have to fix this. > > > > > > > > > > Got a new one for you: > > > 1) panic: wrong b_bufobj 0 should be 0xc2679c10 > > > 2) panic: unexpected clean buffer 0xc6624bc8 > > > > > > http://www.holm.cc/stress/log/jeff04.html > > > > I fixed your last panic. The new patch is up at the same URL. I'll look > > at these now, thanks. This tool is really working out well. > > Also fixed the unexpected clean buffer. That was mostly just a bad > assert. I'm still baffled by wrong bufobj. > OK. I just do not seem to be able to get past the double panic problem: $ grep -A 3 ppanic /tmp/tip11.log ppanic: unexpected clean buffer 0xc6624bc8 cpuid = 0 KDB: enter: panic [thread pid 54 tid 100042 ] -- ppanic: unexpected clean buffer 0xc6667ec0 cpuid = 0 KDB: enter: panic [thread pid 54 tid 100042 ] -- ppanic: unexpected clean buffer 0xc66564e0 cpuid = 0 KDB: enter: panic [thread pid 54 tid 100042 ] so I've just updated with your last patch. - Peter > > > > > > > > - Peter > > > > > > > > > > > > > - Peter > > > > > > > > > > > It includes bug fixes for a handful of problems that were reported, and a > > > > > > few more that I found myself. It also unwinds giant from open(), which is > > > > > > a very high risk area, but after a few days of working out bugs it seems > > > > > > to be functioning quite well for me. > > > > > > > > > > > > I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let > > > > > > 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I > > > > > > did some mount/unmount/single user tests as well. > > > > > > > > > > > > Use at your own risk. I still haven't locked quotas, so if you're using > > > > > > quota, don't run with this patch. > > > > > > > > > > > > Thanks, > > > > > > Jeff > > > > > > _______________________________________________ > > > > > > freebsd-current@freebsd.org mailing list > > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > > > -- > > > > > Peter Holm > > > > > _______________________________________________ > > > > > freebsd-current@freebsd.org mailing list > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > > > > -- > > > Peter Holm > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Peter Holm