Date: Wed, 1 Dec 2004 18:52:19 -0500 (EST) From: Jeff Roberson <jroberson@chesapeake.net> To: Peter Holm <peter@holm.cc> Cc: current@freebsd.org Subject: Re: SMP VFS Part 2 Message-ID: <20041201185146.W18185@mail.chesapeake.net> In-Reply-To: <20041201184238.K18185@mail.chesapeake.net> References: <20041201055115.I18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> <20041201184238.K18185@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > > > > > - 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041201185146.W18185>