r234 - in mdadm/trunk/debian: . initramfs

madduck at users.alioth.debian.org madduck at users.alioth.debian.org
Thu Oct 26 18:40:27 UTC 2006


Author: madduck
Date: 2006-10-26 18:40:26 +0000 (Thu, 26 Oct 2006)
New Revision: 234

Modified:
   mdadm/trunk/debian/FAQ
   mdadm/trunk/debian/initramfs/script.local-top
Log:
faq updates

Modified: mdadm/trunk/debian/FAQ
===================================================================
--- mdadm/trunk/debian/FAQ	2006-10-26 09:57:55 UTC (rev 233)
+++ mdadm/trunk/debian/FAQ	2006-10-26 18:40:26 UTC (rev 234)
@@ -129,6 +129,9 @@
 
 4b. Can a 4-disk RAID10 survive two disk failures?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+  I am assuming that you are talking about a setup with two copies of each
+  block, so --layout=near2/far2/offset2:
+
   In half of the cases, yes [0], and it does not matter which layout you use.
   When you assemble 4 disks into a RAID10, you essentially stripe a RAID0
   across two RAID1, so the four disks A,B,C,D become two pairs: A,B and C,D.
@@ -138,7 +141,8 @@
   Thus, if you see a disk failing, replace it as soon as possible!
 
   If you need to handle two failing disks out of a set of four, you have to
-  use RAID6.
+  use RAID6, or store more than two copies of each block (see the --layout
+  option in the mdadm(8) manpage).
 
   0. it's actually 1/(n-1), where n is the number of disks. I am not
      a mathematician, see http://aput.net/~jheiss/raid10/

Modified: mdadm/trunk/debian/initramfs/script.local-top
===================================================================
--- mdadm/trunk/debian/initramfs/script.local-top	2006-10-26 09:57:55 UTC (rev 233)
+++ mdadm/trunk/debian/initramfs/script.local-top	2006-10-26 18:40:26 UTC (rev 234)
@@ -106,13 +106,4 @@
   done
 fi
 
-verbose && log_begin_msg "Triggering udev events for assembled arrays"
-for uevent in /sys/block/md*/uevent; do
-  test -w $uevent || continue
-  echo add > $uevent
-  uevent=${uevent#/sys/block/}
-  verbose && log_success_msg "triggered uevent for ${uevent%/uevent}"
-done
-verbose && log_end_msg
-
 exit 0




More information about the pkg-mdadm-commits mailing list