You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more a statement / opinion / warning than a bug, I just want to leave an artifact here to help others understand the situation around Ubuntu's ZSYS subsystem and a little rant on zfs-on-linux in general.
First, I want to say I really LIKE the ideas behind zsys. From a high-level perspective, it's a major missing component for what's needed to make linux more resilient to software failures like failed system updates, leveraging the power of zfs snapshots while not unduly burdening the user with management tasks. Further, the clear thought and good engineering work that went into zsys is impressive.
However, I've decided to remove zsys and search for another or roll my own solution for a number of reasons:
Apparent abandonment by Canonical. No updates beyond bare compatibility with Ubuntu 22.04.
Lack of support, here or elsewhere, either by Canonical or the community. It wasn't even installed by default on a new 22.04 system.
Bugs. Bug USERDATA datasets removed #218, etc really concern me. Putting a system at risk of unbootable self-destruciton should be considered a CRITICAL bug and should either be fixed or the package should be removed. And I can't even find guidance for how to safely remove system states with confidence of not encountering USERDATA datasets removed #218 using zsys gc or user-error attempting a home-rolled solution.
As a zfs-on-linux early-adopter/enthusiast who's experienced a boot failure first-hand need to say for the record that ZoL system recovery is ugly at best. About a year ago I experienced a failure (due to grub customizer combined with hubris from a false sense of security based on the promise of zfs & zsys). Complexity of the implementation combined with lack of support by the zfs-on-linux community "what? documentation? we just figure it out. conflicts with selinux? ah, well..." led me, after about a week of lost time struggling to recover the system, to just reinstall from scratch and recover my data filesets from a backup. It was a painful but educational experience.
Finally I just want to say I regret having to say this. ZFS and ZSYS are both great technologies. They're ideal solutions to big problems and really move the state of the art forward. Unfortunately, their implementations are both 90% ideal but 10% incomplete. And when it comes to system/data integrity that last 10% is to critical to avoid risk. Sadly it appears that @canonical has abandoned (or at a minimum depreciated) all the the hard work they put into supporting zfs. It's missed the Ubuntu 22.04 LTS bandwagon. Hopefully they or some other distro will take up the effort and complete that last 10%. I switched to Ubuntu for it's zfs support and I'll strongly consider switching to another distro if/when it better supports zfs-on-linux.
@didrocks is an excellent & dedicated developer, I hope he's given the time to get zsys over the finish line.
(Feel free to close this thread if it's felt to not be helpful.)
This is more a statement / opinion / warning than a bug, I just want to leave an artifact here to help others understand the situation around Ubuntu's ZSYS subsystem and a little rant on zfs-on-linux in general.
First, I want to say I really LIKE the ideas behind zsys. From a high-level perspective, it's a major missing component for what's needed to make linux more resilient to software failures like failed system updates, leveraging the power of zfs snapshots while not unduly burdening the user with management tasks. Further, the clear thought and good engineering work that went into zsys is impressive.
However, I've decided to remove zsys and search for another or roll my own solution for a number of reasons:
As a zfs-on-linux early-adopter/enthusiast who's experienced a boot failure first-hand need to say for the record that ZoL system recovery is ugly at best. About a year ago I experienced a failure (due to grub customizer combined with hubris from a false sense of security based on the promise of zfs & zsys). Complexity of the implementation combined with lack of support by the zfs-on-linux community "what? documentation? we just figure it out. conflicts with selinux? ah, well..." led me, after about a week of lost time struggling to recover the system, to just reinstall from scratch and recover my data filesets from a backup. It was a painful but educational experience.
Finally I just want to say I regret having to say this. ZFS and ZSYS are both great technologies. They're ideal solutions to big problems and really move the state of the art forward. Unfortunately, their implementations are both 90% ideal but 10% incomplete. And when it comes to system/data integrity that last 10% is to critical to avoid risk. Sadly it appears that @canonical has abandoned (or at a minimum depreciated) all the the hard work they put into supporting zfs. It's missed the Ubuntu 22.04 LTS bandwagon. Hopefully they or some other distro will take up the effort and complete that last 10%. I switched to Ubuntu for it's zfs support and I'll strongly consider switching to another distro if/when it better supports zfs-on-linux.
@didrocks is an excellent & dedicated developer, I hope he's given the time to get zsys over the finish line.
(Feel free to close this thread if it's felt to not be helpful.)