| 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: | 188 |
| Popularity: | 2.32 |
| First Submitted: | 2015-08-31 12:01 (UTC) |
| Last Updated: | 2025-05-03 09:40 (UTC) |
@thedanbob: a (legally) safer way would be to integrate patches 3ace9de and 2e9c9b7 from github. Using the sed command only makes the kernel module lie about it's license which is legally wrong.
https://github.com/openzfs/zfs/issues/14658
The patches rewrites the the offending parts of the code to not use the two offending GPL-only symbols. You need to rerun autogen.sh once the patches are applied. I've tested this on both 2.1.9 and git and they work, so I can vouch for it.
It just broke on x86_64 too with kernel 6.2.8. A workaround is to edit the PKGBUILD to change the license to GPL:
prepare() {
cd "${srcdir}"/${pkgname%-dkms}-${pkgver}
sed -i 's/CDDL/GPL/' META # <-- add this line
@Taurolyon: This is a known issue. Reported 2 weeks ago for kernel 6.2.1 on github: https://github.com/openzfs/zfs/issues/14555
Getting the following when building.
==> dkms install --no-depmod zfs/2.1.9 -k 6.2.5-1-MANJARO-ARM
Error! Bad return status for module build on kernel: 6.2.5-1-MANJARO-ARM (aarch64)
Consult /var/lib/dkms/zfs/2.1.9/build/make.log for more information.
==> WARNING: `dkms install --no-depmod zfs/2.1.9 -k 6.2.5-1-MANJARO-ARM' exited 10
Checked the log and got these GPL errors:
MODPOST /var/lib/dkms/zfs/2.1.9/build/module/Module.symvers
ERROR: modpost: GPL-incompatible module zcommon.ko uses GPL-only symbol 'kernel_neon_begin'
ERROR: modpost: GPL-incompatible module zcommon.ko uses GPL-only symbol 'kernel_neon_end'
ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_end'
ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_begin'
make[2]: *** [scripts/Makefile.modpost:138: /var/lib/dkms/zfs/2.1.9/build/module/Module.symvers] Error 1
make[1]: *** [Makefile:1973: modpost] Error 2
make: *** [Makefile:55: modules-Linux] Error 2
make: Leaving directory '/var/lib/dkms/zfs/2.1.9/build/module'
If anyone gets a GPG error saying that the key to import has no user ID, execute gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 4F3BA9AB6D1F8D683DC2DFB56AD860EED4598027
I wasn't able to install the local packages with pacman -U as indicated, but had to do it using pacman -Udd to skip all checks
Updated zfs-utils and zfs-dkms, and included the patch to resolve this issue related to send/receive.
@korimitsu Please don't flag the package as out-of-date when you run into errors. Only flag the package as out-of-date when the version here is behind the upstream one.
To resolve your error, first build the zfs-utils package.
To get around mutal dependency, do
makepkg -s
For both packages. That will produce the package files
then
pacman -U pkg_file1 pkg_file2
Or just use ignore dependencies argument
Still not working:
$ git clone https://aur.archlinux.org/zfs-dkms.git
$ cd zfs-dkms
$ makepkg -si
==> Installing package zfs-dkms with pacman -U...
loading packages...
resolving dependencies...
warning: cannot resolve "zfs-utils=2.1.7", a dependency of "zfs-dkms"
:: The following package cannot be upgraded due to unresolvable dependencies:
zfs-dkms
:: Do you want to skip the above package for this upgrade? [y/N]
Pinned Comments
kstolp commented on 2025-04-29 16:56 (UTC) (edited on 2025-05-03 09:40 (UTC) by kstolp)
OpenZFS currently supports Linux kernel versions 4.18 - 6.14, as declared in the META file.
Options if your Linux kernel's version is not within that range:
1) Switch to another Linux kernel, such as
linux-lts.2) Prevent your kernel package from upgrading to an unsupported version until OpenZFS increases the maximum supported kernel version.
3) Modify this package to support your kernel by patching it on your local machine.
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
validpgpkeysarray. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheckargument tomakepkgwhen building. (not recommended)