Arch Linux User Repository

OpenZFS currently supports Linux kernel versions 4.18 - 6.19, 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 removed the repo definition and it looks like yay is finding 2.4.0. Thanks I will try that. My fault for trusting an AI answer.

@malibu: zfs-dkms 2.4.0 should automatically be installed when you do a "yay -S zfs-dkms zfs-utils". You seem to have an old package database. A simple "yay -Syyu" should to the trick. This is all in the AUR. You do not need https://archzfs.com .

How do I switch my package source? I installed native arch, then installed yay, then did yay -S zfs-dkms zfs-utils. Should that not give me the latest version? Admittedly I did try the zfs repository first, does it have the wrong version? Would yay pull the package from the repository instead of from AUR? This is the repo I have configured: https://archzfs.com/$repo/$arch.

@malibu Please update your package source, the current version is 2.4.0, not 2.3.3.

I have been using zfs-dkms for some time, but recently I had to rebuild my system and I cannot build zfs-dkms. During the build I get a message "WARNING: `dkms install --no-depmod zfs/2.3.3 -k 6.18.5-arch1-1' exited 1"

If I try modprobe status I get: modprobe: FATAL: Module status not found in directory /lib/modules/6.18.5-arch1-1

I get a similar result whether I install zfs-dkms from the zfs repository or from AUR. This is a basic arch install.

Can't build against linux-hardened, even though 6.16 is supported. Something about CONFIG_MODULES being disabled even though it is enabled in that kernel. Any idea?

checking whether CONFIG_MODULES is defined... no
configure: error: 
                *** This kernel does not include the required loadable module
                *** support!
                ***
                *** To build OpenZFS as a loadable Linux kernel module
                *** enable loadable module support by setting
                *** `CONFIG_MODULES=y` in the kernel configuration and run
                *** `make modules_prepare` in the Linux source tree.
                ***
                *** If you don't intend to enable loadable kernel module
                *** support, please compile OpenZFS as a Linux kernel built-in.
                ***
                *** Prepare the Linux source tree by running `make prepare`,
                *** use the OpenZFS `--enable-linux-builtin` configure option,
                *** copy the OpenZFS sources into the Linux source tree using
                *** `./copy-builtin <linux source directory>`,
                *** set `CONFIG_ZFS=y` in the kernel configuration and compile
                *** kernel as usual.

supported kernel version has been updated in the 2.3.4 release to 4.18 - 6.16 https://github.com/openzfs/zfs/blob/zfs-2.3.4/META

From comment by @dkadioglu in aur/vmware-workstation:

Maybe you can add one small fix for a deprecated dkms feature, according to https://github.com/dell/dkms/pull/514#issuecomment-2821267860

Replace CLEAN="make clean" with CLEAN=true in scripts/dkms.mkconf.

Thanks!

Sorry, I didn't realize I was only reading the pinned comments a while ago. Also yeah, I didn't know it was a staging branch it was building. I do realize they do not have a whole lot of testing, but I've been through it before.

I also keep relatively well backed up. I wish I'd known about the staging branch the last time I was using ZFS on Arch, as then, I was using the dang -git package every major kernel version bump. I also didn't use a chroot based building process, so upgrading was painful.

@kode54 to be completely fair 99% of the times there is absolutely no need to apply any patches on top of the staging branch (the branch where the fixes for the next minor release end up piling) to make it work with latest upstream kernel. I had to backport compatibility fixes mainly during the transitioning period to the next major release (2.2.x -> 2.3.x).

I would not call zfs-dkms-staging-git inherently safe (there is definitely a risk of data loss due to how little testing newer kernel versions received) but it's not that bad either (or at least I trust it with my main laptop's fs). For sure it's much, MUCH safer than using zfs-dkms-git as LUKS2 users can testify.