RAID (Redundant Array of Inexpensive (Independent) Disks)

RAID stands for Redundant Array of Inexpensive (Independent) Disks.

In all the diagrams mentioned below:

• A, B, C, D, E and F – represents blocks
• p1, p2, and p3 – represents parity

RAID LEVEL 0

Following are the key points to remember for RAID level 0.

• Minimum 2 disks.
• Excellent performance ( as blocks are striped ).
• No redundancy ( no mirror, no parity ).
• Don’t use this for any critical system.

RAID LEVEL 1

Following are the key points to remember for RAID level 1.

• Minimum 2 disks.
• Good performance ( no striping. no parity ).
• Excellent redundancy ( as blocks are mirrored ).

RAID 2

• This uses bit level striping. i.e Instead of striping the blocks across the disks, it stripes the bits across the disks.
• In the above diagram b1, b2, b3 are bits. E1, E2, E3 are error correction codes.
• You need two groups of disks. One group of disks are used to write the data, another group is used to write the error correction codes.
• This uses Hamming error correction code (ECC), and stores this information in the redundancy disks.
• When data is written to the disks, it calculates the ECC code for the data on the fly, and stripes the data bits to the data-disks, and writes the ECC code to the redundancy disks.
• When data is read from the disks, it also reads the corresponding ECC code from the redundancy disks, and checks whether the data is consistent. If required, it makes appropriate corrections on the fly.
• This uses lot of disks and can be configured in different disk configuration. Some valid configurations are 1) 10 disks for data and 4 disks for ECC 2) 4 disks for data and 3 disks for ECC
• This is not used anymore. This is expensive and implementing it in a RAID controller is complex, and ECC is redundant now-a-days, as the hard disk themselves can do this.

RAID 3

• This uses byte level striping. i.e Instead of striping the blocks across the disks, it stripes the bits across the disks.
• In the above diagram B1, B2, B3 are bytes. p1, p2, p3 are parities.
• Uses multiple data disks, and a dedicated disk to store parity.
• The disks have to spin in sync to get to the data.
• Sequential read and write will have good performance.
• Random read and write will have worst performance.
• This is not commonly used.

RAID 4

• This uses block level striping.
• In the above diagram B1, B2, B3 are blocks. p1, p2, p3 are parities.
• Uses multiple data disks, and a dedicated disk to store parity.
• Minimum of 3 disks (2 disks for data and 1 for parity)
• Good random reads, as the data blocks are striped.
• Bad random writes, as for every write, it has to write to the single parity disk.
• It is somewhat similar to RAID 3 and 5, but little different.
• This is just like RAID 3 in having the dedicated parity disk, but this stripes blocks.
• This is just like RAID 5 in striping the blocks across the data disks, but this has only one parity disk.
• This is not commonly used.

RAID LEVEL 5

Following are the key points to remember for RAID level 5.

• Minimum 3 disks.
• Good performance ( as blocks are striped ).
• Good redundancy ( distributed parity ).
• Best cost effective option providing both performance and redundancy. Use this for DB that is heavily read oriented. Write operations will be slow.

RAID 6

• Just like RAID 5, this does block level striping. However, it uses dual parity.
• In the above diagram A, B, C are blocks. p1, p2, p3 are parities.
• This creates two parity blocks for each data block.
• Can handle two disk failure
• This RAID configuration is complex to implement in a RAID controller, as it has to calculate two parity data for each data block.

RAID LEVEL 10

Following are the key points to remember for RAID level 10.

• Minimum 4 disks.
• This is also called as “stripe of mirrors”
• Excellent redundancy ( as blocks are mirrored )
• Excellent performance ( as blocks are striped )
• If you can afford the dollar, this is the BEST option for any mission critical applications (especially databases).