man: full stop at EOL
Reviewed by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Closes #13116
This commit is contained in:
parent
6985944e2f
commit
2d232ca806
|
@ -1087,7 +1087,8 @@ This should be less than
|
|||
.It Sy zfs_wrlog_data_max Ns = Pq int
|
||||
The upper limit of write-transaction zil log data size in bytes.
|
||||
Once it is reached, write operation is blocked, until log data is cleared out
|
||||
after transaction group sync. Because of some overhead, it should be set
|
||||
after transaction group sync.
|
||||
Because of some overhead, it should be set
|
||||
at least 2 times the size of
|
||||
.Sy zfs_dirty_data_max
|
||||
.No to prevent harming normal write throughput.
|
||||
|
@ -1622,8 +1623,8 @@ After this threshold is crossed, additional frees will wait until the next TXG.
|
|||
.
|
||||
.It Sy zfs_prefetch_disable Ns = Ns Sy 0 Ns | Ns 1 Pq int
|
||||
Disable predictive prefetch.
|
||||
Note that it leaves "prescient" prefetch (for. e.g.\&
|
||||
.Nm zfs Cm send )
|
||||
Note that it leaves "prescient" prefetch
|
||||
.Pq for, e.g., Nm zfs Cm send
|
||||
intact.
|
||||
Unlike predictive prefetch, prescient prefetch never issues I/O
|
||||
that ends up not being needed, so it can't hurt performance.
|
||||
|
|
|
@ -701,7 +701,7 @@ For more information about redacted sends, see
|
|||
.feature com.delphix redacted_datasets no extensible_dataset
|
||||
This feature enables the receiving of redacted
|
||||
.Nm zfs Cm send Ns
|
||||
streams. which create redacted datasets when received.
|
||||
streams, which create redacted datasets when received.
|
||||
These datasets are missing some of their blocks,
|
||||
and so cannot be safely mounted, and their contents cannot be safely read.
|
||||
For more information about redacted receives, see
|
||||
|
|
|
@ -188,7 +188,7 @@ layer and a ZFS internal exception list.
|
|||
I/O operations will be aligned to the specified size boundaries.
|
||||
Additionally, the minimum (disk)
|
||||
write size will be set to the specified size, so this represents a
|
||||
space vs. performance trade-off.
|
||||
space/performance trade-off.
|
||||
For optimal performance, the pool sector size should be greater than
|
||||
or equal to the sector size of the underlying disks.
|
||||
The typical case for setting this property is when
|
||||
|
|
|
@ -188,7 +188,7 @@ Each number is in hexadecimal, and only one block can be specified.
|
|||
.It Fl C Ar dvas
|
||||
Inject the given error only into specific DVAs.
|
||||
The mask should be specified as a list of 0-indexed DVAs separated by commas
|
||||
.No (ex. Ar 0,2 Ns No ).
|
||||
.No (e.g. Ar 0,2 Ns No ).
|
||||
This option is not applicable to logical data errors such as
|
||||
.Sy decompress
|
||||
and
|
||||
|
|
|
@ -45,7 +45,8 @@ Removes ZFS label information from the specified
|
|||
If the
|
||||
.Ar device
|
||||
is a cache device, it also removes the L2ARC header
|
||||
(persistent L2ARC). The
|
||||
(persistent L2ARC).
|
||||
The
|
||||
.Ar device
|
||||
must not be part of an active pool configuration.
|
||||
.Bl -tag -width Ds
|
||||
|
|
Loading…
Reference in New Issue