Arch Linux User Repository

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!

[UPDATED after verification] @lebel: you can recompile all the zfs/spl packages before reboot - it will find the new kernel headers despite that an old kernel is still used (in memory). If the install script of zfs/spl produces a warning, you might need to run `depmod $NEW_KERNEL_VERSION` manually.

@lebel: you can recompile all the zfs packages before reboot. Though, the install scripts will produce an error - depmod will fail and after reboot the new kernel will not find zfs and spl modules. Easy solution is to run depmod against the new kernel before reboot manually. (I think -k switch is the one. Check the man page.)

Well, seeing that I'll lose access to my zfs drives after the first reboot, I was looking into ways in upgrading zfs packages even while still running 3.7.6.

@lebel Two options: 1.) Exclude the Kernel from updates # pacman -Syu --ignore=linux,linux-headers,linux-api-headers 2.) Remove zfs $ yaourt -R zfs zfs-utils spl spl-utils Update # pacman -Syu Reboot Reinstall zfs $ yaourt -S zfs Make sure that a zfs update for the new kernel is available before updating the kernel

I guess it is normal, but a little bit awkward right now. I'm running linux-3.7.6 with the associated zfs and now that a new kernel version is out, it is impossible for me to upgrade. It says: error: failed to prepare transaction (could not satisfy dependencies) :: Starting full system upgrade... :: spl: requires linux=3.7.6 :: spl-utils: requires linux=3.7.6 :: zfs: requires linux=3.7.6 :: zfs-utils: requires linux=3.7.6

I have pushed a new update that contains fixes for issues #2 and #3 (https://github.com/demizer/archzfs/issues/2) relating to missing files when trying to build the initramfs.

With the recent announcement by the Arch Devs. that the old sysvinit system is going to be dropped, I am looking to file a few issues with upstream regarding Arch Linux support in ZOL. These issues include: * Remove initscript generation from the ZOL build system. * Remove Arch Linux package generation from the ZOL build system. (See below.) * Provide a link to the ZFS wiki article on the zfsonlinux.org page. Currently, both of the spl and zfs packages have configuration options to create generic packages for arch linux. I am not sure when this support was last maintained, but I had a look at the packages it created once and they are very basic. The PKBGBUILDs on AUR provide better packages. With the support I provide, I don't think this support is necessary in the upstream packages, but I could be wrong. I don't see it being very effective supporting two package systems when AUR is all anyone needs. So to anyone subscribed to this stream, if you have any objections voice them now. Thanks, Jesus A.

@darklajid: There were two annoying problems I have run into so far while getting the bugs out of my build system and maintainership. First, there was one dependency rejection issue a month or two ago because I changed the structure of the pkgver variable in all of archzfs PKGBUILDs to include the kernel version to prevent issues with pkgrel collisions. I was having trouble keeping track of what pkgrel belonged to what kernel version, especially when new kernels appeared in testing, and core at the same time. I will not change the the structure of the pkgver variable in the pkgbuilds again. The second problem happened a few weeks ago when I had to change the repo url path because I added a testing repository and wanted to keep a uniform url path for all of the different repos used by archzfs (archiso, testing, core). I have been ironing out my build process and I have seem to have finally hit a groove, so there should not be any more breakage regarding the archzfs repo. Hopefully! The archzfs repository is the best automatic updates you can get for ZOL on Arch. There is zero building. The only thing is is that you have to wait for me to update the packages. I can usually get them uploaded within a few hours. I try my best. That being said, I was waiting for mkinitcpio build hooks to be integrated into mkinitcpio. I am definitely going to take a look. mkinitcpio build hooks are like DKMS, but done in the "Arch Way". As far as I can tell. Thanks for letting me know!