Re: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository

2017-08-24 Thread John D Groenveld
In message , Paul Jochum writes : >configuration. >Additional details: > >Unable to contact valid package repository >Encountered the following error(s): >Unable to contact any configured publishers. >This is likely a network configuration problem. >Unable to locate a CA directory: /etc/openssl/cer

[OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository

2017-08-24 Thread Paul Jochum
Hi All: I am working on updating a number of omnios machines from r151022 (under OmniOS TI) to R151022 (under OmniOS CE). I am having problems updating one of my zones. I am at the point now where I have unset all of the publishers in that zone, but I can not add the omniosce publisher. #

Re: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance

2017-08-24 Thread Artem Penner
Hi, can you post output of https://github.com/d-helios/dtrace/blob/master/zfs/zfs_rwlatency.d And if you have separate log device output of https://github.com/d-helios/dtrace/blob/master/zfs/zil_latency.d --- What is your nfs-server settings? (sharectl get nfs) чт, 24 авг. 2017 г. в 19:35, Richar

Re: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance

2017-08-24 Thread Richard Elling
> On Aug 24, 2017, at 5:41 AM, Schweiss, Chip wrote: > > I just move one of my production systems to OmniOS CE 151022m from 151014 and > my NFS performance has tanked. > > Here's a snapshot of nfssvrtop: > > 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 KB, > awrite

Re: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance

2017-08-24 Thread Bob Friesenhahn
On Thu, 24 Aug 2017, Schweiss, Chip wrote: I switched back to 014 for now, it was too bad to inflict on my users. I have some new systems coming in soon that I'll test on r151022 before making them live. I will start with the NFS defaults. No evidence has been presented that there is a NFS

Re: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance

2017-08-24 Thread Schweiss, Chip
I switched back to 014 for now, it was too bad to inflict on my users. I have some new systems coming in soon that I'll test on r151022 before making them live. I will start with the NFS defaults. -Chip On Thu, Aug 24, 2017 at 8:35 AM, Dan McDonald wrote: > > > On Aug 24, 2017, at 8:41 AM, S

Re: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance

2017-08-24 Thread Dan McDonald
> On Aug 24, 2017, at 8:41 AM, Schweiss, Chip wrote: > > I just move one of my production systems to OmniOS CE 151022m from 151014 and > my NFS performance has tanked. > > Here's a snapshot of nfssvrtop: > > 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 KB, > awrite

[OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance

2017-08-24 Thread Schweiss, Chip
I just move one of my production systems to OmniOS CE 151022m from 151014 and my NFS performance has tanked. Here's a snapshot of nfssvrtop: 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 KB, awrite: 9634 KB Ver Client NFSOPS Reads SWrites AWrites Commit

Re: [OmniOS-discuss] Constantly losing nfs shares smb shares?

2017-08-24 Thread Oliver Weinmann
Hi, I have done some more investigation and I found the cause for this problem. It always happens when running zfs send from a Nexenta system. [cid:Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1.png] Oliver Weinmann Senior Unix VMWare, Storage Engineer

[OmniOS-discuss] zfs recv causes system to crash / hang

2017-08-24 Thread Oliver Weinmann
Hi all, every time trying to do zfs send | recv between OmniOS 151022.x and Nexenta 4.0.5x the Nexenta node crashes. This is very critical to us as we either want to use the OmniOS system for DR or migrate some files between the two. I raised a ticket with Nexenta and they pointed me in the rig