From vab at bb-c.de  Fri Jul  1 16:43:55 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Fri, 1 Jul 2016 18:43:55 +0200
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
	installation --> breakage
Message-ID: <22390.40395.562012.432115@shelob.bb-c.de>

Hi Dan!


This is

  GZ# uname -a
  SunOS radbug 5.11 omnios-r151018-95eaa7e i86pc i386 i86pc

on a newly installed box with one BE:

  GZ# beadm list
  BE     Active Mountpoint Space Policy Created
  omnios NR     /          1.02G static 2016-06-29 22:36

Activating that BE is a no-op, and works, except for one error message:

  GZ# beadm activate omnios
  be_get_uuid: failed to get uuid property from BE root dataset user properties.
  Activated successfully

However, immediately after creation of a brand new NGZ, inside that
NGZ the single existing BE is marked "xNb":

  NGZ# beadm list
  BE  Active Mountpoint Space Policy Created
  zbe xNb2016-07-01 15:40 /          538M  static 2016-07-01 15:40

(The broken formatting is verbatim from the beadm output.)

This makes "pkg install" unhappy, which is how I found the problem.

I then try to activate the single BE in the NGZ.
This should also be a no-op.  But it does not work:

  # beadm activate -v zbe
  be_zone_get_parent_uuid: failed to parse parentuuid
  be_zone_compare_uuids: failed to get parentbe uuid from the given BE
  be_zone_get_parent_uuid: failed to parse parentuuid
  be_zone_compare_uuids: failed to get parentbe uuid from the given BE
  be_activate: activating zone root dataset from non-active global BE is not supported
  Unable to activate zbe.
  Operation not supported.
  Exit 190

It turns out that the GZ active BE root dataset was missing the libbe
properties

  org.opensolaris.libbe:policy
  org.opensolaris.libbe:uuid

and the NGZ dataset was missing

  org.opensolaris.libbe:parentbe

So I just set some arbitrary values:

  GZ# zfs set org.opensolaris.libbe:policy=static rpool/ROOT/omnios
  GZ# zfs set org.opensolaris.libbe:uuid=deadbeef-f00d-cafe-a278-ad6cde331234 rpool/ROOT/omnios
  GZ# zfs set org.opensolaris.libbe:parentbe=deadbeef-f00d-cafe-a278-ad6cde331234 rpool/zones/omnib0/ROOT/zbe

Now everything works again!  And "pkg install" is happy, too.

Looking at "zpool history rpool", I see:

  2016-07-01.15:39:27 zfs create -o mountpoint=legacy -o zoned=on rpool/zones/omnib0/ROOT
  2016-07-01.15:39:32 zfs create -o org.opensolaris.libbe:active=on -o org.opensolaris.libbe:parentbe=(null) -o canmount=noauto rpool/zones/omnib0/ROOT/zbe
  2016-07-01.15:56:20 zfs create -o mountpoint=legacy -o zoned=on rpool/zones/omnit0/ROOT

Note the "(null)" value for the parent BE... probably a follow-on error
because there was no uuid in the GZ BE in the first place.

The GZ was installed via Kayak using the vanilla 95eaa7e r151018.zfs.bz2
and the NGZ was installed with a simple "zoneadm install", no clone or
anything special.

Do you have any idea?  I am willing to supply further data if you want.


Thanks -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"

From danmcd at omniti.com  Fri Jul  1 16:50:54 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Fri, 1 Jul 2016 12:50:54 -0400
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
	installation --> breakage
In-Reply-To: <22390.40395.562012.432115@shelob.bb-c.de>
References: <22390.40395.562012.432115@shelob.bb-c.de>
Message-ID: <154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>


> On Jul 1, 2016, at 12:43 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> 
> Note the "(null)" value for the parent BE... probably a follow-on error
> because there was no uuid in the GZ BE in the first place.
> 
> The GZ was installed via Kayak using the vanilla 95eaa7e r151018.zfs.bz2
> and the NGZ was installed with a simple "zoneadm install", no clone or
> anything special.
> 
> Do you have any idea?  I am willing to supply further data if you want.

The creation of the Kayak ZFS send stream probably needs to set these properties.  Looking around here:

	https://github.com/omniti-labs/kayak/blob/master/build_zfs_send.sh#L68

that seems the natural place to do it.  If you're feeling ambitious, you can fix this script and see if you can build your own Kayak send stream.  We do consider pull requests in any omniti-labs repo for OmniOS (illumos-omnios, omnios-build, pkg5, kayak).

I'm not able to fix it today, and I'm on vacation starting COB today.  After I get back, I can probably respin media with a fixed version of this in place.

Dan


From vab at bb-c.de  Fri Jul  1 17:13:15 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Fri, 1 Jul 2016 19:13:15 +0200
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
	installation --> breakage
In-Reply-To: <154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
Message-ID: <22390.42155.984584.441268@shelob.bb-c.de>

Dan McDonald writes:
> > On Jul 1, 2016, at 12:43 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> >
> > Note the "(null)" value for the parent BE... probably a follow-on error
> > because there was no uuid in the GZ BE in the first place.
> >
> > The GZ was installed via Kayak using the vanilla 95eaa7e r151018.zfs.bz2
> > and the NGZ was installed with a simple "zoneadm install", no clone or
> > anything special.
> >
> > Do you have any idea?  I am willing to supply further data if you want.
>
> The creation of the Kayak ZFS send stream probably needs to set these properties.  Looking around here:
>
> 	https://github.com/omniti-labs/kayak/blob/master/build_zfs_send.sh#L68
>
> that seems the natural place to do it.

But wouldn't that mean that all instances installed via Kayak have
the same uuid?  Not sure I like that... IMHO this should rather go
into the actual client installation process somewhere.

> I'm not able to fix it today, and I'm on vacation starting COB today.
> After I get back, I can probably respin media with a fixed version of
> this in place.

I have a workaround, so there's no rush.  Have a good vacation!
We can continue the discussion when you're back.


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"

From danmcd at omniti.com  Fri Jul  1 17:14:15 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Fri, 1 Jul 2016 13:14:15 -0400
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
	installation --> breakage
In-Reply-To: <22390.42155.984584.441268@shelob.bb-c.de>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
	<22390.42155.984584.441268@shelob.bb-c.de>
Message-ID: <400E236B-2223-44FF-A039-F35DEF9E8689@omniti.com>


> On Jul 1, 2016, at 1:13 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> 
> I have a workaround, so there's no rush.  Have a good vacation!
> We can continue the discussion when you're back.

I'm also trying to get LX up and running on OmniOS.  I'll have some status for the list today, but there's still a lot of work to be done.

Dan


From eric.sproul at circonus.com  Fri Jul  1 17:28:27 2016
From: eric.sproul at circonus.com (Eric Sproul)
Date: Fri, 1 Jul 2016 13:28:27 -0400
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
 installation --> breakage
In-Reply-To: <22390.42155.984584.441268@shelob.bb-c.de>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
	<22390.42155.984584.441268@shelob.bb-c.de>
Message-ID: <CAO8hXRBaN2OKJKG4YjV9KYBCaoCcJMh3j_JOepDCdjxPFgt8BA@mail.gmail.com>

On Fri, Jul 1, 2016 at 1:13 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> But wouldn't that mean that all instances installed via Kayak have
> the same uuid?  Not sure I like that... IMHO this should rather go
> into the actual client installation process somewhere.

Yes, building those properties into the image would be bad. I'd say
the proper thing would be to either add the necessary commands to the
ApplyChanges function [1] or make a new function and have it run
before MakeBootable.

Eric

[1] https://github.com/omniti-labs/kayak/blob/master/install_help.sh#L202-L209

From vab at bb-c.de  Fri Jul  1 17:36:42 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Fri, 1 Jul 2016 19:36:42 +0200
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
 installation --> breakage
In-Reply-To: <CAO8hXRBaN2OKJKG4YjV9KYBCaoCcJMh3j_JOepDCdjxPFgt8BA@mail.gmail.com>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
	<22390.42155.984584.441268@shelob.bb-c.de>
	<CAO8hXRBaN2OKJKG4YjV9KYBCaoCcJMh3j_JOepDCdjxPFgt8BA@mail.gmail.com>
Message-ID: <22390.43562.719782.327846@shelob.bb-c.de>

Eric Sproul writes:
> On Fri, Jul 1, 2016 at 1:13 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> > But wouldn't that mean that all instances installed via Kayak have
> > the same uuid?  Not sure I like that... IMHO this should rather go
> > into the actual client installation process somewhere.
>
> Yes, building those properties into the image would be bad. I'd say
> the proper thing would be to either add the necessary commands to the
> ApplyChanges function [1] or make a new function and have it run
> before MakeBootable.

Yes, the install_help.sh is definitely where it should go.  I think it
should be in the BuildBE() shell function somewhere after the "zfs set
mountpoint" line.  I'll try to come up with something.


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"

From vab at bb-c.de  Fri Jul  1 18:24:07 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Fri, 1 Jul 2016 20:24:07 +0200
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
 installation --> breakage
In-Reply-To: <22390.43562.719782.327846@shelob.bb-c.de>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
	<22390.42155.984584.441268@shelob.bb-c.de>
	<CAO8hXRBaN2OKJKG4YjV9KYBCaoCcJMh3j_JOepDCdjxPFgt8BA@mail.gmail.com>
	<22390.43562.719782.327846@shelob.bb-c.de>
Message-ID: <22390.46407.935584.524539@shelob.bb-c.de>

Volker A. Brandt writes:
> Yes, the install_help.sh is definitely where it should go.  I think it
> should be in the BuildBE() shell function somewhere after the "zfs set
> mountpoint" line.  I'll try to come up with something.

Some nice people put a bash-only version of a UUID generator up on
serverfault.  So here is a first stab:

--8<----------------------------------------------------------------8<--
*** install_help.sh.orig	Thu Apr 14 18:29:37 2016
--- install_help.sh	Fri Jul  1 20:22:16 2016
***************
*** 99,104 ****
--- 99,131 ----
    sleep 1
  }
  
+ # taken from https://gist.github.com/markusfisch/6110640
+ CreateUUID() {
+   local N B C='89ab'
+ 
+   for (( N=0; N < 16; ++N ))
+   do
+     B=$(( $RANDOM%256 ))
+ 
+     case $N in
+       6)
+          printf '4%x' $(( B%16 ))
+          ;;
+       8)
+          printf '%c%x' ${C:$RANDOM%${#C}:1} $(( B%16 ))
+          ;;
+       3 | 5 | 7 | 9)
+          printf '%02x-' $B
+          ;;
+       *)
+          printf '%02x' $B
+          ;;
+     esac
+   done
+ 
+  echo
+ }
+ 
  BuildBE() {
    BOOTSRVA=`/sbin/dhcpinfo BootSrvA`
    MEDIA=`getvar install_media`
***************
*** 112,117 ****
--- 139,148 ----
    curl -s $MEDIA | pv -B 128m | bzip2 -dc | zfs receive -u rpool/ROOT/omnios
    zfs set canmount=noauto rpool/ROOT/omnios
    zfs set mountpoint=legacy rpool/ROOT/omnios
+   UUID=`CreateUUID`
+   log "Generated UUID $UUID for BE root dataset"
+   zfs set org.opensolaris.libbe:uuid=$UUID  rpool/ROOT/omnios
+   zfs set org.opensolaris.libbe:policy=static rpool/ROOT/omnios
    log "Cleaning up boot environment"
    beadm mount omnios /mnt
    ALTROOT=/mnt
***************
*** 225,231 ****
  }
  
  RunInstall(){
!   FetchConfig || bomb "Could not fecth kayak config for target"
    . $ICFILE
    Postboot 'exit $SMF_EXIT_OK'
    ApplyChanges || bomb "Could not apply all configuration changes"
--- 256,262 ----
  }
  
  RunInstall(){
!   FetchConfig || bomb "Could not fetch kayak config for target"
    . $ICFILE
    Postboot 'exit $SMF_EXIT_OK'
    ApplyChanges || bomb "Could not apply all configuration changes"
--8<----------------------------------------------------------------8<--

Sorry about the diff; my github-fu is currently zero.  Also sorry
about fixing the ancient typo in RunInstall; could not resist.

I can't test this until I have a new box to install; feel free to play
with it or ignore me until I follow up with a "confirmed working" mail.


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"

From eric.sproul at circonus.com  Fri Jul  1 18:51:48 2016
From: eric.sproul at circonus.com (Eric Sproul)
Date: Fri, 1 Jul 2016 14:51:48 -0400
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
 installation --> breakage
In-Reply-To: <22390.46407.935584.524539@shelob.bb-c.de>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
	<22390.42155.984584.441268@shelob.bb-c.de>
	<CAO8hXRBaN2OKJKG4YjV9KYBCaoCcJMh3j_JOepDCdjxPFgt8BA@mail.gmail.com>
	<22390.43562.719782.327846@shelob.bb-c.de>
	<22390.46407.935584.524539@shelob.bb-c.de>
Message-ID: <CAO8hXRAxcAWPnEFN5awu3ee+GROK9bMRj_OnYqKJQCfCt8Ov2w@mail.gmail.com>

On Fri, Jul 1, 2016 at 2:24 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> Some nice people put a bash-only version of a UUID generator up on
> serverfault.

FWIW, since https://www.illumos.org/issues/4769 integrated we have
/usr/bin/uuidgen.  All currently-supported OmniOS releases should have
that (I know 014 does).

From danmcd at omniti.com  Fri Jul  1 18:53:22 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Fri, 1 Jul 2016 14:53:22 -0400
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
	installation --> breakage
In-Reply-To: <CAO8hXRAxcAWPnEFN5awu3ee+GROK9bMRj_OnYqKJQCfCt8Ov2w@mail.gmail.com>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
	<22390.42155.984584.441268@shelob.bb-c.de>
	<CAO8hXRBaN2OKJKG4YjV9KYBCaoCcJMh3j_JOepDCdjxPFgt8BA@mail.gmail.com>
	<22390.43562.719782.327846@shelob.bb-c.de>
	<22390.46407.935584.524539@shelob.bb-c.de>
	<CAO8hXRAxcAWPnEFN5awu3ee+GROK9bMRj_OnYqKJQCfCt8Ov2w@mail.gmail.com>
Message-ID: <A6790935-7AB8-49FD-886A-7DD877A15A97@omniti.com>


> On Jul 1, 2016, at 2:51 PM, Eric Sproul <eric.sproul at circonus.com> wrote:
> 
> FWIW, since https://www.illumos.org/issues/4769 integrated we have
> /usr/bin/uuidgen.  All currently-supported OmniOS releases should have
> that (I know 014 does).

Yeah, uuidgen is the right way to do this, and since 014 is the earliest supported release, you're insured of success.

Thanks!
Dan


From danmcd at omniti.com  Fri Jul  1 19:04:52 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Fri, 1 Jul 2016 15:04:52 -0400
Subject: [OmniOS-discuss] LX on OmniOS update
Message-ID: <1DF63836-3440-4F7C-B035-8DADE794E7B5@omniti.com>

Hello!

I'm BCc:ing the illumos developer and illumos discussion lists.  This thread should continue on omnios-discuss.  Please note I will be very slow to get back to emails until July 12th.

I'd like to report some progress on the LX zones for OmniOS work.

First some URLs.  The git repos are:

	https://github.com/danmcd/io-lx-public/

	https://github.com/danmcd/ob-lx-public/

The latter has only one small change in its manifests.  The former is where the big work is.  Feel free to clone/pull and toy around. At this time, I will consider PRs, but likely not issues unless they accompany a PR.  If you have LX-for-OmniOS suggestions or issues, please bring them up on the omnios-discuss mailing list.

I have webrevs of io-lx against illumos-omnios AND against illumos-joyent:

	http://kebe.com/~danmcd/webrevs/io-lx-public/

	http://kebe.com/~danmcd/webrevs/io-lx-public-vs-joyent/

And finally, I have an IPS server with bloody + LX on it.  You should retarget your "omnios" publisher on a bloody install to it if you want to try them out:

	http://pkg.omniti.com/omnios/LX/

The bits so far are able to install an LX zone.  Here's a sample zone configuration (you'll have to create an "lx0" vNIC):

# zonecfg -z lx0 export
create -b
set zonepath=/zones/lx0
set brand=lx
set autoboot=false
set ip-type=exclusive
add net
set physical=lx0
end
# 

To install an LX zone on OmniOS, first you must install the LX brand:

	pkg install brand/lx

then you need either a compressed or uncompressed ZFS send stream.  The Joyent image repo has these compressed.  To grab one for Alpine, e.g.:

	curl -O alpine.gz https://images.joyent.com/images/d8830f1e-3680-11e6-be72-2ba188e02d31/file

The UUID portion of that URL can be modifed to match a given "imgadm" UUID you find on a SmartOS box.

Once you have that, place it somewhere and use its absolute path:

	zoneadm -z lx0 install -s /path/to/alpine.gz

You can then ATTEMPT to boot the zone:

	zoneadm -z lx0 boot

ONLY ALPINE is known to reach a login prompt on the console.  You will also have to manually configure networking on it using the /native tools:

	/native/sbin/ifconfig lx0 addr/prefix up

In the limited testing I've done thus far, Alpine appears to work.  Note my phrasing "appears to work".  I've been able to configure networking using /native tools and been able to ssh in once I've edited /etc/ssh/sshd_config to be more permissive.

NOTE:  LX zones and their Datasets are currently independent of boot environments.  One of the upcoming design decisions is how to handle LX zones on OmniOS, where BEs are very important.  Input on this mailing list would be appreciated.  Currently, if you change BEs, you may not have an LX zone configured, but its dataset will still be around.  You can use "zoneadm attach" after "zonecfg" if you wish.

Two other distro images -- Ubuntu 14.04 and Centos 6.8 -- have been attempted, but their /sbin/init exits with EBADF on a writev to stdout (fd == 2).  I suspect I'm doing something wrong with them (as pfiles(1) shows me no open FDs on /sbin/init), but I will not have time to debug them until July 12th at the earliest.  I will also be mostly away from email during this time as well.

It's progress.  Thanks go out to Joyent folks who've been VERY HELPFUL and whose LX code has been mostly free of SmartOS-specific assumptions thus far.  Thus far I've had to make only one change to zoneadmd that's truly deviant from illumos-joyent and not just a merge or mismerge.

Happy (alpine-only) LX-ing,
Dan


From vab at bb-c.de  Fri Jul  1 19:21:13 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Fri, 1 Jul 2016 21:21:13 +0200
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
	installation --> breakage
In-Reply-To: <A6790935-7AB8-49FD-886A-7DD877A15A97@omniti.com>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
	<22390.42155.984584.441268@shelob.bb-c.de>
	<CAO8hXRBaN2OKJKG4YjV9KYBCaoCcJMh3j_JOepDCdjxPFgt8BA@mail.gmail.com>
	<22390.43562.719782.327846@shelob.bb-c.de>
	<22390.46407.935584.524539@shelob.bb-c.de>
	<CAO8hXRAxcAWPnEFN5awu3ee+GROK9bMRj_OnYqKJQCfCt8Ov2w@mail.gmail.com>
	<A6790935-7AB8-49FD-886A-7DD877A15A97@omniti.com>
Message-ID: <22390.49833.474106.549060@shelob.bb-c.de>

Dan McDonald writes:
> > On Jul 1, 2016, at 2:51 PM, Eric Sproul <eric.sproul at circonus.com> wrote:
> > 
> > FWIW, since https://www.illumos.org/issues/4769 integrated we have
> > /usr/bin/uuidgen.  All currently-supported OmniOS releases should have
> > that (I know 014 does).
> 
> Yeah, uuidgen is the right way to do this, and since 014 is the earliest supported release, you're insured of success.

In that case, you need to put it on the miniroot. :-)


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"

From danmcd at omniti.com  Fri Jul  1 19:21:41 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Fri, 1 Jul 2016 15:21:41 -0400
Subject: [OmniOS-discuss] GZ BE missing libbe:uuid property after Kayak
	installation --> breakage
In-Reply-To: <22390.49833.474106.549060@shelob.bb-c.de>
References: <22390.40395.562012.432115@shelob.bb-c.de>
	<154EE53A-9B7F-4C73-8355-BBD58DF3EFCF@omniti.com>
	<22390.42155.984584.441268@shelob.bb-c.de>
	<CAO8hXRBaN2OKJKG4YjV9KYBCaoCcJMh3j_JOepDCdjxPFgt8BA@mail.gmail.com>
	<22390.43562.719782.327846@shelob.bb-c.de>
	<22390.46407.935584.524539@shelob.bb-c.de>
	<CAO8hXRAxcAWPnEFN5awu3ee+GROK9bMRj_OnYqKJQCfCt8Ov2w@mail.gmail.com>
	<A6790935-7AB8-49FD-886A-7DD877A15A97@omniti.com>
	<22390.49833.474106.549060@shelob.bb-c.de>
Message-ID: <871273BC-81A8-4C1B-9024-DFA39CFD5E05@omniti.com>


> On Jul 1, 2016, at 3:21 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> 
> In that case, you need to put it on the miniroot. :-)

Dammit.  That too.

Thanks,
Dan


From wonko at 4amlunch.net  Fri Jul  1 22:37:01 2016
From: wonko at 4amlunch.net (wonko at 4amlunch.net)
Date: Fri, 1 Jul 2016 18:37:01 -0400
Subject: [OmniOS-discuss] LX on OmniOS update
In-Reply-To: <1DF63836-3440-4F7C-B035-8DADE794E7B5@omniti.com>
References: <1DF63836-3440-4F7C-B035-8DADE794E7B5@omniti.com>
Message-ID: <82FD45A5-8BE4-4572-A000-AC2A654D3AF9@4amlunch.net>

You are amazing. Keep up the great work. We love you!!

I'll test this out as I have time. I'm very excited for this!

-brian

> On Jul 1, 2016, at 15:04, Dan McDonald <danmcd at omniti.com> wrote:
> 
> Hello!
> 
> I'm BCc:ing the illumos developer and illumos discussion lists.  This thread should continue on omnios-discuss.  Please note I will be very slow to get back to emails until July 12th.
> 
> I'd like to report some progress on the LX zones for OmniOS work.
> 
> First some URLs.  The git repos are:
> 
>    https://github.com/danmcd/io-lx-public/
> 
>    https://github.com/danmcd/ob-lx-public/
> 
> The latter has only one small change in its manifests.  The former is where the big work is.  Feel free to clone/pull and toy around. At this time, I will consider PRs, but likely not issues unless they accompany a PR.  If you have LX-for-OmniOS suggestions or issues, please bring them up on the omnios-discuss mailing list.
> 
> I have webrevs of io-lx against illumos-omnios AND against illumos-joyent:
> 
>    http://kebe.com/~danmcd/webrevs/io-lx-public/
> 
>    http://kebe.com/~danmcd/webrevs/io-lx-public-vs-joyent/
> 
> And finally, I have an IPS server with bloody + LX on it.  You should retarget your "omnios" publisher on a bloody install to it if you want to try them out:
> 
>    http://pkg.omniti.com/omnios/LX/
> 
> The bits so far are able to install an LX zone.  Here's a sample zone configuration (you'll have to create an "lx0" vNIC):
> 
> # zonecfg -z lx0 export
> create -b
> set zonepath=/zones/lx0
> set brand=lx
> set autoboot=false
> set ip-type=exclusive
> add net
> set physical=lx0
> end
> # 
> 
> To install an LX zone on OmniOS, first you must install the LX brand:
> 
>    pkg install brand/lx
> 
> then you need either a compressed or uncompressed ZFS send stream.  The Joyent image repo has these compressed.  To grab one for Alpine, e.g.:
> 
>    curl -O alpine.gz https://images.joyent.com/images/d8830f1e-3680-11e6-be72-2ba188e02d31/file
> 
> The UUID portion of that URL can be modifed to match a given "imgadm" UUID you find on a SmartOS box.
> 
> Once you have that, place it somewhere and use its absolute path:
> 
>    zoneadm -z lx0 install -s /path/to/alpine.gz
> 
> You can then ATTEMPT to boot the zone:
> 
>    zoneadm -z lx0 boot
> 
> ONLY ALPINE is known to reach a login prompt on the console.  You will also have to manually configure networking on it using the /native tools:
> 
>    /native/sbin/ifconfig lx0 addr/prefix up
> 
> In the limited testing I've done thus far, Alpine appears to work.  Note my phrasing "appears to work".  I've been able to configure networking using /native tools and been able to ssh in once I've edited /etc/ssh/sshd_config to be more permissive.
> 
> NOTE:  LX zones and their Datasets are currently independent of boot environments.  One of the upcoming design decisions is how to handle LX zones on OmniOS, where BEs are very important.  Input on this mailing list would be appreciated.  Currently, if you change BEs, you may not have an LX zone configured, but its dataset will still be around.  You can use "zoneadm attach" after "zonecfg" if you wish.
> 
> Two other distro images -- Ubuntu 14.04 and Centos 6.8 -- have been attempted, but their /sbin/init exits with EBADF on a writev to stdout (fd == 2).  I suspect I'm doing something wrong with them (as pfiles(1) shows me no open FDs on /sbin/init), but I will not have time to debug them until July 12th at the earliest.  I will also be mostly away from email during this time as well.
> 
> It's progress.  Thanks go out to Joyent folks who've been VERY HELPFUL and whose LX code has been mostly free of SmartOS-specific assumptions thus far.  Thus far I've had to make only one change to zoneadmd that's truly deviant from illumos-joyent and not just a merge or mismerge.
> 
> Happy (alpine-only) LX-ing,
> Dan
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From geoffn at gnaa.net  Sat Jul  2 06:06:53 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Fri, 1 Jul 2016 23:06:53 -0700
Subject: [OmniOS-discuss] virtualbox memory fault -- fixed
In-Reply-To: <C449089C-D789-4168-8265-D04C56D7B92B@omniti.com>
References: <5772C723.80509@gnaa.net>
	<201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
	<5772CBE6.4010608@gnaa.net>
	<9B1B1587-CDC7-463C-B727-8FE4CB0CDBC3@omniti.com>
	<5772D692.6010108@gnaa.net> <57731575.7010502@gnaa.net>
	<C6340EF3-00C2-4C3E-B508-55847D83F431@omniti.com>
	<57741AD6.3080009@gnaa.net>
	<C449089C-D789-4168-8265-D04C56D7B92B@omniti.com>
Message-ID: <577759FD.3040804@gnaa.net>

Good news!!

Oracle fixed the problem and it works now with a test build (>= 108405).



On 2016-06-29 01:11 PM, Dale Ghent wrote:
>> On Jun 29, 2016, at 3:00 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>
>>
>>
>> On 2016-06-28 06:18 PM, Dale Ghent wrote:
>>>> On Jun 28, 2016, at 8:25 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>>>
>>>>
>>>>
>>>> On 2016-06-28 12:57 PM, Geoff Nordli wrote:
>>>>> On 2016-06-28 12:23 PM, Dale Ghent wrote:
>>>>>> Is the vbox version you?re using on your new server different from that which you are using on existing ones?
>>>>>>
>>>>>> Are you compiling vbox on OmniOS, or using the pre-compiled Solaris binaries from Oracle?
>>>>>>
>>>>>> /dale
>>>>>>
>>>>>>> On Jun 28, 2016, at 3:11 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 2016-06-28 11:59 AM, John D Groenveld wrote:
>>>>>>>> In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>>>>>>>>> I am running OmniOS v11 r151018.
>>>>>>>>>
>>>>>>>>> I have quite a few OI/Omnios OS boxes running Virtualbox. I haven't see
>>>>>>>>> this before.  On a new server I just installed I am getting a memory
>>>>>>>>> fault right away when starting a vm.
>>>>>>>> Perhaps set disable_smap=1?
>>>>>>>> <URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html>
>>>>>>>>
>>>>>>>> BTW have you done any benchmarking between VBox and KVM?
>>>>>>>> John
>>>>>>>> groenveld at acm.org
>>>>>>>>
>>>>>>> Hi John.
>>>>>>>
>>>>>>> Yes, I set the disable_smap in the system and rebooted, but it doesn't seem to help.  That setting supposedly prevents the host from rebooting.
>>>>>>>
>>>>>>> On a Windows Server 2012 R2 I am getting the following networking performance with iperf (default settings).
>>>>>>>
>>>>>>> Client -> VM  903Mbps
>>>>>>> VM -> Client  572Mbps
>>>>>>>
>>>>>>> I am focused on small business systems and protecting their data, so these numbers are more than good enough.
>>>>>>>
>>>>>>>
>>>>> Hi Dale.
>>>>>
>>>>> I am using the pre-compiled binaries from the vbox download site.
>>>>>
>>>>> I have another server using the same OmniOS release.   The one that works is running 5.0.20, but i have tried both versions of vbox on the new server and both are producing the memory fault.
>>>>>
>>>>> The only thing that seems to be different about these boxes are the CPUs.   The one that works has older Xeons, the new one that doesn't work is running E5-2630V3 (haswell).
>>>>>
>>>>> thanks,
>>>>>
>>>>> Geoff
>>>>>
>>>>>
>>>> Just tried the newly released 5.0.24 and it still gives the same error.
>>> Well, using Solaris on illumos is going to be a more and more iffy proposition as time marches on; it's hard to say what might have changed on Oracle Solaris, if anything; that the vbox packages were compiled on.
>>>
>>> How about trying a earlier release of vbox, to perhaps isolate the issue further? Since there is no guarantee for Oracle Solaris binary compatibility, this is kind of an ambiguous zone here.
>>>
>>> /dale
>>>
>> Dale, you are probably right, that is a tough pill to swallow though since I have a lot of scripts/tools to manage vbox and it works really well on OmniOS -- when it works :)
> One of the underlying reasons for this is that illumos (and by extension, OmniOS) still identify as ?SunOS 5.11?, which the vbox build system equates to ?Oracle Solaris 11?
>
> Since Oracle Solaris 11 and illumos are moving on in their own directions and the technical differences between them only grow over time, this is a pain point when it comes to trying to get binaries that were compiled on one to work on the other. A good example of this in the context of vbox is vboxfs, which now uses some symbols added in a Oracle Solaris 11 update, but do not exist on illumos.
>
> /dale


From mir at miras.org  Sat Jul  2 13:42:13 2016
From: mir at miras.org (Michael Rasmussen)
Date: Sat, 2 Jul 2016 15:42:13 +0200
Subject: [OmniOS-discuss] missing md2.h in openssl
Message-ID: <20160702154213.45b54a7e@sleipner.datanom.net>

Hi list,

cat /etc/release 
  OmniOS v11 r151014
  Copyright 2015 OmniTI Computer Consulting, Inc. All rights reserved.
  Use is subject to license terms.

Seems openssl is missing a header file:
SSLeay.xs:171:25: fatal error: openssl/md2.h: No such file or directory

find / -xdev -name md2.h gives no hit.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
/usr/games/fortune -es says:
Snakes.  Why did it have to be snakes?
		-- Indiana Jones, "Raiders of the Lost Ark"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160702/c7d9831d/attachment.bin>

From danmcd at omniti.com  Sat Jul  2 18:05:00 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Sat, 2 Jul 2016 14:05:00 -0400
Subject: [OmniOS-discuss] missing md2.h in openssl
In-Reply-To: <20160702154213.45b54a7e@sleipner.datanom.net>
References: <20160702154213.45b54a7e@sleipner.datanom.net>
Message-ID: <3B6A2B84-1C59-4220-8BD2-BF1C502350A3@omniti.com>

Yes - one of the very recent OpenSSL updates eol'ed md2.  It's not clear what this is blocking you on.

Dan

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

> On Jul 2, 2016, at 9:42 AM, Michael Rasmussen <mir at miras.org> wrote:
> 
> Hi list,
> 
> cat /etc/release 
>  OmniOS v11 r151014
>  Copyright 2015 OmniTI Computer Consulting, Inc. All rights reserved.
>  Use is subject to license terms.
> 
> Seems openssl is missing a header file:
> SSLeay.xs:171:25: fatal error: openssl/md2.h: No such file or directory
> 
> find / -xdev -name md2.h gives no hit.
> 
> -- 
> Hilsen/Regards
> Michael Rasmussen
> 
> Get my public GnuPG keys:
> michael <at> rasmussen <dot> cc
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
> mir <at> datanom <dot> net
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
> mir <at> miras <dot> org
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
> --------------------------------------------------------------
> /usr/games/fortune -es says:
> Snakes.  Why did it have to be snakes?
>        -- Indiana Jones, "Raiders of the Lost Ark"
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From mir at miras.org  Sat Jul  2 18:47:22 2016
From: mir at miras.org (Michael Rasmussen)
Date: Sat, 2 Jul 2016 20:47:22 +0200
Subject: [OmniOS-discuss] missing md2.h in openssl
In-Reply-To: <3B6A2B84-1C59-4220-8BD2-BF1C502350A3@omniti.com>
References: <20160702154213.45b54a7e@sleipner.datanom.net>
	<3B6A2B84-1C59-4220-8BD2-BF1C502350A3@omniti.com>
Message-ID: <20160702204722.01a2a36d@sleipner.datanom.net>

On Sat, 2 Jul 2016 14:05:00 -0400
Dan McDonald <danmcd at omniti.com> wrote:

> Yes - one of the very recent OpenSSL updates eol'ed md2.  It's not clear what this is blocking you on.
> 
Compiling SSLeay does not work when using defaults but using this when
compiling SSLeay solves the matter:
perl Makefile.PL CCCDLFLAGS='-DOPENSSL_NO_MD2 -fPIC'

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
/usr/games/fortune -es says:
The verdict of a jury is the a priori opinion of that juror who smokes
the worst cigars.
		-- H. L. Mencken
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160702/e8953465/attachment.bin>

From mir at miras.org  Sat Jul  2 19:56:15 2016
From: mir at miras.org (Michael Rasmussen)
Date: Sat, 2 Jul 2016 21:56:15 +0200
Subject: [OmniOS-discuss] kernel hardware error info
Message-ID: <20160702215615.1fac6d28@sleipner.datanom.net>

Hi all,

On my console and log this message has just be written:
 kernel:[39306.138997] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD

Somebody which could explain was this mean and whether I should worry?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
/usr/games/fortune -es says:
In /users3 did Kubla Kahn
A stately pleasure dome decree,
Where /bin, the sacred river ran
Through Test Suites measureless to Man
Down to a sunless C.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160702/9aa6e724/attachment.bin>

From lotheac at iki.fi  Sat Jul  2 20:03:07 2016
From: lotheac at iki.fi (Lauri Tirkkonen)
Date: Sat, 2 Jul 2016 23:03:07 +0300
Subject: [OmniOS-discuss] missing md2.h in openssl
In-Reply-To: <20160702204722.01a2a36d@sleipner.datanom.net>
References: <20160702154213.45b54a7e@sleipner.datanom.net>
	<3B6A2B84-1C59-4220-8BD2-BF1C502350A3@omniti.com>
	<20160702204722.01a2a36d@sleipner.datanom.net>
Message-ID: <20160702200307.GA10350@kekkonen.niksula.hut.fi>

On Sat, Jul 02 2016 20:47:22 +0200, Michael Rasmussen wrote:
> On Sat, 2 Jul 2016 14:05:00 -0400
> Dan McDonald <danmcd at omniti.com> wrote:
> 
> > Yes - one of the very recent OpenSSL updates eol'ed md2.  It's not clear what this is blocking you on.
> > 
> Compiling SSLeay does not work when using defaults but using this when
> compiling SSLeay solves the matter:
> perl Makefile.PL CCCDLFLAGS='-DOPENSSL_NO_MD2 -fPIC'

Works fine for me out of the box with
gcc48 at 4.8.1-0.151014:20160516T163714Z.
https://github.com/omniti-labs/omnios-build/issues/85

-- 
Lauri Tirkkonen | lotheac @ IRCnet

From stephan.budach at JVM.DE  Sun Jul  3 14:33:24 2016
From: stephan.budach at JVM.DE (Stephan Budach)
Date: Sun, 3 Jul 2016 16:33:24 +0200
Subject: [OmniOS-discuss] Chasing down scsi-related warnings
Message-ID: <0b28dbf6-1039-56e8-2718-6a28de1df6a3@jvm.de>

Hi all,

I am having trouble chasing down some network or drive-related errors on 
one of my OmniOS r018 boxes. It started by me noticing these errors in 
the syslog on one of my RSF-1 nodes. These are just a few, but I found 
almost every drive/LUN of that target node mentioned in the syslogd on 
the RSF-1 node:

Jul  3 15:51:01 zfsha01colt scsi: [ID 107833 kern.warning] WARNING: 
/scsi_vhci/disk at g600144f0564d504f4f4c3033534c3034 (sd4):
Jul  3 15:51:01 zfsha01colt     incomplete write- retrying
Jul  3 15:51:29 zfsha01colt scsi: [ID 107833 kern.warning] WARNING: 
/scsi_vhci/disk at g600144f0564d504f4f4c3033534c3035 (sd5):
Jul  3 15:51:29 zfsha01colt     incomplete write- retrying
Jul  3 15:55:25 zfsha01colt scsi: [ID 107833 kern.warning] WARNING: 
/scsi_vhci/disk at g600144f0564d504f4f4c3033534c3039 (sd6):
Jul  3 15:55:25 zfsha01colt     incomplete write- retrying
Jul  3 16:06:43 zfsha01colt scsi: [ID 107833 kern.warning] WARNING: 
/scsi_vhci/disk at g600144f0564d504f4f4c3033534c3135 (sd43):
Jul  3 16:06:43 zfsha01colt     incomplete write- retrying

Also, iostat -exM is showing HW errors for those LUNs, although I can't 
confirm that the actual drives are at fault on the iSCSI target, which 
is provided by another OmniOS box.

I then failed the zpools over from that target to the second HA node and 
the errors went along with it, so I am assuming that these errors are 
either network related to the storage node or maybe even 
drive/controller related to the storage node. However, I can't seem to 
pin point the problem. As these are only warnings, there is no visisble 
sign about any issue on the storage node, but nonetheless I'd like to 
know, what the underlying issue is.

Any ideas, anyone?

Thanks,
Stephan

From skeltonr at btconnect.com  Tue Jul  5 20:06:45 2016
From: skeltonr at btconnect.com (Richard Skelton)
Date: Tue, 05 Jul 2016 21:06:45 +0100
Subject: [OmniOS-discuss] How do I start apache when installed from
	ms.omniti.com repo
Message-ID: <577C1355.5010508@btconnect.com>

Hi
I have installed the apache pkg from ms.omniti.com
pkg set-publisher -g http://pkg.omniti.com/omniti-ms/ ms.omniti.com
pkg install apache22
pkg install php-54
pkg install mysql-55

Are there any SMF manifest?

I  also need to config php 5.4 and start mysql 55

Any help much appreciated

Cheer
Richard.

From vab at bb-c.de  Tue Jul  5 20:29:15 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Tue, 5 Jul 2016 22:29:15 +0200
Subject: [OmniOS-discuss] How do I start apache when installed
	from	ms.omniti.com repo
In-Reply-To: <577C1355.5010508@btconnect.com>
References: <577C1355.5010508@btconnect.com>
Message-ID: <22396.6299.264650.822637@shelob.bb-c.de>

> I have installed the apache pkg from ms.omniti.com
> pkg set-publisher -g http://pkg.omniti.com/omniti-ms/ ms.omniti.com
> pkg install apache22
> pkg install php-54
> pkg install mysql-55
> 
> Are there any SMF manifest?

The SMF manifest for the ms.omniti.com version of the Apache 2.2 package
is included; check the file "/opt/apache22/conf/http-apache.xml".


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"

From skeltonr at btconnect.com  Tue Jul  5 21:01:49 2016
From: skeltonr at btconnect.com (Richard Skelton)
Date: Tue, 05 Jul 2016 22:01:49 +0100
Subject: [OmniOS-discuss] How do I start apache when installed
 from	ms.omniti.com repo
In-Reply-To: <22396.6299.264650.822637@shelob.bb-c.de>
References: <577C1355.5010508@btconnect.com>
	<22396.6299.264650.822637@shelob.bb-c.de>
Message-ID: <577C203D.6010001@btconnect.com>

Hi Volker,
Thanks for that :-)
I ran :-
svccfg import /opt/apache22/conf/http-apache.xml
then mkdir /www
svcadm enable svc:/network/http:apache22
but it fails :-
httpd: Syntax error on line 116 of /opt/apache22/conf/httpd.conf: Cannot
load /opt/apache22/libexec/amd64/mod_log_rotate.so into server: ld.so.1:
httpd: fatal: /opt/apache22/libexec/amd64/mod_log_rotate.so: open
failed: No such file or directory

I can see there is a pkg
omniti/server/apache22/mod_log_rotate at 2-0.151014:20150611T161005Z
<http://pkg.omniti.com/omniti-ms/info/0/omniti%2Fserver%2Fapache22%2Fmod_log_rotate%402%2C5.11-0.151014%3A20150611T161005Z>

Is there a way to install all the dependent packages?


Volker A. Brandt wrote:
>> I have installed the apache pkg from ms.omniti.com
>> pkg set-publisher -g http://pkg.omniti.com/omniti-ms/ ms.omniti.com
>> pkg install apache22
>> pkg install php-54
>> pkg install mysql-55
>>
>> Are there any SMF manifest?
>>     
>
> The SMF manifest for the ms.omniti.com version of the Apache 2.2 package
> is included; check the file "/opt/apache22/conf/http-apache.xml".
>
>
> Regards -- Volker
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160705/35f65ff2/attachment.html>

From bfriesen at simple.dallas.tx.us  Tue Jul  5 22:34:55 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Tue, 5 Jul 2016 17:34:55 -0500 (CDT)
Subject: [OmniOS-discuss] How do I start apache when installed from
 ms.omniti.com repo
In-Reply-To: <577C203D.6010001@btconnect.com>
References: <577C1355.5010508@btconnect.com>
	<22396.6299.264650.822637@shelob.bb-c.de>
	<577C203D.6010001@btconnect.com>
Message-ID: <alpine.GSO.2.20.1607051726360.21946@freddy.simplesystems.org>

On Tue, 5 Jul 2016, Richard Skelton wrote:

> Hi Volker,
> Thanks for that :-)
> I ran :-
> svccfg import /opt/apache22/conf/http-apache.xml
> then mkdir /www
> svcadm enable svc:/network/http:apache22
> but it fails :-
> httpd: Syntax error on line 116 of /opt/apache22/conf/httpd.conf: Cannot
> load /opt/apache22/libexec/amd64/mod_log_rotate.so into server: ld.so.1:
> httpd: fatal: /opt/apache22/libexec/amd64/mod_log_rotate.so: open
> failed: No such file or directory
>
> I can see there is a pkg
> omniti/server/apache22/mod_log_rotate at 2-0.151014:20150611T161005Z
> <http://pkg.omniti.com/omniti-ms/info/0/omniti%2Fserver%2Fapache22%2Fmod_log_rotate%402%2C5.11-0.151014%3A20150611T161005Z>
>
> Is there a way to install all the dependent packages?

This is "unsupported" software.  You could choose to comment out line 
116 of /opt/apache22/conf/httpd.conf if you don't plan to use its 
log-rotate functionality.  My recollection is that OmniTI's httpd.conf 
is compact and written from scratch.  It is possible to restore the 
default Apache "It works!" configuration.

After seeing the "unsupported" nature of the OmniTI packages and that 
many of them are for rather old OmniOS, I decided to create my own 
Apache package.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

From geoffn at gnaa.net  Tue Jul  5 22:47:50 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 5 Jul 2016 15:47:50 -0700
Subject: [OmniOS-discuss] How do I start apache when installed from
 ms.omniti.com repo
In-Reply-To: <alpine.GSO.2.20.1607051726360.21946@freddy.simplesystems.org>
References: <577C1355.5010508@btconnect.com>
	<22396.6299.264650.822637@shelob.bb-c.de>
	<577C203D.6010001@btconnect.com>
	<alpine.GSO.2.20.1607051726360.21946@freddy.simplesystems.org>
Message-ID: <577C3916.5000902@gnaa.net>



On 2016-07-05 03:34 PM, Bob Friesenhahn wrote:
> On Tue, 5 Jul 2016, Richard Skelton wrote:
>
>> Hi Volker,
>> Thanks for that :-)
>> I ran :-
>> svccfg import /opt/apache22/conf/http-apache.xml
>> then mkdir /www
>> svcadm enable svc:/network/http:apache22
>> but it fails :-
>> httpd: Syntax error on line 116 of /opt/apache22/conf/httpd.conf: Cannot
>> load /opt/apache22/libexec/amd64/mod_log_rotate.so into server: ld.so.1:
>> httpd: fatal: /opt/apache22/libexec/amd64/mod_log_rotate.so: open
>> failed: No such file or directory
>>
>> I can see there is a pkg
>> omniti/server/apache22/mod_log_rotate at 2-0.151014:20150611T161005Z
>> <http://pkg.omniti.com/omniti-ms/info/0/omniti%2Fserver%2Fapache22%2Fmod_log_rotate%402%2C5.11-0.151014%3A20150611T161005Z> 
>>
>>
>> Is there a way to install all the dependent packages?
>
> This is "unsupported" software.  You could choose to comment out line 
> 116 of /opt/apache22/conf/httpd.conf if you don't plan to use its 
> log-rotate functionality.  My recollection is that OmniTI's httpd.conf 
> is compact and written from scratch.  It is possible to restore the 
> default Apache "It works!" configuration.
>
> After seeing the "unsupported" nature of the OmniTI packages and that 
> many of them are for rather old OmniOS, I decided to create my own 
> Apache package.
>
> Bob

There is also pkgsrc: https://pkgsrc.joyent.com/install-on-illumos/ if 
you want the amp stack.

Geoff




From vab at bb-c.de  Wed Jul  6 07:38:26 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Wed, 6 Jul 2016 09:38:26 +0200
Subject: [OmniOS-discuss] How do I start apache when installed
 from	ms.omniti.com repo
In-Reply-To: <577C203D.6010001@btconnect.com>
References: <577C1355.5010508@btconnect.com>
	<22396.6299.264650.822637@shelob.bb-c.de>
	<577C203D.6010001@btconnect.com>
Message-ID: <22396.46450.112757.280717@shelob.bb-c.de>

> I can see there is a pkg omniti/server/apache22/
> mod_log_rotate at 2-0.151014:20150611T161005Z

Yes, that is what you need.

> Is there a way to install all the dependent packages?

The dependent packages that are marked as such in the apache22 package
are installed automatically.  For some reason, the OmniOS people have
decided that mod_log_rotate is optional and there is no dependency.

Fortunately, this is the only such package you need to install. :-)

As others have pointed out, the packages are "unsupported".  To me, that
means they have exactly the same support as anything I'd compile myself:
If something doesn't work, I'll have to fix it.

We have found that the apache22 package from the ms.omniti.com repo is
"good enough" for our in-house use.  So we happily use it.  Your needs
might differ...


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"

From bfriesen at simple.dallas.tx.us  Wed Jul  6 13:31:04 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Wed, 6 Jul 2016 08:31:04 -0500 (CDT)
Subject: [OmniOS-discuss] How do I start apache when installed from
 ms.omniti.com repo
In-Reply-To: <577C3916.5000902@gnaa.net>
References: <577C1355.5010508@btconnect.com>
	<22396.6299.264650.822637@shelob.bb-c.de>
	<577C203D.6010001@btconnect.com>
	<alpine.GSO.2.20.1607051726360.21946@freddy.simplesystems.org>
	<577C3916.5000902@gnaa.net>
Message-ID: <alpine.GSO.2.20.1607060823180.17565@freddy.simplesystems.org>

On Tue, 5 Jul 2016, Geoff Nordli wrote:
>
> There is also pkgsrc: https://pkgsrc.joyent.com/install-on-illumos/ if you 
> want the amp stack.

This is a very large collection of packages which are easy to install, 
but it uses a different package manager than IPS.  Installed packages 
are sometimes redundant with what comes with OmniOS and more software 
may be installed than strictly needed since most package options are 
enabled (similar to Linux).  This is not much of a problem for the 
global zone but seems expensive (for space consumed) for non-global 
zones.

I was intially put-off by the pkgsrc solution when I wanted to install 
just a subversion VCS client and observed that a great many packages 
where installed, including Apache, which was automatically started up.

If you start with pkgsrc, you probably want to use it for everything.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

From bfriesen at simple.dallas.tx.us  Wed Jul  6 13:37:35 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Wed, 6 Jul 2016 08:37:35 -0500 (CDT)
Subject: [OmniOS-discuss] How do I start apache when installed from
 ms.omniti.com repo
In-Reply-To: <22396.46450.112757.280717@shelob.bb-c.de>
References: <577C1355.5010508@btconnect.com>
	<22396.6299.264650.822637@shelob.bb-c.de>
	<577C203D.6010001@btconnect.com>
	<22396.46450.112757.280717@shelob.bb-c.de>
Message-ID: <alpine.GSO.2.20.1607060834060.17565@freddy.simplesystems.org>

On Wed, 6 Jul 2016, Volker A. Brandt wrote:

>> I can see there is a pkg omniti/server/apache22/
>> mod_log_rotate at 2-0.151014:20150611T161005Z
>
> Yes, that is what you need.
>
>> Is there a way to install all the dependent packages?
>
> The dependent packages that are marked as such in the apache22 package
> are installed automatically.  For some reason, the OmniOS people have
> decided that mod_log_rotate is optional and there is no dependency.
>
> Fortunately, this is the only such package you need to install. :-)

I am using the Solaris log rotation program (via /etc/logadm.conf) to 
perform Apache log rotation.  The rule is similar to

apache -C 24 -a '/usr/local/apache22/bin/i386/apachectl graceful' \
   -p 1m -t '/logs/old/$basename.%Y-%m' '/logs/*{access,error}_log'

YMMV.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

From horacek at ssi.cz  Fri Jul 15 15:47:47 2016
From: horacek at ssi.cz (=?utf-8?q?Hor=c3=a1=c4=8dek=20Radim?=)
Date: Fri, 15 Jul 2016 15:47:47 +0000
Subject: [OmniOS-discuss] firefox24
Message-ID: <em3bfa6250-f9ad-45a0-a872-76b785d391ec@horaceknbw7-2>

Dear,

please, how to install Firefox24 on OmniOS (bloody)? I used 
pkgsrc-2016Q1 - installed firefox24 and firefox24-l10n. But I get an 
error when running:

Segmentation fault (core dumped)

Any ideas?


Radim Hor??ek

IT Specialista | IT Specialist
+420 773 798 837 | horacek at ssi.cz


Special Service International, spol. s r. o.
Palmovka Business Centre, Na ?ertv?ch 2247/29, 180 00 Praha 8
+ 420 222 722 590 | www.ssi.cz

IT'SSIMPLE

UPOZORN?N? O D?V?RN?M CHARAKTERU ZPR?VY Informace obsa?en? v t?to zpr?v? 
mohou b?t d?v?rn?ho charakteru a mohou pou??vat zvl??tn? ochrany. Jsou 
ur?eny v?hradn? uveden?m adres?t?m. Pokud nejste adres?tem, obratem m?, 
pros?m, informujte (zasl?n?m zpr?vy zp?t odes?lateli) a zpr?vu vyma?te 
ze syst?mu. Bez ??dn? vydan?ho souhlasu je zak?z?no informace obsa?en? 
ve zpr?v? jak?mkoliv zp?sobem pou??vat ?i je d?le ???it.

PRIVACY AND CONFIDENTIALITY NOTICE This e-mail may contain privileged 
and confidential information. It is intended for the named recipients 
only. If you are not an intended recipient, please notify us immediately 
(by reply e-mail) and delete this e-mail from your system. Any use or 
retransmission without proper authorization is prohibited.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160715/2540d6fb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SSI_GROUP_logo.jpg
Type: image/jpeg
Size: 3101 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160715/2540d6fb/attachment-0001.jpg>

From jimklimov at cos.ru  Fri Jul 15 18:06:38 2016
From: jimklimov at cos.ru (Jim Klimov)
Date: Fri, 15 Jul 2016 20:06:38 +0200
Subject: [OmniOS-discuss] firefox24
In-Reply-To: <em3bfa6250-f9ad-45a0-a872-76b785d391ec@horaceknbw7-2>
References: <em3bfa6250-f9ad-45a0-a872-76b785d391ec@horaceknbw7-2>
Message-ID: <0EEF3788-B62D-4533-9905-AF2B97F26ED4@cos.ru>

15 ???? 2016??. 17:47:47 CEST, "Hor??ek Radim" <horacek at ssi.cz> ?????:
>Dear,
>
>please, how to install Firefox24 on OmniOS (bloody)? I used 
>pkgsrc-2016Q1 - installed firefox24 and firefox24-l10n. But I get an 
>error when running:
>
>Segmentation fault (core dumped)
>
>Any ideas?
>
>
>Radim Hor??ek
>
>IT Specialista | IT Specialist
>+420 773 798 837 | horacek at ssi.cz
>
>
>Special Service International, spol. s r. o.
>Palmovka Business Centre, Na ?ertv?ch 2247/29, 180 00 Praha 8
>+ 420 222 722 590 | www.ssi.cz
>
>IT'SSIMPLE
>
>UPOZORN?N? O D?V?RN?M CHARAKTERU ZPR?VY Informace obsa?en? v t?to
>zpr?v? 
>mohou b?t d?v?rn?ho charakteru a mohou pou??vat zvl??tn? ochrany. Jsou 
>ur?eny v?hradn? uveden?m adres?t?m. Pokud nejste adres?tem, obratem m?,
>
>pros?m, informujte (zasl?n?m zpr?vy zp?t odes?lateli) a zpr?vu vyma?te 
>ze syst?mu. Bez ??dn? vydan?ho souhlasu je zak?z?no informace obsa?en? 
>ve zpr?v? jak?mkoliv zp?sobem pou??vat ?i je d?le ???it.
>
>PRIVACY AND CONFIDENTIALITY NOTICE This e-mail may contain privileged 
>and confidential information. It is intended for the named recipients 
>only. If you are not an intended recipient, please notify us
>immediately 
>(by reply e-mail) and delete this e-mail from your system. Any use or 
>retransmission without proper authorization is prohibited.
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>OmniOS-discuss mailing list
>OmniOS-discuss at lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

Ahoj Radime,

As a first shot, I'd suggest 'truss -fl'ing your invokation of firefox to see at which syscall it breaks. Using 'ldd' can also help research the libs it wants. My guess would be that it dies using libs that are absent or incompatible on your system. Maybe it should have pulled additional packages with proper lib builds but does not call them correctly (viz. ldd - are resolved paths in opt or usr?)

Also you may want to check if Martin Bochnig's FF43.0b3 or FF37 ports would "just work" for your system, see http://opensxce.org/.FF/

Hope this helps,
Jim Klimov
--
Typos courtesy of K-9 Mail on my Samsung Android

From danmcd at omniti.com  Fri Jul 15 18:12:52 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Fri, 15 Jul 2016 14:12:52 -0400
Subject: [OmniOS-discuss] VT how-to now on Wiki
References: <932FFC5A-9BD6-4202-BCD8-158F96B51D9A@omniti.com>
Message-ID: <69253D3E-BDD3-4FD8-A1EF-A58BF0C0B364@omniti.com>

The OmniOS wiki now has instructions for enabling Virtual Termainl (VT) consoles.  Useful for developers on {lap,desk}top-hosted VMs, e.g.

Thanks to Mayuresh & Volker for writing the text.  I just put it on the wiki (link below).

Dan

> Begin forwarded message:
> 
> From: Dan McDonald <danmcd at omniti.com>
> Subject: Re: OmniOS for developers!
> Date: July 15, 2016 at 1:57:36 PM EDT
> To: Mayuresh Kathe <mayuresh at kathe.in>, "Volker A. Brandt" <vab at bb-c.de>
> Cc: Dan McDonald <danmcd at omniti.com>
> 
> How's this?
> 
> 	https://omnios.omniti.com/wiki.php/GeneralAdministration#MultipleConsoles
> 
> If this is what you wanted, I'll forward this to the OmniOS discussion list as well.
> 
> Thanks!
> Dan
> 


From vab at bb-c.de  Fri Jul 15 18:43:08 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Fri, 15 Jul 2016 20:43:08 +0200
Subject: [OmniOS-discuss] VT how-to now on Wiki
In-Reply-To: <69253D3E-BDD3-4FD8-A1EF-A58BF0C0B364@omniti.com>
References: <932FFC5A-9BD6-4202-BCD8-158F96B51D9A@omniti.com>
	<69253D3E-BDD3-4FD8-A1EF-A58BF0C0B364@omniti.com>
Message-ID: <22409.11964.639189.324188@shelob.bb-c.de>

> The OmniOS wiki now has instructions for enabling Virtual Termainl (VT) consoles.  Useful for developers on {lap,desk}top-hosted VMs, e.g.
> 
> Thanks to Mayuresh & Volker for writing the text.  I just put it on the wiki
> (link below). 

Thanks Dan.  It is really just Mayuresh's work and initiative.


Cheers -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"


From danmcd at omniti.com  Wed Jul 20 01:59:20 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Tue, 19 Jul 2016 21:59:20 -0400
Subject: [OmniOS-discuss] Bloody Update for July 19th
Message-ID: <CC12A2F8-4BD5-404C-846F-4CE35BD71F44@omniti.com>

It's been over a month, but with progress in LX (more on that in its own thread tomorrow) and vacations finished, I've updated the Bloody IPS server (http://pkg.omniti.com/omnios/bloody/).  illumos-omnios is from master commit 0e4287b, and omnios-build is from master commit f7881f6.  "uname -v" will show omnios-master-0e4287b.

New in this update:

- Bind updated to 9.10.4-P2

- /usr/lib symlinks for libxml2 are now tracking the correct version again.  (Thanks Alexander Eremin for finding the bug.)

- mozilla-nss up to 3.25 (already in releases too)

- wget up to 1.18

- ixgbe X550 support (soon to be upstreamed)

- various man page spelling fixes

- labelled device support (/dev/dsk/XXXX) for lofi.

- MSI-x on KVM prevents VMs from accessing the network (illumos 7089) now fixed.

- COMPRESSED ARC -- (Thanks OpenZFS for this long-desired feature).

- Indirect block size increased in ZFS

Release media for ISO, USB, and kayak will be out very late tonight or tomorrow (the 20th).

Happy updating!
Dan


From fabio at fabiorabelo.wiki.br  Wed Jul 20 11:28:47 2016
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Wed, 20 Jul 2016 08:28:47 -0300
Subject: [OmniOS-discuss] ASMedia 1061
Message-ID: <CAEekY66T-372F44mG3B5dj4onQVS07NqVhGHc4Sv2cOHAHdOhQ@mail.gmail.com>

Hi to all

I am sorry if this  subject hass allready been here, but I cannot find
anything, so :

Are the Sata cards baesd on ASMedia ASM 1061 supported by OmniOS ?

Thanks in advance ...


F?bio Rabelo

From stephan.budach at JVM.DE  Wed Jul 20 11:59:57 2016
From: stephan.budach at JVM.DE (Stephan Budach)
Date: Wed, 20 Jul 2016 13:59:57 +0200
Subject: [OmniOS-discuss] Bloody Update for July 19th
In-Reply-To: <CC12A2F8-4BD5-404C-846F-4CE35BD71F44@omniti.com>
References: <CC12A2F8-4BD5-404C-846F-4CE35BD71F44@omniti.com>
Message-ID: <ab1905d9-2570-640b-604e-5689bdc2948b@jvm.de>

Awesome! I will try that out asap.

Cheers,
Stephan

From mir at miras.org  Wed Jul 20 12:19:30 2016
From: mir at miras.org (Michael Rasmussen)
Date: Wed, 20 Jul 2016 14:19:30 +0200
Subject: [OmniOS-discuss] ASMedia 1061
In-Reply-To: <CAEekY66T-372F44mG3B5dj4onQVS07NqVhGHc4Sv2cOHAHdOhQ@mail.gmail.com>
References: <CAEekY66T-372F44mG3B5dj4onQVS07NqVhGHc4Sv2cOHAHdOhQ@mail.gmail.com>
Message-ID: <20160720141930.675c673e@sleipner.datanom.net>

On Wed, 20 Jul 2016 08:28:47 -0300
F?bio Rabelo <fabio at fabiorabelo.wiki.br> wrote:

> 
> Are the Sata cards baesd on ASMedia ASM 1061 supported by OmniOS ?
> 
1062 according to pci.ids is supported in 151014 which should be the
ASM 1061 chip:
03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) (prog-if 01 [AHCI 1.0])


-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
/usr/games/fortune -es says:
Nadia Comaneci, simple perfection.
		-- '76 Olympics
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160720/04e9b0c0/attachment.bin>

From danmcd at omniti.com  Wed Jul 20 19:47:55 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Wed, 20 Jul 2016 15:47:55 -0400
Subject: [OmniOS-discuss] Bloody Update for July 19th
In-Reply-To: <CC12A2F8-4BD5-404C-846F-4CE35BD71F44@omniti.com>
References: <CC12A2F8-4BD5-404C-846F-4CE35BD71F44@omniti.com>
Message-ID: <E511D7DA-DE60-41DE-8E7B-50419E780F1D@omniti.com>


> On Jul 19, 2016, at 9:59 PM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> Release media for ISO, USB, and kayak will be out very late tonight or tomorrow (the 20th).
> 

Release media is now on the OmniOS Installation page.

Dan

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

From daleg at omniti.com  Wed Jul 20 23:41:20 2016
From: daleg at omniti.com (Dale Ghent)
Date: Wed, 20 Jul 2016 19:41:20 -0400
Subject: [OmniOS-discuss] Security updates for OmniOS 014 and 018
Message-ID: <8E541063-0693-4E24-8912-85D82995D537@omniti.com>

Several packages have been updated for OmniOS r151014 (LTS) and r151018 (Stable) and are now available.

- Mozilla NSPR and NSS to 4.11 and 3.25 respectively.

- CA cert bundle updated to those provided with NSS 3.25

- BIND 9.10.4-P2

- libxml2 - corrected /lib symlinks delivered by the package (Thanks Alexander Eremin for finding the bug.)

r151014 package FMRIs:
pkg://omnios/incorporation/jeos/omnios-userland at 11-0.151014:20160713T153445Z
pkg://omnios/library/libxml2 at 2.9.4-0.151014:20160720T225846Z
pkg://omnios/library/nspr at 4.12-0.151014:20160713T153326Z
pkg://omnios/library/nspr/header-nspr at 4.12-0.151014:20160713T153311Z
pkg://omnios/system/library/mozilla-nss at 3.25-0.151014:20160713T153043Z
pkg://omnios/system/library/mozilla-nss/header-nss at 3.25-0.151014:20160713T153028Z
pkg://omnios/network/dns/bind at 9.10.4.2-0.151014:20160720T230619Z
pkg://omnios/web/ca-bundle at 5.11-0.151014:20160720T230856Z

r151018 package FMRIs:
pkg://omnios/incorporation/jeos/omnios-userland at 11-0.151018:20160713T213159Z
pkg://omnios/library/libxml2 at 2.9.4-0.151018:20160720T230048Z
pkg://omnios/library/nspr at 4.12-0.151018:20160713T165745Z
pkg://omnios/library/nspr/header-nspr at 4.12-0.151018:20160713T165732Z
pkg://omnios/system/library/mozilla-nss at 3.25-0.151018:20160713T165714Z
pkg://omnios/system/library/mozilla-nss/header-nss at 3.25-0.151018:20160713T165659Z
pkg://omnios/network/dns/bind at 9.10.4.2-0.151018:20160720T230607Z
pkg://omnios/web/ca-bundle at 5.11-0.151018:20160720T230853Z

From danmcd at omniti.com  Thu Jul 21 00:23:59 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Wed, 20 Jul 2016 20:23:59 -0400
Subject: [OmniOS-discuss] Fwd: [developer] Heads-up: 6950 ARC should cache
	compressed data
References: <CA+j07uZCTRW=d2w-WZu6aS5Oy3114k7AyuxhX7=qTvV_n=ZHoA@mail.gmail.com>
Message-ID: <3EB00D3D-6968-4163-9829-E4D1CD3BCB71@omniti.com>

The most recent bloody update has this feature.  Bloody users should read below.

Dan


> Begin forwarded message:
> 
> From: "George Wilson" <george.wilson at delphix.com>
> Subject: [developer] Heads-up: 6950 ARC should cache compressed data
> Date: July 14, 2016 at 3:57:13 PM EDT
> To: "<developer at lists.illumos.org>" <developer at lists.illumos.org>
> Reply-To: developer at lists.illumos.org
> 
> The compressed ARC feature has just integrated into illumos. This feature introduces compression into the ZFS cache and will keep blocks compressed in memory if they are compressed on disk. Blocks will be decompressed on demand and the uncompressed copy will be discarded once the consumer is no longer referencing it. Users can disable the compressed ARC feature by doing the following:
> 
> mdb -ke "zfs_compressed_arc_enabled/W 0"
> 
> This can be done dynamically and will only impact newly cached blocks. Blocks already in the cache will remain compressed until they are evicted. 
> 
> This feature also include a 100MB (by default) dbuf cache which keep blocks uncompressed that are recently accessed.
> 
> You can adjust the default value of the dbuf cache by doing the following:
> 
> mdb -ke "dbuf_cache_max_bytes/Z 0t209715200" /* 200MB dbuf cache */
> 
> For more information you can check out the slides on open-zfs.org <http://postlink.www.listbox.com/2166757/3affccb54cf4be1589fb8cea18eeda1a/21175029/47b6a23e?uri=aHR0cDovL29wZW4temZzLm9yZw> located here: 
> 
> http://goo.gl/Ra4fw9 <http://postlink.www.listbox.com/2166758/4a0070dc45fa6e9f739152f11e35726e/21175029/47b6a23e?uri=aHR0cHM6Ly9nb28uZ2wvUmE0Znc5>
> 
> Please contact me if you have any questions.
> 
> Enjoy,
> George
> 
> 
> illumos-developer | Modify <https://www.listbox.com/member/?member_id=21175029&id_secret=21175029-471fe0d4> Your Subscription | Unsubscribe Now <https://www.listbox.com/unsubscribe/?member_id=21175029&id_secret=21175029-d21cb572&post_id=20160714155720:2AB53070-49FD-11E6-816C-A7C8DC2B917E>	  <http://postlink.www.listbox.com/2166759/ceaef0abaafb826b7a7a90ddf36178e1/21175029/47b6a23e?uri=aHR0cDovL3d3dy5saXN0Ym94LmNvbQ>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160720/80a0e867/attachment.html>

From danmcd at omniti.com  Thu Jul 21 00:38:45 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Wed, 20 Jul 2016 20:38:45 -0400
Subject: [OmniOS-discuss] OmniOS LX Update
References: <EADE8283-CBA6-489A-89F9-736A63F7C300@kebe.com>
Message-ID: <165D2EC0-40B9-4459-9F1F-76A6392841F5@omniti.com>

Hello folks!

I've now updated the bloody+LX repo:

  http://pkg.omniti.com/omnios/LX/

If you change your "omnios" publisher from bloody to this, you can get bloody PLUS the in-progress LX bits.

  pkg set-publisher -G http://pkg.omniti.com/omnios/bloody/ -g http://pkg.omniti.com/omnios/LX/ omnios

Also, don't forget to install the LX brand along with the update (LX is not tied to "entire" or any other incorporation currently):

  pkg install brand/lx

As with r151018 and later, the debug.illumos variant is available for DEBUG kernel BEs.

LX is now booting LX zones with appropriate configuration.  ipkg and lipkg zones should also boot without issue.  This project does require further regression testing on ipkg/lipkg zones, AND LX functional testing, plus unresolved design issues for proper integration into OmniOS (see below).

To install an LX zone, obtain a ZFS send stream with an LX image.  The Joyent image servers have plenty of these.  To use their latest CentOS image, one would do the following:

1.) Get information (including kernel version) about the image:

  https://images.joyent.com/images/5b7e86e4-2797-11e6-b7d7-cbe6a1a48791

   Note the 2.6.32 kernel version.

2.) Get the actual image:

  curl -o centos6.zss.gz https://images.joyent.com/images/5b7e86e4-2797-11e6-b7d7-cbe6a1a48791/file

3.) Create the zone.  Assign a vnic and zoneroot per normal, but also include the kernel version in zonecfg(1M):

# zonecfg -z lx0 export
create -b
set zonepath=/zones/lx0
set brand=lx
set autoboot=false
set ip-type=exclusive
add net
set physical=lx0
end
add attr
set name=kernel-version
set type=string
set value=2.6.32
end
# 

4.) Install the zone using the aforementioned image:

  zoneadm -z lx0 install -s /full/path/to/centos6.zss.gz

5.) Boot the zone.

6.) Login using zlogin to change root's password:

  zlogin lx0
  <motd + shell shows>
  passwd

7.) Use the /native tools to set up networking.  You may wish to place these into the CentOS startup system somewhere:

  /native/sbin/ipadm -t -T static -a <addr>/<prefix> <intf>/v4
  /native/sbin/route add default <router>

8.) Try LX stuff out.



I'd VERY MUCH appreciate people trying this out.  I'm not sure if LX will make it in for OmniOS r151020, but it's a stretch goal.  There are outstanding design issues with LX for OmniOS that need resolving.  These include (but are not limited to):

- How much of the Joyent image API do we want to use?  Porting all of vmadm(1M) is a NON-GOAL of this project.

- As of now, LX zones are "BE resistant", meaning libbe and beadm are not aware of them as entities.  At first, this seems mostly a feature, because the /native is just lofs-mounted read-only from the global zone.  On the other hand, it means the zone's root doesn't instantiate differently between BEs like it does in ipkg/lipkg zones.  My thoughts right now are for beadm(1M) to do something brand-appropriate for LX, but I'm not sure HOW that will happen yet.

- Right now "-s" for zoneadm install takes gzipped or uncompresses ZFS send streams.  Could it also take a snapshot pointer?  That way could lie an imgadm(1M) port, which is also a NON-GOAL.

- How do we suss out the appropriate kernel-version for each image, without going down {img,vm}adm?



Have fun with this.  I will be returning to LX later this week or early next.

Dan


From peter.tribble at gmail.com  Thu Jul 21 09:12:57 2016
From: peter.tribble at gmail.com (Peter Tribble)
Date: Thu, 21 Jul 2016 10:12:57 +0100
Subject: [OmniOS-discuss] Security updates for OmniOS 014 and 018
In-Reply-To: <8E541063-0693-4E24-8912-85D82995D537@omniti.com>
References: <8E541063-0693-4E24-8912-85D82995D537@omniti.com>
Message-ID: <CAEgYsbHc-vHwkA_7vCrcuK_QSDzekawMdv9F=Q1nVXKghVjGqw@mail.gmail.com>

On Thu, Jul 21, 2016 at 12:41 AM, Dale Ghent <daleg at omniti.com> wrote:

> Several packages have been updated for OmniOS r151014 (LTS) and r151018
> (Stable) and are now available.
>
> - libxml2 - corrected /lib symlinks delivered by the package (Thanks
> Alexander Eremin for finding the bug.)
>

This one looks broken to me (on r151014 anyway). Before. we had:

lrwxrwxrwx 1 root root      26 May 16 18:25 /usr/lib/libxml2.so ->
../../lib/libxml2.so.2.9.3
lrwxrwxrwx 1 root root      26 May 16 18:25 /usr/lib/libxml2.so.2 ->
../../lib/libxml2.so.2.9.3
lrwxrwxrwx 1 root root      26 May 16 18:25 /usr/lib/libxml2.so.2.9.3 ->
../../lib/libxml2.so.2.9.3

whereas now it says:

lrwxrwxrwx 1 root root      21 Jul 21 09:02 /usr/lib/libxml2.so ->
../../lib/libxml2.so.
lrwxrwxrwx 1 root root      21 Jul 21 09:02 /usr/lib/libxml2.so. ->
../../lib/libxml2.so.
lrwxrwxrwx 1 root root      21 Jul 21 09:02 /usr/lib/libxml2.so.2 ->
../../lib/libxml2.so.

I guess the original bug was that it should actually be 2.9.4, but now
there's no
version at all. (So it's not actually any worse.)

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160721/219797e3/attachment-0001.html>

From alexander.r.eremin at gmail.com  Thu Jul 21 09:22:50 2016
From: alexander.r.eremin at gmail.com (Alexander)
Date: Thu, 21 Jul 2016 12:22:50 +0300
Subject: [OmniOS-discuss] Security updates for OmniOS 014 and 018
In-Reply-To: <CAEgYsbHc-vHwkA_7vCrcuK_QSDzekawMdv9F=Q1nVXKghVjGqw@mail.gmail.com>
References: <8E541063-0693-4E24-8912-85D82995D537@omniti.com>
	<CAEgYsbHc-vHwkA_7vCrcuK_QSDzekawMdv9F=Q1nVXKghVjGqw@mail.gmail.com>
Message-ID: <etPan.5790946a.3a3ad1ca.283@gmail.com>

Yes, move_libs() in build.sh should use $VER instead of $VERSION

Yst?v?llisin terveisin
Alexander

On 21 July 2016 at 12:15:14, Peter Tribble (peter.tribble at gmail.com) wrote:

On Thu, Jul 21, 2016 at 12:41 AM, Dale Ghent <daleg at omniti.com> wrote:
Several packages have been updated for OmniOS r151014 (LTS) and r151018 (Stable) and are now available.

- libxml2 - corrected /lib symlinks delivered by the package (Thanks Alexander Eremin for finding the bug.)

This one looks broken to me (on r151014 anyway). Before. we had:

lrwxrwxrwx 1 root root????? 26 May 16 18:25 /usr/lib/libxml2.so -> ../../lib/libxml2.so.2.9.3
lrwxrwxrwx 1 root root????? 26 May 16 18:25 /usr/lib/libxml2.so.2 -> ../../lib/libxml2.so.2.9.3
lrwxrwxrwx 1 root root????? 26 May 16 18:25 /usr/lib/libxml2.so.2.9.3 -> ../../lib/libxml2.so.2.9.3

whereas now it says:

lrwxrwxrwx 1 root root????? 21 Jul 21 09:02 /usr/lib/libxml2.so -> ../../lib/libxml2.so.
lrwxrwxrwx 1 root root????? 21 Jul 21 09:02 /usr/lib/libxml2.so. -> ../../lib/libxml2.so.
lrwxrwxrwx 1 root root????? 21 Jul 21 09:02 /usr/lib/libxml2.so.2 -> ../../lib/libxml2.so.

I guess the original bug was that it should actually be 2.9.4, but now there's no
version at all. (So it's not actually any worse.)

--
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
_______________________________________________  
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: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160721/d9348b59/attachment.html>

From bfriesen at simple.dallas.tx.us  Thu Jul 21 13:27:45 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Thu, 21 Jul 2016 08:27:45 -0500 (CDT)
Subject: [OmniOS-discuss] Security updates for OmniOS 014 and 018
In-Reply-To: <etPan.5790946a.3a3ad1ca.283@gmail.com>
References: <8E541063-0693-4E24-8912-85D82995D537@omniti.com>
	<CAEgYsbHc-vHwkA_7vCrcuK_QSDzekawMdv9F=Q1nVXKghVjGqw@mail.gmail.com>
	<etPan.5790946a.3a3ad1ca.283@gmail.com>
Message-ID: <alpine.GSO.2.20.1607210825520.17565@freddy.simplesystems.org>

On Thu, 21 Jul 2016, Alexander wrote:

>
> lrwxrwxrwx 1 root root????? 21 Jul 21 09:02 /usr/lib/libxml2.so -> ../../lib/libxml2.so.
> lrwxrwxrwx 1 root root????? 21 Jul 21 09:02 /usr/lib/libxml2.so. -> ../../lib/libxml2.so.
> lrwxrwxrwx 1 root root????? 21 Jul 21 09:02 /usr/lib/libxml2.so.2 -> ../../lib/libxml2.so.
>
> I guess the original bug was that it should actually be 2.9.4, but now there's no
> version at all. (So it's not actually any worse.)

Urrgh!  I am seeing the same problem on OmniOS 018.  We should make 
sure not to compile any code (luckily compilation is likely to fail) 
until this is fixed.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

From danmcd at omniti.com  Thu Jul 21 14:21:41 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Thu, 21 Jul 2016 10:21:41 -0400
Subject: [OmniOS-discuss] Security updates for OmniOS 014 and 018
In-Reply-To: <alpine.GSO.2.20.1607210825520.17565@freddy.simplesystems.org>
References: <8E541063-0693-4E24-8912-85D82995D537@omniti.com>
	<CAEgYsbHc-vHwkA_7vCrcuK_QSDzekawMdv9F=Q1nVXKghVjGqw@mail.gmail.com>
	<etPan.5790946a.3a3ad1ca.283@gmail.com>
	<alpine.GSO.2.20.1607210825520.17565@freddy.simplesystems.org>
Message-ID: <36D5D21A-7520-41F5-A4A1-8ADF48633350@omniti.com>

I'm very sorry about this.  I've pushed the fix that Alexander pointed out into master.  I will have full bandwidth at 1pm ET, and will start the update of libxml2 at that time.

Dan

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

> On Jul 21, 2016, at 9:27 AM, Bob Friesenhahn <bfriesen at simple.dallas.tx.us> wrote:
> 
>> On Thu, 21 Jul 2016, Alexander wrote:
>> 
>> 
>> lrwxrwxrwx 1 root root      21 Jul 21 09:02 /usr/lib/libxml2.so -> ../../lib/libxml2.so.
>> lrwxrwxrwx 1 root root      21 Jul 21 09:02 /usr/lib/libxml2.so. -> ../../lib/libxml2.so.
>> lrwxrwxrwx 1 root root      21 Jul 21 09:02 /usr/lib/libxml2.so.2 -> ../../lib/libxml2.so.
>> 
>> I guess the original bug was that it should actually be 2.9.4, but now there's no
>> version at all. (So it's not actually any worse.)
> 
> Urrgh!  I am seeing the same problem on OmniOS 018.  We should make sure not to compile any code (luckily compilation is likely to fail) until this is fixed.
> 
> Bob
> -- 
> Bob Friesenhahn
> bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From danmcd at omniti.com  Thu Jul 21 14:53:28 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Thu, 21 Jul 2016 10:53:28 -0400
Subject: [OmniOS-discuss] Security updates for OmniOS 014 and 018
In-Reply-To: <36D5D21A-7520-41F5-A4A1-8ADF48633350@omniti.com>
References: <8E541063-0693-4E24-8912-85D82995D537@omniti.com>
	<CAEgYsbHc-vHwkA_7vCrcuK_QSDzekawMdv9F=Q1nVXKghVjGqw@mail.gmail.com>
	<etPan.5790946a.3a3ad1ca.283@gmail.com>
	<alpine.GSO.2.20.1607210825520.17565@freddy.simplesystems.org>
	<36D5D21A-7520-41F5-A4A1-8ADF48633350@omniti.com>
Message-ID: <DAACA2DA-0F35-4530-A7F9-11B38D0799C9@omniti.com>


> On Jul 21, 2016, at 10:21 AM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> I'm very sorry about this.  I've pushed the fix that Alexander pointed out into master.  I will have full bandwidth at 1pm ET, and will start the update of libxml2 at that time.

Got some full bandwidth earlier.  The Alexander correction is now in place and working:

r151018(~)[0]% ls -ld /usr/lib/libxml* ; sudo pkg update -v --no-backup-be ; ls -ld /usr/lib/libxml*
lrwxrwxrwx   1 root     root          21 Jul 20 21:42 /usr/lib/libxml2.so -> ../../lib/libxml2.so.
lrwxrwxrwx   1 root     root          21 Jul 20 21:42 /usr/lib/libxml2.so. -> ../../lib/libxml2.so.
lrwxrwxrwx   1 root     root          21 Jul 20 21:42 /usr/lib/libxml2.so.2 -> ../../lib/libxml2.so.
            Packages to update:        1
     Estimated space available: 70.57 GB
Estimated space to be consumed: 22.83 MB
       Create boot environment:       No
Create backup boot environment:       No
          Rebuild boot archive:       No

Changed packages:
omnios
  library/libxml2
    2.9.4-0.151018:20160720T230048Z -> 2.9.4-0.151018:20160721T144336Z
DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
Completed                                1/1         10/10      1.5/1.5  1.4M/s

PHASE                                          ITEMS
Removing old actions                             3/3
Installing new actions                           3/3
Updating modified actions                      64/64
Updating package state database                 Done 
Updating package cache                           1/1 
Updating image state                            Done 
Creating fast lookup database                   Done 

---------------------------------------------------------------------------
NOTE: Please review release notes posted at:

http://omnios.omniti.com/ReleaseNotes
---------------------------------------------------------------------------

lrwxrwxrwx   1 root     root          26 Jul 21 10:52 /usr/lib/libxml2.so -> ../../lib/libxml2.so.2.9.4*
lrwxrwxrwx   1 root     root          26 Jul 21 10:52 /usr/lib/libxml2.so.2 -> ../../lib/libxml2.so.2.9.4*
lrwxrwxrwx   1 root     root          26 Jul 21 10:52 /usr/lib/libxml2.so.2.9.4 -> ../../lib/libxml2.so.2.9.4*
r151018(~)[0]% 


Again, sorry for this,
Dan


From shaun at rackcentral.com  Tue Jul 26 00:24:21 2016
From: shaun at rackcentral.com (Shaun McGuane)
Date: Tue, 26 Jul 2016 00:24:21 +0000
Subject: [OmniOS-discuss] Multiple faulty SSD's ?
Message-ID: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>

Hi List,

I want to report very strange SSD behaviour on a new pool I setup.

The hardware is a HP DL180 G6 Server with the LSI 9207-8i Card
And 8x 1TB Samsung SSD Pro drives. Running omnios-10b9c79

All the drives are brand spanking new setup in a raidz2 array.

Within 2 months the below has happened and there has been very
Little use on this array.

  pool: SSD-TANK
state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
        repaired.
  scan: scrub repaired 23K in 1h12m with 0 errors on Mon Jul 25 20:13:04 2016
config:

        NAME                       STATE     READ WRITE CKSUM
        SSD-TANK                   DEGRADED     1    67    35
          raidz2-0                 DEGRADED     4    72   113
            c5t500253884014D0D3d0  ONLINE       0     0     2
            c5t50025388401F767Ad0  DEGRADED     0     0    19  too many errors
            c5t50025388401F767Bd0  FAULTED      0     0     0  too many errors
            c5t50025388401F767Dd0  ONLINE       0     0     0
            c5t50025388401F767Fd0  ONLINE       0     0     1
            c5t50025388401F7679d0  ONLINE       0     0     2
            c5t50025388401F7680d0  REMOVED      0     0     0
            c5t50025388401F7682d0  ONLINE       0     0     1

Can anyone suggest why I would have this problem where I am seeing CKSUM errors
On most disks and while only one has faulted others have been degraded or removed.

Thanks
Shaun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160726/ab74f7ac/attachment-0001.html>

From skeltonr at btconnect.com  Tue Jul 26 17:04:46 2016
From: skeltonr at btconnect.com (Richard Skelton)
Date: Tue, 26 Jul 2016 18:04:46 +0100
Subject: [OmniOS-discuss] Multiple faulty SSD's ?
In-Reply-To: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>
References: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>
Message-ID: <5797982E.9060807@btconnect.com>

Hi Shaun,
I have seen something very similar on an Oracle X4-2
I added two 256MB Samsung 850 PRO and created a mirrored zpool
The system zpool was a mirror of two SAS Seagate 600GB which came withe
the system.
The system was running Solaris 10 with latest patches.
After a few hours I saw checksum errors on both disks.
Oracle told me they did not support the Samsung disks so I swapped them
for Intel DC S3500 which have been working fine for months.
The 850 PRO drives worked fine on a X4140 but this has a different raid
controller.
So I guess you need to be careful which SSD's you use with certain
controllers :-(

Shaun McGuane wrote:
>
> Hi List,
>
>  
>
> I want to report very strange SSD behaviour on a new pool I setup.
>
>  
>
> The hardware is a HP DL180 G6 Server with the LSI 9207-8i Card
>
> And 8x 1TB Samsung SSD Pro drives. Running omnios-10b9c79
>
>  
>
> All the drives are brand spanking new setup in a raidz2 array.
>
>  
>
> Within 2 months the below has happened and there has been very
>
> Little use on this array.
>
>  
>
>   pool: SSD-TANK
>
> state: DEGRADED
>
> status: One or more devices are faulted in response to persistent errors.
>
>         Sufficient replicas exist for the pool to continue functioning
> in a
>
>         degraded state.
>
> action: Replace the faulted device, or use 'zpool clear' to mark the
> device
>
>         repaired.
>
>   scan: scrub repaired 23K in 1h12m with 0 errors on Mon Jul 25
> 20:13:04 2016
>
> config:
>
>  
>
>         NAME                       STATE     READ WRITE CKSUM
>
>         SSD-TANK                   DEGRADED     1    67    35
>
>           raidz2-0                 DEGRADED     4    72   113
>
>             c5t500253884014D0D3d0  ONLINE       0     0     2
>
>             c5t50025388401F767Ad0  DEGRADED     0     0    19  too
> many errors
>
>             c5t50025388401F767Bd0  FAULTED      0     0     0  too
> many errors
>
>             c5t50025388401F767Dd0  ONLINE       0     0     0
>
>             c5t50025388401F767Fd0  ONLINE       0     0     1
>
>             c5t50025388401F7679d0  ONLINE       0     0     2
>
>             c5t50025388401F7680d0  REMOVED      0     0     0
>
>             c5t50025388401F7682d0  ONLINE       0     0     1
>
>  
>
> Can anyone suggest why I would have this problem where I am seeing
> CKSUM errors
>
> On most disks and while only one has faulted others have been degraded
> or removed.
>
>  
>
> Thanks
>
> Shaun
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160726/8200bd6d/attachment.html>

From estibi at me.com  Tue Jul 26 17:28:45 2016
From: estibi at me.com (Piotr Jasiukajtis)
Date: Tue, 26 Jul 2016 19:28:45 +0200
Subject: [OmniOS-discuss] Multiple faulty SSD's ?
In-Reply-To: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>
References: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>
Message-ID: <51697F54-16BB-46BC-A59F-D7BAE53FF34E@me.com>

You may want to force the driver to use 4k instead of 512b for those drivers and create a new pool:

https://github.com/joyent/smartos-live/commit/dd25937d2f9725def16f5e8dbb16a8bcbc2213d5

--
Piotr Jasiukajtis

> On 26 Jul 2016, at 02:24, Shaun McGuane <shaun at rackcentral.com> wrote:
> 
> Hi List,
>  
> I want to report very strange SSD behaviour on a new pool I setup.
>  
> The hardware is a HP DL180 G6 Server with the LSI 9207-8i Card
> And 8x 1TB Samsung SSD Pro drives. Running omnios-10b9c79
>  
> All the drives are brand spanking new setup in a raidz2 array.
>  
> Within 2 months the below has happened and there has been very
> Little use on this array. 
>  
>   pool: SSD-TANK
> state: DEGRADED
> status: One or more devices are faulted in response to persistent errors.
>         Sufficient replicas exist for the pool to continue functioning in a
>         degraded state.
> action: Replace the faulted device, or use 'zpool clear' to mark the device
>         repaired.
>   scan: scrub repaired 23K in 1h12m with 0 errors on Mon Jul 25 20:13:04 2016
> config:
>  
>         NAME                       STATE     READ WRITE CKSUM
>         SSD-TANK                   DEGRADED     1    67    35
>           raidz2-0                 DEGRADED     4    72   113
>             c5t500253884014D0D3d0  ONLINE       0     0     2
>             c5t50025388401F767Ad0  DEGRADED     0     0    19  too many errors
>             c5t50025388401F767Bd0  FAULTED      0     0     0  too many errors
>             c5t50025388401F767Dd0  ONLINE       0     0     0
>             c5t50025388401F767Fd0  ONLINE       0     0     1
>             c5t50025388401F7679d0  ONLINE       0     0     2
>             c5t50025388401F7680d0  REMOVED      0     0     0
>             c5t50025388401F7682d0  ONLINE       0     0     1
>  
> Can anyone suggest why I would have this problem where I am seeing CKSUM errors
> On most disks and while only one has faulted others have been degraded or removed.
>  
> Thanks
> Shaun
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From danmcd at omniti.com  Tue Jul 26 18:06:26 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Tue, 26 Jul 2016 14:06:26 -0400
Subject: [OmniOS-discuss] Multiple faulty SSD's ?
In-Reply-To: <51697F54-16BB-46BC-A59F-D7BAE53FF34E@me.com>
References: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>
	<51697F54-16BB-46BC-A59F-D7BAE53FF34E@me.com>
Message-ID: <0567742A-50F5-4A00-9C3C-AF4CFF88FAB6@omniti.com>

I wonder if those sd.conf changes should be upstreamed or not?

Dan

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

> On Jul 26, 2016, at 1:28 PM, Piotr Jasiukajtis <estibi at me.com> wrote:
> 
> You may want to force the driver to use 4k instead of 512b for those drivers and create a new pool:
> 
> https://github.com/joyent/smartos-live/commit/dd25937d2f9725def16f5e8dbb16a8bcbc2213d5
> 
> --
> Piotr Jasiukajtis
> 
>> On 26 Jul 2016, at 02:24, Shaun McGuane <shaun at rackcentral.com> wrote:
>> 
>> Hi List,
>> 
>> I want to report very strange SSD behaviour on a new pool I setup.
>> 
>> The hardware is a HP DL180 G6 Server with the LSI 9207-8i Card
>> And 8x 1TB Samsung SSD Pro drives. Running omnios-10b9c79
>> 
>> All the drives are brand spanking new setup in a raidz2 array.
>> 
>> Within 2 months the below has happened and there has been very
>> Little use on this array. 
>> 
>>  pool: SSD-TANK
>> state: DEGRADED
>> status: One or more devices are faulted in response to persistent errors.
>>        Sufficient replicas exist for the pool to continue functioning in a
>>        degraded state.
>> action: Replace the faulted device, or use 'zpool clear' to mark the device
>>        repaired.
>>  scan: scrub repaired 23K in 1h12m with 0 errors on Mon Jul 25 20:13:04 2016
>> config:
>> 
>>        NAME                       STATE     READ WRITE CKSUM
>>        SSD-TANK                   DEGRADED     1    67    35
>>          raidz2-0                 DEGRADED     4    72   113
>>            c5t500253884014D0D3d0  ONLINE       0     0     2
>>            c5t50025388401F767Ad0  DEGRADED     0     0    19  too many errors
>>            c5t50025388401F767Bd0  FAULTED      0     0     0  too many errors
>>            c5t50025388401F767Dd0  ONLINE       0     0     0
>>            c5t50025388401F767Fd0  ONLINE       0     0     1
>>            c5t50025388401F7679d0  ONLINE       0     0     2
>>            c5t50025388401F7680d0  REMOVED      0     0     0
>>            c5t50025388401F7682d0  ONLINE       0     0     1
>> 
>> Can anyone suggest why I would have this problem where I am seeing CKSUM errors
>> On most disks and while only one has faulted others have been degraded or removed.
>> 
>> Thanks
>> Shaun
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From estibi at me.com  Tue Jul 26 18:30:57 2016
From: estibi at me.com (Piotr Jasiukajtis)
Date: Tue, 26 Jul 2016 20:30:57 +0200
Subject: [OmniOS-discuss] Multiple faulty SSD's ?
In-Reply-To: <0567742A-50F5-4A00-9C3C-AF4CFF88FAB6@omniti.com>
References: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>
	<51697F54-16BB-46BC-A59F-D7BAE53FF34E@me.com>
	<0567742A-50F5-4A00-9C3C-AF4CFF88FAB6@omniti.com>
Message-ID: <40ACCC6D-BBB7-4857-8811-8240FF41E3D0@me.com>

I don?t know a root cause, but it?s better to have a workaround than a corrupted pools. 

--
Piotr Jasiukajtis

> On 26 Jul 2016, at 20:06, Dan McDonald <danmcd at omniti.com> wrote:
> 
> I wonder if those sd.conf changes should be upstreamed or not?
> 
> Dan
> 
> Sent from my iPhone (typos, autocorrect, and all)
> 
>> On Jul 26, 2016, at 1:28 PM, Piotr Jasiukajtis <estibi at me.com> wrote:
>> 
>> You may want to force the driver to use 4k instead of 512b for those drivers and create a new pool:
>> 
>> https://github.com/joyent/smartos-live/commit/dd25937d2f9725def16f5e8dbb16a8bcbc2213d5
>> 
>> --
>> Piotr Jasiukajtis
>> 
>>> On 26 Jul 2016, at 02:24, Shaun McGuane <shaun at rackcentral.com> wrote:
>>> 
>>> Hi List,
>>> 
>>> I want to report very strange SSD behaviour on a new pool I setup.
>>> 
>>> The hardware is a HP DL180 G6 Server with the LSI 9207-8i Card
>>> And 8x 1TB Samsung SSD Pro drives. Running omnios-10b9c79
>>> 
>>> All the drives are brand spanking new setup in a raidz2 array.
>>> 
>>> Within 2 months the below has happened and there has been very
>>> Little use on this array. 
>>> 
>>> pool: SSD-TANK
>>> state: DEGRADED
>>> status: One or more devices are faulted in response to persistent errors.
>>>       Sufficient replicas exist for the pool to continue functioning in a
>>>       degraded state.
>>> action: Replace the faulted device, or use 'zpool clear' to mark the device
>>>       repaired.
>>> scan: scrub repaired 23K in 1h12m with 0 errors on Mon Jul 25 20:13:04 2016
>>> config:
>>> 
>>>       NAME                       STATE     READ WRITE CKSUM
>>>       SSD-TANK                   DEGRADED     1    67    35
>>>         raidz2-0                 DEGRADED     4    72   113
>>>           c5t500253884014D0D3d0  ONLINE       0     0     2
>>>           c5t50025388401F767Ad0  DEGRADED     0     0    19  too many errors
>>>           c5t50025388401F767Bd0  FAULTED      0     0     0  too many errors
>>>           c5t50025388401F767Dd0  ONLINE       0     0     0
>>>           c5t50025388401F767Fd0  ONLINE       0     0     1
>>>           c5t50025388401F7679d0  ONLINE       0     0     2
>>>           c5t50025388401F7680d0  REMOVED      0     0     0
>>>           c5t50025388401F7682d0  ONLINE       0     0     1
>>> 
>>> Can anyone suggest why I would have this problem where I am seeing CKSUM errors
>>> On most disks and while only one has faulted others have been degraded or removed.
>>> 
>>> Thanks
>>> Shaun
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>> 
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From chip at innovates.com  Tue Jul 26 19:55:21 2016
From: chip at innovates.com (Schweiss, Chip)
Date: Tue, 26 Jul 2016 14:55:21 -0500
Subject: [OmniOS-discuss] Multiple faulty SSD's ?
In-Reply-To: <40ACCC6D-BBB7-4857-8811-8240FF41E3D0@me.com>
References: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>
	<51697F54-16BB-46BC-A59F-D7BAE53FF34E@me.com>
	<0567742A-50F5-4A00-9C3C-AF4CFF88FAB6@omniti.com>
	<40ACCC6D-BBB7-4857-8811-8240FF41E3D0@me.com>
Message-ID: <CALeZrrSFppzucJa9sZiTBUKos9WJH=QBPKAfwAx0PKH=wK8krg@mail.gmail.com>

I don't have a lot of experience with the 850 Pro, but a lot with the 840
Pro under OmniOS

With 4K block size set in sd.conf and slicing them to only use 80% of their
capacity a pool of 72 of them has been under near constant heavy read/write
workload for over 3 years without a single chksum error.

-Chip

On Tue, Jul 26, 2016 at 1:30 PM, Piotr Jasiukajtis <estibi at me.com> wrote:

> I don?t know a root cause, but it?s better to have a workaround than a
> corrupted pools.
>
> --
> Piotr Jasiukajtis
>
> > On 26 Jul 2016, at 20:06, Dan McDonald <danmcd at omniti.com> wrote:
> >
> > I wonder if those sd.conf changes should be upstreamed or not?
> >
> > Dan
> >
> > Sent from my iPhone (typos, autocorrect, and all)
> >
> >> On Jul 26, 2016, at 1:28 PM, Piotr Jasiukajtis <estibi at me.com> wrote:
> >>
> >> You may want to force the driver to use 4k instead of 512b for those
> drivers and create a new pool:
> >>
> >>
> https://github.com/joyent/smartos-live/commit/dd25937d2f9725def16f5e8dbb16a8bcbc2213d5
> >>
> >> --
> >> Piotr Jasiukajtis
> >>
> >>> On 26 Jul 2016, at 02:24, Shaun McGuane <shaun at rackcentral.com> wrote:
> >>>
> >>> Hi List,
> >>>
> >>> I want to report very strange SSD behaviour on a new pool I setup.
> >>>
> >>> The hardware is a HP DL180 G6 Server with the LSI 9207-8i Card
> >>> And 8x 1TB Samsung SSD Pro drives. Running omnios-10b9c79
> >>>
> >>> All the drives are brand spanking new setup in a raidz2 array.
> >>>
> >>> Within 2 months the below has happened and there has been very
> >>> Little use on this array.
> >>>
> >>> pool: SSD-TANK
> >>> state: DEGRADED
> >>> status: One or more devices are faulted in response to persistent
> errors.
> >>>       Sufficient replicas exist for the pool to continue functioning
> in a
> >>>       degraded state.
> >>> action: Replace the faulted device, or use 'zpool clear' to mark the
> device
> >>>       repaired.
> >>> scan: scrub repaired 23K in 1h12m with 0 errors on Mon Jul 25 20:13:04
> 2016
> >>> config:
> >>>
> >>>       NAME                       STATE     READ WRITE CKSUM
> >>>       SSD-TANK                   DEGRADED     1    67    35
> >>>         raidz2-0                 DEGRADED     4    72   113
> >>>           c5t500253884014D0D3d0  ONLINE       0     0     2
> >>>           c5t50025388401F767Ad0  DEGRADED     0     0    19  too many
> errors
> >>>           c5t50025388401F767Bd0  FAULTED      0     0     0  too many
> errors
> >>>           c5t50025388401F767Dd0  ONLINE       0     0     0
> >>>           c5t50025388401F767Fd0  ONLINE       0     0     1
> >>>           c5t50025388401F7679d0  ONLINE       0     0     2
> >>>           c5t50025388401F7680d0  REMOVED      0     0     0
> >>>           c5t50025388401F7682d0  ONLINE       0     0     1
> >>>
> >>> Can anyone suggest why I would have this problem where I am seeing
> CKSUM errors
> >>> On most disks and while only one has faulted others have been degraded
> or removed.
> >>>
> >>> Thanks
> >>> Shaun
> >>> _______________________________________________
> >>> OmniOS-discuss mailing list
> >>> OmniOS-discuss at lists.omniti.com
> >>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> >>
> >> _______________________________________________
> >> OmniOS-discuss mailing list
> >> OmniOS-discuss at lists.omniti.com
> >> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
> _______________________________________________
> 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: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160726/94fe5dfd/attachment-0001.html>

From shaun at rackcentral.com  Wed Jul 27 01:01:40 2016
From: shaun at rackcentral.com (Shaun McGuane)
Date: Wed, 27 Jul 2016 01:01:40 +0000
Subject: [OmniOS-discuss] Multiple faulty SSD's ?
In-Reply-To: <CALeZrrSFppzucJa9sZiTBUKos9WJH=QBPKAfwAx0PKH=wK8krg@mail.gmail.com>
References: <SY3PR01MB03635DB5EE8D2EFA9222740CAC0E0@SY3PR01MB0363.ausprd01.prod.outlook.com>
	<51697F54-16BB-46BC-A59F-D7BAE53FF34E@me.com>
	<0567742A-50F5-4A00-9C3C-AF4CFF88FAB6@omniti.com>
	<40ACCC6D-BBB7-4857-8811-8240FF41E3D0@me.com>
	<CALeZrrSFppzucJa9sZiTBUKos9WJH=QBPKAfwAx0PKH=wK8krg@mail.gmail.com>
Message-ID: <SY3PR01MB03632FCEF3577D5C6A5A6454AC0F0@SY3PR01MB0363.ausprd01.prod.outlook.com>

Thanks everyone for you advice on this.

What a pain in the ass?..

Shaun


From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On Behalf Of Schweiss, Chip
Sent: Wednesday, 27 July 2016 5:55 AM
To: Piotr Jasiukajtis <estibi at me.com>
Cc: omnios-discuss <omnios-discuss at lists.omniti.com>
Subject: Re: [OmniOS-discuss] Multiple faulty SSD's ?

I don't have a lot of experience with the 850 Pro, but a lot with the 840 Pro under OmniOS

With 4K block size set in sd.conf and slicing them to only use 80% of their capacity a pool of 72 of them has been under near constant heavy read/write workload for over 3 years without a single chksum error.

-Chip

On Tue, Jul 26, 2016 at 1:30 PM, Piotr Jasiukajtis <estibi at me.com<mailto:estibi at me.com>> wrote:
I don?t know a root cause, but it?s better to have a workaround than a corrupted pools.

--
Piotr Jasiukajtis

> On 26 Jul 2016, at 20:06, Dan McDonald <danmcd at omniti.com<mailto:danmcd at omniti.com>> wrote:
>
> I wonder if those sd.conf changes should be upstreamed or not?
>
> Dan
>
> Sent from my iPhone (typos, autocorrect, and all)
>
>> On Jul 26, 2016, at 1:28 PM, Piotr Jasiukajtis <estibi at me.com<mailto:estibi at me.com>> wrote:
>>
>> You may want to force the driver to use 4k instead of 512b for those drivers and create a new pool:
>>
>> https://github.com/joyent/smartos-live/commit/dd25937d2f9725def16f5e8dbb16a8bcbc2213d5
>>
>> --
>> Piotr Jasiukajtis
>>
>>> On 26 Jul 2016, at 02:24, Shaun McGuane <shaun at rackcentral.com<mailto:shaun at rackcentral.com>> wrote:
>>>
>>> Hi List,
>>>
>>> I want to report very strange SSD behaviour on a new pool I setup.
>>>
>>> The hardware is a HP DL180 G6 Server with the LSI 9207-8i Card
>>> And 8x 1TB Samsung SSD Pro drives. Running omnios-10b9c79
>>>
>>> All the drives are brand spanking new setup in a raidz2 array.
>>>
>>> Within 2 months the below has happened and there has been very
>>> Little use on this array.
>>>
>>> pool: SSD-TANK
>>> state: DEGRADED
>>> status: One or more devices are faulted in response to persistent errors.
>>>       Sufficient replicas exist for the pool to continue functioning in a
>>>       degraded state.
>>> action: Replace the faulted device, or use 'zpool clear' to mark the device
>>>       repaired.
>>> scan: scrub repaired 23K in 1h12m with 0 errors on Mon Jul 25 20:13:04 2016
>>> config:
>>>
>>>       NAME                       STATE     READ WRITE CKSUM
>>>       SSD-TANK                   DEGRADED     1    67    35
>>>         raidz2-0                 DEGRADED     4    72   113
>>>           c5t500253884014D0D3d0  ONLINE       0     0     2
>>>           c5t50025388401F767Ad0  DEGRADED     0     0    19  too many errors
>>>           c5t50025388401F767Bd0  FAULTED      0     0     0  too many errors
>>>           c5t50025388401F767Dd0  ONLINE       0     0     0
>>>           c5t50025388401F767Fd0  ONLINE       0     0     1
>>>           c5t50025388401F7679d0  ONLINE       0     0     2
>>>           c5t50025388401F7680d0  REMOVED      0     0     0
>>>           c5t50025388401F7682d0  ONLINE       0     0     1
>>>
>>> Can anyone suggest why I would have this problem where I am seeing CKSUM errors
>>> On most disks and while only one has faulted others have been degraded or removed.
>>>
>>> Thanks
>>> Shaun
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com<mailto:OmniOS-discuss at lists.omniti.com>
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com<mailto:OmniOS-discuss at lists.omniti.com>
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss

_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com<mailto:OmniOS-discuss at lists.omniti.com>
http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160727/b47ead78/attachment.html>

From ioiioi at live.cn  Sat Jul 30 05:14:15 2016
From: ioiioi at live.cn (=?gb2312?B?s8IgyPE=?=)
Date: Sat, 30 Jul 2016 05:14:15 +0000
Subject: [OmniOS-discuss] how to destroy an old zpool belong to another
	system
Message-ID: <SG2PR0601MB1392DB988F6755FE3D2DEA93CF020@SG2PR0601MB1392.apcprd06.prod.outlook.com>

hello, I am a newbie on zfs. I have a nas installed solaris 11.2, the zpool version was upgrade to 31. couple days ago, I reinstalled the nas with omnios(I didn't zpool destroy or zpool export before reinstallation, just overwrite the system drive), and I would like to destroy the zpool on solaris11 and re-create a new one. but there is a problem, here we go

root at storage1:/dev# zpool import
   pool: tank
     id: 2217486955835333869
  state: FAULTED
 status: The pool was last accessed by another system.
 action: The pool cannot be imported due to damaged devices or data.
        The pool may be active on another system, but can be imported using
        the '-f' flag.
   see: http://illumos.org/msg/ZFS-8000-EY
 config:

        tank                    FAULTED  corrupted data
          raidz1-0              DEGRADED
            /dev/label/wd160_1  UNAVAIL  cannot open
            c1t9d0p0            ONLINE
root at storage1:/dev# zpool status
  pool: rpool
 state: ONLINE
  scan: resilvered 13.9G in 0h4m with 0 errors on Thu Jul 28 15:12:10 2016
config:

        NAME          STATE     READ WRITE CKSUM
        rpool         ONLINE       0     0     0
          mirror-0    ONLINE       0     0     0
            c1t9d0s0  ONLINE       0     0     0
            c1t8d0s0  ONLINE       0     0     0

errors: No known data errors

I can not destory the old pool: tank, how to fix it?
there is another question: does c1t9d0p0 belong to the old tank pool?but it is belong to rpool now, what happen to it?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160730/d9cc90f9/attachment-0001.html>

From daleg at omniti.com  Sat Jul 30 05:30:30 2016
From: daleg at omniti.com (Dale Ghent)
Date: Sat, 30 Jul 2016 01:30:30 -0400
Subject: [OmniOS-discuss] how to destroy an old zpool belong to another
	system
In-Reply-To: <SG2PR0601MB1392DB988F6755FE3D2DEA93CF020@SG2PR0601MB1392.apcprd06.prod.outlook.com>
References: <SG2PR0601MB1392DB988F6755FE3D2DEA93CF020@SG2PR0601MB1392.apcprd06.prod.outlook.com>
Message-ID: <0DBBB7EE-9DB1-4048-8F6C-5AEAB39DDBA6@omniti.com>


> On Jul 30, 2016, at 1:14 AM, ? ? <ioiioi at live.cn> wrote:
> 
> hello, I am a newbie on zfs. I have a nas installed solaris 11.2, the zpool version was upgrade to 31. couple days ago, I reinstalled the nas with omnios(I didn't zpool destroy or zpool export before reinstallation, just overwrite the system drive), and I would like to destroy the zpool on solaris11 and re-create a new one. but there is a problem, here we go

<snip>

> I can not destory the old pool: tank, how to fix it? 
> there is another question: does c1t9d0p0 belong to the old tank pool?but it is belong to rpool now, what happen to it?

Just force-create a new one:

zpool create -f tank ...

/dale

From ioiioi at live.cn  Sat Jul 30 05:37:48 2016
From: ioiioi at live.cn (=?gb2312?B?s8IgyPE=?=)
Date: Sat, 30 Jul 2016 05:37:48 +0000
Subject: [OmniOS-discuss] =?gb2312?b?tPC4tDogIGhvdyB0byBkZXN0cm95IGFuIG9s?=
 =?gb2312?b?ZCB6cG9vbCBiZWxvbmcgdG8gYW5vdGhlciBzeXN0ZW0=?=
In-Reply-To: <0DBBB7EE-9DB1-4048-8F6C-5AEAB39DDBA6@omniti.com>
References: <SG2PR0601MB1392DB988F6755FE3D2DEA93CF020@SG2PR0601MB1392.apcprd06.prod.outlook.com>,
	<0DBBB7EE-9DB1-4048-8F6C-5AEAB39DDBA6@omniti.com>
Message-ID: <SG2PR0601MB139265EE0BB293D1E147A789CF020@SG2PR0601MB1392.apcprd06.prod.outlook.com>

thanks, I do it as your suggestion.

zpool create -f tank mirror c1t0d0 c1t1d0 mirror c1t2d0 c1t3d0 mirror ....


but "zpool import" still show up the faulted "tank" zpool information, does it matter?

________________________________
???: Dale Ghent <daleg at omniti.com>
????: 2016?7?30? 13:30
???: ? ?
??: omnios-discuss at lists.omniti.com
??: Re: [OmniOS-discuss] how to destroy an old zpool belong to another system


> On Jul 30, 2016, at 1:14 AM, ? ? <ioiioi at live.cn> wrote:
>
> hello, I am a newbie on zfs. I have a nas installed solaris 11.2, the zpool version was upgrade to 31. couple days ago, I reinstalled the nas with omnios(I didn't zpool destroy or zpool export before reinstallation, just overwrite the system drive), and I would like to destroy the zpool on solaris11 and re-create a new one. but there is a problem, here we go

<snip>

> I can not destory the old pool: tank, how to fix it?
> there is another question: does c1t9d0p0 belong to the old tank pool?but it is belong to rpool now, what happen to it?

Just force-create a new one:

zpool create -f tank ...

/dale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160730/893557f9/attachment.html>

From johan.kragsterman at capvert.se  Sat Jul 30 06:32:44 2016
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Sat, 30 Jul 2016 08:32:44 +0200
Subject: [OmniOS-discuss] volumes as char dev
Message-ID: <OF84319408.067E2E2F-ONC1258000.0023F4B2-C1258000.0023F4B4@inse.com>


Hi!


Just would like to know why zvols need to be represented as both block and char devices?

In /dev/zvol/{dsk};{rdsk}

What purpose do they have as char dev? Is it old legacy only, or of any use today?

Regards Johan


From an3s.annema at gmail.com  Sat Jul 30 15:37:58 2016
From: an3s.annema at gmail.com (Andries Annema)
Date: Sat, 30 Jul 2016 17:37:58 +0200
Subject: [OmniOS-discuss] r151014 repo offline?
Message-ID: <8ecefd54-9758-98c8-d83e-0935d0aec4fd@gmail.com>

Hello there guys,

Is it me or is the r151014 repo offline?
http://pkg.omniti.com/omnios/r151014/
Have been trying for a few days, but getting timeouts when trying to browse.

On a side note: is it possible to host a (public) mirror of these repos?

Regards,

An3s

From danmcd at omniti.com  Sat Jul 30 16:09:08 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Sat, 30 Jul 2016 12:09:08 -0400
Subject: [OmniOS-discuss] r151014 repo offline?
In-Reply-To: <8ecefd54-9758-98c8-d83e-0935d0aec4fd@gmail.com>
References: <8ecefd54-9758-98c8-d83e-0935d0aec4fd@gmail.com>
Message-ID: <52CBF697-0C20-4665-A7FF-119B3381F0DB@omniti.com>


> On Jul 30, 2016, at 11:37 AM, Andries Annema <an3s.annema at gmail.com> wrote:
> 
> Hello there guys,
> 
> Is it me or is the r151014 repo offline?
> http://pkg.omniti.com/omnios/r151014/
> Have been trying for a few days, but getting timeouts when trying to browse.

I just visited it now and it seems okay, and my r151014 box is accessing it okay.  Can you please try now?  (Knowing about your IP address may be helpful as well.)

> On a side note: is it possible to host a (public) mirror of these repos?

It's possible, but I don't know if anyone has the infrastructure to volunteer it.


Dan


From andreas at luka-online.de  Sat Jul 30 16:27:28 2016
From: andreas at luka-online.de (Andreas Luka)
Date: Sat, 30 Jul 2016 09:27:28 -0700
Subject: [OmniOS-discuss] r151014 repo offline?
In-Reply-To: <52CBF697-0C20-4665-A7FF-119B3381F0DB@omniti.com>
References: <8ecefd54-9758-98c8-d83e-0935d0aec4fd@gmail.com>
	<52CBF697-0C20-4665-A7FF-119B3381F0DB@omniti.com>
Message-ID: <op.yle9cbzojdf4tt@ws01-win7>

Hi Dan,

I just checked from my Blackberry
http://pkg.omniti.com/omnios/r151014/en/index.shtml
works fine
but
http://pkg.omniti.com/omnios/r151014/en/catalog.shtml
gets time out

Andreas


On Sat, 30 Jul 2016 09:09:08 -0700, Dan McDonald <danmcd at omniti.com> wrote:

>
>> On Jul 30, 2016, at 11:37 AM, Andries Annema <an3s.annema at gmail.com>  
>> wrote:
>>
>> Hello there guys,
>>
>> Is it me or is the r151014 repo offline?
>> http://pkg.omniti.com/omnios/r151014/
>> Have been trying for a few days, but getting timeouts when trying to  
>> browse.
>
> I just visited it now and it seems okay, and my r151014 box is accessing  
> it okay.  Can you please try now?  (Knowing about your IP address may be  
> helpful as well.)
>
>> On a side note: is it possible to host a (public) mirror of these repos?
>
> It's possible, but I don't know if anyone has the infrastructure to  
> volunteer it.
>
>
> Dan
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


-- 
Using Opera's mail client: http://www.opera.com/mail/

From an3s.annema at gmail.com  Sat Jul 30 17:34:14 2016
From: an3s.annema at gmail.com (Andries Annema)
Date: Sat, 30 Jul 2016 19:34:14 +0200
Subject: [OmniOS-discuss] r151014 repo offline?
In-Reply-To: <op.yle9cbzojdf4tt@ws01-win7>
References: <8ecefd54-9758-98c8-d83e-0935d0aec4fd@gmail.com>
	<52CBF697-0C20-4665-A7FF-119B3381F0DB@omniti.com>
	<op.yle9cbzojdf4tt@ws01-win7>
Message-ID: <a4e0f888-6eb4-be71-74bd-b30bb08fa601@gmail.com>

Hi guys,

It was exactly like Andreas says: ../index.shtml worked fine, while 
../catalog.shtml timed out.
By now, however, the index times out as well.

Furthermore, my r151014 box was and is unable to access it as well. 
Earlier it returned this error:

pkg: Some repositories failed to respond appropriately:
omnios:
Framework error: code: 28 reason: Operation too slow. Less than 1024 
bytes/sec transferred the last 30 seconds
URL: 
'http://pkg.omniti.com/omnios/r151014/omnios/search/1/False_2_None_None_%3A%3A%3Abind' 
(happened 4 times)


Tried it again just now, and now it returns this:

pkg: Some repositories failed to respond appropriately:
omnios:
http protocol error: code: 500 reason: Internal Server Error
URL: 
'http://pkg.omniti.com/omnios/r151014/omnios/search/1/False_2_None_None_%3A%3A%3Abind'


Regards,

Andries

On 2016-07-30 18:27, Andreas Luka wrote:
> Hi Dan,
>
> I just checked from my Blackberry
> http://pkg.omniti.com/omnios/r151014/en/index.shtml
> works fine
> but
> http://pkg.omniti.com/omnios/r151014/en/catalog.shtml
> gets time out
>
> Andreas
>
>
> On Sat, 30 Jul 2016 09:09:08 -0700, Dan McDonald <danmcd at omniti.com> 
> wrote:
>
>>
>>> On Jul 30, 2016, at 11:37 AM, Andries Annema <an3s.annema at gmail.com> 
>>> wrote:
>>>
>>> Hello there guys,
>>>
>>> Is it me or is the r151014 repo offline?
>>> http://pkg.omniti.com/omnios/r151014/
>>> Have been trying for a few days, but getting timeouts when trying to 
>>> browse.
>>
>> I just visited it now and it seems okay, and my r151014 box is 
>> accessing it okay.  Can you please try now?  (Knowing about your IP 
>> address may be helpful as well.)
>>
>>> On a side note: is it possible to host a (public) mirror of these 
>>> repos?
>>
>> It's possible, but I don't know if anyone has the infrastructure to 
>> volunteer it.
>>
>>
>> Dan
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>


From danmcd at omniti.com  Sat Jul 30 20:00:41 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Sat, 30 Jul 2016 16:00:41 -0400
Subject: [OmniOS-discuss] r151014 repo offline?
In-Reply-To: <a4e0f888-6eb4-be71-74bd-b30bb08fa601@gmail.com>
References: <8ecefd54-9758-98c8-d83e-0935d0aec4fd@gmail.com>
	<52CBF697-0C20-4665-A7FF-119B3381F0DB@omniti.com>
	<op.yle9cbzojdf4tt@ws01-win7>
	<a4e0f888-6eb4-be71-74bd-b30bb08fa601@gmail.com>
Message-ID: <F387C521-2FF0-439D-A9CD-43FECADBEF86@omniti.com>

I checked the internal-side of things, and also had problems with catalog.shtml.

I've since done "pkgrepo rebuild" and "pkgrepo refresh", and I got a catalog.shtml list, but it took a long time.

I will investigate further on Monday.

Thanks for the report,
Dan


From alexander.r.eremin at gmail.com  Sat Jul 30 21:22:31 2016
From: alexander.r.eremin at gmail.com (Alexander)
Date: Sun, 31 Jul 2016 00:22:31 +0300
Subject: [OmniOS-discuss] another illumos SPARC distro (IPS)
Message-ID: <etPan.579d1a97.18f2a76a.c41@gmail.com>

Hi all,
I've put a new IPS-based SPARC iso at https://sourceforge.net/projects/v9os/

I hope to ?maintain it and produce periodically updates.?
Currently I?m looking for some hosting for the IPS repository,
so I'll be grateful if someone can help here.


Yst?v?llisin terveisin
Alexander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160731/aec67c2f/attachment.html>

