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.2 supports kernel versions 4.18 - 6.14. When kernel 6.15 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!

The ZFS package has been updated to pkgrel 5 and now supports for kernel 3.6.8. Changes include: * mkinitcpio hooks rewrite thanks to falconindy. * Removed support for spl_hostid kernel parameter. * Rewrite of systemd unit file thanks to duncant. * Experimental handling of /etc/hostid. /etc/hostid is now tracked by the spl-utils package. * Rewrite package descriptions. I apologize in advance for the long post, but a lot has changed. The systemd unit rewrite now properly loads the kernel modules with modprobe and also exports the zfs shares. The mkinitcpio hooks have been rewritten to support the next version of mkinitcpio. The spl-utils package now tracks the /etc/hostid file. This file is used by zfs to include in the storage pool metadata when creating pools. In some cases if this value differs from /etc/hostid and the pool metadata, zfs will refuse to import the pool producing an error saying that the foreign pool could not be imported. Supposedly, the hostid command produces a 32 bit unique identifier on every fresh reboot using the systems IP address. So the hostid gathered when you created the pool can be different from what the hostid command currently produces. I say supposedly because in my tests, my hostid has not changed from boot to boot. This could be because I use a static IP address though. The hostid used when creating your zfs pools can be gathered by using the command "zdb". The /etc/hostid file itself is a 4 byte little endian binary file. So `echo $(hostid) >/etc/hostid` is not the proper way to set the hostid value. One way to set the hostid is the following: HOSTID=$(hostid) sudo sh -c "printf $(echo -n $HOSTID | sed 's/\(..\)\(..\)\(..\)\(..\)/\\x\4\\x\3\\x\2\\x\1/') >/etc/hostid" You could also make a quick and dirty C program that calls sethostid(id). The spl-utils package now tracks the /etc/hostid file. If it already exists on your system, you will need to record the value somewhere and let the spl-utils package overwrite it using "pacman -Sf" (or delete the file yourself). If the value in your /etc/hostid is correctly set, than you can retrieve it using the following command: $ od -A n -t x1 /etc/hostid > 00 01 7f 00 Note: If correctly set, this value will have the low-order byte first, so it will have to be saved back to /etc/hostid with: sudo sh -c "printf $(echo -n 00017F00 | sed 's/\(..\)\(..\)\(..\)\(..\)/\\x\1\\x\2\\x\3\\x\4/') >/etc/hostid" The value produced should be only 4 bytes! If it is not, then it is okay to let the spl-utils post_install hook produce a proper hostid for you. Since the proper hostid is now included in the initramfs, I dropped support for the spl_hostid kernel parameter check in the initcpio hook. All it did anyways was echo the value to /etc/hostid, which is incorrect. NOTE: If you are using this parameter, you will be kicked out to the repair command line in the initramfs! You should now instead use the method described above to set this value to /etc/hostid. You will then need to rebuild your initramfs with "mkinitcpio -p linux". One last thing, To be on the safe side, make sure you have good backups before performing any updates ALWAYS. Whew! - demizer

The ZFS packages have been flagged out of date. Kernel 3.6.8 is now in [core]. I am currently working on fixing hostid issues in the spl package. The new packages should be uploaded to AUR within the next day or two. Thanks!

@ronnylov, copy http://pastebin.com/jTZUusG5 to /usr/lib/systemd/system/zfs.service for the time being. I will update the packages in AUR once kernel 3.6.8 is out of testing. Thanks!

Directories shared by sharenfs=on are not automatically shared after reboot when moving from rc.conf to zfs systemd unit file. I have to manually export and import my pool to make it enable the sharing again. How can I solve this? Maybe I have to make sure zfs is started after the nfs services...

The ZFS package has been updated to pkgrel 4. Changes include: * mkinitcpio updates for the initramfs install hook. * Cleaned up mkinitcpio install hook help documentation (mkinitcpio -H zfs). * Added a systemd unit file The systemd unit file allows the mounting of zpools at startup. This also makes it possible for the ZFS packages to not have to depend on initscripts for initialization. If ZFS is your last hold out for initscripts, like it was for me, you can now remove initscripts. The usage of the new unit file is pretty typical for systemd unit files: # systemctl enable zfs # systemctl start zfs # systemctl status zfs # systemctl stop zfs I have not fully tested all of these changes, especially in the updates to the mkinitcpio install hook. But they are not considered dangerous or data threatening. The systemd unit file only calls 'zfs mount -a' and 'zfs unmount -a' for example. To be on the safe side, make sure you have good backups before performing any updates ALWAYS.

@falconindy, thanks for the heads up! Will do.

Hi, this mkinitcpio hook is going to break soon. Please avoid using MODULES and SCRIPT and use the functions "add_module" and "add_runscript" instead.

@ronnylov, So sorry! I pushed packages that didn't have any kernel modules in them, yikes! I have changed my procedures so this doesn't happen again. In this case, instead of building from scratch, I repackaged. Somewhere in development the kernel modules got deleted. I also didn't perform a proper test before pushing the repository. There won't be future packaging errors like this as I now have a checklist. Thanks for the report!

I fixed it by installing the zfs and spl packages from AUR instead from the repository.