Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: TjLaZer on September 19, 2004, 08:29:05 AM
-
Whats the largest partition size allowed in OS3.9? I have a 20GB HD and I have a 9.9GB partition set at the end. It worked but then the HD icon is gone for it, but the device is still listed and avail to shell and DirOpus (DH3:) Is 10GB too large for a partition?
-edit-
Never mind, I created a dir called disk and it overwrote the disk.info !! DUH... :-?
-
:roflmao:
-
:lol:
I always keep partitions under 4Gb in 3.9, but I can't remember why.
-
I think AmigaOS 3.9 has drivers to support drives bigger than 4 Gig but I think if you store more than 4 Gigs on the partition it will overwrite the front of your partition when you get to the back of the first 4 Gigs. :-(
-
No idea; my biggest is just 15.5Gigs. I wouldn't vote for over 127 gigs...
-
I think AmigaOS 3.9 has drivers to support drives bigger than 4 Gig but I think if you store more than 4 Gigs on the partition it will overwrite the front of your partition when you get to the back of the first 4 Gigs.
No, it doesn't, at least if you have full OS properly installed (incl. ROMUpdate scsi.device).
The boot partition needs to be < 4Gig *area* of the disk since the system will initially start using ROM scsi.device which has no idea how to access >= 4Gig.
Once the setpatch has loaded the ROMUpdate (new scsi.device and fastfilesystem etc), the system is able to access arbitraty disk size (at least upto 127 gigs), and partitions can be larger than 4gig. Note that accessing these >= 4Gig area partitions is only safe when ROMUpdate is loaded properly.
The "wrapping" you talk about doesn't happen inside the partition. In case you use old scsi.device and try to write past 4gig border, it will not understand the 64bit offset and will wrap to beginning of disk, thus overwriting the RDB and first partition(s). So it is not triggered by partition size, but absolute write offset from the start of the disk. It is well possible to trigger the problem with 5 MB partition placed so that it overlaps the 4Gig border.
There are also application level incompatibilities. For example old disk repair/recovery tools won't understand partitions >= 4Gig border. They might also fail to handle >= 2Gig partitions. Also some old programs have problems with very large partitions, for example in "disk free storage" check (they might warn about lack of disk storage when the disk free storage is close to 2GB or 4GB multiples).
So to my knowlege OS 3.9 should work with >= 4Gig ffs partitions.
-
@SamuraiCrow
Yup, OS3.9 supports >4Gb after the SetPatch update (it was SetPatch that does the ROM update isn't it? It's been so long since I had to look).
(>4Gb partition overwriting...) that's the reason I kept my partitions low :-)
-
Just a thought but with ROMupdate in my KickFlashOS4 I should be able to have a sys disk larger than 4GB right (though I guess I wouldn't want that in case I want to be able to reflash the card easily)?
-
I have a 2GB boot partition, two 4GB, and a 10GB. Seems to work fine. I would like to know what the MAX partition size would be. Not HD, but partition. 127Gigs? Wow.
-
Ive had a 70 gig partition
with pfsDirectScsi filesystem
for years now without probs.
I think the only things u need to consider is
to have FIRST partition less than 4 or 2 gigs,
use fastfilesystem on the boot partition,
and use os3.9 scsi.device.
-
@Im>bE
Yeah, PFS3 is fine with proper scsi.device.
I've got 100GB PFS3 partition on my peg2. That seems to be PFS3 limitation (larger partition wouldn't mount).
-
Im>bE wrote:
I think the only things u need to consider is
to have FIRST partition less than 4 or 2 gigs,
use fastfilesystem on the boot partition,
and use os3.9 scsi.device.
I've had my boot partition as SFS and have had absolutely no problems so far (a good few months of use).