Arch Linux User Repository

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.

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)

I cannot install version 0.8.3 on a system running the 5.4.39-1-lts kernel (latest lts kernel as of today).

The initial build process concludes successfully (but see below), then dkms fails with this message:

==> dkms install zfs/0.8.3 -k 5.4.39-1-lts
configure: error: 
        *** Unable to build an empty module.

Error! Bad return status for module build on kernel: 5.4.39-1-lts (x86_64)
Consult /var/lib/dkms/zfs/0.8.3/build/make.log for more information.

The log is not very helpful:

DKMS make.log for zfs-0.8.3 for kernel 5.4.39-1-lts (x86_64)
Mon 11 May 2020 12:45:19 PM CDT
make: Entering directory '/var/lib/dkms/zfs/0.8.3/build/module'
make: *** No targets specified and no makefile found.  Stop.
make: Leaving directory '/var/lib/dkms/zfs/0.8.3/build/module'
/var/lib/dkms/zfs/0.8.3/build/make.log (END)

Perhaps something went wrong earlier in the build process?

(please use markdown to post command output)

"It broke" isn't very useful debug info. If you cannot find the make.log, try rerunning the dkms install ... command in question manually, since it is only the pacman hook that hides the output.

I just updated to 5.6.8 and the kernel modules built fine.

The only thing I did different is, I was on 5.6.8 briefly and then downgraded back to 5.6.7 (testing dracut) a couple of days ago. I have a make.log if anyone might find it interesting.

I'm getting a build error on the latest system update:

==> dkms install zfs/0.8.3 -k 5.6.8-arch1-1
Error! Bad return status for module build on kernel: 5.6.8-arch1-1 (x86_64)
Consult /var/lib/dkms/zfs/0.8.3/build/make.log for more information.

Any suggestions on how to proceed?

The log file does not seem to exist, BTW.

Cheers and good to know about LTS. On a test rig, I released gcc and gcc-libs, did a full update but no newer versions were installed. I took the plunge and upgraded the kernel, rebuilt zfs-dkms with that 5.6 kernel running, rebooted, did a modprobe zfs and all was well. Many thanks to all for the assist.

I think you want to be running the same gcc/glibc that your kernel was built with. Normally, that just means keeping current. I would release gcc and gcc-libs and update. Then update your kernel. Then if zfs-dkms isn't latest, update and let it build for your newly updated kernel.

FWIW, I have both linux and linux-lts installed and my archzfs/zfs-dkms builds just fine.

I get adding the key, really I do :-) It's just that during my testing, on a 5.5 kernel I'm using, I cannot build this with the 'horrible but quick test hack' makepkg --skippgpcheck. On a 5.6 kernel, it builds just fine. This of course might all be me, so I wanted to highlight that when we had the zfs issues with moving to kernel 5.5 from 5.4, I know we had to keep the gcc versions in line with the kernel. Since the 5.6 issue was raised, I've had the follow in my pacman.conf

IgnorePkg=linux linux-headers gcc gcc-libs

As a workaround, I was considering removing zfs-dkms from my 5.5 main desktop as I can just about manage with it in the short term. Then upgrading to 5.6 and finally popping zfs-dkms back in again. I'd prefer to be able to upgrade other, older 5.5 kernel machines without doing those steps, but if that's the best way forward to upgrade, I'm happy to do that. Any thoughts appreciated.

Thanks for the help, in my case I get:

==> 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!

If I use --skippgpcheck, the resulting build gives:

libtoolize: copying file 'config/lt~obsolete.m4'
configure:24227: error: possibly undefined macro: 
ZFS_AC_KERNEL_SRC_BLKG_TRYGET
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure:41387: error: possibly undefined macro: ZFS_AC_KERNEL_BLKG_TRYGET
autoreconf: /usr/bin/autoconf failed with exit status: 1
==> ERROR: A failure occurred in prepare().
Aborting...

This is with 5.5.13-arch2-1 that is up to date.