joshuaboniface/raidisnotabackup
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Revamp wording throughout

Browse Source
This commit is contained in:
Joshua Boniface
2022-10-13 09:39:59 -04:00
parent a0fb0f422e
commit 80cb58b762
5 changed files with 16 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/1.md
View File

@ -8,9 +8,9 @@ class="post first"
RAID is a common technique to provide _resiliency_ and _availability_ to a set of data and protect against one of the most common data loss scenarios: the failure of a disk.
The simplest type of RAID is a 'mirror', which keeps two or more copies of data on two or more different disks. If one disk fails, the second copy is still available and no data loss has occurred. You would usually see this for system disks in uptime-critical servers.
The simplest type of RAID is a 'mirror', which keeps two or more copies of data on two or more different disks. If one disk fails, the second copy is still available and no availability or data loss has occurred. You would usually see this for system disks in uptime-critical servers.
There also exist more advanced modes, the most common of which are RAID-5 and RAID-6, and consists of 3-4 or more disks with data stripped (written sequentially), along with parity information, across all disks.
More common for bulk data are more advanced modes like RAID-5 and RAID-6, which consists of 3-4 or more disks with data stripped (written sequentially), along with parity information, across all disks, and which can tolerate losing 1 or 2 (respectively) disks in the array before losing data.
It's worth noting that a pure 'stripe', also called RAID-0, is not really a RAID level - it *increases* the risk of data loss rather than decreasing it, since one disk failure destroys the whole array. It should never be used for redundancy or any critical data.