Merging upstream version 4.23.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 38 insertions, 46 deletions

diff --git a/upstream/archlinux/man8/mkfs.btrfs.8 b/upstream/archlinux/man8/mkfs.btrfs.8
index d3a88275..03e2b774 100644
--- a/upstream/archlinux/man8/mkfs.btrfs.8
+++ b/upstream/archlinux/man8/mkfs.btrfs.8
@@ -1,3 +1,4 @@
+'\" t
 .\" Man page generated from reStructuredText.
 .
 .
@@ -27,7 +28,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
-.TH "MKFS.BTRFS" "8" "Feb 14, 2024" "6.7.1" "BTRFS"
+.TH "MKFS.BTRFS" "8" "May 03, 2024" "6.8.1" "BTRFS"
 .SH NAME
 mkfs.btrfs \- create a btrfs filesystem
 .SH SYNOPSIS
@@ -63,7 +64,7 @@ effectively specifies the size of the filesystem.
 .BI \-\-csum \ <type>\fR,\fB \ \-\-checksum \ <type>
 Specify the checksum algorithm. Default is \fIcrc32c\fP\&. Valid values are \fIcrc32c\fP,
 \fIxxhash\fP, \fIsha256\fP or \fIblake2\fP\&. To mount such filesystem kernel must support the
-checksums as well. See section \fI\%CHECKSUM ALGORITHMS\fP
+checksums as well. See section \X'tty: link #man-mkfs-checksum-algorithms'\fI\%CHECKSUM ALGORITHMS\fP\X'tty: link'
 in \fI\%btrfs(5)\fP\&.
 .UNINDENT
 .INDENT 0.0
@@ -169,7 +170,7 @@ Specify the sectorsize, the minimum data block allocation unit.
 Versions prior to 6.7 set the sectorsize matching the host CPU
 page size, starting in 6.7 this is 4KiB for cross\-architecture
 compatibility. Please read more about the \fI\%subpage block size support\fP
-and \fI\%its status\fP\&.
+and \X'tty: link #status-subpage-block-size'\fI\%its status\fP\X'tty: link'\&.
 .UNINDENT
 .UNINDENT
 .sp
@@ -232,11 +233,9 @@ for more details.  To see all available features that
 .INDENT 7.0
 .INDENT 3.5
 .sp
-.nf
-.ft C
+.EX
 $ mkfs.btrfs \-O list\-all
-.ft P
-.fi
+.EE
 .UNINDENT
 .UNINDENT
 .TP
@@ -309,11 +308,9 @@ devices to scan at the time of mount.
 .INDENT 0.0
 .INDENT 3.5
 .sp
-.nf
-.ft C
+.EX
 # mount \-o device=/dev/sdb,device=/dev/sdc /dev/sda /mnt
-.ft P
-.fi
+.EE
 .UNINDENT
 .UNINDENT
 .sp
@@ -337,7 +334,7 @@ RAID5/6 has known problems and should not be used in production.
 .SH FILESYSTEM FEATURES
 .sp
 Features that can be enabled during creation time. See also \fI\%btrfs(5)\fP section
-\fI\%FILESYSTEM FEATURES\fP\&.
+\X'tty: link #man-btrfs5-filesystem-features'\fI\%FILESYSTEM FEATURES\fP\X'tty: link'\&.
 .INDENT 0.0
 .TP
 .B mixed\-bg
@@ -379,7 +376,7 @@ stored as an extent, saves a few percent of metadata if sparse files are used
 (kernel support since 5.12)
 .sp
 zoned mode, data allocation and write friendly to zoned/SMR/ZBC/ZNS devices,
-see \fI\%ZONED MODE\fP in
+see \X'tty: link #man-btrfs5-zoned-mode'\fI\%ZONED MODE\fP\X'tty: link' in
 \fI\%btrfs(5)\fP, the mode is automatically selected when a
 zoned device is detected
 .TP
@@ -422,14 +419,23 @@ conversion is not possible.
 .INDENT 0.0
 .TP
 .B raid\-stripe\-tree
-(kernel support since 6.7)
+(kernel support since 6.7, CONFIG_BTRFS_DEBUG)
 .sp
-New tree for logical file extent mapping where the physical mapping
-may not match on multiple devices. this is now used in zoned mode to
+Separate tree for logical file extent mapping where the physical mapping
+may not match on multiple devices. This is now used in zoned mode to
 implement RAID0/RAID1* profiles, but can be used in non\-zoned mode as
 well. The support for RAID56 is in development and will eventually
 fix the problems with the current implementation. This is a backward
 incompatible feature and has to be enabled at mkfs time.
+.sp
+\fBNOTE:\fP
+.INDENT 7.0
+.INDENT 3.5
+Due to the status of implementation it is enabled only in
+builds with CONFIG_BTRFS_DEBUG. Support by the kernel module
+can be found in the sysfs feature list.
+.UNINDENT
+.UNINDENT
 .TP
 .B squota
 (kernel support since 6.7)
@@ -479,9 +485,8 @@ and constraints, see the section \fI\%PROFILES\fP for more details
 .sp
 There are the following block group types available:
 .TS
-center;
-|l|l|l|l|l|l|.
-_
+box center;
+l|l|l|l|l|l.
 T{
 Profiles
 T}	T{
@@ -615,7 +620,6 @@ T}	T{
 T}	T{
 3/any (see note 3)
 T}
-_
 .TE
 .sp
 \fBWARNING:\fP
@@ -654,9 +658,8 @@ the free/allocated space and may appear random. All devices are assumed to be
 present at the time of the blocks would have been written.
 .SS RAID1
 .TS
-center;
-|l|l|l|l|.
-_
+box center;
+l|l|l|l.
 T{
 device 1
 T}	T{
@@ -698,13 +701,11 @@ T}	T{
 B
 T}	T{
 T}
-_
 .TE
 .SS RAID1C3
 .TS
-center;
-|l|l|l|l|.
-_
+box center;
+l|l|l|l.
 T{
 device 1
 T}	T{
@@ -750,13 +751,11 @@ C
 T}	T{
 B
 T}
-_
 .TE
 .SS RAID0
 .TS
-center;
-|l|l|l|l|.
-_
+box center;
+l|l|l|l.
 T{
 device 1
 T}	T{
@@ -806,13 +805,11 @@ C4
 T}	T{
 A4
 T}
-_
 .TE
 .SS RAID5
 .TS
-center;
-|l|l|l|l|.
-_
+box center;
+l|l|l|l.
 T{
 device 1
 T}	T{
@@ -862,13 +859,11 @@ PC
 T}	T{
 PA
 T}
-_
 .TE
 .SS RAID6
 .TS
-center;
-|l|l|l|l|.
-_
+box center;
+l|l|l|l.
 T{
 device 1
 T}	T{
@@ -918,7 +913,6 @@ PC
 T}	T{
 PA
 T}
-_
 .TE
 .SH DUP PROFILES ON A SINGLE DEVICE
 .sp
@@ -967,8 +961,7 @@ to be created and could end up in the following situation:
 .INDENT 0.0
 .INDENT 3.5
 .sp
-.nf
-.ft C
+.EX
 # mkfs.btrfs \-f \-n 65536 /dev/loop0
 btrfs\-progs v3.19\-rc2\-405\-g976307c
 See https://btrfs.readthedocs.io for more information.
@@ -992,8 +985,7 @@ Devices:
 
 # mount /dev/loop0 /mnt/
 mount: mount /dev/loop0 on /mnt failed: No space left on device
-.ft P
-.fi
+.EE
 .UNINDENT
 .UNINDENT
 .sp
@@ -1003,12 +995,12 @@ than can fit into the filesystem.
 .SH AVAILABILITY
 .sp
 \fBbtrfs\fP is part of btrfs\-progs.  Please refer to the documentation at
-\fI\%https://btrfs.readthedocs.io\fP\&.
+\X'tty: link https://btrfs.readthedocs.io'\fI\%https://btrfs.readthedocs.io\fP\X'tty: link'\&.
 .SH SEE ALSO
 .sp
 \fI\%btrfs(5)\fP,
 \fI\%btrfs(8)\fP,
 \fI\%btrfs\-balance(8)\fP,
-\fBwipefs(8)\fP
+\X'tty: link https://man7.org/linux/man-pages/man8/wipefs.8.html'\fI\%wipefs(8)\fP\X'tty: link'
 .\" Generated by docutils manpage writer.
 .