Xref: utzoo comp.sys.amiga:19975 comp.sys.amiga.tech:973
Path: utzoo!attcan!uunet!nuchat!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Disk corrupt - task held
Message-ID: <2115@sugar.UUCP>
Date: 13 Jun 88 19:25:15 GMT
References: <1657@vaxb.calgary.UUCP> <7416@swan.ulowell.edu>
Distribution: na
Organization: Sugar Land UNIX - Houston, TX
Lines: 21

In article <7416@swan.ulowell.edu>, page@swan.ulowell.edu (Bob Page) writes:
> Oh, in case you think this is just an AmigaDOSism ... here's a line
> from the UNIX (4BSD) man page for mount(1):

>      Mounting file systems full of garbage will crash the system.

Bob, that's misleading. Yes, the Amiga handles disks that are full of
garbage a whole lot better than UNIX. On the other hand, we're talking
of disks that are just slightly damaged. Once you mount the disk
successfully, UNIX will stay up even in the face of *rampant* disk
corruption (ever try looking at a 35 sector disk with a 36 sector
filesystem on it). It's just not at all reasonable to treat a bad block
number as a fatal (guru-style) disk error. Print a message on the console
or put up a requestor saying the disk is corrupted. Then you can fsck or
diskdoctor or disksalv it. Return an I/O error code to the program.

But guru? No.
-- 
-- Peter da Silva      `-_-'      ...!hoptoad!academ!uhnix1!sugar!peter
-- "Have you hugged your U wolf today?" ...!bellcore!tness1!sugar!peter
-- Disclaimer: These may be the official opinions of Hackercorp.