From owner-freebsd-current@FreeBSD.ORG Fri Mar 5 06:29:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5F1516A4CE; Fri, 5 Mar 2004 06:29:23 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EFFC43D39; Fri, 5 Mar 2004 06:29:23 -0800 (PST) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Fri, 5 Mar 2004 09:29:22 -0500 Message-ID: From: Don Bowman To: 'Tim Robbins' , Don Bowman Date: Fri, 5 Mar 2004 09:29:20 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" cc: "'current@freebsd.org'" Subject: RE: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2004 14:29:24 -0000 From: Tim Robbins [mailto:tjr@freebsd.org] > > On Fri, Mar 05, 2004 at 12:31:51AM -0500, Don Bowman wrote: > > > periodically (once a day or so), i'm getting a panic > > as 'panic: ffs_blkfree: freeing free block'. > [...] > > Suggestions on what I should look for or try? > > Dropping to single user mode & forcing a fsck (with the -f > option) should > fix this. It's a symptom of some kind of filesystem inconsistency > that soft updates isn't expecting, and that background fsck > isn't trying > to detect or repair. > Each time i do that, the problem comes back shortly afterwards. I know its not bad hardware, the disks all check out ok, its a U320 scsi raid, disks do auto bad block sparing, scsi has all kinds of crc and checksum. Is anyone else using ASR on current? Are you using it with a large filesystem like this (~400GB)?