zsys | nix | |
---|---|---|
15 | 2 | |
298 | 1 | |
0.3% | - | |
5.4 | 9.1 | |
19 days ago | 4 months ago | |
Go | Nix | |
GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zsys
-
How to maintain 20% minimum free space on bpool
From this bug report on github, here is a clear explanation of the problem:
-
The Future of ZFS on Ubuntu Desktop Is Not Looking Good
This is a good thing for ZFS and public perception of ZFS. Ubuntu has made some very poor choices with how they've integrated ZFS -
* zsys has both implementation and design flaws. They utilize two zpools - one with limited feature flags that GRUB can use and one general pool, and then try to tightly couple datasets between those two pools while coordinating snapshots. zsys routinely runs a system out of space due to not cleaning up snapshots. It's been known to destroy user data as well.
https://github.com/ubuntu/zsys/issues/196
-
Desktop OS with ZFS
Example: https://github.com/ubuntu/zsys/issues/155
- Don't use ZSYS (on Ubuntu 22.04)
-
Backup Solution: fully automated, complete system backup, incremental and with web GUI functionality (snapshots / history)?
Heard of it, but I have no idea how it works and if I must install ubuntu server completely new. After a bit googling it seems dead? “It seems the project has been dead for months now. What going on?” https://github.com/ubuntu/zsys/issues/213
-
Ubuntu 22.04 Root on ZFS
Ubuntu isn't my preferred OS these days, but I've had excellent experiences with it's ZFS root installs as well as it's included zsys: https://github.com/ubuntu/zsys
-
zfs on root with 22.04 without zsys
Re: things I've actually dealt with, see -- #172
-
Moving rpool/USERDATA to separate pool
I even filed a very polite GH issue about how zsys doesn't handle other systems/sanoid snapshots well, to which I got no response. However, a previous response to a user with the same issue was "Turn that other method of snapshot-ing off and delete your other snapshots" which, I'm sorry, just doesn't make any sense to say to any ZFS user -- "Pound sand and delete some of your data, then maybe it will work." Say what?
- Canonical puts zsys on life support (2.5 Admins)
-
Help with ZFS on Ubuntu
https://github.com/ubuntu/zsys/issues/112 - This could be an incompatibility with the way docker stores volumes, but this looks like it should've been fixed a while ago?
nix
What are some alternatives?
zectl - ZFS Boot Environment manager for Linux
ALEZ - Arch Linux Easy ZFS installer
ubuntu-server-zfsbootmenu
dotfiles
simple-ubuntu-installer - simple encrypted zfs ubuntu installer
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption
kanata - Improve keyboard comfort and usability with advanced customization
zsysctl-manual-gc - Manual zsys garbage collection script.