Skip to content

Commit

Permalink
man: update recordsize max size info
Browse files Browse the repository at this point in the history
Reflect f2330bd
change in our man pages and add some context.

Wording is primarily copy-pasted from code comments.

Signed-off-by: George Melikov <mail@gmelikov.ru>
  • Loading branch information
gmelikov committed Sep 28, 2024
1 parent b1958b5 commit bdbecad
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 1 deletion.
5 changes: 5 additions & 0 deletions man/man4/zfs.4
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
12 changes: 11 additions & 1 deletion man/man7/zfsprops.7
Original file line number Diff line number Diff line change
Expand Up @@ -1527,11 +1527,21 @@ 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.
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.
Expand Down

0 comments on commit bdbecad

Please sign in to comment.