From owner-freebsd-hackers  Tue Nov 26 14:21:11 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA00583
          for hackers-outgoing; Tue, 26 Nov 1996 14:21:11 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00569
          for <hackers@freebsd.org>; Tue, 26 Nov 1996 14:21:08 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.3/8.6.9) with ESMTP id KAA13398; Tue, 26 Nov 1996 10:32:06 -0800 (PST)
To: Robert Nordier <rnordier@iafrica.com>
cc: grog@lemis.de, hackers@freebsd.org
Subject: Re: A simple way to crash your system. 
In-reply-to: Your message of "Sat, 26 Nov 1996 12:49:02 +0200."
             <199611261049.MAA02308@eac.iafrica.com> 
Date: Tue, 26 Nov 1996 10:32:06 -0800
Message-ID: <13396.849033126@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> FWIW, the table below represents a couple of months of collecting
> data from users on -questions, who reported that the msdosfs had
> seriously corrupted a UFS partition.

Cool!  I'd hoped someone was working on trying to establish the common
aspects of these failures, since they only seem to bite some people
and not others, but again - I'd not dared to hope too much. :-)

> Unless someone is aware of the problem being more general, it may
> be worth patching the msdosfs code to (by default) refuse to access
> DOS FSes with > 16 sectors per cluster on such drives.

Sounds reasonable to me.  If you have any diffs, I'd be happy to
commit them.  We can't get much worse than we are at the moment. ;)

					Jordan