From owner-freebsd-hackers  Wed May 20 21:03:15 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA09565
          for freebsd-hackers-outgoing; Wed, 20 May 1998 21:03:15 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA09472
          for <freebsd-hackers@FreeBSD.ORG>; Wed, 20 May 1998 21:02:51 -0700 (PDT)
          (envelope-from mrcpu@internetcds.com)
Received: (qmail 1513 invoked from network); 21 May 1998 04:02:47 -0000
Received: from schizo.cdsnet.net (204.118.244.32)
  by mail.cdsnet.net with SMTP; 21 May 1998 04:02:47 -0000
Date: Wed, 20 May 1998 21:02:46 -0700 (PDT)
From: Jaye Mathisen <mrcpu@internetcds.com>
X-Sender: mrcpu@schizo.cdsnet.net
To: Igor Timkin <ivt@gamma.ru>
cc: Terry Lambert <tlambert@primenet.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: panic: blkfree: freeling free block/frag
In-Reply-To: <199805191226.QAA16988@crocus.gamma.ru>
Message-ID: <Pine.NEB.3.95.980520210225.27459B-100000@schizo.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Exact same problem and resolution I reported a looong time ago.  3.0, no
problem, 2.2.5, crash city.

Glad it worked.

On Tue, 19 May 1998, Igor Timkin wrote:

> Terry Lambert writes:
> > > 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.
> > 
> 
> I solved this problem. After upgrade 2.2.5-REL to 3.0-971225-SNAP
> my nntp server has uptime:
>  4:20PM  up 38 days, 17:46, 7 users, load averages: 1.92, 1.68, 1.92
> kernel configs and patches for 512M RAM are identical for both 2.2.5 and 3.0.
> No any panics.
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
> 


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