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)

@sausix - I run linux-lts & linux-hardened (built with arch-sign-modules so the zfs modules are signed) - I find that linux-lts always builds & never needs a rebuild when gcc changes to a new major version.

As I build my own kernels & add them to IgnorePkg in /etc/pacman.conf, needing to stick on a minor version of my preferred (non LTS) kernel is not an issue. This has worked well for at least 5 years. When zfs-dkms changes, the first thing I check is the zfs release on Github - this shows the supported kernel versions.

@sausix: zfs ist not in "danger zone" ;-) What you see here is the typical scenario for zfs to catch up with the changes in the newest kernel. This is normal and can take a while. If you use zfs you should consider to use an LTS kernel.

==> dkms install --no-depmod zfs/2.2.4 -k 6.9.5-arch1-1
configure: error: 
        *** Cannot build against kernel version 6.9.5-arch1-1.
        *** The maximum supported kernel version is 6.8.

So ZFS is in danger zone because of the developers can't follow the Kernel's release frequency. Am I correct? Should at least be pinned here.

@FrederickZh Thanks for the accurate analysis. I've appended ?full_index=1 to the source URL for that patch.

Folks, the last commit here in this package was committed on 2 May. The commit that added 2b481b5477d3a95d0eab723c6639f7114e146ae1.patch was even older.

What happened was that https://github.com/openzfs/zfs/commit/2b481b5477d3a95d0eab723c6639f7114e146ae1.patch started returning index hashes with 11 characters, while it used to return 12 characters, e.g. index 000000000000..ffb4997e8b14 instead of index 00000000000..ffb4997e8b1.

To avoid such issues, it's better to use https://github.com/openzfs/zfs/commit/2b481b5477d3a95d0eab723c6639f7114e146ae1.patch?full_index=1. It has nothing to do with not running updpkgsums.

I use zfs-dkms from EndeavourOS repos

# /etc/pacman.conf
[endeavouros]
SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist

@kstolp - for pkgsums I use a BASH alias: alias pkgsums='updpkgsums && makepkg --printsrcinfo > .SRCINFO' & got into the habit of makepkg -sf before I push changes (after I previously pushed a mismatch)

Patch file didn't pass validity check.

aur@archiso $ aur sync --no-view zfs-dkms zfs-utils
==> Using [aur] repository
  -> zfs-dkms (none) -> 2.2.4-1
  -> zfs-utils (none) -> 2.2.4-1
==> Retrieving package files
fetch: zfs-utils: already up to date
fetch: zfs-dkms: already up to date
==> Making package: zfs-dkms 2.2.4-1 (Sat 18 May 2024 07:18:03 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found zfs-2.2.4.tar.gz
  -> Found zfs-2.2.4.tar.gz.asc
  -> Found 2b481b5477d3a95d0eab723c6639f7114e146ae1.patch
  -> Found 0001-only-build-the-module-in-dkms.conf.patch
==> Validating source files with sha256sums...
    zfs-2.2.4.tar.gz ... Passed
    zfs-2.2.4.tar.gz.asc ... Skipped
    2b481b5477d3a95d0eab723c6639f7114e146ae1.patch ... FAILED
    0001-only-build-the-module-in-dkms.conf.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

Just tried to install 2.2.4-1 version and got this:

==> Validating source files with sha256sums...
    zfs-2.2.4.tar.gz ... Passed
    zfs-2.2.4.tar.gz.asc ... Skipped
    2b481b5477d3a95d0eab723c6639f7114e146ae1.patch ... FAILED
    0001-only-build-the-module-in-dkms.conf.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

Could someone please fix the hash of that patch?

kernel 6.8 builds ok with zfs-dkms-2.2.4:

( 4/11) Install DKMS modules
==> dkms install --no-depmod lkrg/0.9.8 -k 6.8.9-hardened1-2-hardened
==> dkms install --no-depmod zfs/2.2.4 -k 6.8.9-hardened1-2-hardened
==> dkms install --no-depmod nvidia/550.78 -k 6.8.9-hardened1-2-hardened
==> depmod 6.8.9-hardened1-2-hardened

on arch-sign-modules I needed to recompile the kernel as gcc-libs just changed to v14