Re: [OmniOS-discuss] [developer] NVMe Performance

[Josh Coombs]

On Fri, Apr 15, 2016 at 9:26 PM, Richard Yao  wrote:

>
> The first is to make sure that ZFS uses proper alignment on the device.
> According to what I learned via Google searches, the Intel DC P3600
> supports both 512-byte sectors and 4096-byte sectors, but is low leveled
> formatted to 512-byte sectors by default. You could run fio to see how the
> random IO performance differs on 512-byte IOs at 512-byte formatting vs 4KB
> IOs at 4KB formatting, but I expect that you will find it performs best in
> the 4KB case like Intel's enterprise SATA SSDs do. If the 512-byte random
> IO performance was notable, Intel would have advertised it, but they did
> not do that:
>
>
> http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/ssd-dc-p3600-spec.pdf
>
> http://www.cadalyst.com/%5Blevel-1-with-primary-path%5D/how-configure-oracle-redo-intel-pcie-ssd-dc-p3700-23534
>
> So, I played around with this.  Intel's isdct tool will let you secure
erase the P3600 and set it up as a 4k sector device, or a 512, with a few
other options as well.  I have to re-look but it might support 8k sectors
too.  Unfortunately the NVMe driver doesn't play well with the SSD
formatted for anything other than 512 byte sectors.  I noted my findings in
Illumos bug #6912.

I need to look at how Illumos partitions the devices if you just feed zpool
the device rather than a partition, I didn't look to see if it was aligning
things correctly or not on it's own.

The second is that it is possible to increase IOPS beyond Intel's
> specifications by doing a secure erase, giving SLOG a tiny 4KB aligned
> partition and leaving the rest of the device unused. Intel's numbers are
> for steady state performance where almost every flash page is dirty. If you
> leave a significant number of pages clean (i.e. unused following a secure
> erase), the drive should perform better than what Intel claims by virtue of
> the internal book keeping and garbage collection having to do less. Anandtech
> has benchmarks numbers showing this effect on older consumer SSDs on
> Windows in a comparison with the Intel DC S3700:
>

Using isdct I have mine set to 50% over-provisioning, so they show up as
200GB devices now.  As noted in bug 6912 you have to secure erase after
changing that setting or the NVMe driver REALLY gets unhappy.

Josh C
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] cifs anonymous troubles

[Jeff Berkembrock]

Hello,

I wanted to chime in and say I also experienced this. Guest smb access
seems broken both when I upgrade to 18 as well as when I perform a fresh
install and create new pool & share.

Best Regards,

Jeff Berkembrock
On Apr 15, 2016 1:06 PM, "Natxo Asenjo"  wrote:

> hi,
>
> trying to set up an anonymous share on workgroup mode  I do not get it
> working.
>
> I have a dataset tank/test with these sharesmb properties:
>
> zfs get sharesmb tank/testshare
> NAMEPROPERTY  VALUE   SOURCE
> tank/testshare  sharesmb  name=test,guestok=true  local
>
> These are the permissions on that path:
>
> # /usr/bin/ls -Vd /tank/testshare/
> drwxrwxrwx+ 14 root root  14 Sep 11  2015 /tank/testshare/
>   everyone@:rwxpdDaARWcCos:fd-:allow
>
> Both using a windows client (win 2012r2) as a linux smbclient (fedora 23),
> both quite modern, I cannot access the share:
>
> Linux smbclient:
> $ smbclient -U " " -L //192.168.0.172 -N
> Anonymous login successful
> Domain=[WORKGROUP] OS=[SunOS 5.11 omnios-r151018-ae314] Server=[Native SMB
> service]
>
> Sharename   Type  Comment
> -     ---
> c$  Disk  Default Share
>
> testDisk
> Connection to 192.168.0.172 failed (Error NT_STATUS_CONNECTION_REFUSED)
> NetBIOS over TCP disabled -- no workgroup available
>
>
> Windows client:
> C:\Users\Administrator>net view \\192.168.0.172
> System error 5 has occurred.
>
> Access is denied.
>
>
> Using a local user works, with smb2 ;-)
>
> Any one success with guestok=true and cifs?
>
> --
> Groeten,
> natxo
>
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151018 is now out!

[Stephan Budach]

Hi Dan,

Am 15.04.16 um 20:20 schrieb Dan McDonald:

Follow the "change to openssh or sunssh" instructions on the 016 release notes. 
 You appear to have conflicting packages, one from each, which was a bug in the 016 
installer.

Or you can add "--exclude ssh-common" to your pkg update.

Dan

Sent from my iPhone (typos, autocorrect, and all)


On Apr 15, 2016, at 12:57 PM, Stephan Budach  wrote:

Hi Dan,

I actually ran into this issue, when tying to upgrade my 016 to 018:

root@zfsha01colt:/root# pkg update -v --be-name=OmniOS-r151018 entire
Creating Plan (Es wird auf widersprüchliche Aktionen geprüft): /
pkg update: Folgende Pakete stellen widersprüchliche Aktionstypen in 
usr/share/man/man4/ssh_config.4 bereit:

  link:
pkg://omnios/service/network/ssh-common@0.5.11,5.11-0.151018:20160412T195038Z
  file:
pkg://omnios/network/openssh@7.1.2,5.11-0.151016:20160114T155110Z


How can I resolve this issue?

Thanks,
Stephan
___



thanks, I already thought to try that and now both of my RSF-1 hosts are 
happy on r018.


Cheers,
Stephan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] cifs anonymous troubles

[Natxo Asenjo]

hi,

trying to set up an anonymous share on workgroup mode  I do not get it
working.

I have a dataset tank/test with these sharesmb properties:

zfs get sharesmb tank/testshare
NAMEPROPERTY  VALUE   SOURCE
tank/testshare  sharesmb  name=test,guestok=true  local

These are the permissions on that path:

# /usr/bin/ls -Vd /tank/testshare/
drwxrwxrwx+ 14 root root  14 Sep 11  2015 /tank/testshare/
  everyone@:rwxpdDaARWcCos:fd-:allow

Both using a windows client (win 2012r2) as a linux smbclient (fedora 23),
both quite modern, I cannot access the share:

Linux smbclient:
$ smbclient -U " " -L //192.168.0.172 -N
Anonymous login successful
Domain=[WORKGROUP] OS=[SunOS 5.11 omnios-r151018-ae314] Server=[Native SMB
service]

Sharename   Type  Comment
-     ---
c$  Disk  Default Share

testDisk
Connection to 192.168.0.172 failed (Error NT_STATUS_CONNECTION_REFUSED)
NetBIOS over TCP disabled -- no workgroup available


Windows client:
C:\Users\Administrator>net view \\192.168.0.172
System error 5 has occurred.

Access is denied.


Using a local user works, with smb2 ;-)

Any one success with guestok=true and cifs?

--
Groeten,
natxo
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151018 is now out!

[Stephan Budach]

Hi Dan,

I actually ran into this issue, when tying to upgrade my 016 to 018:

root@zfsha01colt:/root# pkg update -v --be-name=OmniOS-r151018 entire
Creating Plan (Es wird auf widersprüchliche Aktionen geprüft): /
pkg update: Folgende Pakete stellen widersprüchliche Aktionstypen in 
usr/share/man/man4/ssh_config.4 bereit:


  link:
pkg://omnios/service/network/ssh-common@0.5.11,5.11-0.151018:20160412T195038Z
  file:
pkg://omnios/network/openssh@7.1.2,5.11-0.151016:20160114T155110Z


How can I resolve this issue?

Thanks,
Stephan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151018 is now out!

[Natxo Asenjo]

On Thu, Apr 14, 2016 at 8:47 PM, Dan McDonald  wrote:

> Start with the release notes:
>
> http://omnios.omniti.com/wiki.php/ReleaseNotes/r151018
>

home box upgraded, zero problems ;-)

Thanks!
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss