Re: SMP VFS Part 2

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_at_freebsd.org mailing list
> > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> > > > >
> > > > > --
> > > > > Peter Holm
> > > > > _______________________________________________
> > > > > freebsd-current_at_freebsd.org mailing list
> > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> > > > >
> > >
> > > --
> > > Peter Holm
> > >
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> >

-- 
Peter Holm