@darkbasic - Glad you are watching carefully. When we inexorably transition to the 6.9-x kernels, I would be happy to test your proposed PKGBUILD.
Please let me know when available.
Cheers
Git Clone URL: | https://aur.archlinux.org/zfs-utils.git (read-only, click to copy) |
---|---|
Package Base: | zfs-utils |
Description: | Userspace utilities for the Zettabyte File System. |
Upstream URL: | https://zfsonlinux.org/ |
Licenses: | CDDL |
Submitter: | eschwartz |
Maintainer: | kstolp |
Last Packager: | kstolp |
Votes: | 75 |
Popularity: | 1.92 |
First Submitted: | 2018-10-28 22:49 (UTC) |
Last Updated: | 2025-05-03 09:40 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 13 Next › Last »
@darkbasic - Glad you are watching carefully. When we inexorably transition to the 6.9-x kernels, I would be happy to test your proposed PKGBUILD.
Please let me know when available.
Cheers
Good news: zfs-utils installed and operates correctly against the 6.8.0 linux and -zen kernels released today, 11 March!
6.8 compat patches made their way into the 2.2.3-staging branch just days before the 2.2.3 release, but it's a rare occurrence. Most likely by the time 6.9 stable gets released there won't by any support in any released version. I'd like to add official patches to the PKGBUILD to remedy that but the current maintainers are against it, so I'm going to create my own package. Stay tuned if you are interested.
Good news: zfs-utils installed and operates correctly against the 6.8.0 linux and -zen kernels released today, 11 March!
Cheers
I've just added the patch for the file corruption issue.
Hello,
I posted this in zfs-dkms, but it seems this is a zfs-utils issue. I was told libzfs is owned by zfs-utils.
I froze my kernal at 6.4.12-arch1-1 and had zfs 2.2.0 running since it came out.
Yesterday, my power went out, and when the machine came back on, my zfs pool wasn't mounted. I used:
sudo zpool import -a -d (etc)
I receive:
Failed to initialize the libzfs library
I get the same error with zfs set.
I rebuilt the zfs-dkms and zfs-utils packages and reinstalled, with the same result.
What is the solution?
The PKGBUILD uses --libexecdir=/usr/lib/zfs
which leads to files installed in the directory /usr/lib/zfs/zfs
instead of /usr/lib/zfs
. This can be avoided by using --libexecdir=/usr/lib
, which is also what archzfs.com
does.
libexecdir
is only used to set zfsexecdir
to ${libexecdir}/zfs
. I couldn't find any other uses in the source code.
@gromit Yes, I am aware. I noticed it immediately after I pushed, so it was too late.
Hey @kstolp, you forgot to reset pkgrel to 1 for this release :) https://wiki.archlinux.org/title/PKGBUILD#pkgrel
I just noticed because I had already updated the package locally ^^
FAILED (unknown public key 0AB9E991C6AF658B)
I was confounded by being confronted by the error message above and the community's lack of guidance beyond "RTFM". I'll share what I learned in the hope that it saves some newbie some time.
makepkg
uses PGP keys to validate the packages. Makepkg does NOT use the system PGP keyring at /etc/pacman.d/gnupg/pubring.gpg
, so do not include that in your user keyring. And do not execute pacman-key
as some online solutions have suggested .
validpgpkeys
statement, one of which was for Tony Hutter.gpg --recv-key 6AD860EED4598027
to get his key from a keyserver.gpg --list-keys
to view the fingerprint of the newly acquired key. I compared the imported key's fingerprint (second line in the "pub" section) to the one posted on the OpenZFS website. They matched.gpg --lsign KEY_ID
to trust the imported key, as Allan's blog post suggested. I just ran gpg --recv-key
and checked the fingerprint. Your mileage may vary.makepkg -si
then succeeded.Thanks @FrederickZh and @mabod.
I've just added that file to fix the permissions issue. It also looks like they may be fixing it on the systemd side as well.
Anyone who is interested can follow these two issues:
Pinned Comments
eschwartz commented on 2020-12-27 22:43 (UTC)
@Win8Error,
This package doesn't support people who have failed to read the wiki page https://wiki.archlinux.org/index.php/Makepkg, or cannot interpret error messages.
eschwartz commented on 2019-10-16 03:49 (UTC)
aarch64 is not an officially supported architecture for this PKGBUILD, since I don't exactly test it on such architectures. It failing to work is therefore not very surprising.
I guess you can do any necessary followup in that upstream bug report, hopefully upstream can get it into a state of "working out of the box" so that makepkg --ignorearch works. But I'm not investing any of my own time in this...