Arch Linux User Repository

@torben, how do you subscribe to zfs-linux updates?

@CoolGenie: The problem here is, that current Arch is a moving target, that's difficult to follow at times. For me personally I've tried a few options you might try as well:

a) Switch to the ZFS Kernel LFS branch (zfs-linux-lts), this is what I use. You'll less frequent kernel updates, I haven't had much of a problem with the LTS branch and ZFS since I switched to it. Works well and using the LTS kernel might actually be preferrably on servers. On cutting edge desktops/notebooks this might not be an option though; but since ZFS is more of a server technology, this shouldn't be that much of a point. I'd recommend this approach.

b) Subscribe to zfs-linux package updates and do your pacman update right after the ZFS upgrade is out. This worked for me most of the time I was quick enough, I just didn't see any advantage over the LTS branch so I stopped doing so.

c) Use the DKMS version, which custom-builds the modules on your box, I've tried this once but didn't get it to run, however, as far as I understand this should work in principle (probably I missed something when I tried it).

I understand the pains of open source development and much appreciate the work everyone is doing at Arch, however I've been unable to upgrade for over a month now with the error:

error: failed to prepare transaction (could not satisfy dependencies) :: installing linux (5.4.12.arch1-1) breaks dependency 'linux=5.4.1.arch1-1' required by zfs-linux

I think it's important to follow the upstream kernel because this blocks any security updates from the upstream Arch. And, when having migrated important data to ZFS, I can't just uninstall zfs-linux :)

@CoolGenie you need to wait until the zfs-linux package gets updated with the current kernel as dependency.

Anyone know why I'm getting: installing linux (5.4.2.arch1-1) breaks dependency 'linux=5.4.1.arch1-1' required by zfs-linux

Root on encrypted ZFS can be decrypted during boot when adding "zfs load-key -a" around line 54 in the mkinitcpio hook "/usr/lib/initcpio/hooks/zfs". @minextu maybe consider as permanent patch?

@dawnofman It didn't break anything but it's fixed now, thanks!

dunno whether this is relevant or not but: --libexecdir=/usr/lib/zfs-${zfsver} should be: --libexecdir=/usr/lib/zfs-${_zfsver} it is not the same variable; it is being built as: --libexecdir='/usr/lib/zfs-'

It's likely to be part of 0.8.2, but could e5db31349484e5e859c7a942eb15b98d68ce5b4d be cherry-picked to be included in this package? It restores SIMD compatibility on the latest 4.14.x/4.19.x/5.x kernels. Debian is already including this patch in their 0.8.1 package :)

@andybz zfs-utils and zfs-dkms have a different maintainer and I don't have access to update.

You can use https://github.com/archzfs/zfs-dkms and https://github.com/archzfs/zfs-utils in the meantime or update using the archzfs repo (http://archzfs.com)