OmniOS 151032 stable

Discussion in 'Solaris, Nexenta, OpenIndiana, and napp-it' started by gea, Jun 13, 2019.

  1. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    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.
     
    #1
  2. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    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.
     
    #2
    T_Minus likes this.
  3. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    #3
  4. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    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
     
    #4
  5. nle

    nle Member

    Joined:
    Oct 24, 2012
    Messages:
    183
    Likes Received:
    6
    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):
    Code:
    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.
     
    #5
  6. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    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.
     
    #6
    nle likes this.
  7. nle

    nle Member

    Joined:
    Oct 24, 2012
    Messages:
    183
    Likes Received:
    6
    No AD, just local users. Also connecting from latest macOS.

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

    [​IMG]
     
    #7
  8. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    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)
     
    #8
    nle likes this.
  9. nle

    nle Member

    Joined:
    Oct 24, 2012
    Messages:
    183
    Likes Received:
    6
    Thanks. Made a post :)
     
    #9
  10. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    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)
     
    #10
    Last edited: Nov 7, 2019
    sth and nle like this.
  11. sth

    sth Active Member

    Joined:
    Oct 29, 2015
    Messages:
    249
    Likes Received:
    37
    Hi Gea,
    I have the same error in my console too.

    Code:
    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.
     
    #11
  12. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    You should add this to the thread from nle above

    Topicbox
     
    #12
    nle likes this.
  13. nle

    nle Member

    Joined:
    Oct 24, 2012
    Messages:
    183
    Likes Received:
    6
    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.
     
    #13
  14. gea

    gea Well-Known Member

    Joined:
    Dec 31, 2010
    Messages:
    2,243
    Likes Received:
    743
    There are some critical fixes for Open-ZFS available for OmniOS 151032
    omniosorg/omnios-build

    Install via "pkg update"
    A reboot is required
     
    #14
    Last edited: Nov 16, 2019 at 3:50 AM
    sth likes this.
  15. sth

    sth Active Member

    Joined:
    Oct 29, 2015
    Messages:
    249
    Likes Received:
    37
    upgraded this am no problems. Thanks for the update.
     
    #15
Similar Threads: OmniOS 151032
Forum Title Date
Solaris, Nexenta, OpenIndiana, and napp-it Checking complete disks for errors in OmniOS Nov 9, 2019
Solaris, Nexenta, OpenIndiana, and napp-it Intel X553 driver for OmniosCE Sep 19, 2019
Solaris, Nexenta, OpenIndiana, and napp-it Peformances problem using Resolve with folder on Omnios ZFS server Aug 12, 2019
Solaris, Nexenta, OpenIndiana, and napp-it OmniOS 151030 VM (ESXi) with LSI 9400-8i Tri-Mode HBA freezing up Aug 10, 2019
Solaris, Nexenta, OpenIndiana, and napp-it SMB3 development on Illumos (NexentaStor, OmniOS, OpenIndiana and SmartOS) Aug 10, 2019

Share This Page