public inbox for discuss@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Gea <gea@napp-it.org>
To: discuss@lists.illumos.org
Subject: Re: [discuss] Illumos future and compatibility with Open-ZFS
Date: Sat, 7 Sep 2024 13:12:31 +0200	[thread overview]
Message-ID: <71c95212-1882-4739-a00f-a6d8baf1624f@napp-it.org> (raw)
In-Reply-To: <CAEwA5nKOOF=ZwUmnmSsX5V4coqRSygbJbVtat1dgtuXB7s2Tuw@mail.gmail.com>

Thank you for your detailled answer.

I understand the stabilty aspect and value it very high and indeed 
Illumos ZFS has not seen as many problems up to dataloss in 10 years as 
one or the other Linux ZFS distribution in the last year. Unlike Linux 
every Illumos distribution is up to date with a clear and easy way to 
update to newest or downgrade. The OmniOS model of a bloody (current 
Illumos), stable (a freeze every 6 months) and a long term stable, each 
with its own repository undelines this strong focus on stability. This 
is something I don't want to miss so preserve an independent fork. Using 
code from newest Open-ZFS master is surely not a good idea, the question 
is how to take over code from a stable branch ex 2.2.6 or better a 
former with a better stability like 2.2.3 or what TrueNAS is using as 
stable branch.

The real question from a user view is how to preserve compatibility with 
a ZFS pool from a current BSD, Debian, Ubuntu or TrueNAS and when to get 
important Open-ZFS features like ZSTD, Draid, Raid-Z exansion, Fast 
Dedup, direct io or higher limits ex on recsize and much more to come 
while value stability as item2. Stability and compatibility are not 
either or. Find a way to get newer Open-ZFS features including bugfix 
commits with the best achievable stability. Not to have newer ZFS 
features is not an option. Have your cake and eat it.

In a perfect world with endless resources you can check, include and 
maintain every of these features on your own including bugfixes when 
they become known but is this thinkable? I suppose no, so the 
consequence is that you loose compatibility and lack more and more newer 
ZFS features. In the end >95% of all ZFS users are now using Open-ZFS 
and with such many users problem rate is not as bad and bugs are fixed 
in a quite short time.

Maybe a staging model can be one solution like an older more stable 
Open-ZFS branch > Illumos testing > Illumos stable (similar to what 
current Illumos is), just like we see it in Open-ZFS or the OmniOS 
approach or in the Open-ZFS world with Open-ZFS forks on OSX or Windows. 
This would allow newest Open-ZFS features to appear with a delay but to 
appear for sure. Maybe newer long awaited bits like the recent NFS and 
SMB improvements have also a chance to appear in a Illumos testing 
branch for wider testings.

Just one idea but a workable idea how to follow Open-ZFS development is 
critical or user base will lower not from year to year but month to 
month. I can see it in my own user base where most of my former 
Solaris/OI/OmniOS users from some years ago switched to Open-ZFS in the 
meantime, some to Qnap most to Debian/Proxmox/TrueNAS/Ubuntu. This is 
why I also switched my new ZFS client-server cs web-gui to Open-ZFS (any 
OS) without further development in the Solaris/Illumos SE edition beside 
bugfixes.

Gea

  reply	other threads:[~2024-09-07 11:12 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               ` Illumos future and compatibility with Open-ZFS gea
2024-09-07  8:30                 ` [discuss] " Joshua M. Clulow
2024-09-07 11:12                   ` Gea [this message]
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=71c95212-1882-4739-a00f-a6d8baf1624f@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).