I have updated the packages to pkgrel 8 fixing the initial ramdisk generation after installing the updated zfs package in cases of using zfs in the hooks array in mkinitcpio.conf.
Search Criteria
Package Details: zfs-linux 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 modules for the Zettabyte File System. |
Upstream URL: | https://openzfs.org/ |
Keywords: | kernel linux openzfs zfs |
Licenses: | CDDL |
Groups: | archzfs-linux |
Conflicts: | spl-dkms, spl-dkms-git, spl-linux, zfs-dkms, zfs-dkms-git, zfs-dkms-rc, zfs-linux-git, zfs-linux-rc |
Provides: | spl, zfs |
Replaces: | spl-linux |
Submitter: | demizer |
Maintainer: | lightdot |
Last Packager: | lightdot |
Votes: | 275 |
Popularity: | 0.91 |
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 (19)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 61 62 63 64 65 66 67 68 69 70 71 .. 79 Next › Last »
demizer commented on 2012-12-15 18:41 (UTC)
demizer commented on 2012-12-15 06:21 (UTC)
!IMPORTANT!
For users that are using ZFS as root, there is a problem with the current package when generating the ramdisk with mkinitcpio. The problem is that once the kernel is installed, the mkinitcpio is initiated before the ZFS packages have been installed. This produces errors because mkinitcpio cannot find the ZFS binaries needed by the install hook.
To fix this, use:
# depmod -a 3.6.10-1-ARCH
# mkinitcpio -p linux
demizer commented on 2012-12-15 05:49 (UTC)
The packages and repository have been updated for kernel 3.6.10.
demizer commented on 2012-12-14 17:14 (UTC)
Indeed, ZFS does not build against Kernel 3.7. In order not to have these packages be flagged out of date for an extended period of time, I have created patches for ZFS and SPL including the fixes from the ZOL master branches and packaged them using pkgrel 8.
http://demizerone.com/archzfs/pkgsrc/aur/spl-utils-0.6.0_rc12-8.src.tar.gz
http://demizerone.com/archzfs/pkgsrc/aur/spl-0.6.0_rc12-8.src.tar.gz
http://demizerone.com/archzfs/pkgsrc/aur/zfs-utils-0.6.0_rc12-8.src.tar.gz
http://demizerone.com/archzfs/pkgsrc/aur/zfs-0.6.0_rc12-8.src.tar.gz
The patch includes all the changes made up until the last release. ZOL is very weird in how they make releases, they are no rhyme or reason to them, they just happen and it seems anything that touches the master branch is stable. I have been running these updated packages for a couple days without incident.
I also have the packages for 3.6.10 ready to go (pkgrel-7), I am just waiting for 3.6.10 to hit [core].
http://demizerone.com/archzfs/pkgsrc/aur/spl-utils-0.6.0_rc12-7.src.tar.gz
http://demizerone.com/archzfs/pkgsrc/aur/spl-0.6.0_rc12-7.src.tar.gz
http://demizerone.com/archzfs/pkgsrc/aur/zfs-utils-0.6.0_rc12-7.src.tar.gz
http://demizerone.com/archzfs/pkgsrc/aur/zfs-0.6.0_rc12-7.src.tar.gz
I am thinking about creating a testing repository for these packages so I can push updates out for testing.
In other news, I have created a branch that tracks the archiso so we can do emergency maintenance if need be. The server string for pacman.conf is as follows:
[archzfs]
Server = http://demizerone.com/$repo/archiso/$arch
Of course, you will also need to add my key and locally sign it before using, but now we can use zfs in the archiso environment without compiling!
I have installed ZFS on a root filesystem on my wife's laptop, there are changes coming to the packaging to improve the implementation. Most of all I am working on updating the archwiki documentation and that should be up in the next week or two.
chenxiaolong commented on 2012-12-14 17:14 (UTC)
@proxypoke: That has been fixed in the latest zfs git :) You can clone the git repo (https://github.com/zfsonlinux/zfs.git) and run
./autogen.sh
./configure
make pkg
which will create Arch Linux .pkg.tar.xz packages you can install.
proxypoke commented on 2012-12-14 14:27 (UTC)
Ahoy all,
ZFS doesn't compile on Linux 3.7.0 yet. I tested this with the ck patchset, but it should be the same on the standard kernel. It gives an error about GPL-only symbols when linking zfs.ko.
Short error log attached:
https://gist.github.com/4285774
I'd advise against kernel updates if you need ZFS.
Cheers
slowpoke
demizer commented on 2012-11-30 09:21 (UTC)
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
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!