summaryrefslogtreecommitdiff
path: root/debian/FAQ
diff options
context:
space:
mode:
authormadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-09-11 16:34:53 +0000
committermadduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464>2006-09-11 16:34:53 +0000
commitf76f67b278bd7b086570f9ad8dd3dcaec659a06c (patch)
tree1347e94559e3c3e5198f06c2b747583c97d41f89 /debian/FAQ
parent7f96d819343be3a9a7ff731a3a7d6b8fb9a582be (diff)
make MD array and RAID synonymous, fjp request
Diffstat (limited to 'debian/FAQ')
-rw-r--r--debian/FAQ8
1 files changed, 4 insertions, 4 deletions
diff --git a/debian/FAQ b/debian/FAQ
index 6a4ff117..0d93651b 100644
--- a/debian/FAQ
+++ b/debian/FAQ
@@ -3,7 +3,7 @@ Frequently asked questions -- Debian mdadm
Also see /usr/share/doc/mdadm/README.recipes.gz
-0. How do I overwrite ("zero") the superblock?
+1. How do I overwrite ("zero") the superblock?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mdadm --zero-superblock /dev/mdX
@@ -26,12 +26,12 @@ Also see /usr/share/doc/mdadm/README.recipes.gz
this may not be what you want. Instead, zeroing the superblock will
(permanently) prevent a device from being considered as part of an array.
-1. How do I change the preferred minor of a MD array?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+2. How do I change the preferred minor of a MD array (RAID)?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
See item 12 in /usr/share/doc/mdadm/README.recipes.gz and read the mdadm
manpage (search for 'preferred').
-2. How does mdadm determine which /dev/mdX or /dev/md/X to use?
+3. How does mdadm determine which /dev/mdX or /dev/md/X to use?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The logic used by mdadm to determine the device node name in the mdadm
--examine output (which is used to generate mdadm.conf) depends on several