Non-standard RAID levels
Although all RAID implementations differ from the specification to some extent, some companies and open-source projects have developed non-standard RAID implementations that differ substantially from the standard. Additionally, there are non-RAID drive architectures, providing configurations of multiple hard drives not referred to by RAID acronyms.
|This section needs additional citations for verification. (January 2014)|
Now part of RAID 6, double parity (sometimes known as row diagonal parity) features two sets of parity checks, like traditional RAID 6. Differently, the second set is not another set of points in the over-defined polynomial which characterizes the data. Rather, double parity calculates the extra parity against a different group of blocks. For example, in our graph both RAID 5 and 6 consider all A-labeled blocks to produce one or more parity blocks. However, it is fairly easy to calculate parity against multiple groups of blocks, one can calculate all A blocks and a permuted group of blocks.
This is more easily illustrated using RAID 4, Twin Syndrome RAID 4 (RAID 6 with a RAID 4 layout), and double parity RAID 4 (
B1 etc. each represent one data block; each column represents one disk):
Traditional Twin Syndrome Double parity RAID 4 RAID 4 RAID 4 A1 A2 A3 Ap A1 A2 A3 Ap Aq A1 A2 A3 Ap 1n B1 B2 B3 Bp B1 B2 B3 Bp Bq B1 B2 B3 Bp 2n C1 C2 C3 Cp C1 C2 C3 Cp Cq C1 C2 C3 Cp 3n D1 D2 D3 Dp D1 D2 D3 Dp Dq D1 D2 D3 Dp 4n
n blocks are the double parity blocks. Block
1n would be calculated as
A1 xor B2 xor C3, block
2n is calculated as
A2 xor B3 xor Cp, while block
A3 xor Bp xor C1. Because the double parity blocks are correctly distributed, it is possible to reconstruct two lost disks through iterative recovery. For example,
B2 could be recovered without the use of any
x2 blocks, as
B3 xor Cp xor 2n = A2, and then
A1 can be recovered by calculating
A2 xor A3 xor Ap. Finally,
B2 = A1 xor C3 xor 1n.
RAID-DP implements RAID 4, except with an additional disk that is used for a second parity, so it has the same failure characteristics of a RAID 6. The performance penalty of RAID-DP is typically under 2% when compared to a similar RAID 4 configuration.
RAID 5E, RAID 5EE, and RAID 6E
RAID 5E, RAID 5EE, and RAID 6E (with the added E standing for Enhanced) generally refer to variants of RAID 5 or 6 with an integrated hot-spare drive, where the spare drive is an active part of the block rotation scheme. This spreads I/O across all drives, including the spare, thus reducing the load on each drive, increasing performance. It does, however, prevent sharing the spare drive among multiple arrays, which is occasionally desirable.
Intel Matrix RAID
Intel Matrix RAID (a feature of Intel Rapid Storage Technology) is a feature (not a RAID level) present in the ICH6R and subsequent Southbridge chipsets from Intel, accessible and configurable via the RAID BIOS setup utility. Matrix RAID supports as few as two physical disks or as many as the controller supports. The distinguishing feature of Matrix RAID is that it allows any assortment of RAID 0, 1, 5, or 10 volumes in the array, to which a controllable (and identical) portion of each disk is allocated.
As such, a Matrix RAID array can improve both performance and data integrity. A practical instance of this would use a small RAID 0 (stripe) volume for the operating system, program, and paging files; second larger RAID 1 (mirror) volume would store critical data. Linux MD RAID is also capable of this.
Linux MD RAID 10
The Linux kernel's software RAID driver (called "md", coming from "multiple devices") can be used to build a classic RAID 1+0 array, but also for building it as a single-level RAID layout, with some additional features.
The standard "near" layout, where each chunk is repeated
n times in a
k-way stripe array, is equivalent to the standard RAID 10 arrangement, but it does not require that
n evenly divides
k. For example, an
n2 layout on 2, 3, and 4 drives would look like:
2 drives 3 drives 4 drives -------- ---------- -------------- A1 A1 A1 A1 A2 A1 A1 A2 A2 A2 A2 A2 A3 A3 A3 A3 A4 A4 A3 A3 A4 A4 A5 A5 A5 A6 A6 A4 A4 A5 A6 A6 A7 A7 A8 A8 .. .. .. .. .. .. .. .. ..
The four-drive example is identical to a standard RAID 1+0 array, while the three-drive example is a software implementation of RAID 1E. The two-drive example is equivalent to RAID 1.
The driver also supports a "far" layout where all the drives are divided into
f sections. All the chunks are repeated in each section but are switched in groups (for example, in pairs). For example,
f2 layouts on 2-, 3-, and 4-drive arrays would look like this:
2 drives 3 drives 4 drives -------- ------------ ------------------ A1 A2 A1 A2 A3 A1 A2 A3 A4 A3 A4 A4 A5 A6 A5 A6 A7 A8 A5 A6 A7 A8 A9 A9 A10 A11 A12 .. .. .. .. .. .. .. .. .. A2 A1 A3 A1 A2 A2 A1 A4 A3 A4 A3 A6 A4 A5 A6 A5 A8 A7 A6 A5 A9 A7 A8 A10 A9 A12 A11 .. .. .. .. .. .. .. .. ..
"Far" layout is designed for offering striping performance on a mirrored array; sequential reads can be striped, similar to as in RAID 0 configurations. Random reads are somewhat faster, while sequential and random writes offer about equal speed to other mirrored RAID configurations. "Far" layout performs well for systems where reads are more frequent than writes, which is a common case. For a comparison, regular RAID 1 as provided by Linux software RAID, does not stripe reads, but can perform reads in parallel.
The "near" and "far" options can be used together; in that case chunks in each section are offset by
n (near) devices. For example, an
n2 f2 layout stores 2×2 = 4 copies of each sector, thus requiring at least four drives:
4 drives 5 drives -------------- ------------------- A1 A1 A2 A2 A1 A1 A2 A2 A3 A3 A3 A4 A4 A3 A4 A4 A5 A5 A5 A5 A6 A6 A6 A6 A7 A7 A8 A7 A7 A8 A8 A8 A9 A9 A10 A10 .. .. .. .. .. .. .. .. .. A2 A2 A1 A1 A2 A3 A1 A1 A2 A4 A4 A3 A3 A5 A5 A3 A4 A4 A6 A6 A5 A5 A7 A8 A6 A6 A7 A8 A8 A7 A7 A10 A10 A8 A9 A9 .. .. .. .. .. .. .. .. ..
2 drives 3 drives 4 drives -------- ---------- --------------- A1 A2 A1 A2 A3 A1 A2 A3 A4 A2 A1 A3 A1 A2 A4 A1 A2 A3 A3 A4 A4 A5 A6 A5 A6 A7 A8 A4 A3 A6 A4 A5 A8 A5 A6 A7 A5 A6 A7 A8 A9 A9 A10 A11 A12 A6 A5 A9 A7 A8 A12 A9 A10 A11 .. .. .. .. .. .. .. .. ..
It is also possible to combine "near" and "offset" layouts (but not "far" and "offset").
In the examples above,
k is the number of drives, while
o# are parameters to the mdadm's
--layout option. Linux software RAID (Linux kernel's md driver) also supports creation of standard RAID 0, 1, 4, 5, and 6 configurations.
|This section does not cite any references or sources. (April 2014)|
RAID-Z is not actually a kind of RAID, but a higher-level software technology that implements an integrated redundancy scheme in the ZFS file system similar to RAID 5. RAID-Z is a data-protection technology featured by ZFS in order to reduce the block overhead in mirroring.
- RAID-Z avoids the RAID 5 "write hole" using copy-on-write; rather than overwriting data, it writes to a new location and then atomically overwrites the pointer to the old data.
- It avoids the need for read-modify-write operations for small writes by only ever performing full-stripe writes.
- It does not increase random read IOPS performance in the same way that RAID 5 can - it performs near the same rate as just a single disk in the array.
- Resilvering is faster than RAID 5 for empty disks, but slower for full disks (RAID-Z walks the file system using random access).
- RAID-Z space accounting is complicated, and depends on the way data is written to it - small writes reduce overall capacity more:
- For N disks, array capacity for RAID 5 is fixed at (N-1). Capacity for RAID-Z array is between (N-1) when doing large writes to (N/2) for a disk full of 1-block writes. For a disk full of small writes, RAID-1 could give the same capacity (and better random read IOPS).
- E.g. Assuming 100 GB disks:
Disks RAID 5 capacity RAID-Z capacity 3 200 GB 200 GB to 100 GB 4 300 GB 300 GB to 150 GB 5 400 GB 400 GB to 200 GB
Small blocks are mirrored instead of parity protected, which is possible because the file system is aware of the underlying storage structure and can allocate extra space if necessary. RAID-Z2 doubles the parity structure to achieve results similar to RAID 6: the ability to sustain up to two drive failures without losing data.
In July 2009, triple-parity RAID-Z3 was added to provide increased redundancy due to the extended rebuilding times of multi-terabyte disks.
Microsoft announced in 2011 that Drive Extender would no longer be included as part of Windows Home Server Version 2, Windows Home Server 2011 (codename VAIL). As a result there has been a third-party vendor move to fill the void left by DE. Included competitors are Division M, the developers of Drive Bender, DriveHarmony from DataCore, and StableBit's DrivePool.
BeyondRAID is not a true RAID extension, but consolidates up to 10 SATA hard drives into one pool of storage. It has the advantage of supporting multiple disk sizes at once, much like JBOD, while providing redundancy for all disks and allowing a hot-swap upgrade at any time. Internally it uses a mix of techniques similar to RAID 1 and 5. Depending on the fraction of data in relation to capacity, it can survive up to three drive failures, if the "array" can be restored onto the remaining good disks before another drive fails. The amount of usable storage can be approximated by summing the capacities of the disks and subtracting the capacity of the largest disk. For example, if a 500, 400, 200, and 100 GB drive were installed, the approximate usable capacity would be 500+400+200+100+(-500)=700 GB of usable space. Internally the data would be distributed in two RAID 5-like arrays and two RAID 1-like sets:
Drives | 100 GB | 200 GB | 400 GB | 500 GB | ---------- | x | unusable space (100 GB) ---------- ------------------- | A1 | A1 | RAID 1 set (2× 100 GB) ------------------- ------------------- | B1 | B1 | RAID 1 set (2× 100 GB) ------------------- ---------------------------- | C1 | C2 | Cp | RAID 5 array (3× 100 GB) ---------------------------- ------------------------------------- | D1 | D2 | D3 | Dp | RAID 5 array (4× 100 GB) -------------------------------------
unRAID is a Linux-based operating system optimized for media file storage.
Disadvantages include slower write performance than a single disk and bottle necking when multiple drives are written concurrently. However, unRAID allows support of a cache drive which dramatically speeds up the write performance. The data, on the cache drive, is temporarily unprotected until unRAID moves it to the array based on a schedule set within the software. The parity drive must be at least as large as the largest data drive to provide protection.
Advantages include lower power consumption than standard RAID levels, the ability to use multiple hard drives with differing sizes to their full capacity and in the event of multiple concurrent hard drive failures (exceeding the redundancy), only losing the data stored on the failed hard drives compared to standard RAID levels which offer striping in which case all of the data on the array is lost when more hard drives fail than the redundancy can handle.
- Peter Corbett, Bob English, Atul Goel, Tomislav Grcanac, Steven Kleiman, James Leong, and Sunitha Sankar (2004). "Row-Diagonal Parity for Double Disk Failure Correction". USENIX Association. Archived from the original on 2013-11-22. Retrieved 2013-11-22.
- Patrick Schmid (2007-08-07). "RAID 6: Stripe Set With Double Redundancy - RAID Scaling Charts, Part 2". Tomshardware.com. Retrieved 2014-01-15.
- White, Jay; Lueth, Chris; Bell, Jonathan (March 2003). "RAID-DP: NetApp Implementation of Double-Parity RAID for Data Protection". NetApp.com. Network Appliance. Retrieved 2014-06-07.
- "Non-standard RAID levels". RAIDRecoveryLabs.com. Retrieved 2013-12-15.
- "Intel's Matrix RAID Explored". The Tech Report. 2005-03-09. Retrieved 2014-04-02.
- "Setting Up RAID Using Intel Matrix Storage Technology". HP.com. Hewlett Packard. Retrieved 2014-04-02.
- "Intel Matrix Storage Technology". Intel.com. Intel. 2011-11-05. Retrieved 2014-04-02.
- "Managing Software RAIDs 6 and 10 with mdadm". OpenSUSE.org. SUSE. Retrieved 2014-03-08.
- "Linux Software RAID 10 Layouts Performance: Near, Far, and Offset Benchmark Analysis". Ilsistemista.net. 2012-08-28. Retrieved 2014-03-08.
- Jon Nelson (2008-07-10). "RAID5,6 and 10 Benchmarks on 18.104.22.168". Jamponi.net. Retrieved 2014-01-01.
- "Performance, Tools & General Bone-Headed Questions". TLDP.org. Retrieved 2014-01-01.
- "mdadm(8): manage MD devices aka Software RAID - Linux man page". Die.net. Retrieved 2014-03-08.
- "md(4): Multiple Device driver aka Software RAID - Linux man page". Die.net. Retrieved 2014-03-08.
- Many LSI RAID cards include RAID1E functionality, sometimes called Integrated Mirroring Enhanced.
- Separate from Windows' Logical Disk Manager
- "Drive Bender Public Release Arriving This Week". We Got Served. Retrieved 2014-01-15.
- Data Robotics, Inc. implements BeyondRaid in their Drobostorage device.
- Detailed technical information about BeyondRaid, including how it handles adding and removing drives, is: US US20070266037
- "What is unRAID?". Lime-Technology.com. Lime Technology. 2013-10-17. Retrieved 2014-01-15.
- "LimeTech – Technology". Lime-Technology.com. Lime Technology. 2013-10-17. Retrieved 2014-02-09.
- "Manual Pages: softraid(4)". OpenBSD.org. 2013-10-31. Retrieved 2014-01-15.