From owner-freebsd-fs@FreeBSD.ORG  Tue Oct 26 20:25:40 2004
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C40AF16A4CE
	for <freebsd-fs@FreeBSD.org>; Tue, 26 Oct 2004 20:25:40 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8BE9443D2F
	for <freebsd-fs@FreeBSD.org>; Tue, 26 Oct 2004 20:25:40 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id i9QKPXeV018690;
	Tue, 26 Oct 2004 13:25:37 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200410262025.i9QKPXeV018690@gw.catspoiler.org>
Date: Tue, 26 Oct 2004 13:25:33 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: freebsd-fs@merdin.com
In-Reply-To: <1357841854.20041026213409@merdin.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-fs@FreeBSD.org
Subject: Re: Re[2]: panic again
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Oct 2004 20:25:40 -0000

On 26 Oct, Pavel Merdine wrote:

> Again, somehow after a panic on ONE file system, other filesystems are
> not fully synced. The system conplaints that they are dirty after
> restart. So it seems like one panic lead to corruption of another
> systems. Maybe I'm wrong here too. But I dont see any good in fsck-ing
> each time.

When the OS detects these types of problems, then something (we don't
know what) unexpected has happened, so we can no longer trust the state
of the machine.  If we can't trust the state of the machine, then it is
dangerous to sync any of the file systems, because doing so could damage
them with corrupt data.

> Background fsck does not work in reality as well, because the system
> can panic thousand times before errors are fixed.

It might be a good idea to force a foreground fsck if the system panics
before a background fsck has marked a dirty filesystem clean.