Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!umich!sharkey!msuinfo!convex.cl.msu.edu!jap
From: jap@convex.cl.msu.edu (Joe Porkka)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Don't fill your HD
Message-ID: <1990Dec1.193427.7278@msuinfo.cl.msu.edu>
Date: 1 Dec 90 19:34:27 GMT
References: <1990Nov25.093445.10710@evax.arl.utexas.edu> <1990Nov27.223354.25258@ecst.csuchico.edu> <184a393b.ARN04290@adspdk.UUCP>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 30

hclausen@adspdk.UUCP (Henrik Clausen) writes:

>In article <1990Nov27.223354.25258@ecst.csuchico.edu>, Matt "C P." Rush writes:

>> In article <1990Nov25.093445.10710@evax.arl.utexas.edu> hill@evax.arl.utexas.edu (Adam Hill) writes:
>> >
>> > He did tell me two good things:
>> >
>> >Don't EVER fill a CBM hd >95% full.. Why? He did not go in depth.
>> 
>> 	If this didn't happen on files that were good BEFORE the drive reached
>> 97% full, and didn't go away when the drive had more room on it, I'd say there
>> was a problem on the media.  But that ain't it.  AmigaDOS just doesn't like full
>> hard drives, and enquiring minds are little curious as to WHY?

I just did a little scientific test. I have a A590 with 6.0 roms.
20 meg drive, partitioned into 2 equal size 10 meg partitions.
They are 21058 block each.

I had dh1: at about 93%. I just attempted to fill it
to 21059 blocks via C:JOIN. I got a requester "Disk Full",
I hit cancel, join aborted and left the destination file as was.
Now, dh1: is 100%full, and NoProblems.

One time I did fill the disk, as originally shipped it was
a single 20meg partition. It ended up being corrupted, but
I think the cause was a brain dead program - it did not check
for errors - it just kept hitting its head against "Disk
Full" requests - I had to reboot - and BOOM the disk was
Invalidatable - but I didn't lose anything (after backup/restore).