If anyone here is using ZFS, I would love for some additional testing in a new application, ZFS Assistant. The source is available on gitlab.
Unlike Btrfs Assistant which I built to support the community, ZFS Assistant is something I built because I wanted a tool like this for my personal use. As a result, it was built on the ideas I had around ZFS as someone who has been using it for many years.
There are two major goals I had for this application:
- Make managing ZFS easier and more approachable - I wanted to be able to easily spin up new pools and datasets with only a few clicks. Create snapshot policies and apply them to datasets. Most importantly, I wanted it to be easy to replicate those snapshots to local or remote pools.
- Increase observability of ZFS pools and jobs - ZFS is very resilient, it keeps running even when there are issues. But that doesn’t mean you should ignore those issues. I wanted to be visually alerted of any issues with my pools or jobs.
I think I have achieved both those goals. The UI provides nearly the full feature set available in ZFS and the tray icon provides both configurable notifications and a visual indicator of any issues.
Here are the general features available in version 0.8.0:
- A tray icon that monitors pool health and job statuses
- Notifications of poor health
- A CLI with the same functions as the GUI
- Pool overviews and status
- Create, import and destroy pools
- View and set pool and dataset properties
- Take checkpoints
- View pool history
- Create, mount, modify and destroy datasets
- Grant and revoke dataset/pool permissions
- Take and delete snapshots
- Mark snapshots as held
- Restore, clone and rollback snapshots
- Restore files and directories from snapshots
- Create policies for scheduled snapshot creation, pruning and retention
- Add remote targets for snapshots
- Send snapshots to remotes and optionally prune them
If you are interested in trying it out or want to help test it, there are a couple of ways you can get it. There are AUR packages maintained by me, zfs-assistant and zfs-assistant-git. If you would prefer not to use AUR or are on another distro, there are also binary packages on the downloads page and the gitlab release page. Be aware to run the UI you need both zfs-assistant and zfs-assistant-cli from the releases page. Of course, you also need to have the ZFS modules available on your system. Some distros include them, for others you need to install them yourself. Instructions for most distros can be found on the OpenZFS wiki.
Please be aware that it is still considered beta software so you might be careful with how you use it with important data until it has more wide use and testing.
FAQ
What technologies is it built in?
The back-end is entirely written in Rust and the UI is in Qt/C++. I chose C++ for the front-end both because of my familiarity with it and the fact that is the only language with true first class Qt bindings. I chose Rust for the back-end because I wanted to use a more modern language than C++ for the majority of the application.Why did you use Qt widgets in 2026?
The application has lots of dense data and tree views. I didn't think it was particularly well suited to something like QtQuick or Kirigami. In the case of the latter, I also didn't want to add a bunch of KDE dependencies needlessly.In truth, the UI is totally independent of the helper application so it would not be that hard to migrate it to another tech stack or even have a second UI built on something else.
Why does it look so different than Btrfs Assistant?
Btrfs Assistant started life as a single page inside of Garuda Assistant. It eventually grew too big and I split it out into it's own tool. The UI then grew organically from there.ZFS Assistant was built as completely new standalone tool. I started with a UI prototype for the full feature set I wanted and then built the functionality one piece at a time. This resulted in a UI that was more cohesive than one that had been added onto one piece at a time.
