openzfs and the exact version lists behind its support claim
OpenZFS on Linux and FreeBSD
At a glance
- What is it?
- OpenZFS on Linux and FreeBSD is a C tree that published three release lines on the same day and states support as fixed lists of kernels, distributions and FreeBSD releases. What those lists commit to, and exactly where they stop.
- Who is it for?
- Adopt OpenZFS when your kernel and distribution appear by exact version in the supported lists and you can name a release line such as zfs-2.4.4. Hold off if you run a freshly promoted stable kernel, a rolling distribution, or any platform outside Linux and FreeBSD.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- openzfs/zfs12,562 ★ · +98
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| openzfs/zfs | 12.5k | 12.6k |
98 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Longterm kernels are covered, stable kernels wait for the next release
The support policy splits kernel.org kernels into two tiers with different promises. All longterm kernels from kernel.org are supported. Stable kernels are usually supported in the next OpenZFS release, which is a promise about a future build rather than about your machine today. The named longterm list is 6.18, 6.12, 6.6, 6.1, 5.15 and 5.10.
The consequence for an administrator is concrete and not abstract. On a kernel that has already reached longterm status you are inside the supported set. On the newest stable kernel you are outside it until a subsequent OpenZFS release ships, so a machine that auto-updates its kernel can arrive at a pairing nobody has written down yet, and the phrase usually leaves room for the case where a build is skipped.
Each distribution gets a short list of exact point releases
Support is stated per distribution as a list of precise versions rather than as a family. Red Hat Enterprise Linux is covered on the full or maintenance support tracks, and that includes RHEL-compatible systems such as AlmaLinux OS and Rocky Linux; the named releases are 8.10, 9.7 and 10.1. Ubuntu coverage is LTS only, at 26.04 Resolute, 24.04 Noble and 22.04 Jammy. Debian covers stable and LTS releases, at 13 Trixie, 12 Bookworm and 11 Bullseye.
Because the granularity is the point release, a patched 9.6 host is not literally the same string as 9.7, and matching your box against these lines is the fastest way to find out whether you are inside the tested set or inferring your way through it.
Outside those lists there is one sentence of guidance, not a commitment
Everything not named above is handled by a single line: generally, if a distribution is following an LTS kernel, it should work well with OpenZFS. That is a reasonable heuristic and it is not a tested matrix entry.
The consequence is that a rolling distribution, an Arch-style current kernel, or a vendor kernel outside the named versions inherits the burden of proving the combination yourself. There is no per-distro package list, no catalogue of known-broken pairings, and nothing here about which distributions are exercised in CI. The RHEL wording narrows things further still, since a RHEL-compatible build sitting on a track that has dropped out of maintenance is outside the promise even when its kernel is recent enough.
The README contains no install command at all
The installation section is a single paragraph and a link to the Getting Started page in the openzfs documentation. There is no package name, no distribution-specific install line, no configure invocation anywhere in the file. That is a reasonable choice for a project whose deliverable shape differs across kernels and distributions, but the cost falls on the reader, because this repository is a code drop rather than an installation guide.
The information is also split across four destinations rather than kept in one place: the documentation site for using and developing the repo, zfsonlinux.org for Linux release information and links, a mailing lists page, and the OpenZFS site for conference videos and information on other platforms. Expect to leave the repository to learn how to install it.
Linux and FreeBSD only, whatever the project name suggests
The project describes itself as an advanced file system and volume manager originally developed for Solaris and now maintained by the OpenZFS community, and this repository is stated to hold the code for running it on Linux and FreeBSD. Anything else belongs elsewhere, and the OpenZFS site is named as the place for information on other platforms, listing illumos, OSX and Windows among them.
So the project name is wider than the tree it describes. A reader who arrives here looking for the Solaris original, or for illumos or Windows, finds only a link and the community mailing lists as a bridge. On FreeBSD the support contract is defined differently from Linux: it tracks which releases are still receiving security support, currently 15.1 and 14.4.
CDDL with UCRL-CODE-235197, and no license field to read it from
The licensing statement is short: OpenZFS is released under a CDDL license, with details in the NOTICE, LICENSE and COPYRIGHT files and the identifier UCRL-CODE-235197 given for the record. The repository metadata itself asserts no license, so anything that reads only a license field reports nothing back, and the actual terms have to be pulled out of three files sitting in the root.
Those filenames are the point. COPYRIGHT and NOTICE exist to record what upstream code came from and under what terms, which matters more here than in a typical single-origin project, because the codebase descends from Solaris work and carries contributions from many outside sources. If you need the terms for redistribution or compliance, the file list is where you start, not the repository header.
An autotools tree that builds a kernel module and userspace tools together
The root carries configure.ac, Makefile.am and autogen.sh, so the build runs through autotools rather than a language-specific package manager. The subdirectories show what comes out: cmd/ for the command line tools, lib/ for the library layer, module/ for the kernel module, udev/ for device rules, man/ for manual pages, tests/ for the test suite, and rpm/ for packaging, alongside contrib/, etc/ and copy-builtin.
Because the loadable module and the userspace commands that talk to it are produced from a single tree, the kernel version question reaches the build itself, not only the running system. The project keeps RELEASES.md, NEWS, SECURITY.md, TEST and AUTHORS beside the code, so release history and security contact live in the same tree rather than in a separate tracker.
Editorial conclusion
Adopt OpenZFS when your kernel and distribution appear by exact version in the supported lists and you can name a release line such as zfs-2.4.4. Hold off if you run a freshly promoted stable kernel, a rolling distribution, or any platform outside Linux and FreeBSD. Before deploying, work through the Getting Started page yourself, since the README carries no install command, and read NOTICE, LICENSE and COPYRIGHT for the CDDL terms under UCRL-CODE-235197.
Frequently asked questions
What are the key differences between ZFS and OpenZFS?
OpenZFS is described as an advanced file system and volume manager originally developed for Solaris and now maintained by the OpenZFS community, and this repository holds the code for running it on Linux and FreeBSD. Information on other platforms, including illumos, OSX and Windows, is pointed at the OpenZFS site instead of this tree.
What are the downsides of using ZFS?
The constraint the project states is its support window: all longterm kernels from kernel.org are supported while stable kernels are usually supported in the next OpenZFS release, and the named longterm list stops at 6.18, 6.12, 6.6, 6.1, 5.15 and 5.10. The README also carries no install command of its own and sends installation to the Getting Started page.
Is ZFS better than Ext4?
The repository makes no comparison with Ext4 or with any other filesystem. What it does state is the supported set: longterm kernel versions, RHEL 8.10, 9.7 and 10.1 on full or maintenance tracks, Ubuntu LTS releases, Debian stable and LTS, and FreeBSD releases still receiving security support at 15.1 and 14.4.
Which filesystem is better for freeBSD, UFS or ZFS?
For FreeBSD the project states that all releases receiving security support are supported by OpenZFS and names 15.1 and 14.4 as the supported releases. It offers no comparison between OpenZFS and UFS, so that comparison has to be made outside this repository.
Official sources
Where developers are discussing it
Posts on Hacker News, dev.to and Lobsters that link to this repository, found by our scan of those communities. 0 in the last 30 days; newest first.
- ZFS Object Storage (proof of concept)Hacker News · Oct 12, 2026 · 3 points · 0 comments
- 99.26% storage reduction with exact reconstruction on 100-version repoHacker News · Sep 28, 2026 · 2 points · 0 comments
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/openzfs-zfs)Star history chart for your README
[](https://hysenlabs.com/projects/openzfs-zfs)Was this useful?