I may have mentioned that my main computer (A3000 with two 4.3 Gig Quantum hard drives with PFS2) got sick in 2010. Basically, the partitions on the primary HD began to corrupt. Then, the partitions on the backup drive also began to corrupt within a month of the first. It is too strange that both drives would fail at the same time. Some partitions would report that some of their data was outside their boundaries. Strange! This has been a bit depressing for the last 9 months!
Today, I found another 4.3 Gig HD in the basement and it seems to be functional (What luck!). While partitioning it, I wondered what would happen if I formatted all of the available 4.3 Gigs. Would the system immediately report the drive unusable because it requires more than the available addressing range? Or, would my system happily chug along for years until I wrote a file that went beyond the theoretical address limit? Would that data overflow into another partition, corrupting both?
That's it for tonight's brain storm. I may be able to finally salvage my data to the new drive. Maybe a fresh repartitioning (inside the TRUE 4 Gig limit) of the other two supposedly bad drives will save them as well.
Any thoughts?
Using something like the FastATA MKIII hardware or the 4xEIDE hardware they spilt your drives automatically into lots of 4GB partions, but upon actually checking them they are always just a few K under 4GB (never 4GB exactly).
Seems when you try to do this due to the actual way the filesystems work if they were to actually try and write data all the way up to the very last byte of an exact 4GB partition some of the data ends up being written to the previous partition if there is one or if not it overwrites another part of the current partition causing all sorts of data loss...

The applies to the max size of a FFS partition which is supposed to be 2GB but is always just a few K less than 2GB to prevent this overwriting and corruption of other partitions...

That's the simplest explanation I can give you cos it's really a bit more complicated that this...
