-.\" $OpenBSD: bioctl.8,v 1.94 2015/02/28 21:51:57 bentley Exp $
+.\" $OpenBSD: bioctl.8,v 1.95 2015/04/11 16:37:34 jsing Exp $
.\"
.\" Copyright (c) 2004, 2005 Marco Peereboom
.\"
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.Dd $Mdocdate: February 28 2015 $
+.Dd $Mdocdate: April 11 2015 $
.Dt BIOCTL 8
.Os
.Sh NAME
.It 1
RAID 1:
A mirroring discipline.
-.\" .It 5
-.\" RAID 5:
-.\" A striping discipline with floating parity chunk.
+.It 5
+RAID 5:
+A striping discipline with floating parity chunk.
.It C
CRYPTO:
An encrypting discipline.
.Pp
The RAID 0, RAID 1 and CONCAT disciplines require a minimum of two devices to
be provided via
-.Fl l
-.\" RAID 5 requires at least three devices,
+.Fl l .
+RAID 5 requires at least three devices
and the CRYPTO discipline requires exactly one.
.It Fl d
Delete volume specified by device.
-.\" $OpenBSD: softraid.4,v 1.39 2015/02/16 16:38:54 naddy Exp $
+.\" $OpenBSD: softraid.4,v 1.40 2015/04/11 16:37:34 jsing Exp $
.\"
.\" Copyright (c) 2007 Todd T. Fries <todd@OpenBSD.org>
.\" Copyright (c) 2007 Marco Peereboom <marco@OpenBSD.org>
.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
.\"
-.Dd $Mdocdate: February 16 2015 $
+.Dd $Mdocdate: April 11 2015 $
.Dt SOFTRAID 4
.Os
.Sh NAME
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
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 does not initialize parity upon creation, instead parity
+is only updated upon write.
+.Pp
Currently there is no automated mechanism to recover from failed disks.
.Pp
Sparc hardware needs to use fstype