Remove the RAID 4 discipline from softraid. Anyone sensible would use RAID

5 instead of RAID 4, assuming both were functional.

Discussed with krw@

1 files changed, 4 insertions, 12 deletions

diff --git a/share/man/man4/softraid.4 b/share/man/man4/softraid.4
index 7940df7e082..e6b592c3fdf 100644
--- a/share/man/man4/softraid.4
+++ b/share/man/man4/softraid.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: softraid.4,v 1.33 2013/10/31 17:54:57 stsp Exp $
+.\"	$OpenBSD: softraid.4,v 1.34 2014/01/18 09:01:01 jsing Exp $
 .\"
 .\" Copyright (c) 2007 Todd T. Fries   <todd@OpenBSD.org>
 .\" Copyright (c) 2007 Marco Peereboom <marco@OpenBSD.org>
@@ -15,7 +15,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: October 31 2013 $
+.Dd $Mdocdate: January 18 2014 $
 .Dt SOFTRAID 4
 .Os
 .Sh NAME
@@ -78,14 +78,6 @@ 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 4
-A striping discipline with a
-.Em fixed parity
-chunk.
-It stripes data across chunks and provides parity to prevent data loss of
-a single chunk failure.
-Read performance is increased,
-though write performance is limited by the parity chunk.
 .It RAID 5
 A striping discipline with
 .Em floating parity
@@ -93,7 +85,7 @@ 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 should be faster than RAID 4.
+write performance does incur additional overhead.
 .It CRYPTO
 An
 .Em encrypting
@@ -203,7 +195,7 @@ 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 4 and 5 disciplines do not initialize the parity upon creation.
+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.