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)

@fryfrog

Thanks for the link. Basically they fixed a NULL referencing pointer-to-a-struct by actual defining the struct and giving that to the pointer (if you have ever learned some C programming you'll probably know what I mean).

I really like their statement "Ah yes, the fun of compilers getting smarter and noticing when we did something foolish.", because that's so true.

And these things are indeed a good thing, it helps getting a thing like ZFS getting more safe and stable.

Not being able to build something has often very good reasons.

There are a number of commits in github issue #13463, hopefully they'll make a new release soon that supports it.

Looks like 5.18 isn't supported yet so I had to downgrade my kernel in order to not break my system outright.

==> dkms install --no-depmod zfs/2.1.4 -k 5.18.0-zen1-1-zen
Deprecated feature: REMAKE_INITRD
configure: error: 
        *** None of the expected "blk_queue_discard" interfaces were detected.
        *** This may be because your kernel version is newer than what is
        *** supported, or you are using a patched custom kernel with
        *** incompatible modifications.
        ***
        *** ZFS Version: zfs-2.1.4-1
        *** Compatible Kernels: 3.10 - 5.17

Error! Bad return status for module build on kernel: 5.18.0-zen1-1-zen (x86_64)
Consult /var/lib/dkms/zfs/2.1.4/build/make.log for more information.
==> WARNING: `dkms install --no-depmod zfs/2.1.4 -k 5.18.0-zen1-1-zen' exited 10

@daemonjax - https://unix.stackexchange.com/a/364920/93470 (add unknown public key for makepkg)

building the snapshot from this page works ok

==> Leaving fakeroot environment.
==> Finished making: zfs-dkms 2.1.4-1 (Tue 26 Apr 2022 21:59:20 BST)

I had trouble making this package...

ERROR: 0001-only-build-the-module-in-dkms.conf.patch was not found in the build directory and is not a URL.

So I get the patch file from the Sources list on this page, and I still can't build it...

0001-only-build-the-module-in-dkms.conf.patch ... FAILED

ERROR: One or more files did not pass the validity check!

Then I figured if I just cut out some of the junk in the patch file (it looks like a simple copy-paste of an entire email someone got), then it would accept the patch... nope (but I kept my changes). So, then I figured out I need to run makepkg -g >> PKGBUILD to update the hash for the patchfile. Ok... I do that, then I get a new error:

Verifying source file signatures with gpg... zfs-2.1.4.tar.gz ... FAILED (unknown public key 6AD860EED4598027) ERROR: One or more PGP signatures could not be verified!

So, then I figure out I have to add that gpg key to my key ring blindly (which defeats the purpose of using gpg, but whatever -- who is Tony Hutter and why should I trust him? Whose gpg key should I expect? No idea, but I have no choice if I want to continue EDIT: There IS a line about him in PKGBUILD file, so my bad) using the command as the non-root user I'm using the build the package:

gpg --receive-keys 6AD860EED4598027

And now finally I can build the package.

Thoughts:
1) The patch is required to make the package, and it's from the year 2018... so it should probably just be included at this point, right? Can't it be set up to auto-download the file at least? 2) Why I should dis/trust Tony Hutter's GPG key for the zfs-2.1.4.tar.gz file should probably be included in the PKGBUILD file. EDIT: There is a comment line in the PKGBUILD about trusting Tony Hutter, so that's fine. I didn't see it while using a standard tty terminal.

zfs-dkms 2.1.4-1 all ok with 5.15.27.hardened1-1

I had to clean up some old config with rm -rf /var/lib/dkms/zfs/2.1.2 to fix Unable to build an empty module

@jonathon Correct, also with archzfs now. Tried it again. Issues solved with 5.15.23-2-lts.

If you're having an issue at this point it's because you have a partial upgrade. All kernels have been built with GCC 11.2.0, and DKMS will rebuild the ZFS module accordingly.

Currently I am using the archzfs version (but also keeping a copy of this AUR one in a folder so that I can switch things easily), but yesterday the update to LTS kernel 5.15.23-1-lts gave me that exact same ZFS build error, about that it could not build an empty module (I verified it by manually running the dkms build command again to see it's output). Luckily on the regular kernel 5.16.9-arch1-1 it did still build fine (with that same archzfs version) in my case. So with having both kernels installed on my system it wasn't a direct issue. But if it's also gonna happen with the regular kernel.