From 834a6d410c0a1384212cf7dd79290b1916d54f29 Mon Sep 17 00:00:00 2001 From: Richard Elling Date: Tue, 23 Apr 2019 15:40:38 -0700 Subject: [PATCH] added monitoring info to zfs_scan_mem_lim_fact --- ZFS-on-Linux-Module-Parameters.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/ZFS-on-Linux-Module-Parameters.md b/ZFS-on-Linux-Module-Parameters.md index 2279027..f944be7 100644 --- a/ZFS-on-Linux-Module-Parameters.md +++ b/ZFS-on-Linux-Module-Parameters.md @@ -2939,7 +2939,11 @@ by sequential scan algorithm. When the limit is reached scanning metadata is stopped and data verification I/O is started. Data verification I/O continues until the memory used by the sorting -algorith drops below below [zfs_scan_mem_lim_soft_fact](#zfs_scan_mem_lim_soft_fact) +algorithm drops below below [zfs_scan_mem_lim_soft_fact](#zfs_scan_mem_lim_soft_fact) + +Memory used by the sequential scan algorithm can be observed as the kmem sio_cache. +This is visible from procfs as `grep sio_cache /proc/slabinfo` and can be monitored +using slab-monitoring tools such as `slabtop` | zfs_scan_mem_lim_fact | Notes |---|---