c/mirror_zfs
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_zfs.git synced 2024-11-17 01:51:00 +03:00
Code Issues Packages Projects Releases Wiki Activity

man: update recordsize max size info

Browse Source 
Reflect f2330bd156
change in our man pages and add some context.

Wording is primarily copy-pasted from code comments.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by:  Tino Reichardt <milky-zfs@mcmilk.de>
Signed-off-by: George Melikov <mail@gmelikov.ru>
Closes #16581
This commit is contained in:
George Melikov 2024-09-29 23:19:52 +03:00 committed by GitHub
parent b1958b531b
commit 5591505299
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
man/man4/zfs.4
View File

@ -1749,6 +1749,11 @@ Therefore, we formerly forbade creating blocks larger than 1M.
Larger blocks could be created by changing it,
and pools with larger blocks can always be imported and used,
regardless of this setting.
.Pp
Note that it is still limited by default to
.Ar 1 MiB
on x86_32, because Linux's
3/1 memory split doesn't leave much room for 16M chunks.
.
.It Sy zfs_allow_redacted_dataset_mount Ns = Ns Sy 0 Ns | Ns 1 Pq int
Allow datasets received with redacted send/receive to be mounted.

13
man/man7/zfsprops.7
View File

@ -1527,11 +1527,22 @@ and less than or equal to
If the
.Sy large_blocks
feature is enabled on the pool, the size may be up to
.Ar 1 MiB .
.Ar 16 MiB .
See
.Xr zpool-features 7
for details on ZFS feature flags.
.Pp
However, blocks larger than
.Ar 1 MiB
can have an impact on i/o latency (e.g. tying up a spinning disk for
~300ms), and also potentially on the memory allocator.
.Pp
Note that maximum size is still limited by default to
.Ar 1 MiB
on x86_32, see
.Sy zfs_max_recordsize
module parameter.
.Pp
Changing the file system's
.Sy recordsize
affects only files created afterward; existing files are unaffected.