diff options
| author | Garett Boone <freebsd@gbtechlab.com> | 2025-09-27 03:14:32 +0000 |
|---|---|---|
| committer | Alexander Ziaee <ziaee@FreeBSD.org> | 2026-02-03 19:11:00 +0000 |
| commit | 096c63bb9bc238d963d2f2883226354a940dbc74 (patch) | |
| tree | 580241e2668448a08101d0d28a58a918fef23537 | |
| parent | 103a72a45c03b325b67b015d0b2ecbd96c9700f5 (diff) | |
handbook/zfs: Fix vfs.zfs.prefetch.disable sysctl
Reviewed by: ziaee
Closes: https://github.com/freebsd/freebsd-doc/pull/554
| -rw-r--r-- | documentation/content/en/books/handbook/zfs/_index.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/content/en/books/handbook/zfs/_index.adoc b/documentation/content/en/books/handbook/zfs/_index.adoc index 36e79b2308..22d41f6468 100644 --- a/documentation/content/en/books/handbook/zfs/_index.adoc +++ b/documentation/content/en/books/handbook/zfs/_index.adoc @@ -2671,7 +2671,7 @@ Future disks use 4 KB sectors, and `ashift` values cannot change after creating In some specific cases, the smaller 512-byte block size might be preferable. When used with 512-byte disks for databases or as storage for virtual machines, less data transfers during small random reads. This can provide better performance when using a smaller ZFS record size. -* [[zfs-advanced-tuning-prefetch_disable]] `_vfs.zfs.prefetch_disable_` - +* [[zfs-advanced-tuning-prefetch_disable]] `_vfs.zfs.prefetch.disable_` - Disable prefetch. A value of `0` enables and `1` disables it. The default is `0`, unless the system has less than 4 GB of RAM. Prefetch works by reading larger blocks than requested into the crossref:zfs[zfs-term-arc,ARC] in hopes to soon need the data. If the workload has a large number of random reads, disabling prefetch may actually improve performance by reducing unnecessary reads. Adjust this value at any time with man:sysctl[8]. |