[OmniOS-discuss] SMB + Network tuning
Hi all, new to the list.. apologies if this is a tired topic.. I’m seeing poor SMB performance on my gigabit network here, as compared to a Synology filer. With the Synology, my test client can read/write consistently at near line speeds (100MB/s+), while with the OmniOS test filer, I can’t seem to get above 60MB/s. I’ve tried the usual TCP tuning of buffers, ack, and such, to no avail. NFS seems to yield about the same results. Some details: - Server: HP Proliant, DL360 G5, 16GB RAM - OS: tested with both latest OmniOS + Solaris 11.1, with and without Napp-it, same results - NIC: bnx - storage: Xyratex JBOD, SAS - zpool: 2 x 6 disk raidz2 I’m getting hundreds of MB/s off the zpool, so I’m thinking the bottleneck has to be something in the Samba or NIC driver config. Any ideas greatly appreciated! -- Anh Quach Sent with Airmail___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] create ordinary user
Netatalk use regular OmniOS Unix users. If you use napp-it, goto menu user and klick ++add local user You can also use the CLI command useradd Gea Am 31.01.2014 um 17:44 schrieb Fábio Rabelo: > Using the repo http://scott.mathematik.uni-ulm.de/ > wget -O - www.napp-it.org/afp | perl > > Nothing wrong here, but there are no ordinary user on the system, just > the root ... > > > Fábio Rabelo > > 2014-01-31 Zach Malone : >> What package repo did you install Netatalk from, or did you compile it >> yourself? Which utility is missing? >> >> On Thu, Jan 30, 2014 at 8:18 AM, Fábio Rabelo >> wrote: >>> Hi to all >>> >>> I am trying netatalk in an OminOS box, and having problem to create a user >>> ... >>> >>> All and every how-to that I found in the web refers to an utilitary in >>> command line from OpenSolaris, but this tool do not exist in OmniOS >>> ... >>> >>> So, how can I create an ordinary user to authenticate against netatalk ? >>> >>> Thanks in advance ... >>> >>> >>> Fábio Rabelo >>> ___ >>> 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 -- ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Migrating from OpenIndiana
We recently did this on 18 of our storage servers, and the process went smoothly, no issues were encountered. Our setup sounds similar to yours: The OI 151a7 systems were serving LUNs over FC via Comstar. The root pools were mirrored, and each system had at least one other pool for data (zvols backing the Comstar LUNs). I set up a Kayak server which makes the install process go much faster (and minimizes downtime), but it's not necessary to get the job done. The steps we followed were something like this: - Save the Comstar config: svccfg export -a stmf > svccfg-stmf.xml I put the XML file in one of the data pools so it would be easy to access from the new OmniOS install. - save any other files you care about from the root pool - break off one of the mirrored root pool devices to use for the OmniOS install - Install OmniOS onto the free device and boot. - Import the data pools. I didn't export them from the old OI install first, so '-f' was needed on the 'zpool import' command - Restore the Comstar config: svccfg import svccfg-stmf.xml At this point you should be up and running on your OmniOS install, with the old OpenIndiana install still available on the other root pool disk. Once you feel confident things are working and you don't need to fall back to the old OS, remirror the root pool and upgrade the data pools. The total time the systems were unavailable for the upgrade was about 10-15 minutes. Did I mention Kayak was fast? :-) Good luck with your upgrades, Kevin On 01/29/2014 02:59 PM, Nate Smith wrote: > I’m going to migrate the ZFS systems on my OpenIndiana file server to an > Omnios based one for greater stability (my Openindiana server seems to > lose all network connectivity about once every three months, though all > the FC targets stay mounted and accessible). I am running oi_151a7, with > version 28 ZFS volumes. They are presented as block storage Comstar > targets over fibre channel. Should I have any problems migrating these > to Omnios? Thanks in advance. > > > > -Nate > > > > > > ___ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -- --- Kevin Swab UNIX Systems Administrator ACNSColorado State University Phone: (970)491-6572Email: kevin.s...@colostate.edu GPG Fingerprint: 7026 3F66 A970 67BD 6F17 8EB8 8A7D 142F 2392 791C ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] [OmniOS] Two problem for set a zfs dataset in a zone
On 2014-01-31 01:35, Frédéric Alix wrote: Hello :) I have two problem for use a zfs dataset in a zone. First, i would like use it as a device zfs create -V5g rpool/data0 In zonecfg: add device set match = "/dev/zvol/dsk/rpool/data0" end I boot the zone, and the device don't appear. I do have a similar setup on one box, albeit on a SPARC Solaris 10 for a Solaris 8 branded zone (evacuation of an older server to newer hardware), and the zone manifest (/etc/zones/zonename.xml) contains: The volume has no special properties set: # zfs list -r pool/zones/local/colonel-data NAMEUSED AVAIL REFER MOUNTPOINT pool/zones/local/colonel-data 1.25G 16.1G 31.4K /zones/local/colonel-data pool/zones/local/colonel-data/chunk1 1.25G 16.4G 331M - zfs get all pool/zones/local/colonel-data/infx-chunk1 NAME PROPERTY VALUE SOURCE pool/zones/local/colonel-data/chunk1 type volume - pool/zones/local/colonel-data/chunk1 creation Mon Nov 25 8:32 2013 - pool/zones/local/colonel-data/chunk1 used 1.25G - pool/zones/local/colonel-data/chunk1 available 16.4G - pool/zones/local/colonel-data/chunk1 referenced 331M - pool/zones/local/colonel-data/chunk1 compressratio 4.92x - pool/zones/local/colonel-data/chunk1 reservationnone default pool/zones/local/colonel-data/chunk1 volsize2.05G - pool/zones/local/colonel-data/chunk1 volblocksize 8K - pool/zones/local/colonel-data/chunk1 checksum on default pool/zones/local/colonel-data/chunk1 compressiongzip-9 inherited from pool/zones/local pool/zones/local/colonel-data/chunk1 readonly off default pool/zones/local/colonel-data/chunk1 shareiscsi off default pool/zones/local/colonel-data/chunk1 copies 1 default pool/zones/local/colonel-data/chunk1 refreservation 300M local pool/zones/local/colonel-data/chunk1 primarycache all default pool/zones/local/colonel-data/chunk1 secondarycache all default pool/zones/local/colonel-data/chunk1 com.sun:auto-snapshot true inherited from pool In particular, the "zoned" property is "off" on both the volume and its higher containers. This setup works, despite the fact that the branded Solaris 8 image has of course no direct support for ZFS, so delegation of datasets was not an option (either devices, or lofs-mounts, from the GZ into LZ should have worked and did in fact work). Now, this is indeed a different OS, but the basics like this should be the same. Try starting "zlogin -C zonename" before booting the zone, this may log something about some errors that may be in the way? HTH, //Jim ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] create ordinary user
Using the repo http://scott.mathematik.uni-ulm.de/ wget -O - www.napp-it.org/afp | perl Nothing wrong here, but there are no ordinary user on the system, just the root ... Fábio Rabelo 2014-01-31 Zach Malone : > What package repo did you install Netatalk from, or did you compile it > yourself? Which utility is missing? > > On Thu, Jan 30, 2014 at 8:18 AM, Fábio Rabelo > wrote: >> Hi to all >> >> I am trying netatalk in an OminOS box, and having problem to create a user >> ... >> >> All and every how-to that I found in the web refers to an utilitary in >> command line from OpenSolaris, but this tool do not exist in OmniOS >> ... >> >> So, how can I create an ordinary user to authenticate against netatalk ? >> >> Thanks in advance ... >> >> >> Fábio Rabelo >> ___ >> 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] create ordinary user
What package repo did you install Netatalk from, or did you compile it yourself? Which utility is missing? On Thu, Jan 30, 2014 at 8:18 AM, Fábio Rabelo wrote: > Hi to all > > I am trying netatalk in an OminOS box, and having problem to create a user ... > > All and every how-to that I found in the web refers to an utilitary in > command line from OpenSolaris, but this tool do not exist in OmniOS > ... > > So, how can I create an ordinary user to authenticate against netatalk ? > > Thanks in advance ... > > > Fábio Rabelo > ___ > 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] Two problem for set a zfs dataset in a zone
Hello, I don't have much experience with delegating a zfs volume instead of just a data set to a zone, but I believe the "add dataset" method you've used second probably won't work, as that's how you add a regular zfs filesystem. http://lists.omniti.com/pipermail/omnios-discuss/2013-January/000413.html sounds like exactly the same issue though. Going back to the last time I needed a zvol inside a zone, I think I might have tried creating the zvol on a dataset that had been delegated to the zone already, and mounted/delegated the parent dataset to the zone normally. The dataset would have then been created by the zone, rather then the gz. --Zach Malone On Thu, Jan 30, 2014 at 7:35 PM, Frédéric Alix wrote: > Hello :) > > I have two problem for use a zfs dataset in a zone. > > First, i would like use it as a device > > zfs create -V5g rpool/data0 > In zonecfg: > add device > set match = "/dev/zvol/dsk/rpool/data0" > end > > I boot the zone, and the device don't appear. > I read this, but it not resolve the problem > http://lists.omniti.com/pipermail/omnios-discuss/2013-February/000479.html > > After, i try to use it lie this: > add dataset > set name = rpool/data0 > end > > and when i want boot the zone: > root@box:/var/tmp# zoneadm -z nappit0 boot > zone 'nappit0': cannot open ZFS dataset 'rpool/data0' > zoneadm: zone 'nappit0': call to zoneadmd failed > > But my dataset exist > root@box:/var/tmp# zfs list rpool/data0 > NAME USED AVAIL REFER MOUNTPOINT > rpool/data0 5,16G 33,2G16K - > > > > Can you help me please ? > > Regards, Frédéric > > ___ > 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] system/fm/smtp-notify mailing about already-resolved events on boot
Hi Olaf, I provide a patched smtp-notify that does not depend on sendmail. However, you still have to throw out the smf dependency on sendmail manually. Cheers, Steffen Am 30.01.2014 um 21:25 schrieb Olaf Marzocchi : > I didn’t know smtp-notify but looked useful so I tried to install it. > However, it depends on sendmail and I already have postfix, that also > provides a binary /usr/sbin/sendmail, so they conflict (see below). > If I install the ms.omniti package postfix (compiled for r151006 but probably > fine) the conflict should disappear (its sendmail goes to > opt/omni/sbin/sendmail) but then how to be sure that the postfix’s one is > used? > > Could give me some directions? > > Thanks > Olaf > > > $ pfexec pkg install service/fault-management/smtp-notify > Creating Plan | > pkg install: The requested change to the system attempts to install multiple > actions > for link 'usr/sbin/sendmail' with conflicting attributes: > > 1 package delivers 'link path=usr/sbin/sendmail target=../lib/sendmail': > > pkg://omnios/service/network/smtp/sendmail@8.14.4,5.11-0.151008:20131204T024609Z > 1 package delivers 'link path=usr/sbin/sendmail > target=../local/sbin/sendmail': > > pkg://uulm.mawi/service/network/smtp/postfix@2.10.2,5.11-0.151008:20140111T165835Z > > These packages may not be installed together. Any non-conflicting set may > be, or the packages must be corrected before they can be installed. > > The following packages deliver conflicting action types to usr/lib/sendmail: > > link: > > pkg://uulm.mawi/service/network/smtp/postfix@2.10.2,5.11-0.151008:20140111T165835Z > file: > > pkg://omnios/service/network/smtp/sendmail@8.14.4,5.11-0.151008:20131204T024609Z > > These packages may not be installed together. Any non-conflicting set may > be, or the packages must be corrected before they can be installed. > > $ pkg search sendmail > INDEX ACTION VALUE > PACKAGE > basenamefile usr/local/sbin/sendmail > pkg:/service/network/smtp/postfix@2.10.2-0.151008 > basenamelink usr/lib/sendmail > pkg:/service/network/smtp/postfix@2.10.2-0.151008 > basenamelink usr/sbin/sendmail > pkg:/service/network/smtp/postfix@2.10.2-0.151008 > pkg.descr setWietse Venema's mail server alternative to Sendmail > pkg:/omniti/network/smtp/postfix@2.10.2-0.151006 > basenamefile opt/omni/sbin/sendmail > pkg:/omniti/network/smtp/postfix@2.10.2-0.151006 > basenamefile usr/lib/sendmail > pkg:/omniti/network/smtp/postfix@2.10.2-0.151006 > pkg.description setSendmail Utilities > pkg:/service/network/smtp/sendmail@8.14.4-0.151008 > pkg.summary setSendmail > pkg:/service/network/smtp/sendmail@8.14.4-0.151008 > basenamefile etc/init.d/sendmail > pkg:/service/network/smtp/sendmail@8.14.4-0.151008 > basenamefile usr/lib/sendmail > pkg:/service/network/smtp/sendmail@8.14.4-0.151008 > basenamelink usr/sbin/sendmail > pkg:/service/network/smtp/sendmail@8.14.4-0.151008 > pkg.fmrisetomnios/service/network/smtp/sendmail > pkg:/service/network/smtp/sendmail@8.14.4-0.151008 > > > > Il giorno 29/gen/2014, alle ore 19:00, Kevin Swab > ha scritto: > >> We have this issue too. For us, it happens on all versions of OmniOS up >> through r151008 (and all versions of OpenIndiana we've tried too). >> >> It will stop if you clear all the fault management logs using a >> procedure like this: >> >> https://blogs.oracle.com/unixgeek/entry/how_to_clear_fmadm_log >> >> But this seems a bit drastic. A fix would be most welcome! >> >> Kevin >> >> >> >> On 01/29/2014 06:40 AM, Lauri Tirkkonen wrote: >>> smtp-notify seems to be generating emails for every recorded diagnosed >>> event upon system boot, even when those faults have been repaired or >>> resolved long since. We're on r151006. >>> >>> This seems like a bug - is anyone else seeing this? >>> >> >> -- >> --- >> Kevin Swab UNIX Systems Administrator >> ACNSColorado State University >> Phone: (970)491-6572Email: kevin.s...@colostate.edu >> GPG Fingerprint: 7026 3F66 A970 67BD 6F17 8EB8 8A7D 142F 2392 791C >> ___ >> OmniOS-discuss mailing list >> OmniOS-discuss@lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss > > ___ > OmniOS-discuss mailing list > OmniOS
