diff options
| author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-10-26 09:57:55 +0000 |
|---|---|---|
| committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-10-26 09:57:55 +0000 |
| commit | 767210c5fbd689906c7795cacae9904c24d0b113 (patch) | |
| tree | 15913571f57dae7ccf611129562324840c0b84af /debian/FAQ | |
| parent | 848b9ac48750021763dd657c690a8be0118a0b19 (diff) | |
more faq work
Diffstat (limited to 'debian/FAQ')
| -rw-r--r-- | debian/FAQ | 13 |
1 files changed, 9 insertions, 4 deletions
@@ -179,11 +179,16 @@ Also see /usr/share/doc/mdadm/README.recipes.gz 6b. What's the difference between RAID1+0 and RAID0+1? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In short: RAID1+0 concatenates two mirrored arrays while RAID0+1 mirrors two - concatenated arrays. + concatenated arrays. However, the two are also often switched. - RAID1+0 has a greater chance to survive two disk failures, its performance - suffers less when in degraded state, and it resyncs faster after replacing - a failed disk. See http://aput.net/~jheiss/raid10/ for more details. + The linux MD driver supports RAID10, which is equivalent to the above + RAID1+0 definition. + + RAID1+0/10 has a greater chance to survive two disk failures, its + performance suffers less when in degraded state, and it resyncs faster after + replacing a failed disk. + + See http://aput.net/~jheiss/raid10/ for more details. 7. Which RAID10 layout scheme should I use ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |