zfs_resilver_delay - Permission denied (parameter doesn't exist?)

alpha754293

Member
Jan 8, 2023
81
17
8
I am trying to speed up my resilvering process as I am expanding one of my raidz2 vdevs from being 8x HGST 6 TB SATA 6 Gbps 7200 rpm HDDs to 8x WD DC520 12 TB SAS 12 Gbps 7200 rpm HDDs.

From this reddit post, it suggested that I tried to set these ZFS module parameters to achieve this goal:

Code:
echo 0 > /sys/module/zfs/parameters/zfs_resilver_delay
echo 512 > /sys/module/zfs/parameters/zfs_top_maxinflight
echo 8000 > /sys/module/zfs/parameters/zfs_resilver_min_time_ms

However, when I tried to execute the first step, I get:

Code:
-bash: /sys/module/zfs/parameters/zfs_resilver_delay: Permission denied

When I checked the /sys/module/zfs/parameters folder, that parameter doesn't exist.

Is that by design or is this an issue with my system?

Here is the output of my package versions:

Code:
proxmox-ve: 7.4-1 (running kernel: 5.15.149-1-pve)
pve-manager: 7.4-17 (running version: 7.4-17/513c62be)
pve-kernel-5.15: 7.4-12
pve-kernel-5.15.149-1-pve: 5.15.149-1
pve-kernel-5.15.143-1-pve: 5.15.143-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.3
libpve-apiclient-perl: 3.2-2
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.6-1
proxmox-backup-file-restore: 2.4.6-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+3
pve-firewall: 4.3-5
pve-firmware: 3.6-6
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.10-1
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-5
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.15-pve1

Any help or insight as to why this ZFS module parameter appearing to be absent from my system is greatly appreciated.

Thank you.

P.S. I'm running Proxmox 7.4-17 with the 5.15.149-1 Linux kernel.

Hardware specs:
2x Intel Xeon E5-2697A v4
Supermicro X10DRi-T4+
16x Crucial DDR4-2666(?) ECC Reg. RAM running at DDR4-2400 speed (I think? I can't remember anymore)
Broadcom/Avago/LSI 9361-8i MegaRAID SAS 12 Gbps HW SAS RAID HBA
RTX A2000 6 GB
Mellanox ConnectX-4 dual VPI port 100 Gbps IB NIC
4x HGST 3 TB SATA 3 Gbps 7200 rpm HDDs for the Proxmox OS itself (in HW RAID6)
8x HGST 6 TB SATA 6 Gbps 7200 rpm HDDs for VM/CT disks (raidz2)
8x HGST 6 TB + 8x 10 TB + 8x 10 TB HDDs for bulk storage (one pool, three raidz2 vdevs)
Supermicro 4U 36-bay server.

*edit*
It would appear that the ZFS module parameter zfs_top_maxinflight also doesn't exist in /sys/module/zfs/parameters, in Proxmox 7.4-17.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!