From owner-freebsd-fs  Sun Nov  8 07:28:55 1998
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA20470
          for freebsd-fs-outgoing; Sun, 8 Nov 1998 07:28:55 -0800 (PST)
          (envelope-from owner-freebsd-fs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20461
          for <freebsd-fs@FreeBSD.ORG>; Sun, 8 Nov 1998 07:28:50 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA07261;
	Mon, 9 Nov 1998 02:28:35 +1100
Date: Mon, 9 Nov 1998 02:28:35 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811081528.CAA07261@godzilla.zeta.org.au>
To: freebsd-fs@FreeBSD.ORG, richard@jezebel.demon.co.uk
Subject: Re: Should a corrupt floppy disk cause a panic?
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>Subject: Should a corrupt floppy disk cause a panic?

Yes.

>This is question on policy.
>
>The msdosfs will panic and the system will die if you mount a 
>floppy with a corrupt format. I have an image of such a floppy
>and I can crash my system every time.

Suitably damaged ffs file systems should also cause panics (as soon as
possible so that the damage doesn't grow).  fsck_foofs must be run
before mounting [possibly-]damaged foofs file systems.  This is not so
easy for msdosfs file systems since there is no fsck_msdosfs.

Bruce

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