From: "gea@napp-it.org" <gea@napp-it.org>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: Illumos future and compatibility with Open-ZFS
Date: Fri, 6 Sep 2024 13:53:21 +0200 [thread overview]
Message-ID: <2bbc17be-ebb2-4b90-98ef-b804fa57b334@napp-it.org> (raw)
In-Reply-To: <17229544470.58aA.943111@composer.illumos.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]
*There are very good reasons to prefer Illumos ZFS over Open-ZFS like*
- Stability
especially with OmniOS and a bloody,stable,long term stable and a
repository for each
- Easyness
there is one current Illumos with one current ZFS
not the versions chaos of Open-ZFS with a douzen of distributions, each
with its own problems and update paths to Open-ZFS newest.
- Efficiency
the deep OS Integration makes ZFS on Illumos very resource efficient
- Services like Kernel SMB or Comstar iSCSI
especially the kernelbased SMB server is for me the only thinkable
alternative to a Windows Server when it comes to ACL compatibility or
simplicity. SAMBA is a pain compared to the kernelbased SMB.
*But now the great BUT*
Open-ZFS is where the music plays with a lot of new features like ZSTD,
Draid, Raid-Z Expansion or Fast Dedup and more to come. Lack of them
means that you can no longer import a current Open-ZFS pool in Illumos
and more important, these are killer features in some cases and therefor
a criteria to use or not to use Illumos.
If you look at the flavours of "Open-ZFS" with independent repositories,
there are mainly three:
1. Open-ZFS Master (BSD, Linux), currently 2.2.6
no longer a common roof for "Open" ZFS development but the place where
development happens
2. Based on an older Open-ZFS and incompatible to newest Open-ZFS
Illumos and Qnap
3. Open-ZFS on Windows (and OSX), beta/release candidates
This is fork of Open-ZFS that is updated to Open-ZFS Master from release
candidate to release candidate. While I suppose Jorgen Lundman
(maintainer) originally planned a full integration of Windows ZFS
directly into Open-ZFS, it seems that he now intends to use Open-ZFS
simply as upstream, just like Illumos was upstream for a long time for
BSD and Linux.
*
I want to ask.*
When I look at the Illumos Issue tracker, I see mainly small fixes,
hardly new features does not matter regarding Illumos services or
Open-ZFS features. I suppose number of devs is limited.
*What is the future idea of Illumos? *
-Be like Qnap and do not care about Open-ZFS and add one or the other
new feature from time to time?
-Try something like BSD or Windows or OSX (switch to Open-ZFS as full
upstream)?
I know a switch to Open-ZFS as upstream is not easy and can last and I
am not even sure if it is really wanted or possible with current
resources. But maybe this is the only option to make Illumos future proof?
Gea
[-- Attachment #2: Type: text/html, Size: 3829 bytes --]
next prev parent reply other threads:[~2024-09-06 11:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 20:50 shutdown hang with zpools on ISCSI devices Carsten Grzemba
2024-08-05 21:46 ` [discuss] " Joshua M. Clulow
2024-08-06 5:17 ` Carsten Grzemba
2024-08-06 5:29 ` Carsten Grzemba
2024-08-06 5:46 ` Joshua M. Clulow
2024-08-06 6:36 ` Carsten Grzemba
2024-08-06 6:46 ` Joshua M. Clulow
2024-08-06 14:27 ` Carsten Grzemba
2024-08-06 15:16 ` Carsten Grzemba
2024-08-06 19:04 ` Joshua M. Clulow
2024-09-06 11:53 ` gea [this message]
2024-09-07 8:30 ` [discuss] Illumos future and compatibility with Open-ZFS Joshua M. Clulow
2024-09-07 11:12 ` Gea
2024-09-07 16:38 ` Joshua M. Clulow
2024-09-07 21:37 ` Gea
2024-09-08 8:50 ` Jorge Schrauwen
2024-09-08 9:55 ` d
2024-09-09 10:41 ` Gea
2024-09-09 11:32 ` Toomas Soome
2024-09-09 9:29 ` Volker A. Brandt
2024-09-09 9:49 ` bronkoo
2024-09-09 11:13 ` Jorgen Lundman
2024-09-09 12:27 ` Gea
2024-09-09 14:47 ` gea
2024-09-09 19:29 ` Joshua M. Clulow
2024-12-11 8:47 ` zt958bjm via illumos-discuss
2024-12-11 8:56 ` zt958bjm via illumos-discuss
2024-12-11 9:01 ` zt958bjm via illumos-discuss
2024-12-11 10:09 ` Jorgen Lundman
2024-12-11 12:17 ` zt958bjm via illumos-discuss
2024-09-07 14:32 ` Miles Nordin
2024-08-05 22:45 ` [discuss] shutdown hang with zpools on ISCSI devices John D Groenveld
2024-08-05 22:55 ` Joshua M. Clulow
2024-08-06 15:56 ` Gordon Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2bbc17be-ebb2-4b90-98ef-b804fa57b334@napp-it.org \
--to=gea@napp-it.org \
--cc=discuss@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).