![]() In the end I migrated from Ubuntu to this setup in a few hours, where for example I have 802.3ad bonding, SAMBA with fruit extensions for macOS compatibility, suspend support, etc. In the end I chose RHEL+kABI based on the logic above (that FreeBSD in principle is the best, but kABI is directly from upstream, same with FreeBSD) and also because of laziness. I almost make the choice of TrueNAS CORE as I have past experience with FreeNAS briefly, and presumably takes lesser time to setup comparing to vanilla FreeBSD. So of course I'd prefer minimal time investment both in terms of migration and potential future maintenance.įreeBSD-based OS are one of the top choice, as it doesn't have any of the drama induced by the incompatible license of OpenZFS and Linux kernel. In my case, it is just a personal data server. One important factor I didn't mention yet is how long it would takes for me to migrate. (Edit: at time of accessment, it is recently out of beta.) TrueNAS SCALE is dismissed because it was still in beta. Proxmox is dismissed because it is overkill for my application. I observed the problems in 21.10 mentioned above, and experienced problem in 21.04 with mysterious checksum failing after scrub (data corruption always at snapshot so fortunately I can just delete the problematic snapshot.) It also sometimes crashed after suspend. I dismissed Ubuntu as this is where I was migrating away from. But this should not be taken as a dismissal of other implementations on other OSes, but just my ignorance.) Also because I don’t know much about the others say including support status. So from this perspective only Linux and FreeBSD are the “main branch” here. I mean the recent-ish presentation about OpenZFS organization and how ZFSOnLinux is leading in recent years leading to the merge of Linux and FreeBSD ports, which will later include macOS too. (Edit: Sorry, this list contains only Linux or FreeBSD kernel, which is currently the most active in the OpenZFS community. This has been mentioned both in the original post and here.) ![]() (edit: be careful when RHEL new minor version released while upstream doesn’t yet. And using kABI-tracking kmod is also using OpenZFS directly from upstream. The primary logic in this suggestion is that using FreeBSD is essentially using OpenZFS directly from upstream. This has advantage over DKMS where it is pre-compiled by the upstream (and in principle verified by them to be working correctly.) I personally experienced some problems with using DKMS OpenZFS on Arch Linux so the kABI version sounds like a good alternative to me. While RHEL does not support OpenZFS themselves, upstream OpenZFS officially support kABI-tracking kmod for RHEL. A kABI-tracking kmod package contains a kernel module that is compatible with a given kABI, that is, for a given major and minor release of the EL kernel. Each major and minor RHEL kernel release has a set of in-kernel symbols that are whitelisted. The Kernel Application Binary Interface (kABI) is a set of in-kernel symbols used by drivers and other kernel modules. This is an interesting choice so here's some further explanation: RHEL (RedHat Enterprise Linux) with kABI-tracking kmod suggested here. Proxmox, Linux based, officially supporting OpenZFS, backed by Proxmox Server Solutions GmbH. supporting OpenZFS natively, presumably backed by all companies using it at down-stream including iX systems TrueNAS SCALE is Linux based, still in beta at time of assessment (edit: very recently out of beta.) TrueNAS, officially supporting OpenZFS, backed by iX systems ![]() Ubuntu, officially supporting OpenZFS, backed by Canonical Here’s the summary of options after asking people for options in that thread.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |