{"id":43213,"date":"2020-11-26T15:03:40","date_gmt":"2020-11-26T14:03:40","guid":{"rendered":"http:\/\/blog.open-e.com\/?p=43213"},"modified":"2025-04-14T13:38:56","modified_gmt":"2025-04-14T13:38:56","slug":"raid-5-how-does-it-work","status":"publish","type":"post","link":"https:\/\/www.open-e.com\/blog\/raid-5-how-does-it-work\/","title":{"rendered":"RAID 5: How does it work?"},"content":{"rendered":"

\t\t\t\tUpdated 23\/09\/2021<\/em><\/strong><\/p>\n

A few years ago, we published an article \u2018How does RAID 5 work? The shortest and easiest explanation ever\u2019<\/em>. We have to admit that this article enjoyed great popularity among our readers. That\u2019s why we would like to explain this matter once again, but this time we also considered our readers\u2019 questions.<\/p>\n

\n

RAID (redundant array of independent disks; originally redundant array of inexpensive disks) is a data storage virtualization technology that combines multiple disk drive components into a logical unit for the purposes of data redundancy or performance improvement.<\/p>\n

Source: Wikipedia<\/a><\/strong><\/div>\n<\/div>\n

<\/h3>\n

RAID 5 explained
\n<\/strong><\/h3>\n

RAID 5 requires a minimum of 3 drives to implement. Each data block is written on a data disk, and parity for blocks in the same rank is generated on Writes and checked on Reads.<\/p>\n

 <\/p>\n

In order to understand RAID 5, you must know XOR:<\/span><\/p>\n

The binary XOR (exclusive OR) operation has two inputs and one output.\u00a0 The inputs to a binary XOR operation can only be 0 or 1 and the result can only be 0 or 1.<\/span><\/strong><\/p>\n

XOR function result is equal 1 if both arguments are different.<\/p>\n

XOR (0, 1) = 1
\nXOR (1, 0) = 1<\/p>\n

XOR function output is equal 0 if both arguments are the same.<\/p>\n

XOR (0, 0) = 0
\nXOR (1, 1) = 0<\/p>\n

Now let us assume we have 3 drives with the following bits:<\/strong><\/p>\n

| 101 | 010 | 011 |<\/p>\n

We calculate XOR of those data and place it on the 4th<\/sup> drive.<\/p>\n

XOR (101, 010, 011) = 100 (XOR (101,010) = 111 and then XOR (111, 011) = 100<\/p>\n

So the data on the four drives looks like this:<\/p>\n

| 101 | 010 | 011 | 100<\/strong> |<\/p>\n

In case of using more than 3 drives, you must use the same calculation for XOR:<\/p>\n

XOR (0, 0) = 0
\nXOR (0, 1) = 1
\nXOR (1, 0) = 1
\nXOR (1, 1) = 0<\/p>\n

This time, lets assume we are using four drives with the following data:<\/strong><\/p>\n

1,1,0,1
\n1,0,0,0
\n0,0,1,0
\n0,1,1,0<\/p>\n

We calculate XOR of those data and place it on the 5th<\/sup> drive.<\/p>\n

XOR (1,1,0,1) = 1
\nXOR (1,0,0,0) = 1
\nXOR (0,0,1,1) = 1
\nXOR (o,1,1,0) = 0<\/p>\n

So the data looks like this:<\/p>\n

1,1,0,1,1
\n1,0,0,0,1
\n0,0,1,0,1
\n0,1,1,0,0<\/p>\n

And now let’s simulate a break of the 3rd<\/sup> drive:<\/strong><\/p>\n

1,1,x,1,1
\n1,0,x,0,1
\n0,0,x,0,1
\n0,1,x,0,0<\/p>\n

In order to get data from this drive, calculate XOR for x from 1st<\/sup>, 2nd<\/sup>, 4th<\/sup>, and 5th<\/sup> drive:<\/p>\n

x for the 1st<\/sup> from XOR (1,1,1,1) = 0 \/ why? 1,1=0 -> 0,1=1 -> 1,1=0
\nx for the 2nd<\/sup> line from XOR (1,0,0,1) = 0
\nx for the 3rd<\/sup> line from XOR (0,0,0,1) = 1
\nx for the 4th<\/sup> line from XOR (0,1,0,0) = 1<\/p>\n

You have to always calculate the sum of two numbers and the result with the next number. Action is alternate for XOR.<\/p>\n

Let\u2019s assume the second drive has failed.<\/strong><\/p>\n

When we calculate XOR all the remaining data will be present from the missing drive.<\/p>\n

| 101 | 010<\/span><\/em> <\/strong><\/span> | 011 | 100 |<\/p>\n

XOR (101, 011, 100) = 010<\/p>\n

You can check the other missing drives and XOR of the remaining data, which will always give you the exact data of your missing drive.<\/p>\n

| 101 | 010 | 011<\/span><\/em><\/strong><\/span> | 100 |<\/p>\n

XOR (101, 010, 100) = 011<\/p>\n

What works for 3 bits and 4 drives only, works for any number of bits and any number of drives. Real RAID 5 has the most common stripe size of 64k (65,536 * 8 = 524,288 bits).<\/p>\n

The real XOR engine only needs to deal with 524,288 bits and not 3 bits as in our exercise. This is why RAID 5 needs a very efficient XOR engine in order to calculate it fast.<\/p>\n

When adding one drive for parity, you will be able to rebuild the missing data in case of any drive failure.<\/p>\n

In our example, we have explained RAID 4 where parity is on a dedicated drive. The only difference between RAID 4 and RAID 5 is that RAID 5 distributes parities evenly between all drives and RAID 4 keeps parities in a dedicated drive. Distributed parity provides a slight increase in performance but the XOR magic is the same.<\/p>\n

 <\/p>\n

A more detailed description of what Redundant Array of Independent Disks means you can find in the newest article by Grzegorz Walasek: The Fundamentals of RAID<\/a><\/p>\n

RAID – The Series. Check out:<\/h3>\n