From owner-freebsd-current  Sat Nov 14 06:31:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA17274
          for freebsd-current-outgoing; Sat, 14 Nov 1998 06:31:40 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from root.com (root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17268
          for <current@FreeBSD.ORG>; Sat, 14 Nov 1998 06:31:39 -0800 (PST)
          (envelope-from root@root.com)
Received: from root.com (localhost [127.0.0.1])
	by root.com (8.8.8/8.8.5) with ESMTP id GAA13419;
	Sat, 14 Nov 1998 06:32:26 -0800 (PST)
Message-Id: <199811141432.GAA13419@root.com>
To: michael_class@gmx.net
cc: current@FreeBSD.ORG, mckusick@mckusick.com
Subject: Re: SMP-System panics after recent ffs_alloc changes 
In-reply-to: Your message of "Sat, 14 Nov 1998 11:23:14 +0100."
             <Pine.BSF.4.05.9811141122300.432-100000@pc-micha.mc.hp.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sat, 14 Nov 1998 06:32:26 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>the recent changes in vfs_cluster.c, buf.h and ffs_alloc.c cause a
>panic on my SMP-System.
...
>Backing out these changes solves the problem.
>
>The panic is"ffs_blkfree: bad size"

   No need to back out the changes - there is a sysctl knob to shut off the 
code called "vfs.ffs.doreallocblks"...just set it to 0.
   Is there anything unusual about your filesystems? Are you using the
standard 8K/1K block/fragment size?

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

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