summaryrefslogtreecommitdiff
path: root/share
diff options
context:
space:
mode:
Diffstat (limited to 'share')
-rw-r--r--share/man/man4/softraid.47
1 files changed, 5 insertions, 2 deletions
diff --git a/share/man/man4/softraid.4 b/share/man/man4/softraid.4
index 4fa72dd6e67..d4dbc7512ca 100644
--- a/share/man/man4/softraid.4
+++ b/share/man/man4/softraid.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: softraid.4,v 1.42 2017/06/27 16:02:05 tb Exp $
+.\" $OpenBSD: softraid.4,v 1.43 2020/10/25 15:33:19 schwarze 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: June 27 2017 $
+.Dd $Mdocdate: October 25 2020 $
.Dt SOFTRAID 4
.Os
.Sh NAME
@@ -201,6 +201,9 @@ There is no point in wasting a lot of time syncing random data.
The RAID 5 discipline does not initialize parity upon creation, instead parity
is only updated upon write.
.Pp
+Stacking disciplines (CRYPTO on top of RAID 1, for example) is not
+supported at this time.
+.Pp
Currently there is no automated mechanism to recover from failed disks.
.Pp
Certain RAID levels can protect against some data loss