From oliver.weinmann at telespazio-vega.de Thu May 3 07:22:13 2018 From: oliver.weinmann at telespazio-vega.de (Oliver Weinmann) Date: Thu, 3 May 2018 07:22:13 +0000 Subject: [OmniOS-discuss] ZFS Dedup Message-ID: <767138E0D064A148B03FE8EC1E9325A20138E4145F@GEDAEVW01.a.space.corp> Hi, I always hear people saying don't use dedup with ZFS. Is that still the case? We use omnios as a VEEAM backup target and I would assume that using dedup would save a lot of disk space. Best Regards, Oliver [cid:Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png] Oliver Weinmann Head of Corporate ICT Telespazio VEGA Deutschland GmbH Europaplatz 5 - 64293 Darmstadt - Germany Ph: +49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 oliver.weinmann at telespazio-vega.de www.telespazio-vega.de Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png Type: image/png Size: 7535 bytes Desc: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png URL: From alka at hfg-gmuend.de Thu May 3 12:02:33 2018 From: alka at hfg-gmuend.de (Guenther Alka) Date: Thu, 3 May 2018 14:02:33 +0200 Subject: [OmniOS-discuss] ZFS Dedup In-Reply-To: <767138E0D064A148B03FE8EC1E9325A20138E4145F@GEDAEVW01.a.space.corp> References: <767138E0D064A148B03FE8EC1E9325A20138E4145F@GEDAEVW01.a.space.corp> Message-ID: <1bcf2a08-f884-4100-2d1a-b43543455de6@hfg-gmuend.de> I have not seen yet how much better dedup2 in Solaris is, but the current Open-ZFS implementation has the following problems - You must keep the dedup table in any case in RAM as this is realtime dedup otherwise a pool import or snapshot delete can last ages and performance can become unusable slow. - it requires a lot of RAM that you want to use for cachingand performance. Depending on data we talk about 1-5 GB RAM / TB dedup data(that is required additionally to your cache demands). - while you can enable on a filesystem level it operates on pool level. once activated you cannot disable beside a pool destroy. In the end, it may be a good idea but only when you have enough RAM and very high dedup rates (say >5-10) that are much better then the compress rate with lz4 Mostly the dedup rate is not good enough compared to a larger pool with lz4 dedup where you do not need to care about the dedup restrictions. gea @napp-it.org Am 03.05.2018 um 09:22 schrieb Oliver Weinmann: > > Hi, > > I always hear people saying don?t use dedup with ZFS. Is that still > the case? We use omnios as a VEEAM backup target and I would assume > that using dedup would save a lot of disk space. > > Best Regards, > > Oliver > > *Oliver Weinmann* > Head of Corporate ICT > > Telespazio VEGA Deutschland GmbH > Europaplatz 5 - 64293 Darmstadt - Germany > Ph: +49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 > oliver.weinmann at telespazio-vega.de > > www.telespazio-vega.de > > Registered office/Sitz: Darmstadt, Register court/Registergericht: > Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png Type: image/png Size: 7535 bytes Desc: not available URL: From cks at cs.toronto.edu Thu May 3 15:24:27 2018 From: cks at cs.toronto.edu (Chris Siebenmann) Date: Thu, 03 May 2018 11:24:27 -0400 Subject: [OmniOS-discuss] ZFS Dedup In-Reply-To: Your message of Thu, 03 May 2018 14:02:33 +0200. <1bcf2a08-f884-4100-2d1a-b43543455de6@hfg-gmuend.de> Message-ID: <20180503152427.1A51A5A02BD@apps1.cs.toronto.edu> > - while you can enable on a filesystem level it operates on pool > level. once activated you cannot disable beside a pool destroy. As far as I can tell from having looked at the code in the past, dedup is effectively inactive as soon as all data written while dedup was enabled has been removed. To simplify slightly: data blocks written while dedup was active are specially flagged. Even if dedup has been turned off, you have to check and update the DDT when you delete these flagged blocks in order to properly maintain its reference counts. However, once all flagged data blocks have been deleted, your DDT is empty and there are no further effects. Of course deleting all these data blocks may be a problem, especially in the face of things like snapshots, but once you have, you're done. (There is always a DDT in pools; it's just that some or much of the time it's empty.) - cks From danmcd at kebe.com Mon May 7 14:14:40 2018 From: danmcd at kebe.com (Dan McDonald) Date: Mon, 7 May 2018 10:14:40 -0400 Subject: [OmniOS-discuss] Certificate weirdness with omniti-ms? Message-ID: <20180507141440.GA20141@everywhere.work.kebe.com> For OmniTI folks... I'm trying to update my yes-still-uses-Omniti-MS home server to CE's new r151026. I encounter this, alas: Planning linked: 0/4 done; 1 working: zone:webserver Linked progress: -pkg: update failed (linked image exception(s)): A 'update' operation failed for child 'zone:webserver' with an unexpected return value of 1 and generated the following output: pkg update: The certificate which issued this certificate: /C=US/ST=Maryland/O=OmniTI/OU=OmniTI Managed Services/CN=OmniTI Managed Services RPackage Signing Certificate/emailAddress=info at omniti.com could not be found. The issuer is: /C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority The package involved is pkg://ms.omniti.com/omniti/server/apache24 at 2.4.33,5.11-0.151014:20180403T150105Z I hadn't noticed this earlier because the newest Apache 2.4 update depends on libxml 2.9.7 (which isn't in r151024). I'd guess I need a new root CA cert for OmniTI-MS. Where may I find this? Thanks, Dan From danmcd at kebe.com Mon May 7 14:47:52 2018 From: danmcd at kebe.com (Dan McDonald) Date: Mon, 7 May 2018 10:47:52 -0400 Subject: [OmniOS-discuss] Certificate weirdness with omniti-ms? In-Reply-To: <20180507141440.GA20141@everywhere.work.kebe.com> References: <20180507141440.GA20141@everywhere.work.kebe.com> Message-ID: <20180507144752.GB20141@everywhere.work.kebe.com> On Mon, May 07, 2018 at 10:14:40AM -0400, Dan McDonald wrote: > I'd guess I need a new root CA cert for OmniTI-MS. Where may I find this? And the answer is: Use the old one: https://github.com/omniosorg/omnios-build/tree/r151022/build/ca-bundle/files Thanks Andy F. for reminding me of that. Dan From omnios at citrus-it.net Tue May 8 22:32:36 2018 From: omnios at citrus-it.net (Andy Fiddaman) Date: Tue, 8 May 2018 22:32:36 +0000 (UTC) Subject: [OmniOS-discuss] OmniOS stable r151026 released Message-ID: The OmniOS Community Edition Association is proud to announce the availability of the second Community release of OmniOS - r151026 The new release comes 6 months after the the first community release back in November 2017. As per the published release schedule the previous stable version is supported for a further six months to allow time for upgrades and the LTS r151022 version remains supported untilMay 2020. We encourage anyone on the stable r151024 release to begin planning their upgrade to r151026. The release notes for can be found athttps://omniosce.org/releasenotes and instructions for upgrading at https://omniosce.org/upgrade - AWS images have also been pushed out to all regions. For more information, please see our full release announcement at https://omniosce.org/article/release-026 About OmniOS Community Edition Association - this Swiss Association is responsible for the ongoing development and maintenance of OmniOS, having been established in Summer 2017 after OmniTI announced their withdrawal from the project. OmniOSce Association Aarweg 17, 4600 Olten, Switzerland info at omniosce.org -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From chip at innovates.com Wed May 9 12:54:41 2018 From: chip at innovates.com (Schweiss, Chip) Date: Wed, 9 May 2018 07:54:41 -0500 Subject: [OmniOS-discuss] rpcgen Message-ID: I need the rpcgen on OmniOS. Any suggestions on where I can get this, or do I need to build it myself? Thanks, -Chip -------------- next part -------------- An HTML attachment was scrubbed... URL: From chip at innovates.com Wed May 9 13:01:58 2018 From: chip at innovates.com (Schweiss, Chip) Date: Wed, 9 May 2018 08:01:58 -0500 Subject: [OmniOS-discuss] rpcgen In-Reply-To: References: Message-ID: I just found it in 'developer/object-file'. Sorry for the bother. -Chip On Wed, May 9, 2018 at 7:54 AM, Schweiss, Chip wrote: > I need the rpcgen on OmniOS. Any suggestions on where I can get this, or > do I need to build it myself? > > Thanks, > -Chip > -------------- next part -------------- An HTML attachment was scrubbed... URL: From groenveld at acm.org Sat May 12 02:38:57 2018 From: groenveld at acm.org (John D Groenveld) Date: Fri, 11 May 2018 22:38:57 -0400 Subject: [OmniOS-discuss] MEDIA: Initial OmniOS impressions by a BSD user Message-ID: <201805120238.w4C2cvP1006206@groenveld.us> Via BSDnow.TV, YesItsMe on FreeBSD user exploring illumos via OmniOS CE: | As my growing needs require stronger hardware, it was finally time | to rent a new server. I do not intend to run FreeBSD on it. Although | the most obvious choice would be OpenBSD (I run it on another server | and it works just fine), I plan to have a couple of databases | running on the new machine, and database throughput has never been | one of OpenBSD's strong points. This is my chance to give illumos | another try. As neither WiFi nor desktop environments are relevant | on a no-X11 server, the server-focused OmniOS seemed to fit my | needs. BTW thank you to Andy Fiddaman and all contributors for r151026. Keep up the great work! John groenveld at acm.org From pasztor at sagv5.gyakg.u-szeged.hu Sun May 13 12:04:48 2018 From: pasztor at sagv5.gyakg.u-szeged.hu (=?iso-8859-2?Q?P=C1SZTOR_Gy=F6rgy?=) Date: Sun, 13 May 2018 14:04:48 +0200 Subject: [OmniOS-discuss] ipkg zone update after global update Message-ID: <20180513120448.GA5530@linux.gyakg.u-szeged.hu> Hi, I've just followed the directions of the update procedure described here: https://omniosce.org/upgrade.html It seems, the update of the ipkg zones doesn't work that smooth, how the docs says. After the reboot, I tried to reattach the zone but without any success. I usually got this: root at nas-omni:~# zoneadm -z rt attach -u Log File: /var/tmp/rt.attach_log.ZqaOCf Attach Path: /zones/rt/root Attach ZFS Dataset: stash/zones/rt/ROOT/zbe-2 Installing: Using pre-existing data in zonepath Global zone version: entire at 11-0.151026:20180504T112744Z Non-Global zone version: entire at 11-0.151024:20171030T140754Z Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows Creating Plan (Solver setup): -ERROR: Could not update attaching zone Result: Attach Failed. In the logfile, afther the same pre-task information, I can see this: PKG: install --accept --no-refresh entire at 11-0.151026:20180504T112744Z pkg://omnios/system/library/gcc-5-runtime pkg://omnios/system/library/g++-5-runtime pkg://omnios/system/library/gcc-6-runtime pkg://omnios/system/library/g++-6-runtime pkg install: No matching version of entire can be installed: Reject: pkg://omnios/entire at 11-0.151026 Reason: No version matching 'require' dependency SUNWcs at 0.5.11-0.151026 can be installed ---------------------------------------- Reject: pkg://omnios/SUNWcs at 0.5.11-0.151026 Reason: This version is excluded by installed incorporation consolidation/osnet/osnet-incorporation at 0.5.11-0.151024 ---------------------------------------- ... I tried to force-attach it: root at nas-omni:~# zoneadm -z rt attach -F But, boot didn't succeeded: root at nas-omni:~# zoneadm -z rt boot zone 'rt': ERROR: Unable to mount the zone's ZFS dataset. zone 'rt': zoneadm: zone 'rt': call to zoneadmd failed So, to actually fix it, I needed to do the following: root at nas-omni:~# zfs mount stash/zones/rt/ROOT/zbe-2 It was weird, since it seems, the publisher was successfully updated, just the upgrade procedure didn't went that smooth somehow: root at nas-omni:~# pkg -R /zones/rt/root publisher PUBLISHER TYPE STATUS P LOCATION omnios origin online F https://pkg.omniosce.org/r151026/core/ niksula.hut.fi origin online F http://pkg.niksula.hut.fi/ extra.omnios origin online F https://pkg.omniosce.org/r151026/extra/ root at nas-omni:~# pkg -R /zones/rt/root update Packages to remove: 8 Packages to install: 7 Packages to update: 396 Packages to change: 2 Mediators to change: 3 Services to change: 3 DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 413/413 14808/14808 186.0/186.0 635k/s PHASE ITEMS Removing old actions 12646/12646 Installing new actions 9065/9065 Updating modified actions 10734/10734 Updating package state database Done Updating package cache 404/404 Updating image state Done Creating fast lookup database Done Updating package cache 3/3 ------------------------------------------------------------------------------- Find release notes: https://omniosce.org/releasenotes ------------------------------------------------------------------------------- Get a support contract: https://omniosce.org/invoice Sponsor OmniOS development: https://omniosce.org/patron Contribute to OmniOS: https://omniosce.org/joinus ------------------------------------------------------------------------------- Now, at this point, let's try an detach&attach cycle: root at nas-omni:~# zoneadm -z rt detach root at nas-omni:~# zoneadm -z rt attach Log File: /var/tmp/rt.attach_log.SQa42g Attach Path: /zones/rt/root Attach ZFS Dataset: stash/zones/rt/ROOT/zbe-2 Installing: Using pre-existing data in zonepath Global zone version: entire at 11-0.151026:20180504T112744Z Non-Global zone version: entire at 11-0.151026:20180504T112744Z Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows No updates necessary for this image. Result: Attach Succeeded. Step n-1: fingers crossed! Step n: root at nas-omni:~# zoneadm -z rt boot Step n+1, just because I'm paranoid / like to dobulecheck: pasztor at rt:~$ sudo pkg refresh pasztor at rt:~$ sudo pkg update No updates available for this image. Maybe, it could be useful to extend the upgrade instructions with some kind of extra hints, like this, how can someone fix the upgrade of an ipkg zone if that fails. Cheers, Gyu From pkam at bloom.pl Sat May 26 17:57:01 2018 From: pkam at bloom.pl (Piotr Kaminski) Date: Sat, 26 May 2018 19:57:01 +0200 Subject: [OmniOS-discuss] CIFS access denied to some users from AD Message-ID: <2f68e84c-c955-e279-6f8c-519adbd84e3b@bloom.pl> Hi Everybody, My OmniOSce CIFS server is joined to AD domain (based on Samba 4 from Ubuntu). A few days ago some client computers where updated to Win 10 1803 and two users started complaining they cannot access the CIFS share. I have checked everything and cannot find the problem. * There is ACL rule for a "employees" AD group allowing access for the members, * there are about 20 members and only 2 of them have problem, * the two accounts CAN? connect to another Windows machine via RDP and are authorized by AD DC (I even changed passwords to check and still can connect with the new passwords), * the two accounts cannot access the CIFS share from OmniIOSce server. When I try to access the server from Ubuntu machine I get the following with "good_user": # smbclient -U good_user -L //omnios Enter test11's password: Domain=[DOMAIN_NAME] OS=[SunOS 5.11 omnios-r151026-673c5] Server=[Native SMB service] ??????? Sharename?????? Type????? Comment ??????? ---------?????? ----????? ------- ??????? public????????? Disk????? ??????? c$????????????? Disk????? Default Share ??????? test1?????????? Disk????? ??????? test2?????????? Disk????? ??????? ipc$??????????? IPC?????? Remote IPC ??????? test??????????? Disk????? Domain=[DOMAIN_NAME] OS=[SunOS 5.11 omnios-r151026-673c5] Server=[Native SMB service] ??????? Server?????????????? Comment ??????? ---------??????????? ------- ??????? Workgroup??????????? Master ??????? ---------??????????? ------- and with "bad_user" I get # smbclient -U bad_user -L //omnios Enter bad_user's password: session setup failed: NT_STATUS_ACCESS_DENIED I cannot see any difference between the users. They are members of the same AD groups. Even the password is the same! It seems like //omnios does not like the two users (or cannot authorize them). As a workaround I created two new accounts and they work as a charm. But that is just a temporary? workaround. I'd be grateful for a hint where to look for the mistake. With regards -- Piotr -------------- next part -------------- An HTML attachment was scrubbed... URL: From hazzino at gmail.com Mon May 28 15:52:45 2018 From: hazzino at gmail.com (=?UTF-8?Q?cristian_panci=C3=A0?=) Date: Mon, 28 May 2018 17:52:45 +0200 Subject: [OmniOS-discuss] Resize rpool Message-ID: Hi there installed the last omniosce distro on Vmware.i'm encountering error on resizing the rpool from 40Gb to 60. Tried format but expand gives me no expanded capcity is found. Format says that the disk capacity is 60Gb after disk resizing in vmware Any help will be appreciated -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim at multitalents.net Mon May 28 16:17:16 2018 From: tim at multitalents.net (Tim Rice) Date: Mon, 28 May 2018 09:17:16 -0700 (PDT) Subject: [OmniOS-discuss] Resize rpool In-Reply-To: References: Message-ID: Hi Cristian, On Mon, 28 May 2018, cristian panci? wrote: > Hi there installed the last omniosce distro on Vmware.i'm encountering > error on resizing the rpool from 40Gb to 60. > Tried format but expand gives me no expanded capcity is found. > Format says that the disk capacity is 60Gb after disk resizing in vmware > Any help will be appreciated Notes on some of my systems mention these articles. Perhaps they will be helpful. see How to Increase rpool in OmiOS VMware Guest Without a Mirror http://blog.nemtallahdaher.com/wordpress/?p=102 https://hardforum.com/threads/howto-openindiana-growing-resizing-expanding-a-zfs-root-pool-in-esx-hard-drive.1680337/ -- Tim Rice Multitalents tim at multitalents.net From hazzino at gmail.com Mon May 28 16:20:40 2018 From: hazzino at gmail.com (=?UTF-8?Q?cristian_panci=C3=A0?=) Date: Mon, 28 May 2018 18:20:40 +0200 Subject: [OmniOS-discuss] Resize rpool In-Reply-To: References: Message-ID: http://blog.nemtallahdaher.com/wordpress/?p=102 Server not available i tried archive.org no way as well Il lun 28 mag 2018, 18:17 Tim Rice ha scritto: > > Hi Cristian, > > On Mon, 28 May 2018, cristian panci? wrote: > > > Hi there installed the last omniosce distro on Vmware.i'm encountering > > error on resizing the rpool from 40Gb to 60. > > Tried format but expand gives me no expanded capcity is found. > > Format says that the disk capacity is 60Gb after disk resizing in vmware > > Any help will be appreciated > > Notes on some of my systems mention these articles. Perhaps they will be > helpful. > > see How to Increase rpool in OmiOS VMware Guest Without a Mirror > http://blog.nemtallahdaher.com/wordpress/?p=102 > > > https://hardforum.com/threads/howto-openindiana-growing-resizing-expanding-a-zfs-root-pool-in-esx-hard-drive.1680337/ > > > -- > Tim Rice Multitalents > tim at multitalents.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim at multitalents.net Mon May 28 16:46:24 2018 From: tim at multitalents.net (Tim Rice) Date: Mon, 28 May 2018 09:46:24 -0700 (PDT) Subject: [OmniOS-discuss] Resize rpool In-Reply-To: References: Message-ID: On Mon, 28 May 2018, cristian panci? wrote: { http://blog.nemtallahdaher.com/wordpress/?p=102 { Server not available i tried archive.org no way as well Sorry, I should have checked. The link below works though. Have a look at the attached file based on the link below. [snip] { > https://hardforum.com/threads/howto-openindiana-growing-resizing-expanding-a-zfs-root-pool-in-esx-hard-drive.1680337/ -- Tim Rice Multitalents tim at multitalents.net -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: expand-root-pool.txt URL: From hazzino at gmail.com Mon May 28 16:48:30 2018 From: hazzino at gmail.com (=?UTF-8?Q?cristian_panci=C3=A0?=) Date: Mon, 28 May 2018 18:48:30 +0200 Subject: [OmniOS-discuss] Resize rpool In-Reply-To: References: Message-ID: Thanks, I'll check it out. Il lun 28 mag 2018, 18:46 Tim Rice ha scritto: > On Mon, 28 May 2018, cristian panci? wrote: > > { http://blog.nemtallahdaher.com/wordpress/?p=102 > { Server not available i tried archive.org no way as well > > Sorry, I should have checked. The link below works though. > Have a look at the attached file based on the link below. > > [snip] > { > > https://hardforum.com/threads/howto-openindiana-growing-resizing-expanding-a-zfs-root-pool-in-esx-hard-drive.1680337/ > > -- > Tim Rice Multitalents > tim at multitalents.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hazzino at gmail.com Mon May 28 22:45:32 2018 From: hazzino at gmail.com (=?UTF-8?Q?cristian_panci=C3=A0?=) Date: Tue, 29 May 2018 00:45:32 +0200 Subject: [OmniOS-discuss] Omnios rescue mode Message-ID: Hey guys i messed up with my SO,it doesn't boot anymore tried to resize rpool under vmware. Do you think that following this instructions will be ok: https://serverfault.com/questions/460965/x86-solaris-boot-failure Bye bye -------------- next part -------------- An HTML attachment was scrubbed... URL: From meyer at 68netsolutions.com Tue May 29 09:04:01 2018 From: meyer at 68netsolutions.com (meyer at 68netsolutions.com) Date: Tue, 29 May 2018 11:04:01 +0200 Subject: [OmniOS-discuss] OmniOS and FCoE Message-ID: Hello, Has anybody ever successfully configured FCoE on OmniOS or Solaris ? In this case, which HBA was used ? We tried HP NC550SFP (Emulex) and Mellanox ConnectX-2 without success. Andreas -------------- next part -------------- An HTML attachment was scrubbed... URL: From Richard.Jahnel at RealPage.com Tue May 29 15:32:49 2018 From: Richard.Jahnel at RealPage.com (Richard Jahnel) Date: Tue, 29 May 2018 15:32:49 +0000 Subject: [OmniOS-discuss] FW: CIFS access denied to some users from AD In-Reply-To: <2f68e84c-c955-e279-6f8c-519adbd84e3b@bloom.pl> References: <2f68e84c-c955-e279-6f8c-519adbd84e3b@bloom.pl> Message-ID: This may be the root of your issue. There is a registry/gpo edit that might be of assistance. https://blogs.technet.microsoft.com/askpfeplat/2018/05/07/credssp-rdp-and-raven/ Richard Jahnel Backups Team 2201 Lakeside Blvd, Richardson, Tx 75007 Office: (972) 810-2527 From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On Behalf Of Piotr Kaminski Sent: Saturday, May 26, 2018 12:57 PM To: omnios-discuss at lists.omniti.com Subject: [OmniOS-discuss] CIFS access denied to some users from AD Hi Everybody, My OmniOSce CIFS server is joined to AD domain (based on Samba 4 from Ubuntu). A few days ago some client computers where updated to Win 10 1803 and two users started complaining they cannot access the CIFS share. I have checked everything and cannot find the problem. * There is ACL rule for a "employees" AD group allowing access for the members, * there are about 20 members and only 2 of them have problem, * the two accounts CAN connect to another Windows machine via RDP and are authorized by AD DC (I even changed passwords to check and still can connect with the new passwords), * the two accounts cannot access the CIFS share from OmniIOSce server. When I try to access the server from Ubuntu machine I get the following with "good_user": # smbclient -U good_user -L //omnios Enter test11's password: Domain=[DOMAIN_NAME] OS=[SunOS 5.11 omnios-r151026-673c5] Server=[Native SMB service] Sharename Type Comment --------- ---- ------- public Disk c$ Disk Default Share test1 Disk test2 Disk ipc$ IPC Remote IPC test Disk Domain=[DOMAIN_NAME] OS=[SunOS 5.11 omnios-r151026-673c5] Server=[Native SMB service] Server Comment --------- ------- Workgroup Master --------- ------- and with "bad_user" I get # smbclient -U bad_user -L //omnios Enter bad_user's password: session setup failed: NT_STATUS_ACCESS_DENIED I cannot see any difference between the users. They are members of the same AD groups. Even the password is the same! It seems like //omnios does not like the two users (or cannot authorize them). As a workaround I created two new accounts and they work as a charm. But that is just a temporary workaround. I'd be grateful for a hint where to look for the mistake. With regards -- Piotr -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From jub at matchcut.at Wed May 30 07:37:45 2018 From: jub at matchcut.at (=?utf-8?Q?J=C3=BCrgen_Bereuter?=) Date: Wed, 30 May 2018 09:37:45 +0200 Subject: [OmniOS-discuss] disable acpi in loader.conf Message-ID: Hello, i am using a HPE Proliant Gen10 Microserver, i installed omnniosce bloody (omniosce-bloody-20180509.usb-dd, i had to disable acpi). I am not sure, if i am using the new bootloader, but i think so. I should now disable acpi, but i did not find the right config file (/boot/loader.conf: acpi=off). I tried to switch to grub, but there is also an error message: sudo installgrub -fm /boot/grub/stage1 /boot/grub/stage /dev/rdsk/c2t0d0 open: No such file or directory Unable to gather device information for /dev/rdsk/c2t0d0 The disk is s SSD, with an EFI partition/label, configured at installation as a rpool. When i disable the acpi in the boot options manual omniosce boots up without a problem, i cannot make it permanent after a reboot. thanks! j?rgen -------------- next part -------------- An HTML attachment was scrubbed... URL: From jub at matchcut.at Wed May 30 09:28:01 2018 From: jub at matchcut.at (=?utf-8?Q?J=C3=BCrgen_Bereuter?=) Date: Wed, 30 May 2018 11:28:01 +0200 Subject: [OmniOS-discuss] disable acpi in loader.conf In-Reply-To: References: Message-ID: found the solution: create file /boot/loader.conf and add this line boot-args=''-B acpi-user-options=0x2'' thats it > Am 30.05.2018 um 09:37 schrieb J?rgen Bereuter : > > Hello, > i am using a HPE Proliant Gen10 Microserver, i installed omnniosce bloody (omniosce-bloody-20180509.usb-dd, i had to disable acpi). I am not sure, if i am using the new bootloader, but i think so. I should now disable acpi, but i did not find the right config file (/boot/loader.conf: acpi=off). > I tried to switch to grub, but there is also an error message: > > sudo installgrub -fm /boot/grub/stage1 /boot/grub/stage /dev/rdsk/c2t0d0 > open: No such file or directory > Unable to gather device information for /dev/rdsk/c2t0d0 > > The disk is s SSD, with an EFI partition/label, configured at installation as a rpool. > > When i disable the acpi in the boot options manual omniosce boots up without a problem, i cannot make it permanent after a reboot. > > thanks! j?rgen > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: