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)

Hey there, right now it is required to apply this patch to get it to compile 0.7.12 under kernel 4.20: https://github.com/zfsonlinux/zfs/pull/8227.diff

Here is a one-liner to apply the patch:

curl -sSL https://github.com/zfsonlinux/zfs/pull/8227.diff | sudo patch -p1 -d /usr/src/zfs-0.7.12 && sudo dkms autoinstall

@eschwartz: "Are you using some alternative packages that do not come from the AUR?" No.

I reinstalled spl-dkms, zfs-dkms and zfs-utils and then I could remove spl-utils. Thanks again!

Are you using some alternative packages that do not come from the AUR?

The spl-utils package contains some command-line tools used for running the spl module testsuite in case you are a zfsonlinux developer, whereas the zfs-utils package contains command-line tools which are actually useful to end-users in order to administrate a zfs filesystem.

As a result, I've dropped the spl-utils package altogether. If anyone wants to create a package installing these tools, they can... But you don't need it as a dependency of spl-dkms. However: you somehow have an spl-dkms package that does depend on it. It's possible that you've manually bumped the pkgver of the old package before it was updated.

Uninstalling them all and reinstalling from the AUR would fix it, but only because of the reinstall. You should just as easily be able to reinstall them without uninstalling first.

• After reinstalling spl-dkms from the AUR, it will no longer depend on the missing spl-utils package and you can safely remove it.
• If you have not rebuilt zfs-utils or zfs-dkms since I took over maintenance, you should rebuild those as well, for example in order to obtain the initcpio hook updates.

@eschwartz: thanks!

I've updated to the latest version but now when I try to update I see this:

$ aurman -Su --always_edit --show_changes --solution_way                                   
:: Starting full system upgrade...
there is nothing to do

~~ initializing aurman...
~~ the following packages are neither in known repos nor in the aur
:: spl-utils-0.7.11-1
~~ calculating solutions...
:: nothing to do... everything is up to date

and when I try to remove spl-utils:

$ aurman -R spl-utils         
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: spl-dkms: removing spl-utils breaks dependency 'spl-utils=0.7.11-1'

or with the dependencies:

$ aurman -Rc spl-utils                                          
checking dependencies...

Packages (4) spl-dkms-0.7.11-1  zfs-dkms-0.7.11-2  znapzend-0.19.0-1  spl-utils-0.7.11-1

Total Removed Size:  14.46 MiB

:: Do you want to remove these packages? [Y/n] n

Should I remove them all and reinstall zfs-dkms? Or what else can I do to fix it?

To solve the "Unknown public key" issue, just add the PGP keys of the ZFS on Linux maintainers like described here: https://github.com/zfsonlinux/zfs/wiki/Signing-Keys.

If you get the message 'Unknown public key 6AD860EED4598027' when trying to install this, see here: https://wiki.archlinux.org/index.php/Makepkg#Signature_checking . You need to import the mentioned key first. ( A (not very satisfying and usually a bad idea) workaround is to remove the '?signed' at the end of the repo URL. )

I don't understand this thing at all, as splat.ko is provided by spl-dkms alongside the spl module itself, but splat is also a binary which interacts with the kernel module of the same name.

And splat is a testsuite, it certainly doesn't need to be in the initcpio. The error message should be harmless-ish, mkinitcpio is just warning you that it couldn't find one of the files and therefore if your boot process actually relies on the file in question, then it will have errors.

But, this should really be removed from the install hook altogether, along with a couple python scripts that I literally don't comprehend their presence.

There is still one issue. I have a machine with root on ZFS. With the current packages, I cannot build the initial ramdisk, because the module splat, formerly provided by spl-utils, is missing.

~ [1]$ sudo mkinitcpio -p linux-zen
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 4.17.14-zen1-1-zen
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
  -> Running build hook: [zfs]
==> ERROR: file not found: `splat'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-zen.img
==> WARNING: errors were encountered during the build. The image may not be complete.

The provides has been re-added, as also mentioned in the zfs-utils comments.

I'm not going to remove security checks though, especially not for a high-profile package like a kernel module. If following the instructions from https://wiki.archlinux.org/index.php/Makepkg#Signature_checking is a show-stopper for people, then so be it. Hopefully this won't be a big problem for people, though, especially as zfs is a fairly technical thing to use to begin with.

Hi,

in the latest version the "provides=("zfs")" was deleted and so I wasn't able to update the packages since the zfs-snap-manager has a dependency on zfs.

An addition I had to add the pgp keys like described here: https://github.com/zfsonlinux/zfs/wiki/Signing-Keys. This might be a stopper for a lot of people.

Best regards, othiman