mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2026-05-26 20:22:14 +03:00
Fix incorrect use of unit prefix names in man pages
Reviewed-by: George Melikov <mail@gmelikov.ru> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Damian Szuberski <szuberskidamian@gmail.com> Signed-off-by: WHR <msl0000023508@gmail.com> Closes #13363
This commit is contained in:
@@ -157,7 +157,7 @@ separated by whitespace and/or commas.
|
||||
Only features present in all files are enabled.
|
||||
.Pp
|
||||
Simple sanity checks are applied to the files:
|
||||
they must be between 1B and 16kB in size, and must end with a newline character.
|
||||
they must be between 1 B and 16 KiB in size, and must end with a newline character.
|
||||
.Pp
|
||||
The requested features are applied when a pool is created using
|
||||
.Nm zpool Cm create Fl o Sy compatibility Ns = Ns Ar …
|
||||
@@ -446,7 +446,7 @@ or smaller can take advantage of this feature.
|
||||
When this feature is enabled, the contents of highly-compressible blocks are
|
||||
stored in the block "pointer" itself (a misnomer in this case, as it contains
|
||||
the compressed data, rather than a pointer to its location on disk).
|
||||
Thus the space of the block (one sector, typically 512B or 4kB) is saved,
|
||||
Thus the space of the block (one sector, typically 512 B or 4 KiB) is saved,
|
||||
and no additional I/O is needed to read and write the data block.
|
||||
.
|
||||
\*[instant-never]
|
||||
@@ -565,29 +565,29 @@ already exist on the receiving side.
|
||||
\*[instant-never]
|
||||
.
|
||||
.feature org.open-zfs large_blocks no extensible_dataset
|
||||
This feature allows the record size on a dataset to be set larger than 128kB.
|
||||
This feature allows the record size on a dataset to be set larger than 128 KiB.
|
||||
.Pp
|
||||
This feature becomes
|
||||
.Sy active
|
||||
once a dataset contains a file with a block size larger than 128kB,
|
||||
once a dataset contains a file with a block size larger than 128 KiB,
|
||||
and will return to being
|
||||
.Sy enabled
|
||||
once all filesystems that have ever had their recordsize larger than 128kB
|
||||
once all filesystems that have ever had their recordsize larger than 128 KiB
|
||||
are destroyed.
|
||||
.
|
||||
.feature org.zfsonlinux large_dnode no extensible_dataset
|
||||
This feature allows the size of dnodes in a dataset to be set larger than 512B.
|
||||
This feature allows the size of dnodes in a dataset to be set larger than 512 B.
|
||||
.
|
||||
This feature becomes
|
||||
.Sy active
|
||||
once a dataset contains an object with a dnode larger than 512B,
|
||||
once a dataset contains an object with a dnode larger than 512 B,
|
||||
which occurs as a result of setting the
|
||||
.Sy dnodesize
|
||||
dataset property to a value other than
|
||||
.Sy legacy .
|
||||
The feature will return to being
|
||||
.Sy enabled
|
||||
once all filesystems that have ever contained a dnode larger than 512B
|
||||
once all filesystems that have ever contained a dnode larger than 512 B
|
||||
are destroyed.
|
||||
Large dnodes allow more data to be stored in the bonus buffer,
|
||||
thus potentially improving performance by avoiding the use of spill blocks.
|
||||
|
||||
Reference in New Issue
Block a user