[comp.sys.amiga.hardware] A3000 SCSI and drives > 1GB

dave@bryce.UUCP (Dave E Martin) (03/08/91)

Can someone tell me if the A3000 Hardware/software can
properly access drives that are bigger than one GigaByte?
Does it use group 0 or group 1 scsi commands, or something else?
Also, is it SCSI-1 or SCSI-2?

There is an article in the last Digital News about how a lot of
controllers/Device Drivers (on various manufacturers hardware platforms)
are having problems with the new >1GB drives because of using group 0
SCSI commands and when they try to write to the space above the first
gigabyte they end up overwriting the beginning blocks of the disk
instead.

--
VAX Headroom   Speaking for myself only
UUCP:     dave@bryce.uucp        dave@unislc.uucp
INTERNET: DMARTIN@CC.WEBER.EDU   dave@saltlcy-unisys.army.mil
Now was that civilized?  No, clearly not.

blgardne@javelin.es.com (Blaine Gardner) (03/09/91)

dave@bryce.UUCP (Dave E Martin) writes:
>Can someone tell me if the A3000 Hardware/software can
>properly access drives that are bigger than one GigaByte?

Yes, but the version of the FastFileSystem that's in KS 2.02 has a bug
that limits partitions to 512 megabytes. I understand that this has been
fixed for the next release (whenever that is).

>Does it use group 0 or group 1 scsi commands, or something else?

No idea, sorry.

>Also, is it SCSI-1 or SCSI-2?

SCSI-1.
-- 
Blaine Gardner @ Evans & Sutherland  580 Arapeen Drive, SLC, Utah 84108
blgardne@javelin.sim.es.com     or    ...dsd.es.com!javelin!blgardne
DoD #0046   My other motorcycle is a Quadracer.         BIX: blaine_g
  Anticipation, anticipation, is making me late, is keeping me waiting.

jesup@cbmvax.commodore.com (Randell Jesup) (03/19/91)

In article <1991Mar8.200331.5111@javelin.es.com> blgardne@javelin.sim.es.com writes:
>dave@bryce.UUCP (Dave E Martin) writes:
>>Can someone tell me if the A3000 Hardware/software can
>>properly access drives that are bigger than one GigaByte?
>
>Yes, but the version of the FastFileSystem that's in KS 2.02 has a bug
>that limits partitions to 512 megabytes. I understand that this has been
>fixed for the next release (whenever that is).

	Yup.

>>Does it use group 0 or group 1 scsi commands, or something else?
>
>No idea, sorry.

	It uses extended reads/writes for >256 block IOs, and if one fails
due to an unknown command, it sets the max transfer size to 256 blocks (so
it won't try to use them again).  We're looking at putting in a test for
a block number greater than the maximum size read(6) can handle ($1fffff).

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
The compiler runs
Like a swift-flowing river
I wait in silence.  (From "The Zen of Programming")  ;-)