Managing outdated pull requests is time-consuming. Mergify's Merge Queue automates your pull request management & merging. It's fully integrated to GitHub & coordinated with any CI. Start focusing on code. Try Mergify for free. Learn more →
Zfs Alternatives
Similar projects and alternatives to zfs
-
sanoid
Policy-driven snapshot management and replication tools. Using ZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.) Primarily intended for Linux, but BSD use is supported and reasonably frequently tested.
-
Mergify
Tired of breaking your main and manually rebasing outdated pull requests?. Managing outdated pull requests is time-consuming. Mergify's Merge Queue automates your pull request management & merging. It's fully integrated to GitHub & coordinated with any CI. Start focusing on code. Try Mergify for free.
-
-
-
7-Zip-zstd
7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard
-
-
RocksDB
A library that provides an embeddable, persistent key-value store for fast storage.
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
-
-
-
-
Moby
Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
-
-
aero
Aero is a new modern, experimental, UNIX-like operating system following the monolithic kernel design. Supporting modern PC features such as long mode, 5-level paging, and SMP (multicore), to name a few. (by Andy-Python-Programmer)
-
-
-
zfs
OpenZFS on Linux and FreeBSD [Moved to: https://github.com/openzfs/zfs] (by zfsonlinux)
-
-
-
InfluxDB
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
zfs reviews and mentions
-
ZFS for Dummies
Damn good question. I don’t have time to search for duplicates myself right now, but you can look through/ask the mailing list: https://zfsonlinux.topicbox.com/groups/zfs-discuss (looks weird, but this is a legit web front end for the mailing list) and the github issues: https://github.com/openzfs/zfs/issues
-
zrepl: A one-stop, integrated solution for ZFS replication
There are definitely annoyances, but there are workarounds too; you can add additional vdevs to expand the whole pool if you want, and data is striped across them; it even lets you mix and match different raids if you really want to for some reason.
There's some current work to add a disk to existing vdevs, and I think even a semi-working PR for it now: https://github.com/openzfs/zfs/pull/15022. Hopefully in theory that will make ZFS a little less frustrating.
-
My SSD suddenly died. I only lost 10 minutes of data, thanks to ZFS
> the cost, besides having to actually create the file systems, is that moving data between them isn't instant.
No more the case after block cloning support goes production: https://github.com/openzfs/zfs/pull/13392
-
OpenZFS – Incremental add of disks to existing RAIDZ
The big news here seems to be that iXsystems (the company behind FreeNAS/TrueNAS) is sponsoring this work now. This PR supersedes ones that was opened back in 2021
https://github.com/openzfs/zfs/pull/12225#issuecomment-16101...
-
FreeBSD Bhyve Virtualization
I seem to remember zvol having known performance issues that were improved greatly in the latest openzfs release.
If you read https://github.com/openzfs/zfs/issues/11407
It should be in there somewhere
-
ZFS 2.2.0 (RC): Block Cloning merged
https://github.com/openzfs/zfs/pull/13392/files#diff-295f77b...
I believe it needs one such entry in RAM for each duplicated 128kB memory block. Not sure what sizeof(avl_node) is but likely around 32B. So in that case one brt_entry needs 48B RAM per 128kB data block.
One terabyte of deduplicated disk space thus needs 1e12/128e3*48 = 375MB RAM.
Also see this issue: https://github.com/openzfs/zfs/issues/405
> It is in FreeBSD main branch now, but disabled by default just to be safe till after 14.0 released, where it will be included. Can be enabled with loader tunable there.
> more code is needed on the ZFS side for Linux integration. A few people are looking at it AFAIK.
I don't think so. The memory management stuff is pretty well abstracted; on FBSD it just glues into UMA pretty transparently, it's just on Linux there's a lot of machinery for implementing our own little cache allocating because Linux's kernel cache allocator is very limited in what sizes it will give you, and sometimes ZFS wants 16M (not necessarily contiguous) regions because someone said they wanted 16M records.
The ZoL project lead said at one point there were a variety of reasons this wasn't initially done for the Linux integration [1], but that it was worth taking another look at since that was a decade ago now. Having looked at the Linux memory subsystems recently for various reasons, I would suspect the limiting factor is that almost all the Linux memory management functions that involve details beyond "give me X pages" are SYMBOL_GPL, so I suspect we couldn't access whatever functionality would be needed to do this.
I could be wrong, though, as I wasn't looking at the code for that specific purpose, so I might have missed functionality that would provide this.
[1] - https://github.com/openzfs/zfs/issues/10255#issuecomment-620...
> I am looking forward to the Direct IO speed improvements for NVMe drives with https://github.com/openzfs/zfs/pull/10018
See also "Scaling ZFS for NVMe" by Allan Jude at EuroBSDcon 2022:
-
A note from our sponsor - Mergify
blog.mergify.com | 22 Sep 2023
Stats
openzfs/zfs is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of zfs is C.