From: Klemens Nanni <kn@openbsd.org>
Subject: Re: [PATCH] softraid(4) man page clarifications
To: "H. Hartzer" <h@hartzer.sh>, Jason McIntyre <jmc@kerhand.co.uk>, tech@openbsd.org
Date: Sun, 13 Apr 2025 11:23:08 +0000

12.04.2025 19:11, H. Hartzer пишет:
> Jason McIntyre wrote:
>> one more request: the discipline names are marked up, except for RAID 5,
>> which does not mark up "striping". could you make that change too?
>>
>> with that addition, looking for an ok for this.
>>
>> jmc
> 
> Good catch, I've added it.
> 
> Thanks again!

Reads OK to me.

> 
> -Henrich
> 
> --- share/man/man4/softraid.4.old       Fri Apr 11 23:18:05 2025
> +++ share/man/man4/softraid.4   Sat Apr 12 16:09:14 2025
> @@ -79,7 +79,9 @@ 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
> +A
> +.Em striping
> +discipline with
>  .Em floating parity
>  across all chunks.
>  It stripes data across chunks and provides parity to prevent data loss of
> @@ -119,9 +121,9 @@ in the boot storage area of the
>  .Nm
>  volume.
>  All chunks in the volume will then be bootable.
> -Boot support is currently limited to the CRYPTO, RAID 1 disciplines
> -on the amd64, arm64, i386, riscv64 and sparc64 platforms.
> -amd64, arm64, riscv64 and sparc64 also have boot support for the RAID 1C discipline.
> +Boot support is currently limited to the CRYPTO, RAID 1, and RAID 1C
> +disciplines on the amd64, arm64, riscv64 and sparc64 platforms.
> +Boot support on i386 is limited to CRYPTO and RAID 1.
>  On sparc64, bootable chunks must be RAID partitions using the letter
>  .Sq a .
>  At the
> @@ -236,6 +238,7 @@ boot> boot sr0a:/bsd
>  .Sh SEE ALSO
>  .Xr bio 4 ,
>  .Xr bioctl 8 ,
> +.Xr boot 8 ,
>  .Xr boot_sparc64 8 ,
>  .Xr disklabel 8 ,
>  .Xr fdisk 8 ,
> @@ -258,7 +261,7 @@ There is no point in wasting a lot of time syncing ran
>  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
> +Stacking disciplines (CRYPTO on top of RAID 5, for example) is not
>  supported at this time.
>  .Pp
>  Currently there is no automated mechanism to recover from failed disks.
>