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!

Anyone else having problems with ACLs? Just upgraded to kernel 4.5.0-1 and In my journal I now have a number of "ACL operation on /var/log/journal... Failed: invalid argument" errors. Trying to use getfacl errors with invalid argument for any file on the zfs fs, but works on my boot partition files (which is vfat). My pool does have "xattr=sa" and "acltype=posixacl" set, and mount shows it has been mounted with xattr,posixacl options.

@abrilevskiy, try the zfs-dkms-git AUR instead.

https://github.com/severach/ArchLinuxScripts I made a shell script. It applies uname -r or not, as desired to all 4 PKGBUILD.

@techmunk : what file is this patch applied to?

I use the patch below along with clean-chroot-manager (https://aur.archlinux.org/packages/clean-chroot-manager). Works a treat, and I don't have to wait for demizer to update for a new kernel version, but I should still get ZFS updates just fine. diff --git a/PKGBUILD b/PKGBUILD index 2848946..20e1114 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -12,21 +12,9 @@ pkgver=0.6.5.4_r0_g1ffc4c1_4.4.3_1 pkgrel=1 license=('CDDL') -# Used incase the i686 and x86_64 linux packages get out of sync with the -# PKGREL. This occurred on January 31, 2014 where i686 was versioned at -# 3.12.9-1 and x86_64 was versioned at 3.12.9-2. -_kernel_version_x32="4.4.3-1" -_kernel_version_x32_full="4.4.3-1" -_kernel_version_x64="4.4.3-1" -_kernel_version_x64_full="4.4.3-1" - -if [[ $CARCH == "i686" ]]; then - _kernel_version=${_kernel_version_x32} - _kernel_version_full=${_kernel_version_x32_full} -else - _kernel_version=${_kernel_version_x64} - _kernel_version_full=${_kernel_version_x64_full} -fi +_kernel_version="$(/usr/bin/pacman -Ss ^linux$ | /usr/bin/grep ^core/linux | /usr/bin/cut -d ' ' -f 2)" +_kernel_version_full="$_kernel_version" +pkgver="${pkgver%_*_*}_${_kernel_version//-/_}" pkgdesc="Kernel modules for the Zettabyte File System." depends=("spl-git" "zfs-utils-git" "linux=${_kernel_version}")

@abrilevskiy, I will make the requested changes soon. In the next week I am going to spend time clearing out issues in the archzfs issue tracker that have built up over the last year. https://github.com/archzfs/archzfs/issues/28 However, the changes suggested for _kernel_version cannot be implemented because of the comment before that section of code in the PKGBUILD: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=zfs-git#n15 I will test building against linux-vfio and linux-ck.

@demizer, Could you please: 1. use `uname -r` for dynamic kernel version detection? 2. replace kernel variable from: _kernel_version_x32="4.3.3-2" _kernel_version_x32_full="4.3.3-2" _kernel_version_x64="4.3.3-2" _kernel_version_x64_full="4.3.3-2" to something like: _kernel_version_x32="4.3.3-2" _kernel_version_x32_full=${_kernel_version_x32} _kernel_version_x64=${_kernel_version_x32} _kernel_version_x64_full=${_kernel_version_x32} 3. create new variable like kernel_ext that store "-ARCH" by default (kernel_ext="-ARCH") I am using custom kernel (linux-vfio. uname -r: 4.2.5-1-vfio) and each kernel updated I have to: 1. uninstall zfs* packages 2. install kernel 3. download zfs* packages 4. modify PKGBUILD files of zfs* packages 5. compile zfs* packages 5. install zfs* packages Could you please help me to reduce number of steps required to upgrade kernel. Thank you in advance, Andrei.

@justinkb, it's perfectly fine to flag out-of-date to notify me of a problem with the packages. If the reason is for a problem with the package itself (other than a kernel version upgrade), please state so in the comment area. I use google inbox so when the packages are flagged out-of-date it is immediately apparent. Thanks for asking!

Just a little question to the package maintainer about etiquette. Are we supposed to use the "flag out of date" link to notify you of kernel updates or do you consider this rude/annoying?