From owner-freebsd-smp  Wed Dec  4 12:03:20 1996
Return-Path: owner-smp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA19949
          for smp-outgoing; Wed, 4 Dec 1996 12:03:20 -0800 (PST)
Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19887;
          Wed, 4 Dec 1996 12:03:14 -0800 (PST)
Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.8.3/8.7.3) with ESMTP id OAA00722; Wed, 4 Dec 1996 14:03:13 -0600 (CST)
Message-Id: <199612042003.OAA00722@friley216.res.iastate.edu>
X-Mailer: exmh version 1.6.9 8/22/96
To: freebsd-smp@freebsd.org
cc: current@freebsd.org
Subject: Possible file system damage..  
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 04 Dec 1996 14:03:13 -0600
From: Chris Csanady <ccsanady@friley216.res.iastate.edu>
Sender: owner-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've just build another SMP kernel with APIC_IO and SMP_INVLTLB, and so far,
everything seems to be working just fine. :)

The only thing that bothered me was this message I got upon booting the SMP
kernel:

Dec  4 12:17:46 friley216 /kernel: bad block 2240515, ino 20
Dec  4 12:17:46 friley216 /kernel: pid 112 (kvm_mkdb), uid 0 on /var: bad block

I looked at the code, and this looks as if ffs tried to use a block outside the
limits of the file system.  This sounds to me more like a file system problem,
but I thought I'd check here first.  It doesnt sound like it hurt anything, but
it does worry me a bit.  Somehow, invalid data got into in inode on a file
system that was cleanly mounted and unmounted.

--Chris Csanady