Package Details: zfs-utils 2.3.4-1

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: 0.41
First Submitted: 2018-10-28 22:49 (UTC)
Last Updated: 2025-08-26 11:15 (UTC)

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...

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

kstolp commented on 2025-08-25 05:44 (UTC)

@reaperx7, Has something changed since 4d72ad9?

reaperx7 commented on 2025-08-25 05:00 (UTC)

Just an FYI, the package requires libunwind to be installed for the zpool and zfs tools.

mabod commented on 2025-08-01 05:46 (UTC)

@allddd: You are right. The issue is related to me removing zfs-dkms during a test cycle. Sorry for the noise.

allddd commented on 2025-07-31 23:18 (UTC)

@mabod The wiki says the following about .pacsave files:

When pacman removes a package that has a configuration file, it normally creates a backup copy of that configuration file and appends .pacsave to the name of the file.

However, further down in the article, it's also mentioned that this may happen during an upgrade, but only if you remove the package beforehand (whatever that is supposed to mean):

A .pacsave file may be created during a package removal (pacman -R), or by a package upgrade (the package must be removed first).

As the wiki isn't clear on this, I checked the code (lib/libalpm/remove.c) and found that a .pacsave file is indeed only created when a package is removed, so you must have done it at some point.

Pacman is supposed to log when the file is created, so you should be able to see which command you ran at that point if the log hasn't been rotated since then.

kstolp commented on 2025-07-31 22:10 (UTC)

@mabod Are you sure that is what is happening? That file path is in the backup array in the PKGBUILD here. It seems to be working as expected on my system.

mabod commented on 2025-07-18 16:39 (UTC)

This package overwrites /etc/zfs/zed.d/zed.rc on installation. And it creates a zed.rc.pacsave file for my version of the file. I would rather want to keep my zed.rc file and let the package create a zed.rc.pacnew file. Is that possible?

yurikoles commented on 2025-05-06 21:42 (UTC) (edited on 2025-05-06 21:43 (UTC) by yurikoles)

@timemaster

This code sets zfsdecrypt_shell as root's shell inside boot initcpio. So when you connect to the machine via SSH as root during boot, you'll be presented with ZFS encryption unlock prompt. Thus, you unlock the encrypted dataset in order to continue the boot process.

You may read about Generate new checksums on Arch Wiki.

timemaster commented on 2025-05-04 00:31 (UTC) (edited on 2025-05-04 00:31 (UTC) by timemaster)

Security issue/question : could someone explain to me if this is safe ? \\ make_etc_passwd() { echo 'root:x:0:0:root:/root:/bin/zfsdecrypt_shell' >> "${BUILDROOT}"/etc/passwd echo '/bin/zfsdecrypt_shell' > "${BUILDROOT}"/etc/shells }\\ from the zfs.initcpio.zfsencryptssh.install of this package ? Myabe it's a hack/workaround, but it does not looks proper.

if I disable the code when building locally, I end up failing the PGK signature check and the build fail. Thanks !

ipaqmaster commented on 2025-03-02 22:58 (UTC) (edited on 2025-03-02 23:35 (UTC) by ipaqmaster)

I can't get the source to build aarch64 either. Might raise upstream if ./configure can't be tweaked here

ipaqmaster commented on 2025-03-02 22:23 (UTC) (edited on 2025-03-02 22:30 (UTC) by ipaqmaster)

I'm having the same problem. Can you make CARCH=aarch64 build aarch64 binaries please?

My build server made an aarch64 package and bricked my raspberry pi zfs rootfs because its initramfs tried to use /sbin/zpool but that was actually an x86_64 binary not aarch64.

This package needs to package the architecture its been asked to or fail. Not put bad binaries in.

1 2 3 4 5 6 .. 14 Next › Last »