Re: [OmniOS-discuss] Finally - OmniOSce Commercial Support

[Günther Alka]

Thanks
Highly appeciated as this will strengthen the confidence into the 
Illumos + OmniOS platform.

I recommend commercial users to accept the offer.

Gea
napp-it.org


Am 07.02.2018 um 21:40 schrieb Tobias Oetiker:
After getting the release process up and running smoothly, the 
OmniOSce Association is finally ready to start that long awaited 
Commercial Support offering:


Are you running your Servers on OmniOS Community Edition? Would you 
like to ensure you are not left alone if you run into trouble with the 
devices? Would you like to ensure the continued maintenance and 
development of your favorite OS?


Go to our website and request an invoice to get your Organisation 
started on a new OmniOS support contract:


*https://www.omniosce.org/invoice*

cheers
tobi oetiker

OmniOSce Association
Aarweg 17, 4600 Olten, Switzerland



___
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] wiki problems at omniti

[Günther Alka]

It seems that only the wiki is down, repos are working
so you can update.

You may do it according to my HowTo
http://www.napp-it.org/doc/downloads/setup_napp-it_os.pdf
chapter 2.2

Gea
@napp-it.org


Am 08.11.2017 um 20:46 schrieb Jeff Stockett:


I’ve got a few servers still running r151020 I was going to upgrade – 
but the wiki/download link seems to have a problem:



  Proxy Error

The proxy server could not handle the request 
/GET /wiki.php/Installation 
/.


Reason: *Error during SSL Handshake with remote server*

Is this a permanent thing or just temporary?  Is there a way to 
upgrade to omniosCE without first upgrading to R151022?




___
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 based redundant NFS

[Günther Alka]

I have added a similar solution with full service and storage failover 
of two identical storage servers last year into my napp-it web ui as an 
experimental solution. Main difference is that I do nor use single disks 
as targets but the whole ZFS pools on two servers to mirror them over 
the network and share the resulting network mirror. This will allow a 
head to function with full redundancy if the other server fails. As you 
only need one LUN per server this reduces complexity.  I also switch 
target ip and NFS/SMB service ip for an instant service failover, see my 
solution under http://www.napp-it.org/doc/downloads/z-raid.pdf


Gea
@napp-it.org



Am 30.09.2017 um 08:45 schrieb Stephan Budach:

Hi Sergey,

- Ursprüngliche Mail -

Von: "sergey ivanov" 
An: "Stephan Budach" 
CC: "omnios-discuss" 
Gesendet: Freitag, 29. September 2017 22:30:31
Betreff: Re: [OmniOS-discuss] OmniOS based redundant NFS

Thanks, Stephan.
I did a simple test with creating lu over physical disks for use as
ISSI targets, and it worked well. I am going to directly connect 2
servers and export their disks as separate I SCSI targets. Or maybe
different LUNs in a target. And then on the active server start
initiator to get these targets, and combine them into a pool of 2-way
mirrors so that it stays degraded but working if one of the servers
dies.

Well, different targets mean, that you will be able to service single disks on 
one node, without having to degrade the whole zpool, but only the affected 
vdevs. On the other hand, there is more complexity since, you will have of 
course quite a big number of iSCSI targets to login to. This may be ok, if the 
number doesn't get too hight, but going with hundreds of disks, I chose to use 
fewer targets with more LUNs.

One thing to keep in mind is, that stmfad allows you to create the guuid to 
your liking. That is that you can freely choose the last 20 bytes to be 
anything you want. I used that to ascii-code the node name and slot into the 
guid, such as that it displays on my NFS heads, when running format. This helps 
a lot in mapping the LUNs to drives.


So, manual failover for this configuration will be the following. If
the server to be disabled is still active, stop NFS, export zpool on
it, stop iscsiadm, release shared IP. On the other server: import
zpool and start NFS, activate shared IP.

I am using the sharenfs properties of ZFS, but you will likely have to run zpool 
export -f  if you want to fail over the service, since the zpool is 
still busy. Also, you'd better set zpool failmode to panic instead of wait, such as 
that an issue triggers a reboot, rather than keeping you NFS head waiting.


I read once there are some tricks which make clients do not recognize
NFS server is changed underneath all mounts, but I never tried it.

The only issue I came across was, when I deliberatley failed over the NFS 
service forth and back within the a too short period, which causes the NFSd on 
the former primary node to re-use the tcp packets numbers, insisting on reusing 
it's old NFS connections to the clients. I solved that by resetting the NFSd 
each time a service starts on any NFS head. The currently connected NFS clients 
are not affected by that and this solved this particular issue for me.

Cheers,
Stephan


--
   Regards,
   Sergey Ivanov.

Regards,
Sergey Ivanov


On Thu, Sep 28, 2017 at 12:49 AM, Stephan Budach
 wrote:

Hi Sergey,

- Ursprüngliche Mail -

Von: "sergey ivanov" 
An: "Stephan Budach" 
CC: "omnios-discuss" 
Gesendet: Mittwoch, 27. September 2017 23:15:49
Betreff: Re: [OmniOS-discuss] OmniOS based redundant NFS

Thanks, Stephan!

Please, explain "The reason to use two x two separate servers is,
that
the mirrored zpool's vdevs look the same on each NFS head".

I understand that, if I want to have the same zpool based on iscsi
devices, I should not mix local disks with iscsi target disks.

But I think I can have 2 computers, each exporting a set of local
disks as iscsi targets. And to have iscsi initiators on the same
computers importing these targets to build zpools.

Also, looking at sbdadm, I think I can 'create lu
/dev/rdsk/c0t0d3s2'.

Ok, I think I would better try it and report how it goes.

Actually, things can become quite complex, I'd like to reduce the
"mental" involvement to the absolute minimum, mainly because we
often faced a situation where something would suddenly break,
which had been running for a long time without problems. This is
when peeple start… well maybe not panicking, but having to recap
what the current setup was like and what they had to do to tackle
this.

So, uniformity is a great deal of help on such systems - at least
for us. Technically, there is no issue with mixing local and
remote iSCST targets on the same node, which serves as an iSCSI

Re: [OmniOS-discuss] Questions about - End the uncertainty -

[Günther Alka]

Only a personal stance

I am from Germany where a re-unification of Germany happened some year ago.
When this happened there were a lot of different interest involved but 
luckily Cancellor Kohl simply declared this as a golden common future 
for East and West Germany and he succeeded.


A lot went wrong afterwards and for some it was indeed not the golden 
future. But in general, Germany is seen now much better than in any 
other history. Mr Kohl dies recently with the honour of the first 
funeral as a European state ceremony.


Illumos is not nearly as relevant like the future of nations involved in 
wars. But the mood of the persons and the needed decisions are similar.


Lets repeat a similar success with OI + OmniOS despite the problems and 
differences.
They are sisters and want basically the same. In the end both will be 
better off. Just do it.



Gea
@napp-it.org

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

Re: [OmniOS-discuss] Questions about - End the uncertainty -

[Günther Alka]

Thank you Dan

Does this mean
- the problems around a cooperatione with OmniOS were mainly in the past 
prior OI Hipster?

- A a merge would introduce conflicts.

This would require work to solve or both sides agree to use one or the 
other as base?

Each choice would require work to maintain the current features.

Installer seems irrelevant for me unless it offers what is needed.

Your last comment is the core of the problem.
How to coordinate communities!

Gea
@napp-it.org


Am 07.07.2017 um 20:02 schrieb Dan McDonald:

On Jul 7, 2017, at 11:42 AM, Guenther Alka  wrote:

hello Dan

Thanks for jumping in.
You are the person with the very best insights in OmniOSand Illumos
and propably OI. Can you please comment about the options to cooperate with OI.

Is this doable and wishable from your point of viewand how or do you have
an alternative idea for a positive future of OmniOS ce or free Illumos
based general use servers in general.Are there concerns for a project merge?

I had a unicast chat session with someone about this recently.

it's *POSSIBLE*, but remember the half the reason OmniOS happened in the first 
place was because OI focussed way too much on the desktop and all that 
accompanies it.  (The other half, not keeping up with upstream, was fixed by 
Hipster.)

I don't have the cycles to spell out how an OI/OmniOS merge MIGHT happen.  
There are three big technical problems that come to mind:

1.) Package naming:  There are some subtle differences in IPS package names 
outside of illumos between the two.

2.) Perl & Python:  OmniOS picked dual-mode perl and dual-mode Python (64 and 
32 bit).  Not sure what OI does.

3.) Installer:  I chose to abandon Caiman in no small part because it was far 
more bloated than it needed to be for OmniOS.  I wish I'd done Kayak for ISO 
sooner (or Theo or Eric did).  I believe there is a decent post-processing step 
that can be done for Kayak Interactive that can provide the functionality of 
the old Caiman or OI/slim_install.

Beyond that, there's the headaches of community coordination, etc.

All of this I don't have cycles for, I can say for sure.

Sorry,
Dan



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

[OmniOS-discuss] About OmniOS and napp-it

[Günther Alka]

About OmniOS and napp-it
https://forums.servethehome.com/index.php?threads/omnios-151022-long-term-stable.14367/page-4

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

Re: [OmniOS-discuss] Bug ?

[Günther Alka]

Why should one as there remain enough free or nonfree Solaris based 
options that I see as a mostly superiour option for ZFS storage.


Or would you switch (as a Linux user) to BSD or Solaris if RedHat would 
close the door when there are many other Linux options but without 
commercial support available.


If commercial support was your reason for OmniOS, Nexenta and Solaris 
remain an option. If OpenSource is ok, use OI or SmartOS or one of the 
other and hope or help that we/you/they find a way to continue the idea 
of a minimal stable or LTS distribution based on Illumos.Commercial 
support with SLA is not really needed for me and many. We want NetApp 
alike features without the costs.


I second Aurélian coming from the OpenIndiana community with the idea to 
look at OI with its stronger and already working community like a OmniOS 
bloody to create a stable subset/freeze named OmniOS upon.


Gea
@napp-it.org

Am 01.07.2017 um 01:36 schrieb Mini Trader:

Is it going to be FreeBSD or Linux?

On Thu, Jun 29, 2017 at 3:16 AM Oliver Weinmann 
> wrote:


Ohh that is bad news.

I have a productions system that somehow fails to join AD and I
don’t know what is causing this. We had a similar issue on our 
nexenta system and they provided us a patch that solved it.


Idmap:

additional info: SASL(-1): generic failure: GSSAPI Error:
Unspecified GSS failure.  Minor code may provide more information
(Client not found in Kerberos database)

adutils: ldap_lookup_init failed

*Oliver Weinmann*
Senior Unix VMWare, Storage Engineer

Telespazio VEGA Deutschland GmbH
Europaplatz 5 - 64293 Darmstadt - Germany
Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799
oliver.weinm...@telespazio-vega.de

http://www.telespazio-vega.de

Registered office/Sitz: Darmstadt, Register court/Registergericht:
Darmstadt, HRB 89231; Managing Director/Geschäftsführer: Sigmar Keller

*From:* Paul B. Henson [mailto:hen...@acm.org
]
*Sent:* Donnerstag, 29. Juni 2017 08:51
*To:* Oliver Weinmann >
*Cc:* omnios-discuss >
*Subject:* Re: [OmniOS-discuss] Bug ?

Unfortunately OmniTI no longer offers support contracts for
OmniOS. We actually have a contract that's still good through I
think November, but given their main support engineer is no longer
with the company and the OS appears to be in limbo at the moment
I'm not sure what good that does us ;).

If you think you've found a bug, your best bet at the moment is to
just report it to this list, possibly to the upstream illumos
developer list if you can detail it reasonably technically, and
perhaps open an issue on the illumos issue tracker.


On Jun 28, 2017, at 11:29 PM, Oliver Weinmann
> wrote:

Hi,

What if I would like to report a possible bug? Do I need a
valid support contract for this?

Best Regards,

Oliver




*Oliver Weinmann*
Senior Unix VMWare, Storage Engineer

Telespazio VEGA Deutschland GmbH
Europaplatz 5 - 64293 Darmstadt - Germany
Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799
oliver.weinm...@telespazio-vega.de

http://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@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


--

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

Re: [OmniOS-discuss] Dell H330 and mpt_sas on r151022

[Günther Alka]

The driver is related to the firmware.
I suppose you are on an IR/Raid firmware. The better one would be a 
raidless and often faster IT firmware (mpt_sas). But I cannot say if its 
available from Dell or if the one from LSI is working.


Gea
@napp-it.org


Am 30.06.2017 um 18:53 schrieb Aries:

Hello,

I noticed that the r151022 starts to support the Dell H330 via mpt_sas 
driver. So I installed the r151022 fresh on my Dell T630 server with 
H330 as a VM on ESXi. The H330 was PCI-E passthrough with 8x 7k2 disks 
in raid z2.


However when I ran the command dmesg | grep sas, it seems that the 
mr_sas was used for the H330 adapter which is just as same as the 
r151020 and r151014 version.


I also discovered that the disk performance was worse than the 
r151020. To compare, I ran all the tests via napp-it filebench. For 
example, for the fivestreamwrite test, the result of r151020 and 
r151014 is around 1100mb/s, but the r151022 only shows 650mb/s. I 
tried multiple combinations like creating the pool in one version and 
import into another version. The issue seems not related to the 
creation of the pool but the version which runs the pool.


Did I miss something in the setup that leads the H330 to run with the 
wrong driver? Could you please give me some advices? Thank you in advance.


Best regards,
Aries


___
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] Fragmentation

[Günther Alka]

hello Richard

I can follow that the Zil does not add more fragmentation to the free 
space but is this effect relevant?
If a ZIL pre-allocates say 4G and the remaining fragmented poolsize for 
regular writes is 12T


Gea

Am 23.06.2017 um 19:30 schrieb Richard Elling:

A slog helps fragmentation because the space for ZIL is pre-allocated based on 
a prediction of
how big the write will be. The pre-allocated space includes a 
physical-block-sized chain block for the
ZIL. An 8k write can allocate 12k for the ZIL entry that is freed when the txg 
commits. Thus, a slog
can help decrease free space fragmentation in the pool.
  — richard



On Jun 23, 2017, at 8:56 AM, Guenther Alka  wrote:

A Zil or better dedicated Slog device will not help as this is not a write 
cache but a logdevice. Its only there to commit every written datablock and to 
put it onto stable storage. It is read only after a crash to redo a missing 
committed write.

All writes, does not matter if sync or not, are going over the rambased write 
cache (per default up to 4GB). This is flushed from time to time as a large 
sequential write. Writes are fragmented then depending on the fragmentation of 
the free space.

Gea



To prevent it, a ZIL caching all writes (including sync ones, e.g. nfs) can 
help. Perhaps a DDR drive (or mirror of these) with battery and flash 
protection from poweroffs, so it does not wear out like flash would. In this 
case, how-ever random writes come, ZFS does not have to put them on media asap 
- so it can do larger writes later. This can also protect SSD arrays from 
excessive small writes and wear-out, though there a bad(ly sized) ZIL can 
become a bottleneck.

Hope this helps,
Jim
--

___
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] Setup problems with newest OmniOS 151021 on ESXi 6.5

[Günther Alka]

It was the first time I tried bloody with the new loader
on ESXi to fix a Perl TTy incompatibility with napp-it

Gea


Am 14.04.2017 um 16:14 schrieb Dan McDonald:

On Apr 14, 2017, at 6:20 AM, Guenther Alka  wrote:

I found a strange behaviour with the newest 151021 when I tried to setup on 
ESXi 6.5

I created a new VM (Solaris 11-64)  with a DVD device connected to the OS .iso.
On first boot of the VM, the ESXi web console crashed completely with a 
required reload.

After reload, the VM console shows a
- configuring devices
- ..requesting system maintenance, press ctrl-d to continue

After ctrl-d I was able to select a bootdisk and install OmniOS
After setup, reboot work

A power off/on and the ESXi webconsole crashes again (mostly, not always)

Are you saying that older r151021s did not have this problem?

I know Fusion has a "black screen" problem with Loader, GRUB, et. al, but 
that's new, and only with the combination of the latest Fusion and latest MacOS X.

Dan




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

Re: [OmniOS-discuss] VMware tools for Omni

[Günther Alka]

You can also use Open-VM Tools. They are in the OmniOS repo
http://pkg.omniti.com/omnios/r151020/en/search.shtml?token=vmware=Search

Gea

Am 13.03.2017 um 21:05 schrieb Jeff Berkembrock:

Hello,

Has anyone had any success installing VMware tools on Omni r151020?

I'm trying to do so from a ESXi 6.5 host and an Omni r151020 guest 
that runs within. This omni instance was loaded from the omniti ISO 
install media 


root@omnitool:/root# uname -a
SunOS omnitool 5.11 omnios-r151020-b5b8c75 i86pc i386 i86pc

This link  refers to a 
VMware KB 
 
article that explains how to perform the install. Unfortunately when I 
get to step 4 (mounting the virtual DVD install media) I see the error 
below.


I'm seeing the same error with a Solaris 11.3 host.

It seems like VMware removed their installers for Solaris & related OS.


Call "VirtualMachine.MountToolsInstaller" for object "omni" on ESXi 
"10.1.10.11" failed.

vix error code = 21001
Unable to install VMware Tools. An error occurred while trying to 
access image file "/usr/lib/vmware/isoimages/solaris.iso" needed to 
install VMware Tools: 2 (No such file or directory). Please refer the 
product documentation or KB article 2129825 for details about how to 
get VMware Tools package for this guest operating system.


Best Regards,

Jeff Berkembrock
www.1beyond.com 
617-591-2200 x2212


___
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] [smartos-discuss] Bhyve Hyper

[Günther Alka]

I use ESXi (free) as base due the best of all support for any guests 
and  pass-through
of a real HBA with disks and OmniOS ontop see 
http://napp-it.org/doc/downloads/napp-in-one.pdf


some build examples
http://www.napp-it.org/doc/downloads/napp-it_build_examples.pdf

Gea


Am 21.12.2016 um 00:06 schrieb cristian pancià:
Hi there does anyone installed smartos omnios under those virt. Like 
bhyve and hyper-v?

If yes any suggestions,Tut's.
As a home server and virtual lab for pentesting and video streaming 
for my family,I need some tips about a medium high motherboard ,what 
CPU and RAM type max 1300euro

Thank you in advance

*smartos-discuss* | Archives 
 
 
| Modify 
 
Your Subscription 	[Powered by Listbox] 





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

Re: [OmniOS-discuss] LX zones and a small Howto

[Günther Alka]

Most important is the success of the Illumos or Open-ZFS platform.
LX containers are from Joyent (btw have you read this article 
https://www.infoq.com/news/2016/03/containers-summit-nyc ), SMB2+ and 
sequential resilvering are or may come from Nexenta and native 
encryption from ZoL with many features or additions that strengthen the 
platform from others versus Oracle or Linux.


ESXi, SmartOS or Proxmox are very good as a cloud or virtualisation 
platform where you can run or use ZFS  but OmniOS is a perfect NAS/SAN 
filer or server OS with the option to run a Linux container. This is 
indeed new.


Thanks to all

Gea

Am 12.10.2016 um 20:52 schrieb Dan McDonald:

On Oct 12, 2016, at 2:40 PM, Günther Alka <a...@hfg-gmuend.de> wrote:

What I must say is, that this seems to be a real killer innovation for OmniOS 
as you can run OmniOS as a very solid ZFS filer with additional Linux services 
running directly especially with preconfigured services as a container where 
you only need a copy and import/run after some small editings of a config file 
like shares or nics.

Joyent did most of the hard work here with LX -- credit where due, please. :)

By integrating it into OmniOS, though, you get the improvment of a 
fully-working global zone (where many sharing services can only function... 
e.g. no NFS in an NGZ currently) with the capability for closer-to-native Linux 
services (not as much running KVM in a zone now, for example).

Thanks for the napp-it update!
Dan



--

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 627
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

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

Re: [OmniOS-discuss] LX zones and a small Howto

[Günther Alka]

Gratulation!

I have also tried the CentOS example and it works for me.
I have created a small howto setup LX and the VM, see 
http://www.napp-it.org/doc/downloads/zones.pdf


I have not used SmartOS in the past so the concept was at first not 
clear to me.
What I must say is, that this seems to be a real killer innovation for 
OmniOS as you can run OmniOS as a very solid ZFS filer with additional 
Linux services running directly especially with preconfigured services 
as a container where you only need a copy and import/run after some 
small editings of a config file like shares or nics.


What I will add to the current concept in napp-it is deploying 
containers together with the config file (zone.cfg) like it is done on 
ESXi where you can simply provide a folder with the VM that you can 
simply import and run. An option is that one deploy LX images as a 
folder imagefile with the zone config file within and the container with 
the OS as a subfolder.


Gea

Am 12.10.2016 um 04:39 schrieb Dan McDonald:

The bloody repo server has an updated LX brand package with this fix.

Dan

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

On Oct 11, 2016, at 2:20 PM, Richard Skelton > wrote:



Hi All,
Dan provided an updated lx_brand file which I installed in 
/usr/kernel/brand/amd64/lx_brand

After a reboot of the global zone all is now working :-)

CentOS release 6.8 (Final)
Kernel 2.6.32 on an x86_64

lx0 login:



Dan McDonald wrote:

On Oct 11, 2016, at 12:52 PM, Dan McDonald  wrote:

I'm going to check with SmartOS, and see if this is something I fubared, or if 
it's an upstream (i.e. their) problem too.  I suspect I mismerged something.  
It's fairly new, because I swear I used to see CentOS 6 consoles during the 
io-lx days.
 


Not mismerge, but missing bugfix:

 OS-5685 LTP vhangup02 fails and passes

Could you do me a favor and test a replacement lx_brand binary?  Please respond 
unicast, and we'll report back to the list once your post-fix findings match 
mine.  :)

Thanks,
Dan


   



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


--

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 627
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

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

[OmniOS-discuss] Plex mediaserver in an LX zone

[Günther Alka]

about LX
I have not yet worked with this concept.
Main problem seems the lack of documentation, blogs and howtos or a 
simple ready to use example for OmniOS.


A good start would be a documented example like a Plex LX mediaserver.
Has anyone used this in SmartOS and can give some informations about 
doing the same with OmniOS? I will add a support menu for handling and 
management of LX containers in napp-it then as I suppose that many non 
storage related features and add-ons are LX containers in future.


see http://lightsandshapes.com/plex-on-smartos.html

Gea/ napp-it.org


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

Re: [OmniOS-discuss] New bloody (IPS only this time)

[Günther Alka]

Thanks
napp-it is working again with this sudo fix

Gea

Am 12.02.2016 um 23:22 schrieb Dan McDonald:

Based on illumos-omnios master commit cc70d5b, uname -v reports 
"omnios-cc70d5b".

And omnios-build master commit 45f0d7b.

New with this update:

- Case-sensitivity now in ZFS test suite.

- GLDv3 improvement (by OmniTI's own Dale Ghent) which should produce less 
confusing dladm(1M) output.

- SunSSH and sudo now honor the illumos-bug-6057 ways of doing things.  Please PLEASE 
look for other "last login" weirdness, but there shouldn't be any.  If there 
is, PLEASE report it to this list ASAP.

- Speaking of SSH, OpenSSH now includes the full wad of Joyent work (modulo 1-2 
small differences) to be more of a SunSSH replacement.  If you haven't tried 
OpenSSH because you needed something from SunSSH, PLEASE try it now.


There is no new release media for this update, but I did update all of the 
packages, so you'll need to create a new BE and reboot.

Thanks,
Dan

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


--

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 627
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

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

Re: [OmniOS-discuss] Bloody update for December 11th

[Günther Alka]

Many Thanks to Nexenta
and to OmniTi for this december bloody with SMB 2

I have just done some tests on OSX under Solaris 11.3 to check some 
configuration

options for a ZFS video editing storage server for my Mac Pros.

There are two must have principles: SMB2 and Jumboframes
see http://napp-it.org/doc/downloads/performance_smb2.pdf


Gea



On 11.12.2015 16:48, Dan McDonald wrote:

This will be the last bloody update for 2015.  The new install media (ISO, 
USB-DD, or kayak .zfs.bz2) can be obtained via here:

http://omnios.omniti.com/wiki.php/Installation

illumos-omnios is built from revision 2e8c0ba.  omnios-build is built from 
b7ab647, but is a faster moving target.

New in this bloody:

- PCRE to 8.38 (the one already patched in 014 & 016).

- OpenSSH now works properly with the illumos audit system.  This will be 
backported to 014 & 016 soon.

- OpenSSL to 1.0.2e (already patched in 014 & 016).

- Package variant support for DEBUG kernels now built-in (more on this below).

- ZFS receive now works with replication streams with intermediate snapshots 
that exceed refquota (a requested fix)

- SMB2 support (thanks Nexenta)


The "package variant" support (thanks to Jeff Sipek for the inspiration) allows a user of 
OmniOS to create a distinct boot environment with same-time-compiled bits, but with DEBUG enabled.  
To create such a BE, you start by upgrading to these bits, and then you can use the "pkg 
change-variant" command.  The change-variant subcommand works a lot like install.  Here's an 
example:

Last login: Fri Dec 11 10:30:56 2015
OmniOS 5.11 omnios-2e8c0ba  December 2015
# pkg variant -a
VARIANT
VALUE
arch   
i386
debug.illumos  
false
opensolaris.zone   
global
# pkg change-variant -n debug.illumos=true
Packages to change: 188
 Variants/Facets to change:   1
   Create boot environment: Yes
Create backup boot environment:  No

Planning linked: 0/1 done; 1 working: zone:tz2
Linked image 'zone:tz2' output:
| No updates necessary for this image. (zone:tz2)
`
Planning linked: 1/1 done
#

If I wasn't using -n:  boom, instant DEBUG kernel in a new BE.  This will be 
handy for people who encounter problems.  We can request you create a DEBUG BE 
and reproduce your problem without having to ONU or do any other weirdness.

As I said earlier, this is the last bloody update for 2015.  Have a happy 
holiday season (whatever you celebrate, or not) and a happy new year!

Dan

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



--

H  f   G
Hochschule für Gestaltung
university of design

Schwäbisch Gmünd
Rektor Klaus Str. 100
73525 Schwäbisch Gmünd

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 624
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

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

Re: [OmniOS-discuss] SMB 2.1 any many other improvements

[Günther Alka]

I will test the second bloody 151017 when it becomes available.

Hope for some explanations about how to join now correctly
and if it is possible and how to use a secondary AD server
in the Illumos wiki or the OmniOS wiki.

It is hard to find correct infos about new Illumos features
as the docs around are mostly related to Oracle or sometimes
extremely outdated like many entries in the Illumos wiki.

Sometimes you only find infos about new options in the OpenZFS
slides from some conference presentations or with discussions
@hardforum > data storage.. or @servethehome > Solaris..

A short reference with an example for essential new behaviours
or features would be extremely helpful. Maybe the release note
can include a short explanation for new features that require settings.

Thank you all very much


Gea



On 07.11.2015 00:06, Dan McDonald wrote:

A big drop like this likely will not be backported. It will appear in probably 
the second update to this bloody cycle, since the first drop is already frozen.

R151018 will be the first stable release to contain this.

Dan

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


On Nov 6, 2015, at 4:11 PM, Guenther Alka  wrote:

Just saw the notice at Illumos IRC

Long awaited (Gordon Ross from Nexenta, gratulation, among others)
SMB 2.1 is there - my Mac users will be happy

https://www.illumos.org/issues/6399
https://www.illumos.org/issues/6398
https://www.illumos.org/issues/6352
https://www.illumos.org/issues/6400
https://www.illumos.org/issues/1087

soon
https://www.illumos.org/issues/3525

Pretty good news for OmniOS


Two question
- When -  will SMB 2.1 be included - to LTS or 151016??
- Can 6352 support Primary and a Secondary AD Server as a failover - and how

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



--

H  f   G
Hochschule für Gestaltung
university of design

Schwäbisch Gmünd
Rektor Klaus Str. 100
73525 Schwäbisch Gmünd

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 624
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

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

[OmniOS-discuss] stable combinations of OmniOS 151014 andNFS to ESXi and state of open-vm tools (vmxnet3)

[Günther Alka]

In my own setups, I use OmniOS 151014 (initial release) with NFS to ESXi 5.5U2 
which is very stable with vmxnet3 and e1000 (original VMware tools)
In the last time I got several mails about problems on some configurations

Stable configurations
5.5U2 + OmniOS 151014  (April)
6.00b + OmniOS 151014  (April)

problems with
5.5U2 + OmniOS 151014  (July)
6.0 initial release + NFS
6.00b + OmniOS 151014  (July)

example
http://hardforum.com/showpost.php?p=1041787564postcount=6873 
http://hardforum.com/showpost.php?p=1041787564postcount=6873


Are there others experiencing problems or stabiliy on these combinations?



beside that
Are there news about open vmware tools in OmniOS especially regarding the 
missing vmxnet3 driver___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] ZFS crash/reboot loop

[Günther Alka]

First action:
If you can mount the pool read-only, update your backup

Then
I would expect that a single bad disk is the reason of the problem on a 
write command. I would first check the system and fault log or 
smartvalues for hints about a bad disk. If there is a suspicious disk, 
remove that and retry a regular import.


If there is no hint
Next what I would try is a pool export. Then create a script that 
imports the pool followed by a scrub cancel. (Hope that the cancel is 
faster than the crash). Then check logs during some pool activity.


If this does not help, I would remove all data disks and bootup.
Then hot-plug disk by disk and check if its detected properly and check 
logs. Your pool remains offline until enough disks come back.
Adding disk by disk and checking logs should help to find a bad disk 
that initiates a crash


Next option is, try a pool import where always one or next disk is 
missing. Until there is no write, missing disks are not a problem with 
ZFS (you may need to clear errors).


Last option:
use another server where you try to import (mainboard, power,  hba or 
backplane problem) remove all disks and do a nondestructive or smart 
test on another machine



Gea

On 12.07.2015 20:43, Derek Yarnell wrote:

The on-going scrub automatically restarts, apparently even in read-only
mode.  You should 'zpool scrub -s poolname' ASAP after boot (if you can)
to stop the ongoing scrub.

We have tried to stop the scrub but it seems you can not cancel a scrub
when the pool is mounted readonly.




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

Re: [OmniOS-discuss] OmniOS considered in-memory OS ?

[Günther Alka]

booting from a good pair of 32 GB USB sticks is possible.
(Turn off atime)

But I would prefer a pair of 32 GB DOMs like
http://www.supermicro.com/products/nfo/SATADOM.cfm 
http://www.supermicro.com/products/nfo/SATADOM.cfm



 Am 26.06.2015 um 17:47 schrieb John Barfield john.barfi...@bissinc.com:
 
 I’ve been interested in configuring omnios to run in memory off of a ram 
 disk myself. 
 
 Does anyone know where you could find a good guide for booting Solaris(h) 
 kernel into memory with a ramdisk?
 
 
 
 
 John Barfield / Sr Principal Engineer
 +1 (214) 425-0783/ john.barfi...@bissinc.com
 BISS, Inc. Office: +1 (214) 506-8354 
 
 4925 Greenville Ave Suite 900
 Dallas, TX 75206
 support.bissinc.com http://htmlsig.com/support.bissinc.com
 
 
 
 
 
 
 On 6/26/15, 10:15 AM, Dan McDonald dan...@omniti.com wrote:
 
 
 On Jun 26, 2015, at 10:59 AM, Mick Burns bmx1...@gmail.com wrote:
 
 As per current wikipedia entry for SmartOS,  we can read the following :
 
 SmartOS is an in-memory operating system and boots directly into
 random access memory. It supports various boot mechanisms such as
 booting off of universal serial bus thumbdrive, ISO Image, or over the
 network via PXE boot.
 
 Does this statement applies to OmniOS as well ?
 
 No.  We boot off of traditional media.
 
 Ultimately, what I need to know is if OmniOS is good fit to run OS off
 a pair of either internal SDcards or good quality USB sticks ?
 
 As shipped, no.
 
 Dan
 
 ___
 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] CIFS Issues

[Günther Alka]

Matthew

As you use napp-it and as I have many OmniOS SMB filers in an AD environment 
without such problems 
can to compare what happens when you use napp-it to join the domain instead 
doing manually

(menu Services  SMB  Active Directory)

Gea
 

 
 
 On May 13, 2015, at 6:45 PM, Matthew McGee mc...@sci-world.net wrote:
 
 Interesting. Using the trailing . for an absolute FQDN works.
 Any hints on how to make it work without the full FQDN?
 I assume it's probably a kerberos related issue?
 

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

Re: [OmniOS-discuss] What repos do people use to build a *AMP server?

[Günther Alka]

You can use the pkgin repo from SmartOS as it is the most complete source.
It is used by the amp setup script provided as a community add-on for napp-it

(you do not need napp-it to use the script)
http://napp-it.org/extensions/amp_en.html 
http://napp-it.org/extensions/amp_en.html


Gea


 Am 08.05.2015 um 18:48 schrieb Saso Kiselkov skiselkov...@gmail.com:
 
 I've decided to try and update my r151006 box to something newer, seeing
 as r151014 just came out and it's supposed to be LTS. Trouble is, I'm
 trying to build a *AMP box and I can't find any prebuilt packages for it
 in any of these repos:
 http://omnios.omniti.com/wiki.php/Packaging
 What do you guys use for getting pre-built software? Do all people here
 just roll their own?
 
 Also, allow me to say, I *hate* consolidations and the way they lock
 accessible package versions. Where are the days when OSes used to be
 backwards-compatible?
 
 Cheers,
 -- 
 Saso
 ___
 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] ZFS ACL Solaris CIFS and Windows client

[Günther Alka]

Lets’s begin with ZFS properties
- aclinhert: passthrough
- aclmode: does not matter for CIFS 

Next, set idmappings
- in Workgroup mode: do not set any user mappings (only group mappings)
- in Domain mode: set domainadmins = root

Next: join AD Domain (for domain mode)

Next: SMB connect
- use root (requires a passwd root to generate s SMB password) or
- use an Domain Admin account (requires the idmapping to root)

Windows version:
- you need Windows Pro or Windows server (no home edition)

Now you should be able to set ownership and ACL on files and folders.

If you want to set ACL on shares, you must
- SMB connect as a user that is a member of the Administrators group
- use Computer Management on Windows and connect OmniOS


Gea


 Am 28.04.2015 um 14:09 schrieb Sebastian Gabler sequoiamo...@gmx.net:
 
 Hi,
 
 I am a bit stuck in getting my ACL management straight for the CIFS shares I 
 run. What I would like to do is to set all the ACLs from Windows. What does 
 not work right now is to assign ownership to a sharepoint or an object below 
 it to a different user, i.e. to set ownership as the Domain Administrator to 
 a specific user. I get an error message that a Restore privilege would be 
 missing, but the error message is unclear if that applies to the current 
 context (Domain Administrator), or the prospective owner. I can set full 
 control for that user, however.
 Specifically,
 1. I am wondering how to get, from my illumos machine, the privileges 
 applicable on an object for a certain user.
 2. finding out what is required to take/provide ownership, specifically of a 
 sharepoint, from Windows, (ACLs, idmap, ZFS acl modes and inhertiance modes, 
 etc), and in what hierarchy things apply.
 I am aware that this may be a FAQ, but I didn't find comprehensive 
 documentation on the matter. The Oracle docs are focussed to explain how 
 things work from the Solaris side, most HowTos that include the Windows side 
 are not deep enough.
 
 Thanks for any hints.
 
 With best regards,
 
 Sebastian
 ___
 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] Status of VAAI

[Günther Alka]

I am a programmer but not for OS development but in the GUI/ usability area
otherwise I would help (can help with testing)

It is really a pity.  Ragarding storage and usability, Solaris and OmniOS is 
far better than
Linux that I use as well for my ZFS GUI. With the newest features that Nexenta 
integrates
into NexentaStor (beside VAII this is SMB2 and failure management on slow 
disks), Illumos
has the ability to be the number 1 storage OS - even in the OpenSource or 
low-cost  area,
better than BSD or Linux.

If Nexenta would give Illumian more love, it might become the leading free 
Illumos distribution
but I do not expect that this will happen. The other „big players“ like 
Delphix, Joyent or
OmniOS seems to have no interest  in such storage features as well as 
improvements in
encryption (hey we need this)

Gea/ napp-it.org


Am 05.08.2014 um 19:27 schrieb Floris van Essen ..:: House of Ancients Amstafs 
::.. i...@houseofancients.nl:

 Hi Dan,
  
 Sometimes i wish was a programmer J
 Infra dude here, with plenty of stuff to test thing, but a programmer I am 
 not, however if you need testers….
  
  
  
  
 Van: Dan McDonald [mailto:dan...@omniti.com] 
 Verzonden: dinsdag 5 augustus 2014 18:48
 Aan: Floris van Essen ..:: House of Ancients Amstafs ::..
 CC: omnios-discuss@lists.omniti.com
 Onderwerp: Re: [OmniOS-discuss] Status of VAAI
  
 Someone needs to take the time to port the Illumos-nexenta bits upstream.  
 Nobody has yet stepped up to the plate.  Are you volunteering?  ;)
  
 Dan
 
 Sent from my iPhone (typos, autocorrect, and all)
 
 On Aug 5, 2014, at 1:44 AM, Floris van Essen ..:: House of Ancients Amstafs 
 ::.. i...@houseofancients.nl wrote:
 
 Hi Guys,
  
 Been waiting now for a long time for VAAI (XCOPY and ATS ) to make it into 
 COMSTAR
 Does anyone know if there’s any progress in that area ?
  
 https://www.mail-archive.com/omnios-discuss@lists.omniti.com/msg02095.html
  
 best regards,
  
  
 Floris
 ___
 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] Netatalk Problems on OmniOS

[Günther Alka]

I have done a clean re-install of OmniOS151010 just to be sure

- installing netatalk from mawi gives me netatalk 3.0.2 (not the 
advertised 3.1)
with an error: ld.so.1: afpd: fatal: libgcrypt.so.11: open failed: No 
such file or directory


I then installed libgcrypt from repo http://pkg.niksula.hut.fi/  that 
fixes this problem
I was able to connect the netatalk server (Mavericks) but ended with a 
missing or no shareerror

(afpd.conf is ok at this point)

It seems that mawi has a wrong version currently
My main interest iscompiling it myself to have full control about 
versions and to be in sync with Illumian, OI and Solaris.

But there I ended in a a unsupported server message




On 04.06.2014 19:04, Olaf Marzocchi wrote:

The version from mawi works fine in my case.
What is your config file and exact issue?

Olaf





Il giorno 04/giu/2014, alle ore 16:00, Guenther Alka a...@hfg-gmuend.de ha 
scritto:

With Netatalk from mawi I got errors about missing shares.

___
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] Netatalk Problems on OmniOS

[Günther Alka]

Apple moves to SMB3 as the default protocol in OSX 10.10
so netatalk may be obsolete in future.

The problem remains Illumos as there are no rumors 
whether the Nexntanta SMB2 improvements find their way to Illumos.

Maybee a move to SAMBA4 is unavoidable in near future.




Am 04.06.2014 um 21:25 schrieb Paul B. Henson hen...@acm.org:

 From: Guenther Alka
 Sent: Wednesday, June 04, 2014 7:01 AM
 
 I tried to setup netatalk (tried 3.1.0, 3.1.1 and 3.1.2) on current
 OmniOS stable but failed. I have tried to compile manually and setup
 
 I'm just curious, what is your requirement for netatalk? I think it's been
 well more than a decade since I've used AppleTalk or AppleShare. All of our
 Mac systems nowadays just use CIFS.
 
 

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

Re: [OmniOS-discuss] Boot from mirrored USB?

[Günther Alka]

napp-it has a web menu entry to create ZFS mirrored disks or mirrored 
usb sticks (both bootable)

following the blog of Constantin Gonzales:

http://constantin.glez.de/blog/2011/03/how-set-zfs-root-pool-mirror-oracle-solaris-11-express 



With high quality and fast usb sticks especially in a mirrored config 
and atime disabled,
usb boot is a very attractive boot method where you can easily create 
clones of sticks for backups
or OS deployment (I offer a free Windows clone tool and preconfigured 
OmniOS images for download at napp-it.org).

Performance wise usb boot is quite ok.

Only problem: currently you can only boot from usb when you plugin the 
sticks in those ports
that were used during setup. It would be perfect it you may boot from 
any usb port maybe on similar
mainboards. But this seems a Grub restriction where the physical 
bootdevice is hardcoded during setup.




On 31.10.2013 15:01, Theo Schlossnagle wrote:
I believe napp-it based on OmniOS also boots from USB.  The mirroring 
is hard because I don't think it is a native ZFS boot -- works more 
like a ram disk.



On Thu, Oct 31, 2013 at 9:53 AM, Chris Nehren 
cnehren+omnios-disc...@omniti.com 
mailto:cnehren+omnios-disc...@omniti.com wrote:


On Thu, Oct 31, 2013 at 11:54:50 +, Ben Summers wrote:

 Hello,

 I'm speccing out some new hardware. It seems challenging to get
vendor supported configurations which give you lots of discs on a
Solarish OS, rather than using horrid RAID cards.

 The best config I've found so far seems to be a Fujitsu RX200
with 4 internal 15k SAS discs (the internal supported card can
only do 8 drives if you use RAID), plus a Fujitsu branded LSI
controller connected to an Intel 3.5 JBOD array for bulk storage
and maybe an SSD for ZIL.

 Because I'd like to use all the internal discs for a database as
a pair of mirrors in a single JBOD, I was wondering if anyone
boots from USB discs?

SmartOS is designed to run from USB drives. I don't know if their
configuration supports mirroring, though.

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




--

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle



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



--

H  f   G
Hochschule für Gestaltung
university of design

Schwäbisch Gmünd
Marie-Curie-Str. 19
73529 Schwäbisch Gmünd

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 624
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

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

Re: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS?

[Günther Alka]

I have added a physical slot detection that displays physical
Slot, WWN and serials together with the option to switch on the red
alert led on supported backplanes within napp-it with the help of
sas2ircu (a LSI tool that displays slot and disk serial).


On 30.10.2013 21:25, Chris Siebenmann wrote:

  This is a long shot and I suspect that the answer is no, but: in
OmniOS, is it possible somehow to have disk device names for disks
behind LSI SAS controllers that are based on the physical slot ('phy')
that the disk is found in instead of the disk's reported WNN or serial
number?

(I understand that this is only easy if there are no SAS expanders
involved, which is the situation that I care about.)

  I know that I can recover this information from prtconf -v with
appropriate mangling, but our contemplated environment would be much
more manageable if we could directly use physical slot based device
naming.

  Thanks in advance. I'll post a summary if there are any private
replies (for anything besides 'nope, can't do it').

- cks
___
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] napp-it OmniOS appliance boots very slow, used to work on OpenIndiana

[Günther Alka]

One problem I am  aware if you are using the ESXi appliance
resulting in very slow bootup, extreme high CPU load and even data 
corruption:


If you are on ESXi 5.5, you must use the vmxnet3 vnic
or disable TCP segmentation offload in e1000.conf; add the following and 
reboot


tx_hcksum_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;
lso_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0;

Maybe similar to this problem:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=2058692

(in the current appliance v. 13b, this is disabled per default)


Gea

On 13.10.2013 10:03, Eugen Leitl wrote:

Not sure what is going on, can anyone spot a smoking gun
in this dmesg? System doesn't reboot/init 5 doesn't
shutdown either.

___
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] areca or lsi

[Günther Alka]

I have build a lot of OmniOS boxes and was involved in a lot of
hardware decisions. All of them are using LSI HBAs in raidless IT mode.

If there was ever a consensus in the Solarish world regarding disk 
controller than this:

- prefer pure HBAs, avoid hardware raid cards, use those with IT firmware
- avoid controller cache, ZFS needs full disk control especially with 
sync write -

  your regular RAM, used by ZFS is anyway larger and faster
- prefer LSI (nearly all Solarish ZFS boxes are using LSI) where you can 
expect the best driver quality


My own favourite on OmniOS is the LSI 9207 with PCI-E 3.0 and the new 
2308 chipset
They come out of the box with the desired IT firmware, no need to 
reflash like with other LSI controllers.


I would add:
If you need expanders, use LSI ones paired with LSI HBAs, use SAS disks 
with expanders
or if you intend to use Sata disks, prefer as much HBAs as needed 
without expander.


Gea


On 19.07.2013 00:48, Tobias Oetiker wrote:

Folks,

We are specing a new omnios server box ... and were just told by
our vendor, that LSI HBAs were much slower (50%) than Areca Controllers
running in JBOD mode ... and that they would therefore recommend
Areca (we use areca for raid6 in linux boxes, but have never used it in JBOD
mode with illumos, yet).

Which controller would you choose for a new system ?

cheers
tobi




--

H  f   G
Hochschule für Gestaltung
university of design

Schwäbisch Gmünd
Marie-Curie-Str. 19
73529 Schwäbisch Gmünd

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 624
Fax 07171 69259
guenther.a...@hfg-gmuend.de
http://rz.hfg-gmuend.de

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

Re: [OmniOS-discuss] Omnios as a zfs storage server under esxi 5.1

[Günther Alka]

First of all, a virtualized SAN is not a problem but a good idea on a 
lot of use cases unless you can supply the same CPU, RAM and disk 
recommendations like you would do on on real hardware. It is also not a 
problem, that you cannot do vmotion with your SAN-VM (How would you 
vmotion your physical disks??)


But you must provide:
- real hardware access to controller and disks (needs pass-through/vt-d) 
for your SAN VM OmniOS

- assign enough RAM for caching (Arc-cache), the more the faster
- be not CPU limited

If you need a ZIL or better disable sync write depends on use case.
If you build an All-In-One (ESXi with virtualized SAN), all your guests 
go down together with your SAN,

so mostly a ZIL costs money and performance but cannot improve security.

You should also trythe ESXI highspeed VMXnet3 network drivers (unless 
you find problems with them like some others)
If you intend to use compression, use LZ4 (with newest OmnoOS stable 
with bugfixes for LZ4)


Have you read my manuals (hope they are helpful)?
http://www.napp-it.org/doc/downloads/all-in-one.pdf and
http://napp-it.org/doc/ESXi-OmniOS_Installation_HOWTO_en.pdf

Gea


On 13.05.2013 20:55, C. L. Martinez wrote:

Hi all,

Next month, we need to deploy an omnios virtual machine to act as 
storage server under esxi 5.1. We can not use bare metal server, and I 
know that is a problem.


We are thinking in disable zil. Is it recommended when omnios is 
installed as a vm?? And we can not use pci passthrough esxi feature 
due to vmotion and HA features enabled in these esxi servers.


Any recommendations about how to configure this vm?

At first stage we can allocate 8 gb of ram and 4 vcpus. And wr need to 
manage 5 tb of data with snapshots and maybr compression in certain 
zfs volumes.


Thanks


___
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