Disable the RAID 5 discipline in bioctl, as the current softraid RAID 5

discipline will more than likely eat data if a drive is lost.

Discussed with krw@

1 files changed, 12 insertions, 12 deletions

diff --git a/share/man/man4/softraid.4 b/share/man/man4/softraid.4
index e6b592c3fdf..65760e1a6d2 100644
--- a/share/man/man4/softraid.4
+++ b/share/man/man4/softraid.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: softraid.4,v 1.34 2014/01/18 09:01:01 jsing Exp $
+.\"	$OpenBSD: softraid.4,v 1.35 2014/01/18 09:11:12 jsing Exp $
 .\"
 .\" Copyright (c) 2007 Todd T. Fries   <todd@OpenBSD.org>
 .\" Copyright (c) 2007 Marco Peereboom <marco@OpenBSD.org>
@@ -78,14 +78,14 @@ though at the cost of write speed.
 Unlike traditional RAID 1,
 .Nm
 supports the use of more than two chunks in a RAID 1 setup.
-.It RAID 5
-A striping discipline with
-.Em floating parity
-across all chunks.
-It stripes data across chunks and provides parity to prevent data loss of
-a single chunk failure.
-Read performance is increased;
-write performance does incur additional overhead.
+.\" .It RAID 5
+.\" A striping discipline with
+.\" .Em floating parity
+.\" across all chunks.
+.\" It stripes data across chunks and provides parity to prevent data loss of
+.\" a single chunk failure.
+.\" Read performance is increased;
+.\" write performance does incur additional overhead.
 .It CRYPTO
 An
 .Em encrypting
@@ -195,9 +195,9 @@ The RAID 1 discipline does not initialize the mirror upon creation.
 This is by design because all sectors that are read are written first.
 There is no point in wasting a lot of time syncing random data.
 .Pp
-The RAID 5 discipline do not initialize the parity upon creation.
-This is due to the scrub functionality not being currently implemented.
-.Pp
+.\" The RAID 5 discipline do not initialize the parity upon creation.
+.\" This is due to the scrub functionality not being currently implemented.
+.\" .Pp
 Currently there is no automated mechanism to recover from failed disks.
 .Pp
 Sparc hardware needs to use fstype