Package Details: zfs-linux-lts 2.4.1_6.18.16.1-1

Git Clone URL: https://aur.archlinux.org/zfs-linux-lts.git (read-only, click to copy)
Package Base: zfs-linux-lts
Description: Kernel modules for the Zettabyte File System.
Upstream URL: https://openzfs.org/
Licenses: CDDL-1.0
Groups: archzfs-linux-lts
Conflicts: spl-dkms, spl-dkms-git, spl-linux-lts, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-linux-lts-git, zfs-linux-lts-rc
Provides: spl, zfs
Replaces: spl-linux-lts
Submitter: demizer
Maintainer: gromit
Last Packager: gromit
Votes: 83
Popularity: 0.033073
First Submitted: 2016-04-24 19:05 (UTC)
Last Updated: 2026-03-04 20:36 (UTC)

Required by (19)

Sources (1)

Latest Comments

1 2 3 4 5 6 .. 15 Next › Last »

air-g4p commented on 2026-03-06 06:52 (UTC)

@gromit - thanks for updating to support:

zfs-linux-lts-2.4.1_6.18.16.1-1-x86_64.pkg.tar.zst

To others:

If you haven't run into this already, ensure you've built the updated zfs-utils package, which provides the required 2.4.1-1, first.

Also for the updated zfs-utils package, you may need to import a new gpg key with:

gpg --recv-keys 6AD860EED4598027

Cheers

lightdot commented on 2026-01-10 05:02 (UTC) (edited on 2026-01-10 05:05 (UTC) by lightdot)

If I exclude it, I don't know if the unupdated version of ZFS will work with the new kernel, but also, I don't know if even excluding ZFS will let me upgrade the linux kernel, since that would break the dependency of the current ZFS.

The linux-lts and zfs-linux-lts packages indeed can't be updated separately, only both together.

Exclude the zfs-linux-lts only when it requires the newer linux-lts that is still in testing. This enables you to update the rest of the system while keeping the existing linux-lts and zfs-linux-lts until the next upgrade.

I rather not do partial upgrades since that is like the first thing the Arch Wiki tells you not to do.

That is indeed a very good and important advice that one should generally follow, but keeping an older kernel with the corresponding ZFS packages, while updating the rest of the system, is safe.

In most cases, it won't even be a partial upgrade, since the newer linux-lts will still be in testing, so not released yet.

jcruz commented on 2026-01-09 23:03 (UTC)

It is a chicken and egg problem, If I exclude it, I don't know if the unupdated version of ZFS will work with the new kernel, but also, I don't know if even excluding ZFS will let me upgrade the linux kernel, since that would break the dependency of the current ZFS.

I rather not do partial upgrades since that is like the first thing the Arch Wiki tells you not to do. And considering that all this happens because of following testing instead of stable, which could be a simple fix of just delaying the release a couple days.

Maybe we can have a zfs-linux-lts-testing package that follows the testing channel and leave this following the stable channel? I don't know if it is too much extra work, which I would understand if gromit does not want to do.

lightdot commented on 2026-01-09 10:30 (UTC)

@jcruz, can't you just temporarily exclude the zfs-linux-lts package from the upgrade?

I'm not familiar with yay but I'm sure it's possible to do so, either in its configuration or with a command line switch.

If you temporarily exclude the zfs-linux-lts package, this entire convoluted upgrade procedure you've described becomes redundant.

jcruz commented on 2026-01-08 18:04 (UTC)

@gromit. Thanks for maintaining this package! I see that I am not the only one that gets their updates blocked when there is a new version in testing, but not in stable. Is there an equivalent for testing in the AUR so that you can hold onto updating the stable AUR version into the new kernel hits stable?

I use yay as my AUR helper so every time I have to update my system and this happens, what I normally do is export my ZFS pool, uninstall ZFS and zfs utils, do the regular yay update, reinstall zfs-utils and finally download this PKGBUILD and modify it to point to the previous version for the kernel in stable and build manually instead of with yay. Only then I can import my pool and reboot. I do my updates on a monthly schedule that is hard for me to move, so I would have to wait another month to try again if I didn't do the above steps.

I assume you follow testing precisely to test the new ZFS version works correctly, but is there a way to delay publishing the new PKGBUILD until the kernel hits stable? I understand if there is reason you can't and I can continue doing my ZFS update manually if that is the case, just thought of asking :)

Thanks again for your work!

jaredledvina commented on 2026-01-08 14:12 (UTC)

Ah! Okay, thanks I see https://archlinux.org/packages/core-testing/x86_64/linux-lts/ now. Sounds good, I'll hold off until they promote the package out of testing. Thanks again for maintaining this!

gromit commented on 2026-01-07 23:35 (UTC)

Hey @jaredledvina, see my answer in https://aur.archlinux.org/pkgbase/zfs-linux-lts#comment-1050726

jaredledvina commented on 2026-01-06 18:20 (UTC)

@gromit - Thanks so much for maintaining this! I see your commit two days ago https://aur.archlinux.org/cgit/aur.git/commit/PKGBUILD?h=zfs-linux-lts&id=218b7190ee2fd90525ae26a29b334c16ce5af12f bumped the kernel requirement to 6.12.63-2. but I don't see the -2 version here https://archlinux.org/packages/core/x86_64/linux-lts/. As such, this fails currently with: could not find all required packages: linux-lts-headers =6.12.63-2

Any thoughts?

air-g4p commented on 2025-12-19 06:26 (UTC)

@gromit - thanks for updating to support:

zfs-linux-lts-2.4.0_6.12.63.1-1-x86_64.pkg.tar.zst

To others:

If you haven't run into this already, ensure you've built the updated zfs-utils package, which provides the required 2.4.0-1, first.

Cheers

1 2 3 4 5 6 .. 15 Next › Last »