archzfs VS compsize

# This installs ZFS from the AUR by default. I now use archzfs. It must be setup first. # https://github.com/archzfs/archzfs/wiki paru -S archiso zfs-dkms zfs-utils qemu edk2-ovmf

Just want to add, I didn't have any of these problems using archzfs instead of the AUR packages.

https://aur.archlinux.org/packages/zfs-linux and archzfs.com both get you back to https://github.com/archzfs/archzfs/wiki - have a look at the maintainers name: minextu. So both, the AUR as well as the pacman repo, contain both the very same packages as their storage backend is the same.

Since it's a full kernel why are there issues like this https://github.com/archzfs/archzfs/issues/393? Why would it matter that upstream kernel is newer than archzfs package, how would that break anything?

Which packages are you using? Initcpio hook in AUR zfs-utils doesn't support encrypted root, use archzfs repo.

I watch the aur/zfs-dkms comments and check in on the archzfs github/issues.

No, my information is not outdated. Whether you are getting a package from AUR or from some unofficial repo that you add to your standard repositories doesn't matter. It is still unoffial and if you look at the actual packages in that archzfs repository you will see that the only packages in there are the kernels: https://github.com/archzfs/archzfs/tree/master/packages

I tried reading zfs-utils mkinitcpio/hooks/zfs, and it looks like it mounts child datasets of root and legacy datasets only.

The tool compsize can give you info about the compression state of your data. For example:

The obvious example is the Raid5/Raid6 implementation which is officially not recommended for current use; though that's not something I would use anyways. But I've also found that stuff like listing the compression ratio for volumes requires a separate program, unlike zfs where it's built-in.

If you want to diagnose where you think there may be space used up that you don't quite understand, then btrfs fi du and third party tools btdu and compsize are useful.

I'm going to add my N=1 anecdata if no one minds:

I've been running full Btrfs on my workstation since December 2021 with 0 issues (kernel 5.10). It survived multiple hard reboots and power offs, Ryzen 5000 CPUs seems to lose power every now and then on Linux (it's a known issue for years now that no one has figured out yet).

Having compression is great. compsize reports I've saved 33GB on my /home subvolume so far (https://github.com/kilobyte/compsize). I don't use snapshots, I just backup the whole thing.

Obviously this doesn't mean that in the future Btrfs won't eat my data, but so far it hasn't and I'm happy.

You can also use this tool to find out what the compression ratio of the data is ;).