Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

man: update recordsize max size info #16581

Merged
merged 1 commit into from
Sep 29, 2024
Merged

man: update recordsize max size info #16581

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions man/man4/zfs.4
View file
Open in desktop
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
13 changes: 12 additions & 1 deletion man/man7/zfsprops.7
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Comment on lines +1540 to +1542
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Formally it is any 32-bit, not necessary x86.

.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
Loading