I am aware of the new kernel update. I will update the packages first thing in the morning. Thanks!
Search Criteria
Package Details: zfs-linux-headers 2.3.1_6.13.8.arch1.1-1
Package Actions
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) |
Dependencies (4)
- kmod (kmod-gitAUR)
- linux
- zfs-utilsAUR (zfs-utils-gitAUR, zfs-linux-gitAUR, zfs-utils-staging-gitAUR)
- linux-headers (make)
Required by (0)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 63 64 65 66 67 68 69 70 71 72 73 .. 79 Next › Last »
demizer commented on 2012-11-24 10:20 (UTC)
<deleted-account> commented on 2012-11-18 22:14 (UTC)
Although I don't use this particular PKGBUILD (I build my own), I have no problems running rc12 on my system which is ZFS throughout - root/boot and all, every filesystem is ZFS.
nhelke commented on 2012-11-16 08:32 (UTC)
@proxypoke You are not alone, I too use ZFS on root with Arch. I actually might one day write about my slightly elaborate setup which envolves having /boot also on ZFS so that when things go wrong like they did when I updated to 3.6 and ZFS stoped working, I can simple zfs rollback and everything inluding the kernel and initramfs are rolled back :)
I haven't yet upgraded to rc12, but what seems to be the problem? At what point during the boot does it fail?
demizer commented on 2012-11-16 05:17 (UTC)
The build tool source code is up at http://github.com/demizer/archzfs. I also updated the wiki to reflect the new repository. My next cause is to start looking into systemd support and then DKMS.
proxypoke commented on 2012-11-15 22:14 (UTC)
I will have to add a warning to my earlier enthusiasm:
rc12 doesn't seem to be useable as a root fs - or at least not as far as I have tried. Since I somewhat doubt that there are a lot of (if any) people besides me who try to run Arch on ZFS, so this shouldn't be too important. Just thought I 'd mention it.
senorsmile commented on 2012-11-15 16:00 (UTC)
I think you should add your repository information to the wiki. It would be helpful for newcomers to ZFS without having to search through this page's comments.
demizer commented on 2012-11-15 08:17 (UTC)
@proxypoke, thanks for the notification!
The packages have been updated to 0.6.0-rc12.
I have been working creating a unofficial repository for the Arch ZFS kernel modules. The database and packages are signed with my PGP key, see http://demizerone.com/archzfs/ for more info and instructions on how to add my repository to pacman and add my key (0EE7A125) to your keyring trust.
My signed repository and packages are pre-built _x86_64 packages.
See http://demizerone.com/archzfs/ for more info.
The github master branch for the build tool is not yet up to date. I will have that up and ready sometime tomorrow.
cheers
proxypoke commented on 2012-11-15 03:06 (UTC)
Good news, everyone!
With the latest release of ZFS/SPL on Linux, 0.6.0-rc12 (available as of yesterday), everything builds completely fine on kernel 3.6.5 without the need for any patches.
All PKGBUILDs (spl{,-utils}, zfs{,-utils}) require a quick :%s/rc11/rc12/, generation of new md5sums, and the preempt patch can be removed.
Happy compiling!
demizer commented on 2012-10-29 15:56 (UTC)
Hey everybody, just a quick update. The new build tool I have been working on is now in master, https://github.com/demizer/aur-zfs. With it you can build and package two different groups of packages one for aur and one for split. Again, building the split packages is more efficient. I still have a lot of work to be done, but it is progressing. I will be adding git, dkms, and lts packages after I setup my repo. My next step is to add unofficial repository support to my build tool so I can easily setup a repo with precompiled binaries. I will be hosting the repo on my website at http://demizerone.com/archzfs. Initially it will only be for 64bit code since the ZOL FAQ states that ZOL is very unstable with 32bit code due to memory management differences in Solaris and Linux. I will notify you all in the future when that is ready to go.
@MilanKnizek, Yes updating is a pain. ZFS itself is hard-coded to linux versions at build time. The ZFS build tool puts the modules in "/usr/lib/modules/3.5.6-1-ARCH/addon/zfs/", and this the primary reason it has to be rebuilt each upgrade, even minor point releases. Nvidia for example puts their module in "/usr/lib/modules/extramodules-3.5-ARCH/", so minor point releases are still good and the nvidia package doesn't need to be re-installed. A possible reason for ZOL to be hard-coded like this because ZOL is still technically very beta code.
I do have a question for the community, does anyone use ZFS on a 32bit system?
Thanks!
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!