| OpenZFS | |
|---|---|
| Original author | Sun Microsystems |
| Developer | OpenZFS Project |
| Release | Ported to various systems between 2006 and 2010. Forked from OpenSolaris August 2010 |
| Stable release | |
| Written in | C |
| Operating system | OpenSolaris, illumos, OpenIndiana, FreeBSD, NetBSD, macOS, Linux, OSv |
| License | Common Development and Distribution License |
| Website | openzfs |
| Repository | github |
OpenZFS is an open-source implementation of the ZFS file system and volume manager initially developed by Sun Microsystems for the Solaris operating system, and is now maintained by the OpenZFS Project. Similar to the original ZFS, the implementation supports features like data compression, data deduplication, copy-on-write clones, snapshots, RAID-Z, and virtual devices that can create filesystems that span multiple disks.
One of the main capabilities of OpenZFS is self-healing. Every block is checksummed, so the file system can detect errors while in use, without the need for a dedicated file system checker. In pools with redundancy, such as mirrors, RAID-Z, dRAID or datasets that store multiple copies of each block, a damaged block is repaired automatically from a good copy; without redundancy, OpenZFS can detect and report corruption but cannot repair it. This feature makes it suitable for mission-critical applications that require high availability.
OpenZFS is used in enterprise and data center environments, as well as consumer devices like network-attached storage (NAS) devices, where data reliability and safety is essential. While initially designed for Solaris, development later shifted to the Linux port, which since OpenZFS 2.0 has been the common code base for Linux and FreeBSD; ports also exist for other BSD distributions and macOS, and a port to Windows is in development. Unlike Oracle ZFS, OpenZFS is licensed under the Common Development and Distribution License (CDDL), enabling both open-source and commercial use of the file system.
Founding members of OpenZFS include Matt Ahrens, one of the main architects of ZFS. In 2020, the codebases of OpenZFS and ZFS on Linux, a kernel module allowing ZFS to be used on Linux, were merged and released as OpenZFS 2.0, allowing other non-Linux operating systems to receive the various improvements that the Linux driver had incorporated over time.
The ZFS file system was originally developed by Sun Microsystems for the Solaris operating system. The ZFS source code was released in 2005 under the Common Development and Distribution License as part of the OpenSolaris operating system, and it was later ported to other operating systems and environments.
The following is a list of key events in the development of ZFS and its various implementations:
As the FSF (Free Software Foundation) claimed that there was a legal incompatibility between the CDDL and the GPL in 2005, Sun's implementation of the ZFS file system couldn't be used as a basis for the development of a module in the Linux kernel, couldn't be merged into the mainline Linux kernel, and Linux distributions generally did not include it as a precompiled kernel module. As a workaround, FUSE, a framework that allows file systems to run in userspace, was used on Linux as a separation layer for which the licensing issues did not apply, although with a set of its own issues that includes a performance penalty. However, the April 2016 release of Ubuntu 16.04 LTS includes ZFS as a kernel module.
In the release version of Mac OS X 10.5, ZFS was available in read-only mode from the command line, which lacks the possibility to create z-pools or write to them. Before the 10.5 release, Apple released the "ZFS Beta Seed v1.1", which allowed read-write access and the creation of z-pools; however, the installer for the "ZFS Beta Seed v1.1" has been reported to only work on version 10.5.0, and has not been updated for version 10.5.1 and above. In August 2007, Apple opened a ZFS project on their Mac OS Forge web site. On that site, Apple provided the source code and binaries of their port of ZFS which includes read-write access, but without an installer. In October 2009, Apple discontinued development of the ZFS project on Mac OS Forge with no explanation. Apple removed everything but the CDDL-licensed portion of the source code for their final build of the ZFS project, code named "10a286". Complete ZFS support was originally advertised as a feature of Snow Leopard Server before launch, but by the time the operating system was released all references to this feature had been removed from its features page.
Apple's "10a286" source code release, and versions of the previously released source and binaries, have been preserved and new development had been adopted by the MacZFS project to continue development outside of Apple. As of July 2012, Mac ZFS implements z-pool version 8 and ZFS version 2, released with the October 2008 release of Solaris. Additional historical information and commentary can be found on the Mac ZFS web site and FAQ. However, the project ceased development in mid 2013 with a message asking users to switch to Open ZFS on OSX (abbreviated to O3X).
Although the ZFS filesystem supports Linux-based operating systems, difficulties arise for Linux distribution maintainers wishing to provide native support for ZFS in their products due to legal incompatibilities between the ZFS's CDDL license and the GPL license used by the Linux kernel. To enable ZFS support within Linux, a loadable kernel module containing the CDDL-licensed ZFS code must be compiled and loaded into the kernel. According to the Free Software Foundation, the wording of the GPL license legally prohibits redistribution of the resulting product as a derivative work, though this viewpoint has caused some controversy.
One potential workaround to licensing incompatibility was trialed in 2006, with an experimental port of the ZFS code to Linux's FUSE system. The filesystem ran entirely in userspace instead of being integrated into the Linux kernel, and was therefore not considered a derivative work of the kernel. This approach was functional, but suffered from significant performance penalties when compared with integrating the filesystem as a native kernel module running in kernel space. As of 2016, the ZFS on FUSE project appears to be defunct, as the ZFS on Linux kernel driver has prevailed over the userspace one.
A native port of ZFS for Linux produced by the Lawrence Livermore National Laboratory (LLNL) was released in March 2013, following these key events:
As of August 2014[update], ZFS on Linux uses the OpenZFS pool version number 5000, which indicates that the features it supports are defined via feature flags. This pool version is an unchanging number that is expected to never conflict with version numbers given by Oracle.
Another native port for Linux was developed by KQ InfoTech in 2010. This port used the zvol implementation from the Lawrence Livermore National Laboratory as a starting point. A release supporting zpool v28 was announced in January 2011. In April 2011, KQ Infotech was acquired by sTec, Inc., and their work on ZFS ceased. Source code of this port can be found on GitHub.
The work of KQ InfoTech was ultimately integrated into the LLNL's native port of ZFS for Linux.
While license incompatibilities may arise with the distribution of compiled binaries containing ZFS code, it is generally agreed that distribution of the source code itself is not affected by this. In Gentoo Linux, configuring a ZFS root filesystem is well documented and the required packages can be installed from its package repository. Slackware also provides documentation on supporting ZFS, both as a kernel module and built into the kernel.
The question of the CDDL license's compatibility with the GPL license resurfaced in 2015, when the Linux distribution Ubuntu announced that it intended to make precompiled OpenZFS binary kernel modules available to end-users directly from the distribution's official package repositories. In 2016, Ubuntu announced that a legal review resulted in the conclusion that providing support for ZFS via a binary kernel module was not in violation of the provisions of the GPL license. Other organizations such as the Software Freedom Law Center followed Ubuntu's conclusion, while the FSF and SFC reiterated their opposing views.
Ubuntu 16.04 LTS ("Xenial Xerus"), released on April 21, 2016, allows the user to install the OpenZFS binary packages directly from the Ubuntu software repositories. As of 2024[update], no legal challenge has been brought against Canonical regarding the distribution of these packages.
As of 2019, Ubuntu supports experimental installation of ZFS as a root filesystem, starting with the 19.10 release ("Eoan Ermine"), to support coexistence of a nearly pure ZFS OS with GRUB and other operating systems on the same disk.
A version of TrueNAS by iXsystems, based on Debian Linux. As with TrueNAS Core (based on FreeBSD), it uses OpenZFS for storage and adds a variety of additional features. These include expanded device driver support, KVM virtual machines, PCIe passthrough and container support via Docker, which replaced Kubernetes as the application back end in TrueNAS SCALE 24.10. Furthermore, it allows clustered Docker and ZFS via gluster. Information about the current release can be found at the iXsystems Software Status page. The "Scale" branding was officially dropped from the name with the release of TrueNAS 25.04, Fangtooth, which only has a Linux release.
A port of open source ZFS was attempted in 2010 but after a hiatus of over one year development ceased in 2012. In October 2017, a new port of OpenZFS was announced by Jörgen Lundman at OpenZFS Developer Summit.
A newer open source port of ZFS is also hosted on GitHub. As of 2026[update], its releases tracked the OpenZFS 2.4 series and were still published as release candidates.
| Latest FOSS stable release |
| ZFS Pool Version Number | Release date | Significant changes |
|---|---|---|
| 5000 | OpenZFS | Unchanging pool version to signify that the pool indicates new features after pool version 28 using ZFS feature flags rather than by incrementing the pool version |
ZFS on Linux was tagged as versions 0.4 and 0.5 between 2008 and 2010, followed by fourteen 0.6.0 release candidates between February 2011 and February 2013. Version 0.6.1, released in March 2013, was the first that its developers declared ready for production use. Releases before 2.0 were made by the ZFS on Linux project; since the code bases were unified in 2020, OpenZFS has been developed in a single repository for Linux and FreeBSD. Major releases are listed below; each was followed by maintenance releases.
| Version | Release date | Supported platforms at release | Significant changes |
|---|---|---|---|
| 0.6.1 | March 2013 | Linux up to 3.9 | First release declared ready for production use; snapdev property to control the visibility of zvol snapshots |
| 0.6.2 | August 22, 2013 | Linux up to 3.11 | L2ARC compression and an I/O deadman thread from illumos; SEEK_DATA and SEEK_HOLE support in lseek(); zpool labelclear from FreeBSD |
| 0.6.3 | June 12, 2014 | Linux up to 3.14 | Smoother write throttle; POSIX ACLs; immutable and append-only file attributes; relatime updates; SELinux integration; systemd support; the ZFS Event Daemon (ZED); support for AArch64 and SPARC64 |
| 0.6.4 | April 8, 2015 | Linux 2.6.32–4.0 | Feature flags spacemap_histogram, extensible_dataset, bookmarks, enabled_txg, hole_birth and embedded_data; asynchronous I/O; hole punching with fallocate(); LZ4 compression of metadata |
| 0.6.5 | September 11, 2015 | Linux 2.6.32–4.2 | large_blocks feature for record sizes above 128 KB, up to 16 MB; filesystem_limits feature; LZ4 as the default when compression is enabled; temporary mount options; access to .zfs/snapshot over NFS |
| 0.7 | July 26, 2017 | Linux 2.6.32–4.12 | Resumable and compressed zfs send/receive; multiple import protection (multihost); scrub pause; delegated administration with zfs allow; large dnodes; user and group object quotas; SHA-512, Skein and Edon-R checksums; automatic replacement of failed drives, hot spares and fault LEDs; scatter-list ARC buffers, compressed ARC and vectorized RAID-Z parity |
| 0.8 | May 23, 2019 | Linux 2.6.32–5.1 | Native encryption (AES-256-CCM by default) with raw encrypted zfs send/receive; removal of top-level devices; pool checkpoints; TRIM; pool initialization; project quotas; Lua channel programs; the pyzfs Python library; sequential scrub and resilver; allocation classes for special and dedup vdevs; the Solaris Porting Layer merged into the ZFS repository |
| 2.0 | November 30, 2020 | Linux 3.10–5.9; FreeBSD 12.2 and later | First release from the unified code base, adding FreeBSD support alongside Linux; ZFS on Linux renamed OpenZFS; sequential resilver, persistent L2ARC, Zstandard compression and redacted zfs send/receive; deduplicated send streams deprecated |
| 2.1 | July 2, 2021 | Linux 3.10–5.13; FreeBSD 12.2 and later | Distributed spare RAID (dRAID) vdevs, the compatibility pool property and InfluxDB statistics output; CPU and memory hotplug support; acltype=posixacl renamed acltype=posix, with the old name kept as an alias |
| 2.2 | October 13, 2023 | Linux 3.10–6.5; FreeBSD 12.2 and later | Block cloning, Linux container support, a scrub error log, BLAKE3 checksums, corrective zfs receive, vdev properties, and user properties for vdevs and pools; fully adaptive ARC; hardware-accelerated SHA-2 checksums. Designated the long-term support release. |
| 2.3 | January 14, 2025 | Linux 4.18–6.12; FreeBSD 13.3 and 14.0–14.2 | RAID-Z expansion, fast deduplication, Direct I/O, JSON output and file and directory names up to 1,023 characters |
| 2.4 | December 18, 2025 | Linux 4.18–6.18; FreeBSD 14, 15 and 16 | Default user, group and project quotas; uncached I/O as a fallback for unaligned Direct I/O; unified allocation throttling to reduce vdev fragmentation; faster AES-GCM encryption using AVX2; ZFS intent log (ZIL) placement on special vdevs; physical zfs rewrite that preserves block birth times; scrubbing of specific time ranges; arcstat and arc_summary renamed zarcstat and zarcsummary |
OpenZFS numbers releases as MAJOR.MINOR.PATCH. Minor releases, planned roughly once a year, add new functionality such as feature flags, properties and subcommands, while patch releases contain bug fixes, minor performance improvements and support for new kernels. A designated long-term support (LTS) branch receives backported fixes for at least two years, but not support for kernels released after it; as of November 2026[update], the LTS release is OpenZFS 2.2. OpenZFS 2.2 was developed by 202 contributors, 2.3 by 134 and 2.4 by 121.
Several maintenance releases have fixed serious regressions or data corruption bugs. ZFS on Linux 0.7.7, released in March 2018, contained a regression that could leave some files without directory entries when many files were copied into a directory, so that they appeared to have been lost; 0.7.8, released in April 2018, removed the responsible change, and the developers said that the data itself had not been lost. Version 0.7.10 was followed a week later by 0.7.11, which reverted a change that had caused "attempt to access beyond the end of device" errors. OpenZFS 2.1.1 (September 2021) fixed a data integrity problem when an underlying disk returned an error, 2.0.7 and 2.1.2 (December 2021) fixed data corruption when sending and receiving between pools with different sector sizes, and 2.1.11 (April 2023) fixed a possible data corruption bug.
Maintenance releases have also changed the supported platforms and occasionally added features. OpenZFS 2.2.5 (August 2024) raised the minimum supported Linux kernel from 3.10 to 4.18, and 2.2.7 (December 2024) removed support for FreeBSD releases older than 13.0. OpenZFS 2.3.4 (August 2025) added the zfs rewrite subcommand, which rewrites the blocks of files without changing their contents, as if they had been read and written back, so that they are stored according to the dataset's current properties; it can be used to rewrite blocks written before a RAID-Z expansion at the vdev's new width. The 2.4 maintenance releases added support for Linux 7.0 in 2.4.2 (May 2026) and Linux 7.2 in 2.4.4 (August 2026).
In November 2023, shortly after the release of OpenZFS 2.2.0, users reported a silent data corruption bug. Block cloning, which had been introduced in 2.2.0, was initially suspected and was disabled in OpenZFS 2.2.1, but the cause was found to be an incorrect check of whether a dnode was dirty. The fault was also present in the 2.1 series and possibly dated back to the original release of the ZFS source code; it had become easier to trigger after changes to the cp command in GNU Core Utilities 9.x. The fix was released in OpenZFS 2.2.2 and 2.1.14.
On August 21, 2026, maintenance releases 2.4.4, 2.3.9 and 2.2.11 were published together, fixing a high-severity vulnerability (CVE-2026-79619) in which several authorization checks on Linux accepted capabilities held only inside an unprivileged user namespace. A local user with access to the ZFS control device could use this to perform root-only operations, including creating, importing and destroying pools. All releases from 0.7.0 onward were affected.
Originally, version numbers of the pool and file system were incremented as new features were introduced, in order to designate the on-disk file system format and available features. This worked well when a single entity controlled the development of ZFS, and this versioning scheme is still in use with the ZFS in Oracle Solaris.
In a more distributed development model, having a single version number is far from ideal as all implementations of OpenZFS would need to agree on all changes to the on-disk file system format. The solution selected by OpenZFS was to introduce feature flags as a new versioning system that tags on-disk format changes with unique names, and supports both completely independent format changes and format changes that depend on each other. A pool can be moved and used between OpenZFS implementations as long as all feature flags in use by the pool are supported by both implementations.: 20, 26–27 : 2–3
In OpenZFS, the pool version is permanently set to 5000, signifying that the pool indicates new features by setting or unsetting ZFS feature flags rather than by incrementing the pool version. The number 5000 was chosen because it is expected to never conflict with version numbers given by Oracle. Legacy version numbers still exist for pool versions 1–28. Future on-disk format changes are enabled / disabled independently via these feature flags.
Legacy version numbers still exist for pool versions 1–28, and are implied by the pool version 5000; the initial proposal was to use 1000 as the pool version.: 4 Future on-disk format changes are enabled and disabled independently via feature flags.
Feature flags are exposed as pool properties, following these naming scheme rules:: 4
For example, feature@com.foocompany:async_destroy is a valid property name, and it could be shortened to feature@async_destroy.: 4
Each pool feature can be in either disabled, enabled, or active state. Disabled features are those that will not be used, and no on-disk format changes will be made; as a result, such features are backward-compatible. Enabled features are those that will be used, no on-disk format changes have been made yet, but the software may make the changes at any time; such features are still backward-compatible. Active features are those that have made backward-incompatible on-disk format changes to the pool.: 5
When any pool feature is enabled, legacy version of the pool is automatically upgraded to 5000 and any other prerequisite features are also enabled. By default, new pools are created with all supported features enabled. In general, state of a feature can be changed from active back to enabled, undoing that way performed on-disk format changes and making the pool compatible again with an older OpenZFS implementation; however, for some features that might not be possible.: 5, 9
On-disk format changes can be associated with either features for write or features for read. The former are the features that an OpenZFS implementation must support to be capable of writing to the pool, while supporting such features is not mandatory for opening the pool in read-only mode. The latter are the features that an OpenZFS implementation must support to be able to read from the pool or to just open it, because opening a pool is not possible without actually reading from it.: 7
For example, async_destroy feature adds a new on-disk data structure to keep track of freed datasets, but an OpenZFS implementation does not need to know about this data structure to access the pool in read-only mode. Additionally, writing to a pool that has some features in active state is not possible by an OpenZFS implementation that does not support the same features.: 7–8
A list of feature flags and which operating systems support them is available from the OpenZFS documentation Web site (here the old Open-ZFS.org Web site)
Since OpenZFS 2.1, the compatibility pool property can restrict a pool to a named set of features, so that it remains importable by an older release, another operating system or a boot loader.
Historically, OpenZFS has been implemented as a core ZFS code, with each operating system's team adapting it to fit into their projects. This led in some cases to feature stagnation and divergence of features and command lines, as different operating systems developed divergent features and bug fixes, often for a single platform rather than across all platforms. Over time, new feature development shifted from Illumos to Linux. These new features and fixes then had to be backported to Illumos before they could be re-ported for FreeBSD. But this was difficult because the Linux version also included many smaller changes, which were hard to disentangle.
In 2018, it was agreed that OpenZFS development would be overhauled to remedy these issues. Rather than try to import all the Linux changes to other platforms piecemeal, the entire Linux ZFS code would be 'pivoted' as a whole, with other platforms being based on the more actively developed Linux version. A wide range of ported and new features, including many long-desired enhancements, would also be rolled out or ported across platforms, and future changes would be discussed across platforms before being implemented. The plans included appropriate porting layers to prevent Linux, GPL or Linux-KPI shim code from being introduced to other platform kernels.
The list of features in progress or ported for OpenZFS 2.0 was lengthy, and included the following; some were completed in later releases: