Thanks @Achelous - done, this is exactly the problem and knowing it's 1/32 means I can at least fix to 8GB for now.
Search Criteria
Package Details: zfs-dkms 2.2.6-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/zfs-dkms.git (read-only, click to copy) |
---|---|
Package Base: | zfs-dkms |
Description: | Kernel modules for the Zettabyte File System. |
Upstream URL: | https://zfsonlinux.org/ |
Licenses: | CDDL |
Provides: | SPL-MODULE, zfs, ZFS-MODULE |
Submitter: | isiachi |
Maintainer: | kstolp |
Last Packager: | kstolp |
Votes: | 179 |
Popularity: | 6.41 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2024-09-05 04:42 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR, dkms-fast-zstdAUR)
- zfs-utilsAUR (zfs-utils-gitAUR, zfs-linux-gitAUR, zfs-utils-staging-gitAUR)
Required by (20)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfs-openrc
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 34 35 36 37 38 39 40 41 42 43 44 .. 63 Next › Last »
iusrlinearb commented on 2020-03-26 21:17 (UTC)
Achelous commented on 2020-03-26 19:58 (UTC)
@iusrlinearb
I noticed this bug in zfs a few months ago. It doesn't let you set zfs_arc_max to a value less than the default arc_c_min, which is 1/32 of all RAM.
I've raised a GitHub issue here:
https://github.com/openzfs/zfs/issues/10157
Please feel free to comment on the issue if you think you're seeing the same thing.
iusrlinearb commented on 2020-03-25 15:36 (UTC) (edited on 2020-03-25 16:13 (UTC) by iusrlinearb)
I'm struggling to stop zfs from consuming lots of RAM.
# cat /proc/spl/kstat/zfs/arcstats | grep c_max
c_max 4 135097968640
If I look at arcstats, I see it growing rapidly towards c_max:
# cat /proc/spl/kstat/zfs/arcstats | grep size
size 4 89817294664
[snipped the rest]
I've tried the obvious things. E.g. adding options zfs zfs_arc_max=5368709120 into /etc/modprobe.d/zfs.conf (and rebooting), adding zfs.zfs_arc_max=5368709120 to the end of my GRUB_CMDLINE_LINUX_DEFAULT and grub-mkconfig, rebooting.
I can see that the values are correctly being picked up - e.g. # cat /sys/module/zfs/parameters/zfs_arc_max 5368709120
Have looked at the wiki, for example https://wiki.archlinux.org/index.php/ZFS#ZFS_is_using_too_much_RAM
Also searched forums for zfs_arc_max but no useful messages. Anywhere else I should look? Thanks.
eschwartz commented on 2020-03-23 15:52 (UTC) (edited on 2020-03-23 15:52 (UTC) by eschwartz)
@LinuxIsBest,
Comment deleted, next time you attempt personal attacks on a Trusted User I'll just suspend your account.
eschwartz commented on 2020-03-22 16:01 (UTC) (edited on 2020-03-22 16:03 (UTC) by eschwartz)
iusrlinearb,
Doesn't appear to build, at least on my system.
==> Verifying source file signatures with gpg...
zfs-0.8.3.tar.gz ... FAILED (unknown public key 6AD860EED4598027)
==> ERROR: One or more PGP signatures could not be verified!
...
This package doesn't support people who have failed to read the wiki page https://wiki.archlinux.org/index.php/Makepkg, or cannot interpret error messages.
risto3 commented on 2020-03-17 08:20 (UTC)
I'm using zfs-dkms on x86_64 5.4.25-2-lts is it normal to see the following in boot logs?
mars 16 07:04:09 smicro kernel: zlua: loading out-of-tree module taints kernel.
mars 16 07:04:09 smicro kernel: zlua: module license 'MIT' taints kernel.
mars 16 07:04:09 smicro kernel: Disabling lock debugging due to kernel taint
mars 16 07:04:09 smicro kernel: zlua: module verification failed: signature and/or required key missing - tainting kernel
Pinned Comments
kstolp commented on 2023-09-29 00:34 (UTC)
When requesting changes, please include detailed reasoning for the change.
kstolp commented on 2023-01-07 09:31 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
You have two options:
1) Import the two keys into your keyring. ArchWiki article. You can find the key IDs in the PKGBUILD file, in the
validpgpkeys
array. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheck
argument tomakepkg
when building. (not recommended)