🚀 go-pugleaf

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 use media that has not been mapped.
> >Don't EVER fill a CBM hd >95% full.. Why? He did not go in depth.
>
>	WHY IS THIS???	I've been bitten by this a couple of times now.  I've
> got a SeaGate ST157-N (ya, I know, SeaGate sucks) running on a Pacific
> Peripherals Overdrive controller.
>	When this thing gets anywhere over 97% full, I start getting "Volume
> Overdrive has a Read/Write Error...." messages just from trying to READ a file
> (using 'more', or 'type').
>
>	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?
>
>	Could some CBM guru shed a little light on this, or at least say it's
> been fixed in 2.x...?

  How can you say it's AmigaDos fault?  As far as I'm concerned, it could be
the controller or even the drive (in the case of a SCSI drive).  I've been
using a Seagate ST-251 40M hard disk for 2 years now and it has been most of
the time oscillating between 95% and 100% full.  The controller is a 2090a and
I'm using a 2000 with AmigaDos 1.3.

NOTE:  I moved this discussion to comp.sys.amiga.hardware.

>	-- Matt

 Stephane Laroche   | Email: stephane@Chucla.CAM.ORG
 +1 514 277-8605    |        Montreal, Que.,  Canada