From owner-freebsd-current  Mon Nov 23 09:54:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA12150
          for freebsd-current-outgoing; Mon, 23 Nov 1998 09:54:36 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12145
          for <current@FreeBSD.ORG>; Mon, 23 Nov 1998 09:54:35 -0800 (PST)
          (envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.9.1/8.9.1) id KAA88191;
	Mon, 23 Nov 1998 10:01:50 -0800 (PST)
	(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <199811231801.KAA88191@troutmask.apl.washington.edu>
Subject: Re: Random craches under heavy(?) disk activity
In-Reply-To: <199811231259.OAA00441@medusa.cs.uoi.gr> from Stratos Paschos at "Nov 23, 1998  2:59:17 pm"
To: stratos@medusa.cs.uoi.gr (Stratos Paschos)
Date: Mon, 23 Nov 1998 10:01:50 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

According to Stratos Paschos:
> 
> Hi all,
> 
> After a `make world' of Saturday Nov 21, I noticed random crashes, especially
> when there is disk activity (mail delivery + procmail, or/and update of
> locate DB). The two consequent days I made a complete fresh cvsup 
> and I rebuild everything, but the behavior didn't change. 
> Only once I managed to see for a second the message, that was something
> like:
>   ffs_blkfree bad size .....
> 
> The configuration is : Pentium II (333MHz), 128 MB RAM, 
> 2 SCSI UW disks 4.2GB, Adaptec AHA2940 (UW). 
> OS version 3.0-current
> 
> Any ideas?
> 

Just a me too.  I filed a PR on 14 Nov 98, but it was closed
with an explanation that a commit to vfs_cluster.c fixed the problem.
Problem still presists.

You might disabling the restored ffs_doreallocblks() stuff.

sysctl -w vfs.ffs.doreallocblks=0

-- 
Steve

finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message