From owner-freebsd-current@FreeBSD.ORG Sat Jan 17 06:29:51 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 1887D16A4CE for ; Sat, 17 Jan 2004 06:29:51 -0800 (PST) Received: from users.altadena.net (users.altadena.net [207.151.161.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61CC043D55 for ; Sat, 17 Jan 2004 06:29:50 -0800 (PST) (envelope-from pete@users.altadena.net) Received: from pete by users.altadena.net with local (Exim 4.30) id 1AhrSQ-0007SJ-7W for current@freebsd.org; Sat, 17 Jan 2004 06:29:50 -0800 Date: Sat, 17 Jan 2004 06:29:50 -0800 From: Pete Carah To: current@freebsd.org Message-ID: <20040117142950.GA28573@users.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: Pete Carah X-Mailman-Approved-At: Sat, 17 Jan 2004 11:45:54 -0800 Subject: Re: 5.2-RELEASE: Possible bug in filesystem code? 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: Sat, 17 Jan 2004 14:29:51 -0000 I had observed many times over a long time two things: 1. The background fsck can easily cause a panic with a disk-intensive process going on, and it has not seemed to depend on available space for me. I have disabled background fsck in rc.conf on *all* my systems because of this. 2. The other source of a panic is if the background fsck detects a condition which would cause the "preen" fsck to abort and give the "run fsck manually" message at bootup, it (usually?) panics the system, usually with "freeing freed inode". I can't think of how to handle this case any better; this is a "hobson's choice" condition :-( -- Pete