Package Details: zfs-linux 2.2.7_6.12.6.arch1.1-1

Git Clone URL: https://aur.archlinux.org/zfs-linux.git (read-only, click to copy)
Package Base: zfs-linux
Description: Kernel modules for the Zettabyte File System.
Upstream URL: https://openzfs.org/
Keywords: kernel linux openzfs zfs
Licenses: CDDL
Groups: archzfs-linux
Conflicts: spl-dkms, spl-dkms-git, spl-linux, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-linux-git, zfs-linux-rc
Provides: spl, zfs
Replaces: spl-linux
Submitter: demizer
Maintainer: lightdot
Last Packager: lightdot
Votes: 273
Popularity: 2.20
First Submitted: 2016-04-21 08:45 (UTC)
Last Updated: 2024-12-23 05:08 (UTC)

Required by (19)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 79 Next › Last »

minextu commented on 2020-01-18 20:21 (UTC)

@CoolGenie zfs-linux is in sync with arch core right now. The error you are getting happens because you have an old version of zfs-linux installed. So you need to remove the old one first before updating.

If this is too much effort, you can also use the archzfs repository (https://github.com/archzfs/archzfs/wiki) or zfs-dkms.

PS: There is a variable called _kernelver in the PKGBUILD, which you can adjust and rebuild if the aur version is out of date.

dmp1ce commented on 2020-01-18 19:43 (UTC)

Right! In your account settings "Notify of package updates" needs to be checked too. It was unchecked for me. Now I'll probably get way more emails than I want!

torben commented on 2020-01-18 19:36 (UTC)

qdmp1ce: Just klick on "Enable notifications" in the "Package Actions" box on the top right. IIRC you have to create an account to do so.

dmp1ce commented on 2020-01-18 15:03 (UTC)

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

torben commented on 2020-01-18 10:36 (UTC)

@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).

CoolGenie commented on 2020-01-18 05:35 (UTC)

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 :)

WhiteKnight commented on 2019-12-13 09:08 (UTC)

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

CoolGenie commented on 2019-12-13 06:58 (UTC)

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

Hetsh commented on 2019-10-19 08:21 (UTC)

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?

minextu commented on 2019-09-21 23:09 (UTC)

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