Welcome, Guest. Please login or register.

Author Topic: What is the precise 4 Gig limit?  (Read 4167 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Thomas

Re: What is the precise 4 Gig limit?
« on: January 06, 2011, 09:06:03 AM »
The exact limit is 2^32 bytes a.k.a. 4,294,967,296 bytes or 8,388,608 sectors.

To be sure to stay below the limit, you can change the geometry of the hdd, for example to

cylinders = 8322
heads = 16
blocks per track = 63
blocks per cylinder = 1008

This results in 8,388,576 sectors or 4,294,950,912 bytes.

There is fixhddsize program on Aminet which can do this for you.

Or you can change from PFS2 to PFS2ds which allows you to use 8 GB. (To be precise, 16383 cylinders, 16 heads, 63 sectors which results in 16,514,064 sectors or 8,455,200,768 bytes).

Regarding corrupted partitions, you should upgrade to PFS3. I never had a corrupted partition with PFS3 while it happened with PFS2 every now and then.

Offline Thomas

Re: What is the precise 4 Gig limit?
« Reply #1 on: January 06, 2011, 04:18:09 PM »
I need to correct myself as I didn't notice you are using SCSI. The 8 GB limit mentioned above only applies to IDE. With SCSI + PFS2ds you can actually use hard drives up to 2 TB with partitions up to 104 GB :-)

Offline Thomas

Re: Updated: What is the precise 4 Gig limit?
« Reply #2 on: January 09, 2011, 09:00:18 PM »
Partitions are not stored in an EEPROM. The parttion table is written to the first few blocks of the drive. The drive's firmware does not know about partitions. Partitions are only known to the operating system.

Could it be that it's too hot inside your Amiga?

Offline Thomas

Re: Updated: What is the precise 4 Gig limit?
« Reply #3 on: January 10, 2011, 01:19:36 PM »
Quote from: Zac67;605305
There are various further restrictions due to hardware architecture:
- A1200/4000/600 IDE is limited to 2 GB (32 bit block address)
- many SCSI controller (e.g. WD33C93 based ones) are limited to 2 GB (32 bit block address)
Some of these can be worked around.


This should read 2 TB in both cases.




Quote from: Tenacious;605293
I'm probably more than a little confused.  ;)  I beleive there was a problem (before OS3.5 and also PFS2) addressing drives larger than 4GB.  I'm beginning to beleive this was a limitation of FFS.  I don't know if the limits were the same for SCSI and IDE.

It doesn't seem now that this was my original problem.  I'm left at the moment with several possible causes: PFS2 has a bug, my poor understanding and setting of drive parameters (mask, maxtranfer, etc), too many small files (like those generated by iBrowse, Yam, Palm synchronization, etc) that are constantly being revised, drives do have a finite lifespan.



The problem is in the interface between file system and device driver. It is not specific to 3.1 and below and it is not magically fixed in 3.5 and above. You need to find a combination of file system and device driver which works together in order to bypass the 4GB limit.

The other problem is that the so-called standard was made without talking to the other parties which already had developed a fix. Therefore now there are two "standards" which can be used to bypass the limit, but they are not compatible.

The standard which came with 3.5 is called NSD.

The other command set invented by a group of third-party hardware manufacturers in the time before 3.5 came out is called TD64.

There is a third possibility called Direct-SCSI a.k.a. HD_SCSICMD which has some other limits.

Now fact is that PFS2/3 support TD64 but not NSD, so they do not work with OS 3.5's device driver for the internal IDE controllers on Amiga motherboards. For large hard drives, that is. Hard drives smaller than 4 GB can be accessed by every file system.