From owner-freebsd-hackers  Sat Dec  6 07:29:12 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id HAA25076
          for hackers-outgoing; Sat, 6 Dec 1997 07:29:12 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from crocus.gamma.ru (crocus.gamma.ru [193.124.255.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA25071
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 6 Dec 1997 07:29:03 -0800 (PST)
          (envelope-from ivt@crocus.gamma.ru)
Received: (from ivt@localhost) by crocus.gamma.ru (8.8.5/8.7.3) id SAA16566; Sat, 6 Dec 1997 18:28:41 +0300 (MSK)
Message-Id: <199712061528.SAA16566@crocus.gamma.ru>
Subject: Re: panic: blkfree: freeling free block/frag
In-Reply-To: <199712061501.KAA15170@lakes.dignus.com> from Thomas David Rivers at "Dec 6, 97 10:01:06 am"
To: rivers@dignus.com (Thomas David Rivers)
Date: Sat, 6 Dec 1997 18:28:41 +0300 (MSK)
Cc: ivt@gamma.ru, nectar@NECTAR.COM, freebsd-hackers@FreeBSD.ORG
From: "Igor Timkin" <ivt@gamma.ru>
Organization: Gamma Ltd., Moscow, Russia
X-Class: Fast
X-Mailer: ELM [version 2.4ME+ PL31H (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Thomas David Rivers writes:
> > On Fri, 5 Dec 1997, Igor Timkin wrote:
> > 
> > > Every 4-8 days my news server (~10 full incoming feeds, ~50
> > > outgoing feeds) crash:
> > > panic: blkfree: freeing free block
> > > or
> > > panic: blkfree: freeing free frag
> > > 
> > > I have a P6-200 rinning on a ASUS P65UP5+C-P6ND (BIOS rev. 2.05),
> > > with 512M ECC of RAM (with David Greenman patch).
> > > news spool is 6x4G Barracuda (ST15150W) CCD across two 2940UW.
> 
>  This is very reminiscent of my "Daily panic"s which I used to get
> on a full news server.  I never saw the "freeing free frag" but I
> frequently saw the "freeing free block" panic.  Do you also get
> "dup alloc" panics?

Never. 30% - freeing free block, 70% - freeing free frag.
Today I was get next on turn panic (I was started expire for reduce
of the used spool disk space and I was sure of the panic).
Now I'll make dump/newfs/restore for spool.
 
>  Anyway, suffice it to say that we've been bird-dogging this problem
> for quite some time (since 2.1 came out.)  It has been a bear to track

I have 2.1.5 and 2.2.2 long time and have't such problems.
This problem was arised after several panics (I have some problems
with hardware upgrade). The Terry's suggestion look like trust
in my case.

> down.  And, unfortunately, I lost my news feed; so I don't get it
> every day.  [Although, I can reproduce a problem that is suspiciously
> similar on a stand-alone 386.] The more info we can get, the better.
> 
> 	- Dave Rivers -
> 
> 
> 

Igor