From owner-freebsd-hackers  Wed Mar  5 19:50:57 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA08331
          for hackers-outgoing; Wed, 5 Mar 1997 19:50:57 -0800 (PST)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA08322
          for <Hackers@FreeBSD.ORG>; Wed, 5 Mar 1997 19:50:53 -0800 (PST)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id DAA27035; Thu, 6 Mar 1997 03:50:41 GMT
Date: Thu, 6 Mar 1997 12:50:41 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
cc: FreeBSD Hackers <Hackers@FreeBSD.ORG>
Subject: Re: "dup alloc" - nope - kern/2875 wasn't it.
In-Reply-To: <199703050157.UAA00285@lakes.water.net>
Message-ID: <Pine.SV4.3.95.970306124158.26838B-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 4 Mar 1997, Thomas David Rivers wrote:

> 
> Well; it's a sad day in Mudville...
> 
> Unfortunately, when I built from a pristine source base, with only
> the vfs_subr.c patch; I was able to reproduce my bad inodes....
> Seems that the combination of a couple of printf()s in the kernel
> and that particular splbio()/splx() masks the problem just as my
> printf()s in disksort did...

I guess it would be worth while to take out the printf's until you can
isolate the printf's that "fix" the problem.  Then analyze the effects of
the printfs serializing writes.

Regards,


Mike Hancock