Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
PM G5 and RAID
- Thread starter rickvanr
- Start date
- Sort by reaction score
CanadaRAM
macrumors G5
The drives don;t have to be identicl - they have to be the same size -- although I have heard of people using, say, a 250 Gb drive and a 250 Gb partition on a 400 Gb drive.
I'm just not a fan of RAID 0 in desktop computing scenarios. The risk of failure rises greatly, because any error on either one of the drives destroys the data across both drives. Although the 'strain' on the drive itself is no more than normal use, the consequence of failure is much higher.
And the theoretical (benchmark) speeed improvement is only attained under heavy, non-random loads like capturing digital video or a multi-user server environment. The overhead of the RAID computation nullifies much of the speed gain for small, random files access (such as typical single user desktop use)
I think you get more speed for your money and less risk simply by dividing your data and your OS/Scratch disk space onto two separate spindles. If you can install more than 2 drives, separate out your Applications and your OS onto separate drives as well.
Thanks,
Trevor
CanadaRAM.com
I'm just not a fan of RAID 0 in desktop computing scenarios. The risk of failure rises greatly, because any error on either one of the drives destroys the data across both drives. Although the 'strain' on the drive itself is no more than normal use, the consequence of failure is much higher.
And the theoretical (benchmark) speeed improvement is only attained under heavy, non-random loads like capturing digital video or a multi-user server environment. The overhead of the RAID computation nullifies much of the speed gain for small, random files access (such as typical single user desktop use)
I think you get more speed for your money and less risk simply by dividing your data and your OS/Scratch disk space onto two separate spindles. If you can install more than 2 drives, separate out your Applications and your OS onto separate drives as well.
Thanks,
Trevor
CanadaRAM.com
Calvinatir
macrumors 6502
belvdr
macrumors 603
rickvanr said:
Essentially, the RAID blocks are what split up the data. So it will write 64k to drive 1 then the next 64k to drive 2, then the next 64k back to drive 1, etc.
All the servers I have seen default to 64k and I've never had an issue with performance. If you really want to test it, try one block size, run a benchmark, then change the block size. Keep in mind that changing the block size will cause loss of data.
belvdr
macrumors 603
MacTruck said:
Good question.
With hotplug SCSI drives, it is important to get the drives in the same order as they were removed, but I've never tried it with an external.
So in theory, as long as you could instruct the RAID controller, whether it be in OS X or a hardware type, it should be able to view the configuration and bring it up normally.
EDIT: I am referring to if you attempt to keep the RAID. If you were thinking about removing just one drive and using just that drive as a volume, you won't be able to see any data, because the data is striped across two or more drives.
Brize
macrumors 6502a
rickvanr said:
The chances of an individual drive failing are pretty much the same as if you had two drives running independently; however, the overall odds of losing your data are higher with a RAID 0 configuration, because each drive is dependent on the other.
If you're looking for a speed increase, you'd be better off buying a Western Digital 74GB Raptor for the second bay.
RedTomato
macrumors 601
If you're not looking for speed or data security, why not use it in JBOD mode?
[JBOD = Just a Bunch of Disks]
This aggreates all the disks together into one big disk, and can be used with disks of different size - e.g. one 50GB and one 400GB to make a 450GB virtual disk.
That would answer your seeming need to have maximum storage space on a single virtual drive.
Problem then is i think you won't know which data is on which drive. If one drive fails or is removed, it could be the one with the vital files or part of the OS on it.
I think the above posters are right - simply put as much as you can on one disk so it is as full as possible, e.g. OS, long term apps, stuff that doesn't change round much.
Use the other disk for your large files that you're always moving around.
Keep copies of vital folders e.g. mail backup, essays you've written, personal stuff etc on both disks so that if one goes, you've lost nothing irreplaceable.
xoxo
RedTomato
[JBOD = Just a Bunch of Disks]
This aggreates all the disks together into one big disk, and can be used with disks of different size - e.g. one 50GB and one 400GB to make a 450GB virtual disk.
That would answer your seeming need to have maximum storage space on a single virtual drive.
Problem then is i think you won't know which data is on which drive. If one drive fails or is removed, it could be the one with the vital files or part of the OS on it.
I think the above posters are right - simply put as much as you can on one disk so it is as full as possible, e.g. OS, long term apps, stuff that doesn't change round much.
Use the other disk for your large files that you're always moving around.
Keep copies of vital folders e.g. mail backup, essays you've written, personal stuff etc on both disks so that if one goes, you've lost nothing irreplaceable.
xoxo
RedTomato