Package Details: zfs-linux-headers 2.3.1_6.13.8.arch1.1-1

Git Clone URL: https://aur.archlinux.org/zfs-linux.git (read-only, click to copy)
Package Base: zfs-linux
Description: Kernel headers for the Zettabyte File System.
Upstream URL: https://openzfs.org/
Keywords: kernel linux openzfs zfs
Licenses: CDDL
Conflicts: spl-dkms, spl-dkms-git, spl-headers, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-headers
Provides: spl-headers, zfs-headers
Submitter: demizer
Maintainer: lightdot
Last Packager: lightdot
Votes: 275
Popularity: 0.87
First Submitted: 2016-04-21 08:45 (UTC)
Last Updated: 2025-03-25 23:55 (UTC)

Pinned Comments

lightdot commented on 2025-02-04 21:19 (UTC) (edited on 2025-03-29 20:47 (UTC) by lightdot)

This package will be kept in sync with the openzfs latest stable release and the kernels officially supported by it.

For the supported kernel versions, refer to the respective openzfs release notes (LINK).

E.g. openzfs 2.3.1 supports kernel versions 4.18 - 6.13. When kernel 6.14 is released for Arch, zfs-linux will not be updated until the openzfs project announces that it's compatible. This will most likely happen with the next openzfs release.

The kernel compatibility of the upcoming openzfs release can be seen in their META file (LINK).

For those wishing to use openzfs with unsupported kernels, do note that this could lead to serious issues, including data loss, even though such a zfs-linux package might build and install cleanly. Have reliable backups and use such a package at your peril.

Please do not mark this package as out of date without checking the kernel compatibility first. Thank you!

Latest Comments

« First ‹ Previous 1 .. 57 58 59 60 61 62 63 64 65 66 67 .. 79 Next › Last »

demizer commented on 2013-02-28 02:53 (UTC)

Ok the packages have been updated. Sorry for the misunderstanding everyone! For future reference, the ZFS packages need to be updated even on kernel updates that only effect the kernel packaging, i.e., pkgrel=1 to pkgrel=2.

ezzetabi commented on 2013-02-27 21:52 (UTC)

Yes, updating now the kernel (even if pacman is configured with demizerone repository) breaks the kernel image.

Achterin commented on 2013-02-27 13:18 (UTC)

hi demizer, i've flagged it out of date because the package has linux 3.7.9-1 as dependency while linux 3.7.9-2 is in the core repository. the same problem exists for your pacman repository. so the problem for me is, that i've installed the new kernel and can't use your repository because, as mentioned before, it reqiures the old package. the only 2 solutions for me would be to downgrade the kernel or use the aur pkg and edit it myself. nevertheless your pkg is out of date because it requires an old kernel pkg. sorry for flagging it without a notice.

demizer commented on 2013-02-27 02:12 (UTC)

I will be fixing the hardcoded depmod verison in spl.install and zfs.install soon, it is on my todo list. Also, anyone that is using the official testing repo (which currently has kernel 3.8) can use the archzfs testing repository with [archzfs] Server = http://demizerone.com/$repo/testing/$arch If this is the reason someone flagged the packages out-of-date, please don't do that. Kernel 3.7.9 is still the current kernel in core. As a general courtesy when using AUR, if you flag any packages out of date, please have leave a note on the reason. In the case of ZFS it can be anything, and I have to work to find the reason and this is annoying.

demizer commented on 2013-02-27 01:59 (UTC)

@timemaster, there are no problems updating the zfs packages from a kernel pkgrel update. I just confirmed on my desktop system.

timemaster commented on 2013-02-27 01:11 (UTC)

I see that there is a new revision of the kernel available (3.7.9-2) "-2" and the kernel upgrade does not include new zfs modules for this -2 revision. Is this a changes that you made after the last comment of lebel ? Is it safe to upgrade that kernel revision but keep the same zfs modules ?

demizer commented on 2013-02-19 08:43 (UTC)

@lebel, most (all?) kernel modules are built to a specific kernel version (see nvidia for example). ZFS is hardcoded by upstream to target the kernel that the headers are pulled from when building the module. The kernel version is hardcoded into the path for the ZFS kernel module i.e., "/usr/lib/modules/3.7.9-1-ARCH/addon/zfs/zfs/zfs.ko". So it must target that kernel version or it will not work. Admittedly I have not tried to route around and find a solution because I don't run into problems performing updates. If you don't/can't use the the pre-built packages I have at http://demizerone.com/archzfs, then you can build in a clean chroot using the tool I use https://github.com/demizer/pbldr, or the tools available https://www.archlinux.org/packages/extra/any/devtools/ package. Once you have built packages, add them to a local repo that you maintain and you will have nice clean updates without having to remove anything. See the repo-add command that comes with pacman, or the makechrootpkg command in devtools. Every package I personally use from AUR are built and added to a local repo. This repo is synced to all of my computers so I only have to build once, and update everywhere. The arch devs made greatly useful tools for package management, but little documentation on how to use them it seems.

<deleted-account> commented on 2013-02-18 17:56 (UTC)

Why the need to follow the exact version of kernel? I don't see any particular reason to do it and it breaks updates as soon as there is a new kernel.