From owner-freebsd-current  Sun Jun  2 18:56:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA24894
          for current-outgoing; Sun, 2 Jun 1996 18:56:38 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA24873
          for <current@freebsd.org>; Sun, 2 Jun 1996 18:56:26 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au 
          id <03167-0@bunyip.cc.uq.oz.au>; Mon, 3 Jun 1996 11:55:51 +1000
Received: from netfl15a.devetir.qld.gov.au 
          by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP 
          id JAA12414; Mon, 3 Jun 1996 09:53:16 +1000
Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) 
          id XAA11589; Sun, 2 Jun 1996 23:54:59 GMT
Message-Id: <199606022354.XAA11589@netfl15a.devetir.qld.gov.au>
X-Mailer: exmh version 1.6.5 12/11/95
To: Terry Lambert <terry@lambert.org>
cc: current@freebsd.org
Subject: Re: Latest VM fixes are holding up
In-reply-to: Your message of "Fri, 31 May 1996 13:58:07 MST." <199605312058.NAA18657@phaeton.artisoft.com>
X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 
        7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! 
        >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 
        M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 03 Jun 1996 09:54:57 +1000
From: Stephen Hocking <sysseh@devetir.qld.gov.au>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


	[patch & short discussion trimmed]
>Try the kludge; if you can go through the code and understand why
>it's necessary (but a bad soloution to the problem), you can probably
>think about dealing with the real issue, and maybe come up with your
>own patch.

I tried the patch and then ran my trigger case - it promptly crashed with
"cleaned vnode isn't". Looking at the code I discovered that I had DIAGNOSTIC 
set in my config file. I've now removed it and will run with the new kernel 
for a while (it's compiling now ) before reporting back.

I think I'll also bust my head with trying to understand the FS stuff a bit 
more. Sigh.


	Stephen
-- 
The views expressed above are not those of the Worker's Compensation Board of
Queensland, Australia.