Path: utzoo!utgpu!water!watmath!dalcs!garfield!john13
From: john13@garfield.UUCP (John Russell)
Newsgroups: comp.sys.amiga
Subject: Re: Disk Errors. AmigaDOS file system.
Message-ID: <4404@garfield.UUCP>
Date: 19 Jan 88 05:44:31 GMT
References: <1338@sugar.UUCP> <3080@cbmvax.UUCP> <1368@sugar.UUCP> <3117@cbmvax.UUCP> <1403@sugar.UUCP>
Reply-To: john13@garfield.UUCP (John Russell)
Distribution: na
Organization: Memorial University of Newfoundland, St. John's
Lines: 26

In article <1403@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>It could happen anywhere, and it's equally annoying
>wherever it happens. You can cut things down by not writing to floppies that
>often, but the problem remains. Eventually it's going to bite you.

You may have drive problems. Since I had my external drive fixed last year
I've had ZERO disk problems that weren't due to defective disks, and very
few defective disks. When my drive was acting up I was very antsy about
writing to disks in it, but now I backup my files to disk at every opportunity.

>The problem is that (1) the Amiga is very susceptible to disk errors, and (2)
>that the file system should NOT abort writing a file just because it gets
>a disk error. 

Correct me if I'm wrong, I've seen Shell carry out disk operations where it
hits a bad block and if you retry it keeps going until the files are copied.
You wind up with all files good and usually you never hit the bad block on
the disk again. Does it actually do this or might it just be writing into
marginal sectors?

John
-- 
"A Chinese soldier in Tibet who tried to tear off a British woman's Sergeant
 Bilko T-shirt has become the first known case of someone mistaking Phil
 Silvers for the Dalai Lama."
				-- Toronto Globe & Mail, Nov. 14/87