Path: utzoo!attcan!uunet!husc6!purdue!umd5!trantor.umd.edu!louie
From: louie@trantor.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.amiga
Subject: Re: A plea for bad block handling in the file system.
Message-ID: <2762@umd5.umd.edu>
Date: 20 May 88 21:01:11 GMT
References: <2009@sugar.UUCP> <7144@swan.ulowell.edu> <2026@sugar.UUCP>
Sender: news@umd5.umd.edu
Reply-To: louie@trantor.umd.edu (Louis A. Mamakos)
Organization: University of Maryland, College Park
Lines: 25

In article <2026@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>In article <7144@swan.ulowell.edu>, page@ulowell.UUCP writes:
>> peter@sugar.UUCP (Peter da Silva) wrote:
>> >I'd just like to make another plea for bad block handling in the filesystem.
>
>> And I'll point out again that it's none of the FS' business what the
>> physical device looks like.  Let the driver present a perfect pack to
>> the file system.
>
>Since the drivers (demonstrably) don't do this, this is really not
>a very good argument.

You're wrong.  The device driver (or on-board microcode) for the A2090
controller does this.  Why add needless complexity to the file handler
when the device driver know how to do this better?  And if you're
fortunate, the disk controller or the drive (e.g. SCSI drives) will do
the bad block management for you.

I can't understand why everyone seems to have problems with floppy disks.
Between my A1000 that I had for 2.5 years (since day 0), and the A2000
I've had since then, I've only had 2 or 3 disks ever crap out on me out of
literally hundreds.  Maybe I just live right or something.

Louis A. Mamakos  WA3YMH    Internet: louie@TRANTOR.UMD.EDU
University of Maryland, Computer Science Center - Systems Programming