OmniOS 151032 stable

[gea]

OmniOS 151032 is the next stable release and will be available later this year.
All new improvements for the next stable are going into the OmniOS bloody 151031 version until then.

If you want to try the bloody 151031, you need the newest napp-it 18.12t or 19.06 pro.
Without a napp-it update you see Perl errors in some menus like Users.

 

[gea]

Developers have confirmed that native ZFS encryption will be in OmniOS 151032 stable. For first tests of native ZFS encryption you can use 151031 bloody (the dev version for 151032) that can be updated then later this year to 151032 stable.

 

[gea]

Release notes of OmniOS 151032
omniosorg/omnios-build

 

[gea]

OmniOS 151032 stable is out
This is the most feature rich update for Open-ZFS and OmniOS ever.
download: Downloads

Release notes
omniosorg/omnios-build

Update
http://www.napp-it.org/doc/downloads/setup_napp-it_os.pdf

New Open-ZFS features:
- native ZFS encryption
- raw zfs send of locked and encrypted filesystems
- sequential/sorted resilver (can massively reduce resilver/scrub time
- manual and auto trim for the SSDs/NVMes in a pool
- Allocation classes for metadata, dedup and small io (mixed pool from disk/SSD/NVMe)
see https://www.napp-it.org/doc/downloads/special-vdev.pdf
a warning at this point: a zpool remove of a special vdev with a different ashift than the pool crashes Illumos/ZoL
- force ashift on zpool create/add

OmniOS related
-updated NVMe driver (with basic support for NVMe/U.2 hotplug)
-updates for newer hardware
-installer supports UEFI boot

- SMB 3.02 (kernelbased SMB) with many new features
see illumos/illumos-gate
- improvement for LX/ Linux zones, newer Linux distributions
- improvements for Bhyve
- improvements to the Enlightened Hyper-V drivers for running under Hyper-V or Microsoft Azure.

Napp-it 19.dev/19.h2.x supports the new features

 

[nle]

Thanks for the update.

I just upgraded, and all seems fine, except my console is throwing these errors when accessing SMB shares via macOS (seems to work fine from the clients point of view):

Nov 5 19:15:43 <hostname> smbd[572]: Can't get SID for ID=0 type=0, status=-9977
Nov 5 19:16:12 <hostname> smbd[572]: Can't get SID for ID=0 type=1, status=-9977

Google does not really give much that makes sense.

 

[gea]

The SMB server on Illumos got a huge bunch of new features this summer. You will not find much Google entries about. But when i connect from OSX (Catalina 15.1 in this case) I do not get any console errors, not with local users, not with AD users.

Are there any id-mappings. Did this happen with AD or local users.

 

[nle]

No AD, just local users. Also connecting from latest macOS.

Pretty standard setup (napp-it vm), only one SMB user.

 

[gea]

At the moment I have no idea why you have the error messages while I have not. Only suggestion would be a mail to illumos-discuss to ask if others have the same problem (SMB developpers may read as well)

 

[nle]

Thanks. Made a post

 

[gea]

For a production system, you should wait some days for an update as there seems to be some newly found bugs in Open-ZFS in general (maybe the usual suggestion for an update with that many new features) like crash after an update or crash after remove of a special vdev with a different ashift.

Check Topicbox and
Issues - illumos some days prior such a huge update like with current Open-ZFS.

(This is not Illumos only, bugs are in Open-ZFS so in current ZoL as well)

 

[sth]

Hi Gea,
I have the same error in my console too.

Nov 10 07:30:32 fs01 smbd[590]: [ID 617204 daemon.error] Can't get SID for ID=0 type=1, status=-9977
Nov 10 07:32:23 fs01 mountd[656]: [ID 869243 daemon.warning] invalid access list entry: 192.168.110.0/24/tank2/images
Nov 10 07:35:24 fs01 smbd[590]: [ID 617204 daemon.error] Can't get SID for ID=0 type=1, status=-9977
Nov 10 07:35:25 fs01 mountd[656]: [ID 869243 daemon.warning] invalid access list entry: 192.168.110.0/24/GRAID/images
Nov 10 07:35:34 fs01 smbd[590]: [ID 617204 daemon.error] Can't get SID for ID=0 type=1, status=-9977

Both of these filesystems that are showing the errors don't have SMB shares enabled but do have NFS enabled. Not sure if that helps you understand what's causing it.

I'm running version 19.Dev 05.nov.2019 on OmniOS v11 r151032.

 

[gea]

You should add this to the thread from nle above

Topicbox

 

[nle]

I'm also running NFS shares on the same ZFS file systems as the SMB, but the error occurs when accessing the share with an SMB client. If no SMB client, no errors.

 

[gea]

There are some critical fixes for Open-ZFS available for OmniOS 151032
omniosorg/omnios-build

Install via "pkg update"
A reboot is required

 

[sth]

upgraded this am no problems. Thanks for the update.

 

[nle]

I still have issues, I don't think this update fixed anything related to this anyway.

 

[sth]

I still have the issues with the SMB items logged to the console, but theres more of a serious fix in this build. There wasn't anything new introduced I meant, rather than all issues were fixed.

 

[nle]

Looks like the issue can be solved by disabling and enabling the SMB share.

EDIT: I lied, it did not.

 

[Bronko]

Ok, time to upgrade from OmniOS 151030 to OmniOS 151032 on backup system at first.

Right before upgrade re-loaded napp-it ver. 19.06 via WebGUI and going from 19.06f Pro to 19.06h Pro.

After booting in to new BE I got these via local E-Mail to root:

...
Subject: Cron <root@btanker> perl /var/web-gui/data/napp-it/zfsos/_lib/scripts/auto.pl
...
X-Cron-Job-Name: perl /var/web-gui/data/napp-it/zfsos/_lib/scripts/auto.pl
X-Cron-Job-Type: cron
...
Tty.c: loadable library and perl binaries are mismatched (got handshake key 10080080, needed ff80080)

Napp-it ist working but my TLS E-Mail doesn't worked once more, so I have to re-setup it like on OmniOS 151022 at first.
official: TLS E-Mail on napp-it
TLS-Email is fine now.

Any further problems to await or time to upgrade main storage system?

Ah, don't forget to run:

zpool upgrade <pool_name>

for new features.

Encryption is enabled at all pools (feature@encryption -> enabled), but 'Encryption ZFS >= V.30' keeps 'not available' on Creating new 'ZFS Filesystems'.
Any steps still pending?

 

[gea]

OmniOS 151032 is much newer (oct 2019) than napp-it 19.06 (june 2019). While I have backported basic compatibility (to make it working with 19.06) I have not added support for newer features so 19.06 only supports encryption in Oracle Solaris with pool >=v30.

Support for new features is in 19.dev (the pre release for 20.01) and in 19.10 home.

btw
After a napp-it login/logout the new Perl modules for 151032 are loaded so the Tty message should disappear automatically.