Debian openzfs full#
Full redundancy is restored as quickly as possible and then the pool is automatically scrubbed to verify all of the data checksums.
Debian openzfs code#
The necessary work to change the Linux-specific ZFS on Linux port to something that could replace Illumos as the upstream “source of truth” that other operating systems could safely port from was completed in November 2020 with the announcement of OpenZFS 2.0.0: “ the former ZFS on Linux project has been renamed OpenZFS! Both Linux and FreeBSD are now supported from the same repository making all of the OpenZFS features available on both platforms.”Ĭontinued coordination and collaboration with OpenZFS developers ensures that the same code will continue to work on both Linux and FreeBSD and that new features will be immediately available to developers. While the decisions about OpenZFS 2.0 were made in 2018, it took a lot of work from a lot of developers to do the necessary work to change the OpenZFS framework from its original inception to the proposed “2.0” framework. Matt Ahrens provides a good visual of the workflow difference between the original OpenZFS and OpenZFS 2.0 in his 2019 OpenZFS DevSummit keynote presentation (slides 11-13). Thus, the design of OpenZFS 2.0 was born. Continuous integration (CI) for the repo would ensure that all proposed changes would have to pass CI on both Linux and FreeBSD before they could be merged. And, it was agreed that future changes would be discussed across platforms before being implemented and that there would be appropriate porting layers to prevent GPL’d or Linux-KPI shim code from being introduced to other operating systems.
Since FreeBSD tracked Illumos commits, this meant that any new features and fixes created on Linux had to first be backported to Illumos before they could be reported to FreeBSD.Īfter much discussion and planning it was agreed that it made sense for everyone to switch from Illumos to Linux as the upstream repo. It also became clear that new feature development had shifted from Illumos to Linux. Since each OS had their own community of developers, other communities weren’t always aware of new development efforts, resulting in duplication of effort for the same desired features. Not all of the bug fixes fixed in one OS were upstreamed back, meaning other operating systems had to implement their own versions of bug fixes. Features were beginning to diverge across the various operating systems. That same year, OpenZFS held its first annual Developer Summit to give developers of the various open source ZFS ports the opportunity to meet in person and participate in planning and coordination efforts.Īs communication between developers increased and the actual work of maintaining OS-specific ports continued, it became clearer over time that the development workflow envisioned by the OpenZFS Project needed to be overhauled in order to better meet the needs of both the developers and OpenZFS users. Version numbers were replaced by feature flags to differentiate OpenZFS from Oracle ZFS and to allow developers to decide which features to create and integrate into their OS-specific port. Pull requests for bug fixes and new features would be managed by the Illumos team. In 2013, the OpenZFS project was created to coordinate cross-platform development with a goal of providing a single common repository for OS-independent code. Over time, the Illumos ZFS code was ported to many operating systems, including FreeBSD in 2007 and Linux in 2008. When Oracle bought Sun and ended development of OpenSolaris, some developers, including many of the original ZFS developers, created Illumos, a fork of the last open source version of Sun’s operating system that included ZFS, so that open source development could continue.
Debian openzfs license#
ZFS was originally developed at Sun Microsystems and released under an open source license as part of OpenSolaris. To understand the need for a 2.0, we need to look at a bit of ZFS history.
We wrote some more about ZFS 2.0 in the past in the following article: Getting Started with OpenZFS 2.0 You might be wondering: “I thought OpenZFS did feature flags, not versions, so what is up with the 2.0?” You may have heard rumblings that it is based on (gasp!) Linux and wonder what that is all about. You may know that FreeBSD 13.0 shipped with OpenZFS 2.0.
0 kommentar(er)
