Currently this package overwrites /etc/zfs/zed.d/zed.rc
on each update.
I’ve customized the RC file to include my email address so I get notified by ZFS ZED.
I recommend adding the following to the PKGBUILD:
backup=(etc/zfs/zed.d/zed.rc)
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: | 74 |
Popularity: | 1.64 |
First Submitted: | 2018-10-28 22:49 (UTC) |
Last Updated: | 2025-03-11 07:23 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 13 Next › Last »
Currently this package overwrites /etc/zfs/zed.d/zed.rc
on each update.
I’ve customized the RC file to include my email address so I get notified by ZFS ZED.
I recommend adding the following to the PKGBUILD:
backup=(etc/zfs/zed.d/zed.rc)
I submitted this as a pull request to the alleged upstream mentioned in the PKGBUILD a while ago, but I guess that is derelict.
https://github.com/openzfs/zfs/pull/11468 and https://github.com/openzfs/zfs/pull/11861 added support for compatibility option files that greatly improve sharing/migrating pools between systems (or at the very least allowing that possibility) while using recent features.
The following diff installs the needed files.
diff --git a/PKGBUILD b/PKGBUILD
index 675ece6..e6c13bd 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -63,7 +63,8 @@ package() {
#rm -r "${pkgdir}"/usr/lib/dracut
rm -r "${pkgdir}"/usr/lib/modules-load.d
rm -r "${pkgdir}"/usr/share/initramfs-tools
- rm -r "${pkgdir}"/usr/share/zfs
+ rm -r "${pkgdir}"/usr/share/zfs/*.sh
+ rm -r "${pkgdir}"/usr/share/zfs/{runfiles,test-runner,zfs-tests}
install -D -m644 "${srcdir}"/zfs.initcpio.hook "${pkgdir}"/usr/lib/initcpio/hooks/zfs
install -D -m644 "${srcdir}"/zfs.initcpio.install "${pkgdir}"/usr/lib/initcpio/install/zfs
There is a bug in zfs which causes a core dump during "zfs send" when compiled with GCC 12.
Only if you alter the defaults and set march=zenver3
. If you're doing this sort of thing then you're more likely to hit upstream bugs, and therefore upstream fixes are what's needed.
If the kernel parameter is set to root=zfs
, the system is unbootable because the pool
variable is not set in the initcpio hook. Adding ZFS_DATASET="bootfs"
under line 177 of zfs.initcpio.hook fixes this issue.
There is a bug in zfs which causes a core dump during "zfs send" when compiled with GCC 12. A workaround is to force compiler flag -fno-tree-vectorize. See here: zfs issue 13605
gentoo has already added that flag to their ebuild files. I recommend to add this to zfs-utils PKGBUILD as well. I am not sure about zfs-dkms. May be this flag should be added there too as a precaution.
Can you add provides=('zfs-utils=2.1.4') to the PKGBUILD? The various zfs-linux packages require zfs-utils=2.1.4 which the pkgver 2.1.4+65.r05147319b0 doesn't satisfy.
Please update the initcpio hook to support encryption (https://github.com/eli-schwartz/pkgbuilds/issues/30). The last update cost me some time to recover my system (yes, I should have put the hook to /etc/initcpio/hooks to prevent overwriting, but it would still be nice to get encryption support out of the box).
Hi there, thanks for the package.
I was browsing my file system and was surprised to see that I had files in /usr/var/run
!
I fixed this by adding --localstatedir=/var
to the configure options.
Possibly consider adding "libaio" as (build) dependency. The configure script has checks for libaio.h.
Edit: Never mind. Seems like libaio is only used for test cases. Sorry for the noise.
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...