Module Name: src
Committed By: buhrow
Date: Thu Jul 28 18:25:22 UTC 2011
Modified Files:
src/sbin/raidctl: raidctl.8
Log Message:
Document the need for zeroing out the first 64 blocks of a replacement
component in a failed RAID set in order to avoid potentially configuring
RAId 1 sets with erroneous values taken from random extent data in the
replacement component partitions.
To generate a diff of this commit:
cvs rdiff -u -r1.61 -r1.62 src/sbin/raidctl/raidctl.8
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/sbin/raidctl/raidctl.8
diff -u src/sbin/raidctl/raidctl.8:1.61 src/sbin/raidctl/raidctl.8:1.62
--- src/sbin/raidctl/raidctl.8:1.61 Wed Jan 27 09:26:16 2010
+++ src/sbin/raidctl/raidctl.8 Thu Jul 28 18:25:22 2011
@@ -1,4 +1,4 @@
-.\" $NetBSD: raidctl.8,v 1.61 2010/01/27 09:26:16 wiz Exp $
+.\" $NetBSD: raidctl.8,v 1.62 2011/07/28 18:25:22 buhrow Exp $
.\"
.\" Copyright (c) 1998, 2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
@@ -1597,5 +1597,17 @@
additional space and speed, than it is to use parity, but
not keep the parity correct.
At least with RAID 0 there is no perception of increased data security.
+.Pp
+When replacing a failed component of a RAID set, it is a good
+idea to zero out the first 64 blocks of the new component to insure the
+RAIDframe driver doesn't erroneously detect a component label in the
+new component. This is particularly true on
+.Em
+RAID 1
+sets because there is at most one correct component label in a failed RAID
+1 installation, and the RAIDframe driver picks the component label with the
+highest serial number and modification value as the authoritative source
+for the failed RAID set when choosing which component label to use to
+configure the RAID set.
.Sh BUGS
Hot-spare removal is currently not available.
