From owner-freebsd-hackers  Fri Dec  5 11:53:59 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA00876
          for hackers-outgoing; Fri, 5 Dec 1997 11:53:59 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA00871
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 5 Dec 1997 11:53:56 -0800 (PST)
          (envelope-from tlambert@usr08.primenet.com)
Received: (from daemon@localhost)
	by smtp03.primenet.com (8.8.8/8.8.8) id NAA13257;
	Fri, 5 Dec 1997 13:04:09 -0700 (MST)
Received: from usr08.primenet.com(206.165.6.208)
 via SMTP by smtp03.primenet.com, id smtpd013236; Fri Dec  5 13:04:02 1997
Received: (from tlambert@localhost)
	by usr08.primenet.com (8.8.5/8.8.5) id MAA16124;
	Fri, 5 Dec 1997 12:53:14 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199712051953.MAA16124@usr08.primenet.com>
Subject: Re: panic: blkfree: freeling free block/frag
To: ivt@gamma.ru (Igor Timkin)
Date: Fri, 5 Dec 1997 19:53:14 +0000 (GMT)
Cc: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <199712051553.SAA00865@crocus.gamma.ru> from "Igor Timkin" at Dec 5, 97 06:53:14 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 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

[ ... ]

> /dev/ccd0c	/var/spool/news	ufs	rw,async,noatime,noexec,nosuid 0 2

[ ... ]

> dev=0x1502, block=20372, fs=/var/spool/news
> panic: blkfree: freeing free frag
> syncing disk 
> (unfortunately at this point the system is freeze and I have
> make the hardware reset, so I don't have crash dump).

[ ... ]

> Any suggestion ?

Short answer:

Your options are:

(1)	Live with it
(2)	Don't mount the device async

Long Answer:

Generally, this type of problem means you should rebuild the news spool,
since *any* corruption could result in invalid information on the disk
that could result in a panic.

Most likely, you crashed once, and you expected fsck to do something
that it can't do reliably: recover an async mounted partition.  The
partition was "recovered" and marked clean, but when you reference
a particular disk metadata construct, it goes off into the weeds
because the recovery was imperfect.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.