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.92
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 .. 21 22 23 24 25 26 27 28 29 30 31 .. 79 Next › Last »

onedr0p commented on 2015-06-08 05:12 (UTC)

Whoops, accidentally hit submit $ yaourt -S zfs-git error: failed to prepare transaction (could not satisfy dependencies) :: spl-git: requires linux=4.0.4-2 :: zfs-git: requires linux=4.0.4-2 ==> Restart building spl-git ? [y/N] ==> -------------------------------- ==> $ uname -a Linux serenity 4.0.4-2-ARCH #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015 x86_64 GNU/Linux As you can see it's stuck in a failed loop when trying to update one or the other.

onedr0p commented on 2015-06-08 05:08 (UTC)

@Ibex, I understand that, however, I cannot upgrade the linux package and (spl-git or zfs-git) because they complain about each other being a dependancy. # pacman -S Linux error: failed to prepare transaction (could not satisfy dependencies) :: spl-git: requires linux=4.0.4-2 :: zfs-git: requires linux=4.0.4-2 $ yaourt -S zfs-git

khenderick commented on 2015-05-22 16:37 (UTC)

That's normal sometimes. It means the kernel was updated on the main repo's, but that this package wasn't yet updated. The best thing to do is flag this package out-of-date and wait for the package to get updated. Demizer is usually incredibly quick :).

onedr0p commented on 2015-05-22 15:46 (UTC)

Hello, I get an error trying to update. Please help, thanks. $ uname -a Linux serenity 4.0.2-1-ARCH #1 SMP PREEMPT Thu May 7 06:47:54 CEST 2015 x86_64 GNU/Linux # pacman -Syu :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: spl-git: requires linux=4.0.2-1 :: zfs-git: requires linux=4.0.2-1

senorsmile commented on 2015-05-13 16:35 (UTC)

Definitely local network issue. Seems to be wifi related... yay, wifi troubleshooting :)

demizer commented on 2015-05-13 16:33 (UTC)

@senorsmile, seems like a local network issue. You could run curl to get a better idea of timings: curl -v -s http://demizerone.com/demz-repo-core/x86_64/demz-repo-core.db -w "Total Time: %{time_total}\nName lookup: %{time_namelookup}\nStart transfer: %{time_starttransfer}\n" -o /dev/null Also checkout mtr https://www.linode.com/docs/networking/diagnostics/diagnosing-network-issues-with-mtr

senorsmile commented on 2015-05-12 01:07 (UTC)

@demizer still erring out for me: error: failed retrieving file 'demz-repo-core.db' from demizerone.com : Resolving timed out after 10518 milliseconds error: failed to update demz-repo-core (download library error) with my pacman.conf having this at the end(same as I've had for a long time): [demz-repo-core] SigLevel = Never Server = http://demizerone.com/$repo/$arch I AM able to download the db file manually: wget http://demizerone.com/demz-repo-core/x86_64/demz-repo-core.db --2015-05-11 17:58:20-- http://demizerone.com/demz-repo-core/x86_64/demz-repo-core.db Resolving demizerone.com (demizerone.com)... 184.172.15.230 Connecting to demizerone.com (demizerone.com)|184.172.15.230|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 7836 (7.7K) [text/plain] Saving to: ‘demz-repo-core.db’ demz-repo-core.db 100%[=====================================>] 7.65K --.-KB/s in 0.07s 2015-05-11 17:58:36 (107 KB/s) - ‘demz-repo-core.db’ saved [7836/7836] file demz-repo-core.db demz-repo-core.db: XZ compressed data I wget'd the file again with 'time', and saw it take about 15 seconds to download the file. Presumably, pacman is timing out, and since there are no more mirrors it just fails. I increased the connection timeout in pacman.conf and voila, problem solved. This must be a weird wifi issue that's only presenting itself with this custom repo.

billybigrigger commented on 2015-05-10 11:01 (UTC)

zfs-git builds fine if your NOT using llvm/clang

kerberizer commented on 2015-05-08 19:06 (UTC)

Folks, in an effort to more efficiently maintain the packages, the GitHub repo has been moved to a new, dedicated "archzfs" organization. The main code repo is now here: https://github.com/archzfs/archzfs Please report problems and suggest improvements here: https://github.com/archzfs/archzfs/issues If you have patches, please open pull requests here: https://github.com/archzfs/archzfs/pulls Once again, your active help and support will be much appreciated. :)

demizer commented on 2015-05-08 16:06 (UTC)

@kerberizer, thanks! This is exactly my sentiments. @billy, I am on the email list for new ZOL versions, but I guess the notifications don't include minor point releases. 0.6.4 -> 0.6.4.1, so I missed it completely. Also, my automated version checking scripts did not catch it because I had no idea the point releases went to version numbers that low. I don't have time to check the ZOL website every day, but if you would like to join the project and help out by making sure the version is current, from all sources, please step up. Also, to the community as a whole, if the version is out-of-date, just flag the package out-of-date.