From owner-freebsd-fs Mon Nov 9 02:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10060 for freebsd-fs-outgoing; Mon, 9 Nov 1998 02:21:33 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10054 for ; Mon, 9 Nov 1998 02:21:27 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id LAA20582; Mon, 9 Nov 1998 11:21:01 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA10047; Mon, 9 Nov 1998 11:21:01 +0100 (MET) Message-ID: <19981109112101.13646@follo.net> Date: Mon, 9 Nov 1998 11:21:01 +0100 From: Eivind Eklund To: Bruce Evans , freebsd-fs@FreeBSD.ORG, richard@jezebel.demon.co.uk Subject: Re: Should a corrupt floppy disk cause a panic? References: <199811090821.TAA12725@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199811090821.TAA12725@godzilla.zeta.org.au>; from Bruce Evans on Mon, Nov 09, 1998 at 07:21:51PM +1100 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 09, 1998 at 07:21:51PM +1100, Bruce Evans wrote: > Yes, when a panic occurs (deep in a non-ffs routine, due to memory > corruption caused by using invalid data from the disk), it is easy > for the system to unwind the state to when the error occurred and > make ffs wait there ;-). That doesn't really matter for the 'should' side of this - ideally, it should not always panic() for those corrupted filesystems. This should not be too hard to fix, either - install invariant checks before exiting the FFS routines. Unfortunately, I've not yet found anything that document those invariants, or the on-disk format of FFS. I've seen papers that hint at these, but no actual exact documentation (without reading the code to see what it does, which hardly is documentation, and has to be repeated each time you have to know). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message