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.

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

Spurious warning when setting ARC minimum and maximum values from kernel command line #12504

Open
BrassyPanache opened this issue Aug 23, 2021 · 4 comments
Labels
Bot: Not Stale Override for the stale bot Type: Defect Incorrect behavior (e.g. crash, hang)

Comments

@BrassyPanache
Copy link

System information

Type Version/Name
Distribution Name Gentoo
Distribution Version Stable (it's a rolling release)
Kernel Version 5.10.52
Architecture amd64
OpenZFS Version zfs-2.1.0

Issue

When specifying the following kernel parameters to set the ARC size:

zfs.zfs_arc_min=268435456 zfs.zfs_arc_max=1073741824

I receive the following warning:

[    0.043410] WARNING: ignoring tunable zfs_arc_min (using 0 instead)
[    0.043411] WARNING: ignoring tunable zfs_arc_min (using 0 instead)
[    0.043411] WARNING: ignoring tunable zfs_arc_max (using 0 instead)

The warning appears to be spurious because when I check my ARC size it seems to be set to the expected values:

# cat  /proc/spl/kstat/zfs/arcstats | grep -E "c_m[ax|in]"
c_min                           4    268435456
c_max                           4    1073741824

I compile ZFS statically into the kernel (rather than as a module).

My full kernel command line is as follows:

quiet mitigations=off intel_pstate=disable nosmt zfs.zfs_arc_min=268435456 zfs.zfs_arc_max=1073741824

This log message caused me some confusion and I spent some time investigating the apparent failure.

Thanks for all the efforts.

@BrassyPanache BrassyPanache added the Type: Defect Incorrect behavior (e.g. crash, hang) label Aug 23, 2021
@paulhargreaves
Copy link

Please see #10157 (comment)

@itspngu
Copy link

itspngu commented Feb 21, 2022

In my case the message¹ disappears when setting zfs_arc_max before zfs_arc_min. Tripped over it when skimming through the dmesg of my Proxmox host. My guess is that the defaults have been tampered with so setting zfs_arc_min first fails because it's larger than zfs_arc_max.

¹ I was getting 2 consecutive lines of ignoring tunable zfs_arc_min (using 0 instead) on boot until I swapped the order around in /etc/modprobe.d/zfs.conf.

@BrassyPanache
Copy link
Author

Thanks @paulhargreaves for that link. I've just testing again using release 2.1.2. The error for me still remains.

Thanks @itspngu. I've tried both min before max and max before min to no avail.

@stale
Copy link

stale bot commented Mar 14, 2023

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale No recent activity for issue label Mar 14, 2023
@behlendorf behlendorf added Bot: Not Stale Override for the stale bot and removed Status: Stale No recent activity for issue labels Mar 14, 2023
ProxBot pushed a commit to proxmox/proxmox-backup that referenced this issue Jun 15, 2023
Currently the values set for zfs_arc_min and zfs_arc_max are ignored
by the kernel:
```
Unknown kernel command line parameters... will be passed to user space
```
module parameters provided on the commandline usually need to be
prefixed with the modulename (e.g. zfs.zfs_arc_min, see [0] for a bit
on related information (the issue itself is not related)).

Paradoxically currently ZFS will print spurious warnings about
settings being ignored when they are actually set - see [1].

Booting the debug image and connecting the shell on the serial console
confirmed that the values did not seem to be set:
`grep '^c_' /proc/spl/kstat/zfs/arcstats` showed half of the memory
for c_max.

[0] openzfs/zfs#698
[1] openzfs/zfs#12504

Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot: Not Stale Override for the stale bot Type: Defect Incorrect behavior (e.g. crash, hang)
Projects
None yet
Development

No branches or pull requests

4 participants