From be2a6be965502aeac6512a06357f87d72a8f25f8 Mon Sep 17 00:00:00 2001
From: Garrett Boone <47018474+garrettboone@users.noreply.github.com>
Date: Fri, 26 Sep 2025 23:14:32 -0400
Subject: [PATCH] Update _index.adoc with current zfs prefetch disable sysctl
 value

---
 documentation/content/en/books/handbook/zfs/_index.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/content/en/books/handbook/zfs/_index.adoc b/documentation/content/en/books/handbook/zfs/_index.adoc
index 36e79b230881..22d41f64689c 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].