Arch Linux User Repository

OpenZFS currently supports Linux kernel versions 4.18 - 6.15, 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.

When requesting changes, please include detailed reasoning for the change.

If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.

==> ERROR: One or more PGP signatures could not be verified!

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 to makepkg when building. (not recommended)

My speculation is that maintainers just have not enough time to update this package. Usual lag of ZFS packages is about 1 month. jonathonf maintains 195 packages on AUR and a few dozens of Ubuntu PPA. I use his ZFS PPA on Ubuntu machines.

@habys I'm not a zfs developer, but here's what I think is happening.

The compilation error is caused by this bug. A fix for it was accepted into zfs version 2.1.7. However, this AUR package is still on 2.1.6.

This is just my speculation, but I'm wondering if this package may not have updated to 2.1.7 yet because of this separate severe issue. There is a pull request with people working on a fix, but the bug seems to be still affecting zfs versions starting with 2.1.7.

I think we have to wait for the package maintainer, @jonathon for an answer to this. In the meantime, if you can switch to the LTS kernel, that will solve the compilation error. Or you can switch AUR packages to zfs-dkms-git, just beware of potential crashes if you use zfs send/receive.

Is the compilation error on 6.1 a separate bug? Is it tracked anywhere if so?

As @christian-heusel said, this package (v2.1.6-1) does not build starting with Linux kernel version 6.1.

For anyone that encounters this problem, I was able to install it properly for the current LTS kernel (5.15.85-1-lts), so switching the Linux kernel to LTS is one fix. Just make sure to also install linux-lts-headers and remove linux-headers so that DKMS will compile ZFS for the right kernel version.

If you want to keep the latest kernel version, switching to zfs-dkms-git and zfs-utils-git will fix the compilation errors. Just beware that, as @mabod said, there seems to be a severe issue with zfs send/recieve. I don't think it has been fixed, as of this comment.

For more details, here is the compile error that causes this package's build to fail:

./include/linux/memory_hotplug.h:223:39: error: macro "mutex_init" requires 4 arguments, but only 1 given
  223 |         mutex_init(&pgdat->kswapd_lock);
      |                                       ^
In file included from /var/lib/dkms/zfs/2.1.6/build/module/spl/../os/linux/spl/spl-procfs-list.c:26:
/var/lib/dkms/zfs/2.1.6/build/include/os/linux/spl/sys/mutex.h:99: note: macro "mutex_init" defined here
   99 | #define mutex_init(mp, name, type, ibc)                         \
      |
./include/linux/memory_hotplug.h:223:9: error: ‘mutex_init’ undeclared (first use in this function); did you mean ‘mt_init’?
  223 |         mutex_init(&pgdat->kswapd_lock);
      |         ^~~~~~~~~~
      |         mt_init
./include/linux/memory_hotplug.h:223:9: note: each undeclared identifier is reported only once for each function it appears in
  CC [M]  /var/lib/dkms/zfs/2.1.6/build/module/zcommon/zfs_namecheck.o
  CC [M]  /var/lib/dkms/zfs/2.1.6/build/module/lua/ltablib.o
  CC [M]  /var/lib/dkms/zfs/2.1.6/build/module/zcommon/zfs_prop.o
  CC [M]  /var/lib/dkms/zfs/2.1.6/build/module/zcommon/zpool_prop.o
make[3]: *** [scripts/Makefile.build:250: /var/lib/dkms/zfs/2.1.6/build/module/spl/../os/linux/spl/spl-procfs-list.o] Error 1

I found out this is because in Linux version 6.1, mutex_init() was changed from a macro to a function. This change can be seen here: v6.0.15 v6.1.1.

This has been fixed in ZFS version 2.1.7 by this pull request. By applying the patch described here to this package's version of ZFS (2.1.6), I was able to get the ZFS DKMS module to compile properly. So, it seems to be a simple identifier conflict that is causing this build failure on kernel versions starting with 6.1.

I'm not quite sure what to do with this information, so I'm posting it here in case it is helpful to anyone else.

zfs 2.1.7 has a severe issue with send/receive which can cause coredumps and/or complete zfs freezes:

https://github.com/openzfs/zfs/issues/14252

There is a pull request to fix this: https://github.com/openzfs/zfs/pull/14304

It works well for me.

Just want to confirm that, after updating to 6.1.1 and having a spook this morning, tweaking PKGBUILD to zfs 2.1.7 did the trick on my end as well. (you will need to do the same for zfs-utils and install both at the same time)

PSA: This package does not build the latest kernel (6.1.1-arch1-1)!

==> dkms install --no-depmod zfs/2.1.6 -k 6.1.1-arch1-1
fgrep: warning: fgrep is obsolescent; using grep -F
Error! Bad return status for module build on kernel: 6.1.1-arch1-1 (x86_64)
Consult /var/lib/dkms/zfs/2.1.6/build/make.log for more information.
==> WARNING: `dkms install --no-depmod zfs/2.1.6 -k 6.1.1-arch1-1' exited 10

Manually upgrading the PKGBUILD to use the latest version (at the time its 2.1.7) solved the problem for me :)

Kernel 6.1.1 is out. Will 2.1.7 support it? My system updated to the new kernel and the zfs-dkms modules failed to install properly. I have not rebooted in order to keep my backup array (the only ZFS I have) online.

thanks yurikoles

I see, I tried them too, I will try again soon I find some time

meanwhile I compiled openzfs git 2.1.99 and it installed and works just fine with kernel 6.0.8

Dear Michael,

This AUR page is for zfs-dkms, please report issue with archzfs' zfs-dkms-git to them. I fixed this issue in AUR's zfs-dkms-git, but according to package versions, you are using archzfs' one.