Why is RAID fast?

Soldato
Joined
6 May 2009
Posts
20,356
I dont really understand raid but know that its good for if a drive dies, as the other will just take over. What makes raid faster than running a single drive?

I would have thought that raid would be slower as both drives are reading/writing data at the same time

Is there any point in setting up RAID (if its possible) on 2 500gb different model drives. Would i lose 500gb but gain speed and reliability, if one dies obviously
 
So if one of the drives die then you lose one half of the file? Surely not

I think at work our file server has 8 drives in raid where the data is 'striped' accross them? If one dies does it just shift the data to the others before?
 
a bit risky isnt it? We must be using a different type of raid. One of our disks died a few weeks ago and it was replaced and everything went on as normal

raid 1 is different to raid 0 but has no speed advantages

raid 1 is for copying data from one drive to another


yes, it is more risky having a raid0 but just highlites the need for good backups

you should always have more than one copy of your data no matter what type of drive system you are using
 
Thanks. Think ill stick with a velociraptor (when it arrives) as my primary, 2 500gb drives for storage and a 250gb drive for backing up the velociraptor every few weeks
(and a 1tb external for backup)
 
raid 1 is different to raid 0 but has no speed advantages

Yes it does. It gains a read increase because the OS is able to read the existing files off both disks at the same time. But it gains nothing on writing as obviously both drives are writing exactly the same thing
 
a bit risky isnt it? We must be using a different type of raid. One of our disks died a few weeks ago and it was replaced and everything went on as normal

I would imagine that in a corporate environment, you'll be running something like RAID5, RAID6, RAID10, RAID50 or RAID60.

Both speed and redundancy advantages, without the risk of data loss for one (or more, depending on RAID level) drives.
 
I would imagine that in a corporate environment, you'll be running something like RAID5, RAID6, RAID10, RAID50 or RAID60.

Both speed and redundancy advantages, without the risk of data loss for one (or more, depending on RAID level) drives.

From my brief reading i thought there was only raid 0 (writes 50/50, faster but data loss on both),1 (writes accross all but lose disk space) and 5 (minimum 3 drives, can only lose one drive but a bit faster)

Ill look into raid 6, 10, 50 and 60...

edit - reading this http://en.wikipedia.org/wiki/Nested_RAID_levels#RAID_60_.28RAID_6.2B0.29
looks like we are using raid 60
 
Last edited:
Yes it does. It gains a read increase because the OS is able to read the existing files off both disks at the same time. But it gains nothing on writing as obviously both drives are writing exactly the same thing

only if the controller supports split seeks
 
Basically you require dedicated hardware cards for the other types of RAID. On home setups you only see RAID 0/1/5

Mate has got a hardware card that can do RAID 10. Doesnt it depend on what motherboard you have as to what types of raid can be done?

Think my S939 DFI ultra-D board can do raid 0 and 1, not sure about 5
 
Mate has got a hardware card that can do RAID 10. Doesnt it depend on what motherboard you have as to what types of raid can be done?

Think my S939 DFI ultra-D board can do raid 0 and 1, not sure about 5

Yes but mostly 0 and 1, sometimes 5. Alsom RAID 5 requires a lot of calculations so dedicated cards with XOR processors are very much faster than onboard RAID 5 which does this in software.
 
you'll be likely using raid5 in work

data is striped across many drives


http://en.wikipedia.org/wiki/RAID

I thought RAID0 was for striping.

RAID5 uses parity data, storing enough data in all the drives so that if one fails you can hot swap the other and it will rebuild the data.

Example - if you have 4 drives (3 is minimum for RAID5) for simples sake it will be like.

1 0 1 0

one goes pop

1 0 x 0

will occur and the parity will recognise that it has to be a one in there because they have to be even. Off the top of my head that's what it is. So will go back to 1 0 1 0. I might just be drivvling on though.
 
Back
Top Bottom