summaryrefslogtreecommitdiff
path: root/debian/FAQ
diff options
context:
space:
mode:
authormadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-11-17 19:18:43 +0000
committermadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-11-17 19:18:43 +0000
commit6a2103414bfd42dedd9c943ad1ffb6719cc45aa1 (patch)
tree92be3986021f69e71b3917f1282c9fbc5f62c17d /debian/FAQ
parentb40f7f5065a004d58377aeb5430dc58510c058a0 (diff)
typo
Diffstat (limited to 'debian/FAQ')
-rw-r--r--debian/FAQ2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/FAQ b/debian/FAQ
index 236259ff..fefa05b3 100644
--- a/debian/FAQ
+++ b/debian/FAQ
@@ -118,7 +118,7 @@ The latest version of this FAQ is available here:
At the same time, however, RAID4/5/6 provide somewhat better redundancy in
the event of two failing disks. In a RAID10 configuration, if one disk is
already dead, the RAID can only survive if any of the two disks in the other
- RAID1 array fails, but not if the second disk in the degraded RADI1 array
+ RAID1 array fails, but not if the second disk in the degraded RAID1 array
fails (see next item, 4b). A RAID6 across four disks can cope with any two
disks failing. However, RAID6 is noticeably slower than RAID5. RAID5 and
RAID4 do not differ much, but can only handle single-disk failures.