From takashiary at gmail.com  Sun Jun  2 02:03:21 2013
From: takashiary at gmail.com (takashi ary)
Date: Sun, 2 Jun 2013 15:03:21 +0900
Subject: [OmniOS-discuss] IPMI on Dell R720
Message-ID: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>

Hello,

I'm running OmniOS r151006 on Dell PowerEdge R720.
I'm trying to setup IPMI from IPS but can not read sensor data.

    pkg install /system/management/ipmitool
    pkg install /driver/ipmi

root at omnios:~# ls -la /dev/ipmi0
lrwxrwxrwx 1 root root 29 May 31 15:36 /dev/ipmi0 ->
../devices/pseudo/ipmi at 0:ipmi
root at omnios:~#
root at omnios:~# ls -la /devices/pseudo/ipmi at 0:ipmi
crw------- 1 root sys 265, 0 May 31 15:36 /devices/pseudo/ipmi at 0:ipmi
root at omnios:~#
root at omnios:~# modinfo | grep ipmi
262 fffffffff7e6b000   2b48 265   1  ipmi (ipmi driver)
root at omnios:~#
root at omnios:~# ipmitool sensor
Could not enable event receiver: Invalid argument
Get Device ID command failed
Unable to open SDR for reading
root at omnios:~#


and I can not enable ipmievd.
ipmievd expect "/dev/bmc" at /lib/svc/method/svc-ipmievd.

                if [ ! -c /dev/bmc ]; then
                        echo "$0:  No BMC device found: disabling."
                        /usr/sbin/svcadm disable $SMF_FMRI
                        exit $SMF_EXIT_OK
                fi


how to solve this problem?

Thanks

From omnios at citrus-it.net  Sun Jun  2 05:05:47 2013
From: omnios at citrus-it.net (Andy)
Date: Sun, 2 Jun 2013 09:05:47 +0000 (GMT)
Subject: [OmniOS-discuss] IPMI on Dell R720
In-Reply-To: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>
References: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>
Message-ID: <alpine.GSO.2.00.1306020858310.4730@areb.pvgehf-vg.arg>


On Sun, 2 Jun 2013, takashi ary wrote:

; Hello,
;
; I'm running OmniOS r151006 on Dell PowerEdge R720.
; I'm trying to setup IPMI from IPS but can not read sensor data.
;
;     pkg install /system/management/ipmitool
;     pkg install /driver/ipmi
;
.. snip ..

; root at omnios:~# ipmitool sensor
; Could not enable event receiver: Invalid argument
; Get Device ID command failed
; Unable to open SDR for reading

This is an incompatibility between the version of IPMI tool included
in OmniOS and the Dell BMC. I haven't looked into exactly what the
problem is but 1.8.11 works fine so I just downloaded and built my
own package around that.

host# /usr/sbin/ipmitool fru | grep Board\ Product
Could not enable event receiver: Invalid argument
Get Device ID command failed

host# /opt/ipmitool/bin/ipmitool fru | grep Board\ Product
 Board Product         : PowerEdge R210 II

; and I can not enable ipmievd.

That's a bug in the service manifest. The IPMI package on OmniOS uses
the open driver instead of the BMC which was used in Solaris 10. If you
build your own package you can fix it.

Maybe the OmniOS team would consider making IPMI tool 1.8.11 available
in the repository?

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | enquiries at citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123


From richard.palo at baou.fr  Sun Jun  2 08:36:01 2013
From: richard.palo at baou.fr (Richard PALO)
Date: Sun, 02 Jun 2013 14:36:01 +0200
Subject: [OmniOS-discuss] some problems with last update to bloody
	omnios-8d266aa 64-bit
In-Reply-To: <CACLsApvXm1aYx1GxEduML4mRB2oDhAQzgFyZpSH1tgB1_jM5mA@mail.gmail.com>
References: <kmcuvs$jmu$1@ger.gmane.org> <kn4ca3$148$1@ger.gmane.org>
	<CA+QY2RQHQH2qXGa-vTUVWOm5t=C7tvKaPEitji6RjBU1fC-nQA@mail.gmail.com>
	<kn7h8v$pmv$1@ger.gmane.org>
	<CACLsApuiXqmPn+U9n+Ndpg_+9_DdVs3bz-zVfzhL6ELPN-tF-Q@mail.gmail.com>
	<kn80bg$tmu$1@ger.gmane.org> <kna355$2j0$1@ger.gmane.org>
	<CACLsAps+R84Vi+QLwXbx-ODhLYw01nVqypFy1onyfYafh=BHaA@mail.gmail.com>
	<knaq6m$eh5$1@ger.gmane.org>
	<CACLsApvXm1aYx1GxEduML4mRB2oDhAQzgFyZpSH1tgB1_jM5mA@mail.gmail.com>
Message-ID: <kofe7c$isf$1@ger.gmane.org>

For what it is worth, I seem to have been able to successfully "upgrade" 
to the stable "release" from "bloody"..

I went back to the initial "bloody" install boot environment named 
omnios. I presume any version prior to the release of r151006 should do.

After a
	pkg set-publisher -g http://pkg.omniti.com/omnios/release omnios
and a
	pkg set-publisher -G http://pkg.omniti.com/omnios/bloody omnios

I did a
	pkg refresh --full
and a
	pkg update --be-name omnios-r151006c

Testing it out now...


From ben at fluffy.co.uk  Mon Jun  3 05:29:50 2013
From: ben at fluffy.co.uk (Ben Summers)
Date: Mon, 3 Jun 2013 10:29:50 +0100
Subject: [OmniOS-discuss] Zone creation always downloads packages from repo?
Message-ID: <4C64C555-858A-4396-A40D-200F3A8CCC65@fluffy.co.uk>


Hello,

Now I've upgraded to r151006c, whenever I create a zone, it always downloads all the packages from the repo. It used to only download the packages the first time a zone was created.

Is this expected behaviour?

Ben




--
http://bens.me.uk


From ben at fluffy.co.uk  Mon Jun  3 05:54:06 2013
From: ben at fluffy.co.uk (Ben Summers)
Date: Mon, 3 Jun 2013 10:54:06 +0100
Subject: [OmniOS-discuss] Zone creation always downloads packages from
	repo?
In-Reply-To: <4C64C555-858A-4396-A40D-200F3A8CCC65@fluffy.co.uk>
References: <4C64C555-858A-4396-A40D-200F3A8CCC65@fluffy.co.uk>
Message-ID: <6203EEA0-0A44-4DAE-9E72-69A13E42D953@fluffy.co.uk>


On 3 Jun 2013, at 10:29, Ben Summers <ben at fluffy.co.uk> wrote:

> 
> Hello,
> 
> Now I've upgraded to r151006c, whenever I create a zone, it always downloads all the packages from the repo. It used to only download the packages the first time a zone was created.

It's possible I'm getting confused (sorry). A VM installed from r151006c.iso has just created a zone with cached packages.

It may be worth ignoring me unless someone else has noticed this.

Ben


--
http://bens.me.uk


From takashiary at gmail.com  Mon Jun  3 07:49:44 2013
From: takashiary at gmail.com (takashi ary)
Date: Mon, 3 Jun 2013 20:49:44 +0900
Subject: [OmniOS-discuss] IPMI on Dell R720
In-Reply-To: <alpine.GSO.2.00.1306020858310.4730@areb.pvgehf-vg.arg>
References: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>
	<alpine.GSO.2.00.1306020858310.4730@areb.pvgehf-vg.arg>
Message-ID: <CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>

Hi Andy,

Thanks for your comments.

> This is an incompatibility between the version of IPMI tool included
> in OmniOS and the Dell BMC. I haven't looked into exactly what the
> problem is but 1.8.11 works fine so I just downloaded and built my
> own package around that.

I built 1.8.12 (not 1.8.11) from modified "configure" file as follows.

--- configure 2012-08-10 04:17:27.000000000 +0900
+++ configure.mod 2013-06-03 12:47:07.815766359 +0900
@@ -12328,7 +12328,7 @@
  enable_intf_bmc=yes
  fi
  enable_intf_imb=no
- enable_intf_open=no
+ enable_intf_open=yes
  enable_intf_lipmi=no
  enable_ipmishell=no
  enable_all_options=no


root at omnios:~#
root at omnios:~# /usr/local/bin/ipmitool fru | grep Board\ Product
 Board Product         : PowerEdge R720
 Board Product         : PowerEdge R720
 Board Product         : PWR SPLY,750WP,RDNT,DELTA
 Board Product         : PWR SPLY,750WP,RDNT,DELTA
 Board Product         : DRIVE BACKPLANE
 Board Product         : Intel(R) GbE 4P I350-t rNDC
 Board Product         : Dell Storage Cntlr. H710P-Mini
root at omnios:~#
root at omnios:~#


> That's a bug in the service manifest. The IPMI package on OmniOS uses
> the open driver instead of the BMC which was used in Solaris 10. If you
> build your own package you can fix it.

I modified script file as follows.

--- /lib/svc/method/svc-ipmievd 2013-05-31 15:05:39.558634190 +0900
+++ /lib/svc/method/svc-ipmievd_mod     2013-06-03 13:49:10.809086439 +0900
@@ -30,7 +30,7 @@
 # smf(5)
 . /lib/svc/share/smf_include.sh

-SMF_FMRI="svc:/network/ipmievd:default"
+SMF_FMRI="svc:/network/ipmievd_mod:default"

 if [ $# -eq 0 ]; then
     # No arguments provided - report current status (use "-c" option to
@@ -48,13 +48,13 @@
                # to run.  If one is not detected, then disable the service
                # and exit.

-               if [ ! -c /dev/bmc ]; then
+               if [ ! -c /dev/ipmi0 ]; then
                        echo "$0:  No BMC device found: disabling."
                        /usr/sbin/svcadm disable $SMF_FMRI
                        exit $SMF_EXIT_OK
                fi

-               /usr/lib/ipmievd sel
+               /usr/local/sbin/ipmievd sel
                [ $? -ne 0 ] && exit 1
                ;;


and modified manifest file as follows.

--- /lib/svc/manifest/network/ipmievd.xml       2013-05-31
15:05:39.588058906 +0900
+++ /lib/svc/manifest/network/ipmievd_mod.xml   2013-06-03
13:54:30.309789173 +0900
@@ -30,7 +30,7 @@

 <service_bundle type='manifest' name='SUNWipmi:ipmievd'>

-<service name='network/ipmievd' type='service' version='1'>
+<service name='network/ipmievd_mod' type='service' version='1'>

        <!--
          Configure a default instance for the service since it doesn't
@@ -71,7 +71,7 @@
        <exec_method
                type='method'
                name='start'
-               exec='/lib/svc/method/svc-ipmievd %m'
+               exec='/lib/svc/method/svc-ipmievd_mod %m'
                timeout_seconds='60'/>

        <exec_method
@@ -99,7 +99,7 @@
                </common_name>
                <documentation>
                        <manpage title='ipmievd' section='8'
-                               manpath='/usr/share/man' />
+                               manpath='/usr/local/share/man' />
                        <doc_link name='sourceforge.net'

uri='http://sourceforge.net/projects/ipmitool' />
                </documentation>


root at omnios:~#
root at omnios:~# tail /var/adm/messages
Jun  3 14:48:08 omnios ipmievd: [ID 702911 local4.notice] Reading sensors...
Jun  3 14:48:09 omnios ipmievd: [ID 702911 local4.notice] Waiting for events...
root at omnios:~#


Thanks

From jesus at omniti.com  Mon Jun  3 10:43:28 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Mon, 3 Jun 2013 10:43:28 -0400
Subject: [OmniOS-discuss] IPMI on Dell R720
In-Reply-To: <CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>
References: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>
	<alpine.GSO.2.00.1306020858310.4730@areb.pvgehf-vg.arg>
	<CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>
Message-ID: <CACLsApsbdKxNbkqCfzo680K2PgXCy0_rxyCC+rgy=QUFDSPEkA@mail.gmail.com>

This is very confusing... when I run a build on the ipmitool in the current
tree, I get:

ipmitool 1.8.12

Interfaces
  lan     : yes
  lanplus : yes
  open    : yes
  free    : no
  imb     : no
  bmc     : yes
  lipmi   : no

Extra tools
  ipmievd   : yes
  ipmishell : no

So it would appear it is already building the open intf support.


On Mon, Jun 3, 2013 at 7:49 AM, takashi ary <takashiary at gmail.com> wrote:

> Hi Andy,
>
> Thanks for your comments.
>
> > This is an incompatibility between the version of IPMI tool included
> > in OmniOS and the Dell BMC. I haven't looked into exactly what the
> > problem is but 1.8.11 works fine so I just downloaded and built my
> > own package around that.
>
> I built 1.8.12 (not 1.8.11) from modified "configure" file as follows.
>
> --- configure 2012-08-10 04:17:27.000000000 +0900
> +++ configure.mod 2013-06-03 12:47:07.815766359 +0900
> @@ -12328,7 +12328,7 @@
>   enable_intf_bmc=yes
>   fi
>   enable_intf_imb=no
> - enable_intf_open=no
> + enable_intf_open=yes
>   enable_intf_lipmi=no
>   enable_ipmishell=no
>   enable_all_options=no
>
>
> root at omnios:~#
> root at omnios:~# /usr/local/bin/ipmitool fru | grep Board\ Product
>  Board Product         : PowerEdge R720
>  Board Product         : PowerEdge R720
>  Board Product         : PWR SPLY,750WP,RDNT,DELTA
>  Board Product         : PWR SPLY,750WP,RDNT,DELTA
>  Board Product         : DRIVE BACKPLANE
>  Board Product         : Intel(R) GbE 4P I350-t rNDC
>  Board Product         : Dell Storage Cntlr. H710P-Mini
> root at omnios:~#
> root at omnios:~#
>
>
> > That's a bug in the service manifest. The IPMI package on OmniOS uses
> > the open driver instead of the BMC which was used in Solaris 10. If you
> > build your own package you can fix it.
>
> I modified script file as follows.
>
> --- /lib/svc/method/svc-ipmievd 2013-05-31 15:05:39.558634190 +0900
> +++ /lib/svc/method/svc-ipmievd_mod     2013-06-03 13:49:10.809086439 +0900
> @@ -30,7 +30,7 @@
>  # smf(5)
>  . /lib/svc/share/smf_include.sh
>
> -SMF_FMRI="svc:/network/ipmievd:default"
> +SMF_FMRI="svc:/network/ipmievd_mod:default"
>
>  if [ $# -eq 0 ]; then
>      # No arguments provided - report current status (use "-c" option to
> @@ -48,13 +48,13 @@
>                 # to run.  If one is not detected, then disable the service
>                 # and exit.
>
> -               if [ ! -c /dev/bmc ]; then
> +               if [ ! -c /dev/ipmi0 ]; then
>                         echo "$0:  No BMC device found: disabling."
>                         /usr/sbin/svcadm disable $SMF_FMRI
>                         exit $SMF_EXIT_OK
>                 fi
>
> -               /usr/lib/ipmievd sel
> +               /usr/local/sbin/ipmievd sel
>                 [ $? -ne 0 ] && exit 1
>                 ;;
>
>
> and modified manifest file as follows.
>
> --- /lib/svc/manifest/network/ipmievd.xml       2013-05-31
> 15:05:39.588058906 +0900
> +++ /lib/svc/manifest/network/ipmievd_mod.xml   2013-06-03
> 13:54:30.309789173 +0900
> @@ -30,7 +30,7 @@
>
>  <service_bundle type='manifest' name='SUNWipmi:ipmievd'>
>
> -<service name='network/ipmievd' type='service' version='1'>
> +<service name='network/ipmievd_mod' type='service' version='1'>
>
>         <!--
>           Configure a default instance for the service since it doesn't
> @@ -71,7 +71,7 @@
>         <exec_method
>                 type='method'
>                 name='start'
> -               exec='/lib/svc/method/svc-ipmievd %m'
> +               exec='/lib/svc/method/svc-ipmievd_mod %m'
>                 timeout_seconds='60'/>
>
>         <exec_method
> @@ -99,7 +99,7 @@
>                 </common_name>
>                 <documentation>
>                         <manpage title='ipmievd' section='8'
> -                               manpath='/usr/share/man' />
> +                               manpath='/usr/local/share/man' />
>                         <doc_link name='sourceforge.net'
>
> uri='http://sourceforge.net/projects/ipmitool' />
>                 </documentation>
>
>
> root at omnios:~#
> root at omnios:~# tail /var/adm/messages
> Jun  3 14:48:08 omnios ipmievd: [ID 702911 local4.notice] Reading
> sensors...
> Jun  3 14:48:09 omnios ipmievd: [ID 702911 local4.notice] Waiting for
> events...
> root at omnios:~#
>
>
> Thanks
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>



-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130603/d449cdd9/attachment.html>

From daleg at omniti.com  Mon Jun  3 11:05:54 2013
From: daleg at omniti.com (Dale Ghent)
Date: Mon, 3 Jun 2013 11:05:54 -0400
Subject: [OmniOS-discuss] IPMI on Dell R720
In-Reply-To: <CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>
References: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>
	<alpine.GSO.2.00.1306020858310.4730@areb.pvgehf-vg.arg>
	<CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>
Message-ID: <324B5AA9-C0B4-4CBD-86EE-2CD764784F54@omniti.com>


Can you provide some truss output from a non-working ipmitool command?

truss -xall -tall -vall -wall -rall ipmitool ?.

would suffice.

Thanks
/dale

On Jun 3, 2013, at 7:49 AM, takashi ary <takashiary at gmail.com> wrote:

> Hi Andy,
> 
> Thanks for your comments.
> 
>> This is an incompatibility between the version of IPMI tool included
>> in OmniOS and the Dell BMC. I haven't looked into exactly what the
>> problem is but 1.8.11 works fine so I just downloaded and built my
>> own package around that.
> 
> I built 1.8.12 (not 1.8.11) from modified "configure" file as follows.
> 
> --- configure 2012-08-10 04:17:27.000000000 +0900
> +++ configure.mod 2013-06-03 12:47:07.815766359 +0900
> @@ -12328,7 +12328,7 @@
>  enable_intf_bmc=yes
>  fi
>  enable_intf_imb=no
> - enable_intf_open=no
> + enable_intf_open=yes
>  enable_intf_lipmi=no
>  enable_ipmishell=no
>  enable_all_options=no
> 
> 
> root at omnios:~#
> root at omnios:~# /usr/local/bin/ipmitool fru | grep Board\ Product
> Board Product         : PowerEdge R720
> Board Product         : PowerEdge R720
> Board Product         : PWR SPLY,750WP,RDNT,DELTA
> Board Product         : PWR SPLY,750WP,RDNT,DELTA
> Board Product         : DRIVE BACKPLANE
> Board Product         : Intel(R) GbE 4P I350-t rNDC
> Board Product         : Dell Storage Cntlr. H710P-Mini
> root at omnios:~#
> root at omnios:~#
> 
> 
>> That's a bug in the service manifest. The IPMI package on OmniOS uses
>> the open driver instead of the BMC which was used in Solaris 10. If you
>> build your own package you can fix it.
> 
> I modified script file as follows.
> 
> --- /lib/svc/method/svc-ipmievd 2013-05-31 15:05:39.558634190 +0900
> +++ /lib/svc/method/svc-ipmievd_mod     2013-06-03 13:49:10.809086439 +0900
> @@ -30,7 +30,7 @@
> # smf(5)
> . /lib/svc/share/smf_include.sh
> 
> -SMF_FMRI="svc:/network/ipmievd:default"
> +SMF_FMRI="svc:/network/ipmievd_mod:default"
> 
> if [ $# -eq 0 ]; then
>     # No arguments provided - report current status (use "-c" option to
> @@ -48,13 +48,13 @@
>                # to run.  If one is not detected, then disable the service
>                # and exit.
> 
> -               if [ ! -c /dev/bmc ]; then
> +               if [ ! -c /dev/ipmi0 ]; then
>                        echo "$0:  No BMC device found: disabling."
>                        /usr/sbin/svcadm disable $SMF_FMRI
>                        exit $SMF_EXIT_OK
>                fi
> 
> -               /usr/lib/ipmievd sel
> +               /usr/local/sbin/ipmievd sel
>                [ $? -ne 0 ] && exit 1
>                ;;
> 
> 
> and modified manifest file as follows.
> 
> --- /lib/svc/manifest/network/ipmievd.xml       2013-05-31
> 15:05:39.588058906 +0900
> +++ /lib/svc/manifest/network/ipmievd_mod.xml   2013-06-03
> 13:54:30.309789173 +0900
> @@ -30,7 +30,7 @@
> 
> <service_bundle type='manifest' name='SUNWipmi:ipmievd'>
> 
> -<service name='network/ipmievd' type='service' version='1'>
> +<service name='network/ipmievd_mod' type='service' version='1'>
> 
>        <!--
>          Configure a default instance for the service since it doesn't
> @@ -71,7 +71,7 @@
>        <exec_method
>                type='method'
>                name='start'
> -               exec='/lib/svc/method/svc-ipmievd %m'
> +               exec='/lib/svc/method/svc-ipmievd_mod %m'
>                timeout_seconds='60'/>
> 
>        <exec_method
> @@ -99,7 +99,7 @@
>                </common_name>
>                <documentation>
>                        <manpage title='ipmievd' section='8'
> -                               manpath='/usr/share/man' />
> +                               manpath='/usr/local/share/man' />
>                        <doc_link name='sourceforge.net'
> 
> uri='http://sourceforge.net/projects/ipmitool' />
>                </documentation>
> 
> 
> root at omnios:~#
> root at omnios:~# tail /var/adm/messages
> Jun  3 14:48:08 omnios ipmievd: [ID 702911 local4.notice] Reading sensors...
> Jun  3 14:48:09 omnios ipmievd: [ID 702911 local4.notice] Waiting for events...
> root at omnios:~#
> 
> 
> Thanks
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From takashiary at gmail.com  Mon Jun  3 13:25:46 2013
From: takashiary at gmail.com (takashi ary)
Date: Tue, 4 Jun 2013 02:25:46 +0900
Subject: [OmniOS-discuss] IPMI on Dell R720
In-Reply-To: <324B5AA9-C0B4-4CBD-86EE-2CD764784F54@omniti.com>
References: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>
	<alpine.GSO.2.00.1306020858310.4730@areb.pvgehf-vg.arg>
	<CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>
	<324B5AA9-C0B4-4CBD-86EE-2CD764784F54@omniti.com>
Message-ID: <CANXaD7h_K1m1TQzKy5g=CX64avEWxwgOspVTvgT34HV_wZdwGQ@mail.gmail.com>

Hi dale,

The results below.

root at omnios:~#
root at omnios:~# truss -xall -tall -vall -wall -rall ipmitool fru
execve(0x08047FE6, 0x08047E64, 0x08047E70)  argc = 2
     0x08047FE6: "/usr/sbin/ipmitool"
sysinfo(5, 0x08047A87, 257)                     = 6
     0x08047A87: "i86pc"
mmap(0x00000000, 32, 0x0007, 0x0102, -1, 0)     = 0xFEFB0000
mmap(0x00000000, 4096, 0x0003, 0x0102, -1, 0)   = 0xFEFA0000
mmap(0x00000000, 4096, 0x0003, 0x0102, -1, 0)   = 0xFEF90000
mmap(0x00000000, 4096, 0x0007, 0x0102, -1, 0)   = 0xFEF80000
memcntl(0xFEFB6000, 47484, 4, 0x0003, 0, 0)     = 0
memcntl(0x08050000, 52328, 4, 0x0003, 0, 0)     = 0
resolvepath(0xFEF90020, 0x08047778, 1023)       = 12
     0xFEF90020: "/usr/lib/ld.so.1"
     0x08047778: "/lib/ld.so.1"
resolvepath(0xFEF9000D, 0x08047778, 1023)       = 18
     0xFEF9000D: "/usr/sbin/ipmitool"
     0x08047778: "/usr/sbin/ipmitool"
sysconfig(6)                                    = 4096
stat64(0xFEF9000D, 0x08047AF8)                  = 0
     0xFEF9000D: "/usr/sbin/ipmitool"
    d=0x02B10002 i=70588 m=0100555 l=1  u=0     g=2     sz=1101512
        at = May 28 15:05:39 JST 2013  [ 1369721139.517345846 ]
        mt = May 28 15:05:39 JST 2013  [ 1369721139.550195896 ]
        ct = May 28 15:05:39 JST 2013  [ 1369721139.550314355 ]
    bsz=131072 blks=973   fs=zfs
open(0xFEFE694A, 0, 0)                          Err#2 ENOENT
     0xFEFE694A: "/var/ld/ld.config"
stat64(0xFEF90048, 0x08047318)                  Err#2 ENOENT
     0xFEF90048: "/usr/sfw/lib/libm.so.2"
stat64(0xFEF9005F, 0x08047318)                  = 0
     0xFEF9005F: "/lib/libm.so.2"
    d=0x02B10002 i=3742  m=0100755 l=1  u=0     g=2     sz=343176
        at = May 16 17:00:07 JST 2013  [ 1368691207.302714978 ]
        mt = May  8 06:56:11 JST 2013  [ 1367963771.000000000 ]
        ct = May 16 14:59:28 JST 2013  [ 1368683968.181422283 ]
    bsz=131072 blks=773   fs=zfs
resolvepath(0xFEF9005F, 0x080473E0, 1023)       = 14
     0xFEF9005F: "/lib/libm.so.2"
     0x080473E0: "/lib/libm.so.2"
open(0xFEF9005F, 0, 0)                          = 3
     0xFEF9005F: "/lib/libm.so.2"
mmapobj(3, 0x20000, 0xFEF80AE8, 0x08047384, 0x00000000) = 0
close(3)                                        = 0
memcntl(0xFEBD0000, 25456, 4, 0x0003, 0, 0)     = 0
mmap(0x00000000, 4096, 0x0007, 0x0102, -1, 0)   = 0xFEF70000
stat64(0xFEF9007D, 0x08047318)                  Err#2 ENOENT
     0xFEF9007D: "/usr/sfw/lib/libsocket.so.1"
stat64(0xFEF90099, 0x08047318)                  = 0
     0xFEF90099: "/lib/libsocket.so.1"
    d=0x02B10002 i=70396 m=0100755 l=1  u=0     g=2     sz=74492
        at = May 27 18:39:10 JST 2013  [ 1369647550.030819652 ]
        mt = May 27 18:39:10 JST 2013  [ 1369647550.033246693 ]
        ct = May 27 18:39:10 JST 2013  [ 1369647550.033371174 ]
    bsz=74752 blks=93    fs=zfs
resolvepath(0xFEF90099, 0x080473E0, 1023)       = 19
     0xFEF90099: "/lib/libsocket.so.1"
     0x080473E0: "/lib/libsocket.so.1"
open(0xFEF90099, 0, 0)                          = 3
     0xFEF90099: "/lib/libsocket.so.1"
mmapobj(3, 0x20000, 0xFEF70110, 0x08047384, 0x00000000) = 0
close(3)                                        = 0
memcntl(0xFEF50000, 17040, 4, 0x0003, 0, 0)     = 0
stat64(0xFEF900B9, 0x08047318)                  Err#2 ENOENT
     0xFEF900B9: "/usr/sfw/lib/libnsl.so.1"
stat64(0xFEF900D2, 0x08047318)                  = 0
     0xFEF900D2: "/lib/libnsl.so.1"
    d=0x02B10002 i=70380 m=0100755 l=1  u=0     g=2     sz=542448
        at = May 27 18:39:09 JST 2013  [ 1369647549.962705069 ]
        mt = May 27 18:39:09 JST 2013  [ 1369647549.978942578 ]
        ct = May 27 18:39:09 JST 2013  [ 1369647549.979062036 ]
    bsz=131072 blks=692   fs=zfs
resolvepath(0xFEF900D2, 0x080473E0, 1023)       = 16
     0xFEF900D2: "/lib/libnsl.so.1"
     0x080473E0: "/lib/libnsl.so.1"
open(0xFEF900D2, 0, 0)                          = 3
     0xFEF900D2: "/lib/libnsl.so.1"
mmapobj(3, 0x20000, 0xFEF706F8, 0x08047384, 0x00000000) = 0
close(3)                                        = 0
memcntl(0xFEB30000, 78576, 4, 0x0003, 0, 0)     = 0
stat64(0xFEF900F6, 0x08047318)                  Err#2 ENOENT
     0xFEF900F6: "/usr/sfw/lib/libcrypto.so.1.0.0"
stat64(0xFEF90116, 0x08047318)                  = 0
     0xFEF90116: "/lib/libcrypto.so.1.0.0"
    d=0x02B10002 i=2577  m=0100555 l=1  u=0     g=2     sz=1885652
        at = May 16 15:13:22 JST 2013  [ 1368684802.165208543 ]
        mt = May  8 06:55:58 JST 2013  [ 1367963758.000000000 ]
        ct = May 16 14:59:27 JST 2013  [ 1368683967.788607698 ]
    bsz=131072 blks=3847  fs=zfs
resolvepath(0xFEF90116, 0x080473E0, 1023)       = 23
     0xFEF90116: "/lib/libcrypto.so.1.0.0"
     0x080473E0: "/lib/libcrypto.so.1.0.0"
open(0xFEF90116, 0, 0)                          = 3
     0xFEF90116: "/lib/libcrypto.so.1.0.0"
mmapobj(3, 0x20000, 0xFEF70CF8, 0x08047384, 0x00000000) = 0
close(3)                                        = 0
mmap(0x00000000, 4096, 0x0007, 0x0102, -1, 0)   = 0xFEDA0000
memcntl(0xFEDB0000, 319876, 4, 0x0003, 0, 0)    = 0
stat64(0xFEF90138, 0x08047318)                  Err#2 ENOENT
     0xFEF90138: "/usr/sfw/lib/libc.so.1"
stat64(0xFEF9014F, 0x08047318)                  = 0
     0xFEF9014F: "/lib/libc.so.1"
    d=0x02B10002 i=70152 m=0100755 l=1  u=0     g=2     sz=1570648
        at = May 27 18:39:09 JST 2013  [ 1369647549.051108737 ]
        mt = May 27 18:39:09 JST 2013  [ 1369647549.086174314 ]
        ct = May 27 18:39:09 JST 2013  [ 1369647549.086308518 ]
    bsz=131072 blks=1488  fs=lofs
resolvepath(0xFEF9014F, 0x080473E0, 1023)       = 14
     0xFEF9014F: "/lib/libc.so.1"
     0x080473E0: "/lib/libc.so.1"
open(0xFEF9014F, 0, 0)                          = 3
     0xFEF9014F: "/lib/libc.so.1"
mmapobj(3, 0x20000, 0xFEDA04D0, 0x08047384, 0x00000000) = 0
close(3)                                        = 0
memcntl(0xFEC50000, 244676, 4, 0x0003, 0, 0)    = 0
stat64(0xFEF90166, 0x08047318)                  Err#2 ENOENT
     0xFEF90166: "/lib/libz.so"
stat64(0xFEF90173, 0x08047318)                  = 0
     0xFEF90173: "/usr/lib/libz.so"
    d=0x02B10002 i=38050 m=0100755 l=1  u=0     g=2     sz=102460
        at = May 16 17:00:07 JST 2013  [ 1368691207.302677330 ]
        mt = May  8 06:55:58 JST 2013  [ 1367963758.000000000 ]
        ct = May 16 15:01:06 JST 2013  [ 1368684066.297446668 ]
    bsz=102912 blks=202   fs=zfs
resolvepath(0xFEF90173, 0x080473E0, 1023)       = 22
     0xFEF90173: "/usr/lib/libz.so"
     0x080473E0: "/usr/lib/libz.so.1.2.7"
open(0xFEF90173, 0, 0)                          = 3
     0xFEF90173: "/usr/lib/libz.so"
mmapobj(3, 0x20000, 0xFEDA0F00, 0x08047384, 0x00000000) = 0
close(3)                                        = 0
mmap(0x00000000, 4096, 0x0007, 0x0102, -1, 0)   = 0xFEC40000
memcntl(0xFE7E0000, 8020, 4, 0x0003, 0, 0)      = 0
mmap(0x00010000, 24576, 0x0007, 0x80000302, -1, 0) = 0xFEBC0000
context(0, 0x08047938)
getrlimit(3, 0x08047930)                        = 0
        cur = 10485760  max = RLIM_INFINITY
getpid()                                        = 21688 [21687]
lwp_private(0, 1, 0xFEBC2A40)                   = 0x000001C3
context(3, 0xFEBC2AA0)
sigpendsys(2, 0xFED9CFA0)                       = 0
        sigmask = 0xFFFFFFFF 0xFFFFFFFF 0x000000FF 0
sysi86(41, 0xFED9DF8C, 0x0000133F, 0x00001F80)  = 0x00000001
schedctl()                                      = 0xFEB23000
sigaction(0x00000002, 0x08047CA0, 0x08047D10)   = 0
    new: hand = 0xFED15A41 mask = 0xFFBFFEFF 0xFFFFFFFF 0x000000FF 0
flags = 0x0002
    old: hand = 0x00000000 mask = 0 0 0 0 flags = 0x0000
brk(0x081E2320)                                 = 0
brk(0x081E4320)                                 = 0
ioctl(1, 0x00005401, 0x08047B4E)                = 0
        iflag=0022402 oflag=0014005 cflag=0000275 lflag=0105073 line=0
            cc:  003 034 010 025 004 000 000 000
fstat64(1, 0x08047A90)                          = 0
    d=0x082C0000 i=1103126768 m=0020620 l=1  u=1000  g=7     rdev=0x03980001
        at = Jun  4 01:52:10 JST 2013  [ 1370278330.000000000 ]
        mt = Jun  4 01:52:19 JST 2013  [ 1370278339.000000000 ]
        ct = Jun  3 14:31:00 JST 2013  [ 1370237460.000000000 ]
    bsz=8192  blks=0     fs=dev
FRU Device Description : Builtin FRU Device (ID 0)
write(1, 0xFED9E3C4, 51)                        = 51
   F R U   D e v i c e   D e s c r i p t i o n   :   B u i l t i n
     F R U   D e v i c e   ( I D   0 )\n
open(0x08047B48, 02, 0)                         = 3
     0x08047B48: "/dev/ipmi0"
ioctl(3, 0x40046910, 0x08047B58)                Err#22 EINVAL
                read 4 bytes
fstat64(2, 0x08046B60)                          = 0
    d=0x082C0000 i=1103126768 m=0020620 l=1  u=1000  g=7     rdev=0x03980001
        at = Jun  4 01:52:10 JST 2013  [ 1370278330.000000000 ]
        mt = Jun  4 01:52:19 JST 2013  [ 1370278339.000000000 ]
        ct = Jun  3 14:31:00 JST 2013  [ 1370237460.000000000 ]
    bsz=8192  blks=0     fs=dev
Could not enable event receiverwrite(2, 0x0815F6C0, 31)                 = 31
   C o u l d   n o t   e n a b l e   e v e n t   r e c e i v e r
: write(2, 0xFED9DB54, 2)                               = 2
     0xFED9DB54: " :  "
Invalid argumentwrite(2, 0xFED285BD, 16)                        = 16
   I n v a l i d   a r g u m e n t

write(2, 0xFED9DB54, 1)                         = 1
     0xFED9DB54: "\n"
Get Device ID command failedwrite(2, 0x0815FAC0, 28)                    = 28
   G e t   D e v i c e   I D   c o m m a n d   f a i l e d

write(2, 0xFED9DB54, 1)                         = 1
     0xFED9DB54: "\n"
_exit(1)
root at omnios:~#


Thanks


2013/6/4 Dale Ghent <daleg at omniti.com>:
>
> Can you provide some truss output from a non-working ipmitool command?
>
> truss -xall -tall -vall -wall -rall ipmitool ?.
>
> would suffice.
>
> Thanks
> /dale
>

From omnios at citrus-it.net  Mon Jun  3 14:20:36 2013
From: omnios at citrus-it.net (Andy)
Date: Mon, 3 Jun 2013 18:20:36 +0000 (GMT)
Subject: [OmniOS-discuss] IPMI on Dell R720
In-Reply-To: <CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>
References: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>
	<alpine.GSO.2.00.1306020858310.4730@areb.pvgehf-vg.arg>
	<CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>
Message-ID: <alpine.GSO.2.00.1306031812410.17447@areb.pvgehf-vg.arg>

On Mon, 3 Jun 2013, takashi ary wrote:

; Hi Andy,
;
; Thanks for your comments.
;
; > This is an incompatibility between the version of IPMI tool included
; > in OmniOS and the Dell BMC. I haven't looked into exactly what the
; > problem is but 1.8.11 works fine so I just downloaded and built my
; > own package around that.
;
; I built 1.8.12 (not 1.8.11) from modified "configure" file as follows.

I just did the same and it works fine for me too. Sorry for the confusion,
I had assumed that it was the 1.8.12 version that caused the problem once
it was solved be me downloading and building my own .11.

Very strange indeed.

/usr/sbin/ipmitool

open(0x08047A68, 02, 0)                         = 3
     0x08047A68: "/dev/ipmi0"
ioctl(3, 0x40046910, 0x08047A78)                Err#22 EINVAL
                read 4 bytes

/opt/ipmitool/bin/ipmitool

open(0x08047A60, 02, 0)                         = 3
     0x08047A60: "/dev/ipmi0"
ioctl(3, 0x80046910, 0x08047A58)                = 0
                write 4 bytes
ioctl(3, 0x80046911, 0x08047A5C)                = 0
                write 4 bytes
ioctl(3, 0x8014690D, 0x0804790C)                = 0
                write 20 bytes


-- 
Citrus IT Limited | +44 (0)870 199 8000 | enquiries at citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123


From richard.palo at baou.fr  Tue Jun  4 00:57:26 2013
From: richard.palo at baou.fr (Richard PALO)
Date: Tue, 04 Jun 2013 06:57:26 +0200
Subject: [OmniOS-discuss] some problems with last update to bloody
	omnios-8d266aa 64-bit
In-Reply-To: <kofe7c$isf$1@ger.gmane.org>
References: <kmcuvs$jmu$1@ger.gmane.org> <kn4ca3$148$1@ger.gmane.org>
	<CA+QY2RQHQH2qXGa-vTUVWOm5t=C7tvKaPEitji6RjBU1fC-nQA@mail.gmail.com>
	<kn7h8v$pmv$1@ger.gmane.org>
	<CACLsApuiXqmPn+U9n+Ndpg_+9_DdVs3bz-zVfzhL6ELPN-tF-Q@mail.gmail.com>
	<kn80bg$tmu$1@ger.gmane.org> <kna355$2j0$1@ger.gmane.org>
	<CACLsAps+R84Vi+QLwXbx-ODhLYw01nVqypFy1onyfYafh=BHaA@mail.gmail.com>
	<knaq6m$eh5$1@ger.gmane.org>
	<CACLsApvXm1aYx1GxEduML4mRB2oDhAQzgFyZpSH1tgB1_jM5mA@mail.gmail.com>
	<kofe7c$isf$1@ger.gmane.org>
Message-ID: <kojs3h$n3d$1@ger.gmane.org>

Le 02/06/13 14:36, Richard PALO a ?crit :
> For what it is worth, I seem to have been able to successfully "upgrade"
> to the stable "release" from "bloody"..
>
> I went back to the initial "bloody" install boot environment named
> omnios. I presume any version prior to the release of r151006 should do.
>
> After a
>      pkg set-publisher -g http://pkg.omniti.com/omnios/release omnios
> and a
>      pkg set-publisher -G http://pkg.omniti.com/omnios/bloody omnios
>
> I did a
>      pkg refresh --full
> and a
>      pkg update --be-name omnios-r151006c
>
> Testing it out now...
>
Well, so much for that, rolling back to a fresh update of bloody.

Release locks up during any builds, seems to be a resource problem 
somewhere, unfortunately no apparent messages on the screen or in the 
logs.  This problem I didn't have on bloody.


From jesus at omniti.com  Tue Jun  4 08:57:13 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 4 Jun 2013 08:57:13 -0400
Subject: [OmniOS-discuss] some problems with last update to bloody
 omnios-8d266aa 64-bit
In-Reply-To: <kojs3h$n3d$1@ger.gmane.org>
References: <kmcuvs$jmu$1@ger.gmane.org> <kn4ca3$148$1@ger.gmane.org>
	<CA+QY2RQHQH2qXGa-vTUVWOm5t=C7tvKaPEitji6RjBU1fC-nQA@mail.gmail.com>
	<kn7h8v$pmv$1@ger.gmane.org>
	<CACLsApuiXqmPn+U9n+Ndpg_+9_DdVs3bz-zVfzhL6ELPN-tF-Q@mail.gmail.com>
	<kn80bg$tmu$1@ger.gmane.org> <kna355$2j0$1@ger.gmane.org>
	<CACLsAps+R84Vi+QLwXbx-ODhLYw01nVqypFy1onyfYafh=BHaA@mail.gmail.com>
	<knaq6m$eh5$1@ger.gmane.org>
	<CACLsApvXm1aYx1GxEduML4mRB2oDhAQzgFyZpSH1tgB1_jM5mA@mail.gmail.com>
	<kofe7c$isf$1@ger.gmane.org> <kojs3h$n3d$1@ger.gmane.org>
Message-ID: <CACLsApsWTYFDOc0dZTWjeDrRdLbaq-irSkUaTeOoPnK9Z65tBg@mail.gmail.com>

I'll be pushing a lot of new stuff into bloody very shortly.  While the
current bloody is a bit of a mess and incomplete, I don't think much in
there is broken...  So, I've been working locally for the last few weeks
trying to get things updated without breaking everyone every single day.


On Tue, Jun 4, 2013 at 12:57 AM, Richard PALO <richard.palo at baou.fr> wrote:

> Le 02/06/13 14:36, Richard PALO a ?crit :
>
>  For what it is worth, I seem to have been able to successfully "upgrade"
>> to the stable "release" from "bloody"..
>>
>> I went back to the initial "bloody" install boot environment named
>> omnios. I presume any version prior to the release of r151006 should do.
>>
>> After a
>>      pkg set-publisher -g http://pkg.omniti.com/omnios/**release<http://pkg.omniti.com/omnios/release>omnios
>> and a
>>      pkg set-publisher -G http://pkg.omniti.com/omnios/**bloody<http://pkg.omniti.com/omnios/bloody>omnios
>>
>> I did a
>>      pkg refresh --full
>> and a
>>      pkg update --be-name omnios-r151006c
>>
>> Testing it out now...
>>
>>  Well, so much for that, rolling back to a fresh update of bloody.
>
> Release locks up during any builds, seems to be a resource problem
> somewhere, unfortunately no apparent messages on the screen or in the logs.
>  This problem I didn't have on bloody.
>
>
> ______________________________**_________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.**com <OmniOS-discuss at lists.omniti.com>
> http://lists.omniti.com/**mailman/listinfo/omnios-**discuss<http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>



-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130604/e97f8965/attachment.html>

From senses3 at gmail.com  Mon Jun  3 22:26:50 2013
From: senses3 at gmail.com (senses3)
Date: Mon, 3 Jun 2013 22:26:50 -0400
Subject: [OmniOS-discuss] OVA File downloads for vmware
Message-ID: <CAFV9EuSgQj_UBt1PCBj=DECN7rb4waEXDO=4Suyum3VKpcQcfw@mail.gmail.com>

Hey guys,

I am downloading an OVA vmware image right now, but my browser is
recognizing it as a text file so it isn't bothering to look and see how big
the file actually is. Anyway, it's downloading it but it has no idea how
big the file actually is, so it says 'unknown time remaining - 400mb
downloaded'

I was just wondering if anyone else thinks it's a good idea to compress the
images so they download as a binary file instead of a text file, making
this a non-issue.

Thanks alot!
-Brion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130603/33959da0/attachment-0001.html>

From esproul at omniti.com  Tue Jun  4 10:00:55 2013
From: esproul at omniti.com (Eric Sproul)
Date: Tue, 4 Jun 2013 10:00:55 -0400
Subject: [OmniOS-discuss] OVA File downloads for vmware
In-Reply-To: <CAFV9EuSgQj_UBt1PCBj=DECN7rb4waEXDO=4Suyum3VKpcQcfw@mail.gmail.com>
References: <CAFV9EuSgQj_UBt1PCBj=DECN7rb4waEXDO=4Suyum3VKpcQcfw@mail.gmail.com>
Message-ID: <CA+QY2RSjX3zM4-nH3AHPdEg-av6JkGhX12=+pR3uOk+CY-+H9w@mail.gmail.com>

Hi Brion,
Thanks for reporting this issue.  I've fixed the Apache config that
runs omnios.omniti.com to make .ova files have the generic
"application/octet-stream" MIME type.  This should result in a typical
download.

Eric

$ curl -I http://omnios.omniti.com/media/OmniOS-bloody-first-boot.ova
HTTP/1.1 200 OK
Date: Tue, 04 Jun 2013 13:58:51 GMT
Server: Apache
Last-Modified: Fri, 31 Aug 2012 23:54:09 GMT
ETag: "3a-27fee800-4c89882082a40"
Accept-Ranges: bytes
Content-Length: 671016960
Vary: Accept-Encoding
Content-Type: application/octet-stream


On Mon, Jun 3, 2013 at 10:26 PM, senses3 <senses3 at gmail.com> wrote:
> Hey guys,
>
> I am downloading an OVA vmware image right now, but my browser is
> recognizing it as a text file so it isn't bothering to look and see how big
> the file actually is. Anyway, it's downloading it but it has no idea how big
> the file actually is, so it says 'unknown time remaining - 400mb downloaded'
>
> I was just wondering if anyone else thinks it's a good idea to compress the
> images so they download as a binary file instead of a text file, making this
> a non-issue.
>
> Thanks alot!
> -Brion
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From richard.palo at baou.fr  Wed Jun  5 05:00:09 2013
From: richard.palo at baou.fr (Richard PALO)
Date: Wed, 05 Jun 2013 11:00:09 +0200
Subject: [OmniOS-discuss] to swap or not to swap
In-Reply-To: <CA+QY2RS9ErmH=q313Q4OsWwWuk9d_CbkdB3KyHytPXZTzPoecg@mail.gmail.com>
References: <51703E4C.6010409@acm.org>
	<alpine.GSO.2.01.1304181401370.13747@freddy.simplesystems.org>
	<CA+QY2RS9ErmH=q313Q4OsWwWuk9d_CbkdB3KyHytPXZTzPoecg@mail.gmail.com>
Message-ID: <komumk$9mi$1@ger.gmane.org>

Le 18/04/13 21:17, Eric Sproul a ?crit :
> Swap may also be located off the boot pool if desired.  It is the dump
> volume that must be on the boot pool, because it may need to be
> accessed early in the boot process, before non-root pools have been
> imported.
>
> Eric
>
>
Hi,
Pirating this thread a bit...

Although I can't seem to quickly put my finger on the install script, it 
would be nice if when the swap volume is created that the zfs create 
command specify the blocksize as such :

# zfs create -V 8G -b $(pagesize) rpool/swap

(8G is only an example here)

I noticed 8K default swap blocksize on amd64 instead of 4K, I understand 
8K is normally for SPARC.




From richard.palo at baou.fr  Thu Jun  6 03:34:59 2013
From: richard.palo at baou.fr (Richard PALO)
Date: Thu, 06 Jun 2013 09:34:59 +0200
Subject: [OmniOS-discuss] some problems with last update to bloody
	omnios-8d266aa 64-bit
In-Reply-To: <CACLsApsWTYFDOc0dZTWjeDrRdLbaq-irSkUaTeOoPnK9Z65tBg@mail.gmail.com>
References: <kmcuvs$jmu$1@ger.gmane.org> <kn4ca3$148$1@ger.gmane.org>
	<CA+QY2RQHQH2qXGa-vTUVWOm5t=C7tvKaPEitji6RjBU1fC-nQA@mail.gmail.com>
	<kn7h8v$pmv$1@ger.gmane.org>
	<CACLsApuiXqmPn+U9n+Ndpg_+9_DdVs3bz-zVfzhL6ELPN-tF-Q@mail.gmail.com>
	<kn80bg$tmu$1@ger.gmane.org> <kna355$2j0$1@ger.gmane.org>
	<CACLsAps+R84Vi+QLwXbx-ODhLYw01nVqypFy1onyfYafh=BHaA@mail.gmail.com>
	<knaq6m$eh5$1@ger.gmane.org>
	<CACLsApvXm1aYx1GxEduML4mRB2oDhAQzgFyZpSH1tgB1_jM5mA@mail.gmail.com>
	<kofe7c$isf$1@ger.gmane.org> <kojs3h$n3d$1@ger.gmane.org>
	<CACLsApsWTYFDOc0dZTWjeDrRdLbaq-irSkUaTeOoPnK9Z65tBg@mail.gmail.com>
Message-ID: <kope2t$4r9$1@ger.gmane.org>

BTW, I believe I found the issue with my build on "release", which 
appears to be more an issue with tmp & swap (tmp was being overloaded), 
switching to use /var/tmp seems to get over resource allocation problems 
experienced. Testing with both "release" and "bloody" now..


From jesus at omniti.com  Thu Jun  6 08:53:35 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Thu, 6 Jun 2013 08:53:35 -0400
Subject: [OmniOS-discuss] some problems with last update to bloody
 omnios-8d266aa 64-bit
In-Reply-To: <kope2t$4r9$1@ger.gmane.org>
References: <kmcuvs$jmu$1@ger.gmane.org> <kn4ca3$148$1@ger.gmane.org>
	<CA+QY2RQHQH2qXGa-vTUVWOm5t=C7tvKaPEitji6RjBU1fC-nQA@mail.gmail.com>
	<kn7h8v$pmv$1@ger.gmane.org>
	<CACLsApuiXqmPn+U9n+Ndpg_+9_DdVs3bz-zVfzhL6ELPN-tF-Q@mail.gmail.com>
	<kn80bg$tmu$1@ger.gmane.org> <kna355$2j0$1@ger.gmane.org>
	<CACLsAps+R84Vi+QLwXbx-ODhLYw01nVqypFy1onyfYafh=BHaA@mail.gmail.com>
	<knaq6m$eh5$1@ger.gmane.org>
	<CACLsApvXm1aYx1GxEduML4mRB2oDhAQzgFyZpSH1tgB1_jM5mA@mail.gmail.com>
	<kofe7c$isf$1@ger.gmane.org> <kojs3h$n3d$1@ger.gmane.org>
	<CACLsApsWTYFDOc0dZTWjeDrRdLbaq-irSkUaTeOoPnK9Z65tBg@mail.gmail.com>
	<kope2t$4r9$1@ger.gmane.org>
Message-ID: <CACLsApvv-ehos7NcAa7vqCqDcy=wkq3rqaoAo3rPQsVBE5di7A@mail.gmail.com>

Ah, you're using the omnios-build system? It does use /tmp/ (to be fast),
but all the boxes we run it on have a lot of room there.  There are some
other scenarios where it makes sense to change that to /var/tmp/ as well.
 Maybe we should change the default to be /var/tmp/


On Thu, Jun 6, 2013 at 3:34 AM, Richard PALO <richard.palo at baou.fr> wrote:

> BTW, I believe I found the issue with my build on "release", which appears
> to be more an issue with tmp & swap (tmp was being overloaded), switching
> to use /var/tmp seems to get over resource allocation problems experienced.
> Testing with both "release" and "bloody" now..
>
>
> ______________________________**_________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.**com <OmniOS-discuss at lists.omniti.com>
> http://lists.omniti.com/**mailman/listinfo/omnios-**discuss<http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>



-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130606/16c8d175/attachment.html>

From fabio at fabiorabelo.wiki.br  Thu Jun  6 14:12:21 2013
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Thu, 6 Jun 2013 15:12:21 -0300
Subject: [OmniOS-discuss] statistics
Message-ID: <CAEekY67xkFC77Cf+Ksm-3gBjRYsjazUzi7iF7QwjBr3fsrfQqA@mail.gmail.com>

Hi to all

First, thanks a lot for the product, it is realy great !

My question now :

Is there any way to make a graphical statsics od ZFS performance ?

I have some botleneck in my sistem ( OminOS V 0.9a9 Nightly mar 04 2013 +
Napp-it ) that I can not identify ...

It stores all VMs in a Proxmox Cluster with 5 nodes and 14 mixed VMs ( 3
W2K12 Server, 2 Win7Pro and all others Linux Debian or Ubuntu ) .

There are a 10 GB switcher to interconnect all nodes and Storage .

Almost all aplications are running fine and fast .

The exception are a Debian running Oracle 11G .

I just do not know how to find out what I have to do  ...


F?bio Rabelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130606/42ed9e00/attachment.html>

From palmertime at gmail.com  Thu Jun  6 15:19:50 2013
From: palmertime at gmail.com (Michael Palmer)
Date: Thu, 6 Jun 2013 12:19:50 -0700
Subject: [OmniOS-discuss] statistics
In-Reply-To: <CAEekY67xkFC77Cf+Ksm-3gBjRYsjazUzi7iF7QwjBr3fsrfQqA@mail.gmail.com>
References: <CAEekY67xkFC77Cf+Ksm-3gBjRYsjazUzi7iF7QwjBr3fsrfQqA@mail.gmail.com>
Message-ID: <2424890135644695329@unknownmsgid>

Are you using iSCSI or NFS?
How is your zpool configure?
What raid are you using?
Do you have a zil and/or cache device?
What hard drives or SSDs are you using and how many of each?


Sent from my iPhone

On Jun 6, 2013, at 11:26 AM, "F?bio Rabelo" <fabio at fabiorabelo.wiki.br> wrote:

> Hi to all
>
> First, thanks a lot for the product, it is realy great !
>
> My question now :
>
> Is there any way to make a graphical statsics od ZFS performance ?
>
> I have some botleneck in my sistem ( OminOS V 0.9a9 Nightly mar 04 2013 + Napp-it ) that I can not identify ...
>
> It stores all VMs in a Proxmox Cluster with 5 nodes and 14 mixed VMs ( 3 W2K12 Server, 2 Win7Pro and all others Linux Debian or Ubuntu ) .
>
> There are a 10 GB switcher to interconnect all nodes and Storage .
>
> Almost all aplications are running fine and fast .
>
> The exception are a Debian running Oracle 11G .
>
> I just do not know how to find out what I have to do  ...
>
>
> F?bio Rabelo
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From palmertime at gmail.com  Thu Jun  6 15:34:01 2013
From: palmertime at gmail.com (Michael Palmer)
Date: Thu, 6 Jun 2013 12:34:01 -0700
Subject: [OmniOS-discuss] statistics
In-Reply-To: <CAEekY67xkFC77Cf+Ksm-3gBjRYsjazUzi7iF7QwjBr3fsrfQqA@mail.gmail.com>
References: <CAEekY67xkFC77Cf+Ksm-3gBjRYsjazUzi7iF7QwjBr3fsrfQqA@mail.gmail.com>
Message-ID: <-9131077647197440189@unknownmsgid>

I guess the main question was graphical statistics.  Besides buying
oracle storage I would suggest an network management system like
opennms.  There are lots of chooses out there but not sure if that is
the best solution.

Now for non-graphical,  I would say dtrace.  Google nicstat, zilstat,
arcsummary.  Also, there is 'zpool iostat -v 1' and 'iostat -x 1'

Thanks,
Michael
Sent from my iPhone

On Jun 6, 2013, at 11:26 AM, "F?bio Rabelo" <fabio at fabiorabelo.wiki.br> wrote:

> Hi to all
>
> First, thanks a lot for the product, it is realy great !
>
> My question now :
>
> Is there any way to make a graphical statsics od ZFS performance ?
>
> I have some botleneck in my sistem ( OminOS V 0.9a9 Nightly mar 04 2013 + Napp-it ) that I can not identify ...
>
> It stores all VMs in a Proxmox Cluster with 5 nodes and 14 mixed VMs ( 3 W2K12 Server, 2 Win7Pro and all others Linux Debian or Ubuntu ) .
>
> There are a 10 GB switcher to interconnect all nodes and Storage .
>
> Almost all aplications are running fine and fast .
>
> The exception are a Debian running Oracle 11G .
>
> I just do not know how to find out what I have to do  ...
>
>
> F?bio Rabelo
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From fabio at fabiorabelo.wiki.br  Thu Jun  6 15:59:33 2013
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Thu, 6 Jun 2013 16:59:33 -0300
Subject: [OmniOS-discuss] statistics
In-Reply-To: <2424890135644695329@unknownmsgid>
References: <CAEekY67xkFC77Cf+Ksm-3gBjRYsjazUzi7iF7QwjBr3fsrfQqA@mail.gmail.com>
	<2424890135644695329@unknownmsgid>
Message-ID: <CAEekY67cJEC55rqa_Ns_HoWBU2DZk=gviTPBWQiT8=tF4A4ZZw@mail.gmail.com>

Sorry if I forget some "details" ...


2013/6/6 Michael Palmer <palmertime at gmail.com>

> Are you using iSCSI or NFS?
>

NFS


> How is your zpool configure?
>

12 HDs, SAS WD, 2 GB eatch, 2 are hotspare, Intel SAS controler, Supermicro
Chassis with 16 Sata/SAS Slots, Supermicro dual Opteron with 2 processors,
8 cores eatch, 256 GB of RAM .


> What raid are you using?
>

RaidZ3


> Do you have a zil and/or cache device?
>

one 120 GB Samsung 840PRO


> What hard drives or SSDs are you using and how many of each?
>

just one ...

I am looking this articles :

http://constantin.glez.de/blog/2011/01/my-favorite-oracle-solaris-performance-analysis-commands

http://constantin.glez.de/blog/2010/04/ten-ways-easily-improve-oracle-solaris-zfs-filesystem-performance

And my suspects are going to SSD, too small probably ?!?

Atached disk statistics from napp-it ...


Thanks in advance ...


F?bio Rabelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130606/3cccd784/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: disk.JPG
Type: image/jpeg
Size: 87919 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130606/3cccd784/attachment-0001.jpe>

From richard.elling at richardelling.com  Thu Jun  6 16:05:34 2013
From: richard.elling at richardelling.com (Richard Elling)
Date: Thu, 6 Jun 2013 13:05:34 -0700
Subject: [OmniOS-discuss] statistics
In-Reply-To: <-9131077647197440189@unknownmsgid>
References: <CAEekY67xkFC77Cf+Ksm-3gBjRYsjazUzi7iF7QwjBr3fsrfQqA@mail.gmail.com>
	<-9131077647197440189@unknownmsgid>
Message-ID: <0762E2FA-E733-477E-809F-799309D20F62@RichardElling.com>

On Jun 6, 2013, at 12:34 PM, Michael Palmer <palmertime at gmail.com> wrote:

> I guess the main question was graphical statistics.  Besides buying
> oracle storage I would suggest an network management system like
> opennms.  There are lots of chooses out there but not sure if that is
> the best solution.
> 
> Now for non-graphical,  I would say dtrace.  Google nicstat, zilstat,
> arcsummary.  Also, there is 'zpool iostat -v 1' and 'iostat -x 1'

These tend to be useful for general-purpose bottleneck identification.
But in a storage server situation, you need something that is more specific
to the protocol. Fortunately, there is nfssvrtop and friends:
https://github.com/richardelling/tools

These show the internal latency of serving NFS, iSCSI, and CIFS.
See the preso there to understand where the data is being collected.
 -- richard

> 
> Thanks,
> Michael
> Sent from my iPhone
> 
> On Jun 6, 2013, at 11:26 AM, "F?bio Rabelo" <fabio at fabiorabelo.wiki.br> wrote:
> 
>> Hi to all
>> 
>> First, thanks a lot for the product, it is realy great !
>> 
>> My question now :
>> 
>> Is there any way to make a graphical statsics od ZFS performance ?
>> 
>> I have some botleneck in my sistem ( OminOS V 0.9a9 Nightly mar 04 2013 + Napp-it ) that I can not identify ...
>> 
>> It stores all VMs in a Proxmox Cluster with 5 nodes and 14 mixed VMs ( 3 W2K12 Server, 2 Win7Pro and all others Linux Debian or Ubuntu ) .
>> 
>> There are a 10 GB switcher to interconnect all nodes and Storage .
>> 
>> Almost all aplications are running fine and fast .
>> 
>> The exception are a Debian running Oracle 11G .
>> 
>> I just do not know how to find out what I have to do  ...
>> 
>> 
>> F?bio Rabelo
>> _______________________________________________
>> 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

--

Richard.Elling at RichardElling.com
+1-760-896-4422



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

From fabio at fabiorabelo.wiki.br  Thu Jun  6 16:19:25 2013
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Thu, 6 Jun 2013 17:19:25 -0300
Subject: [OmniOS-discuss] OWC Mercury Accelsior
Message-ID: <CAEekY67n+UsEzegUHdqgnU9A2vBhvmZj64mZzWKBOVPDm=PDNg@mail.gmail.com>

Some one tested one of this babys with OminOS :

http://www.storagereview.com/owc_mercury_accelsior_pcie_ssd_review

Specs are Little sketchy, but mention LSI chipset ...

Thinking about ZIL and/or cache


F?bio Rabelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130606/73e605b6/attachment.html>

From skiselkov.ml at gmail.com  Thu Jun  6 16:52:07 2013
From: skiselkov.ml at gmail.com (Saso Kiselkov)
Date: Thu, 06 Jun 2013 21:52:07 +0100
Subject: [OmniOS-discuss] OWC Mercury Accelsior
In-Reply-To: <CAEekY67n+UsEzegUHdqgnU9A2vBhvmZj64mZzWKBOVPDm=PDNg@mail.gmail.com>
References: <CAEekY67n+UsEzegUHdqgnU9A2vBhvmZj64mZzWKBOVPDm=PDNg@mail.gmail.com>
Message-ID: <51B0F677.5050703@gmail.com>

For to CC the list:

On 06/06/2013 21:19, F?bio Rabelo wrote:
> Some one tested one of this babys with OminOS :
> 
> http://www.storagereview.com/owc_mercury_accelsior_pcie_ssd_review
> 
> Specs are Little sketchy, but mention LSI chipset ...
> 
> Thinking about ZIL and/or cache

PCI-e SSDs are difficult for slog because in case the storage head dies,
you can't fail-over to a backup node. PCIe doesn't support multiple
hosts on the same bus.

Cheers,
-- 
Saso


From reh at hebis.uni-frankfurt.de  Thu Jun  6 18:33:41 2013
From: reh at hebis.uni-frankfurt.de (Uwe Reh)
Date: Fri, 07 Jun 2013 00:33:41 +0200
Subject: [OmniOS-discuss] OWC Mercury Accelsior
In-Reply-To: <CAEekY67n+UsEzegUHdqgnU9A2vBhvmZj64mZzWKBOVPDm=PDNg@mail.gmail.com>
References: <CAEekY67n+UsEzegUHdqgnU9A2vBhvmZj64mZzWKBOVPDm=PDNg@mail.gmail.com>
Message-ID: <51B10E45.80209@hebis.uni-frankfurt.de>

Hi,

I'm using the cheaper but quite comparable OCZ RevoDrive 3 X2 and I like 
it. Building a Lucene index is twice as fast than on 15K SAS drives. 
Unfortunately the card has an unsupported Marvell chip. So I have to 
live with one evil Ubuntu node in my solaris zoo. ;-)

Since I don't have to deal with big data (less than 1T), I decided not 
to do any ZIL or ARC tricks.

Uwe

Am 06.06.2013 22:19, schrieb F?bio Rabelo:
> Some one tested one of this babys with OminOS :
>
> http://www.storagereview.com/owc_mercury_accelsior_pcie_ssd_review
>
> Specs are Little sketchy, but mention LSI chipset ...
>
> Thinking about ZIL and/or cache
>
>
> F?bio Rabelo
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>


From nsmith at careyweb.com  Fri Jun  7 10:22:04 2013
From: nsmith at careyweb.com (Nate Smith)
Date: Fri, 7 Jun 2013 10:22:04 -0400
Subject: [OmniOS-discuss] OWC Mercury Accelsior
In-Reply-To: <51B0F677.5050703@gmail.com>
References: <CAEekY67n+UsEzegUHdqgnU9A2vBhvmZj64mZzWKBOVPDm=PDNg@mail.gmail.com>
	<51B0F677.5050703@gmail.com>
Message-ID: <a2d769e7-891e-445f-b251-b25fa636ef5e@careyweb.com>

Really enjoying the Intel S3700 series.  It seems to be the best mix of enterprise stability (built in capacitors), write endurance, speed, and price.  Working well as a zil.

-----Original Message-----
From: omnios-discuss-bounces at lists.omniti.com [mailto:omnios-discuss-bounces at lists.omniti.com] On Behalf Of Saso Kiselkov
Sent: Thursday, June 06, 2013 4:52 PM
To: F?bio Rabelo
Cc: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] OWC Mercury Accelsior

For to CC the list:

On 06/06/2013 21:19, F?bio Rabelo wrote:
> Some one tested one of this babys with OminOS :
> 
> http://www.storagereview.com/owc_mercury_accelsior_pcie_ssd_review
> 
> Specs are Little sketchy, but mention LSI chipset ...
> 
> Thinking about ZIL and/or cache

PCI-e SSDs are difficult for slog because in case the storage head dies, you can't fail-over to a backup node. PCIe doesn't support multiple hosts on the same bus.

Cheers,
--
Saso

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



From eugen at leitl.org  Fri Jun  7 10:31:55 2013
From: eugen at leitl.org (Eugen Leitl)
Date: Fri, 7 Jun 2013 16:31:55 +0200
Subject: [OmniOS-discuss] OWC Mercury Accelsior
In-Reply-To: <a2d769e7-891e-445f-b251-b25fa636ef5e@careyweb.com>
References: <CAEekY67n+UsEzegUHdqgnU9A2vBhvmZj64mZzWKBOVPDm=PDNg@mail.gmail.com>
	<51B0F677.5050703@gmail.com>
	<a2d769e7-891e-445f-b251-b25fa636ef5e@careyweb.com>
Message-ID: <20130607143155.GG2380@leitl.org>

On Fri, Jun 07, 2013 at 10:22:04AM -0400, Nate Smith wrote:

> Really enjoying the Intel S3700 series.  It seems to be the best mix of
> enterprise stability (built in capacitors), write endurance, speed, and
> price.  Working well as a zil.

Crucial/Micron M500 purportedly comes with a capacitor
http://www.anandtech.com/show/6884/crucial-micron-m500-review-960gb-480gb-240gb-120gb

From robin at smidsrod.no  Fri Jun  7 12:08:57 2013
From: robin at smidsrod.no (=?UTF-8?B?Um9iaW4gU21pZHNyw7hk?=)
Date: Fri, 07 Jun 2013 18:08:57 +0200
Subject: [OmniOS-discuss] statistics
In-Reply-To: <0762E2FA-E733-477E-809F-799309D20F62@RichardElling.com>
References: <CAEekY67xkFC77Cf+Ksm-3gBjRYsjazUzi7iF7QwjBr3fsrfQqA@mail.gmail.com>
	<-9131077647197440189@unknownmsgid>
	<0762E2FA-E733-477E-809F-799309D20F62@RichardElling.com>
Message-ID: <51B20599.5050705@smidsrod.no>

On 06.06.2013 22:05, Richard Elling wrote:
> But in a storage server situation, you need something that is more specific
> to the protocol. Fortunately, there is nfssvrtop and friends:
> https://github.com/richardelling/tools
> 
> These show the internal latency of serving NFS, iSCSI, and CIFS.
> See the preso there to understand where the data is being collected.

Thanks a bunch for posting this link! This is exactly what I also need
to figure out where my iSCSI, CIFS and NFS bottlenecks are.

-- Robin


From henson at acm.org  Fri Jun  7 17:27:10 2013
From: henson at acm.org (Paul B. Henson)
Date: Fri, 07 Jun 2013 14:27:10 -0700
Subject: [OmniOS-discuss] to swap or not to swap
In-Reply-To: <komumk$9mi$1@ger.gmane.org>
References: <51703E4C.6010409@acm.org>
	<alpine.GSO.2.01.1304181401370.13747@freddy.simplesystems.org>
	<CA+QY2RS9ErmH=q313Q4OsWwWuk9d_CbkdB3KyHytPXZTzPoecg@mail.gmail.com>
	<komumk$9mi$1@ger.gmane.org>
Message-ID: <51B2502E.8000002@acm.org>

On 6/5/2013 2:00 AM, Richard PALO wrote:

> Although I can't seem to quickly put my finger on the install script, it
> would be nice if when the swap volume is created that the zfs create
> command specify the blocksize as such :
>
> # zfs create -V 8G -b $(pagesize) rpool/swap
>
> (8G is only an example here)
>
> I noticed 8K default swap blocksize on amd64 instead of 4K, I understand
> 8K is normally for SPARC.

It looks like 4K is still the current recommendation in Solaris 
documentation for creating swap under x86. I'm hoping my swap is very 
rarely used, but still I'd prefer it to be optimal. I'm assuming the 
recommendation is to match the x86 page size of 4K. I guess I'll destroy 
and re-create my swap volume?

Any thoughts on making this the default in the installer?


From omnios at citrus-it.net  Sun Jun  9 15:58:06 2013
From: omnios at citrus-it.net (Andy)
Date: Sun, 9 Jun 2013 19:58:06 +0000 (GMT)
Subject: [OmniOS-discuss] IPMI on Dell R720
In-Reply-To: <alpine.GSO.2.00.1306031812410.17447@areb.pvgehf-vg.arg>
References: <CANXaD7if6DM_Jg_dz38z9xgB6QrhvRwY+eku5DYi0OoNHqnyOQ@mail.gmail.com>
	<alpine.GSO.2.00.1306020858310.4730@areb.pvgehf-vg.arg>
	<CANXaD7it3Yvh=1Zrok3qaK1WNkJqP_vxaD5zL1GGqBzuecoiDw@mail.gmail.com>
	<alpine.GSO.2.00.1306031812410.17447@areb.pvgehf-vg.arg>
Message-ID: <alpine.GSO.2.00.1306091953230.2511@areb.pvgehf-vg.arg>

On Mon, 3 Jun 2013, Andy wrote:

; On Mon, 3 Jun 2013, takashi ary wrote:
;
; ; Hi Andy,
; ;
; ; Thanks for your comments.
; ;
; ; > This is an incompatibility between the version of IPMI tool included
; ; > in OmniOS and the Dell BMC. I haven't looked into exactly what the
; ; > problem is but 1.8.11 works fine so I just downloaded and built my
; ; > own package around that.
; ;
; ; I built 1.8.12 (not 1.8.11) from modified "configure" file as follows.
;
; I just did the same and it works fine for me too. Sorry for the confusion,
; I had assumed that it was the 1.8.12 version that caused the problem once
; it was solved be me downloading and building my own .11.

1.8.12 will not connect to a remote BMC for SOL, 1.8.11 will. Apparently
that's the reason I built a 1.8.11 package for my servers. Now downgraded
again! Not an OmniOS problem unlike the strange ioctl() in the repository
version of ipmitool.

v1.8.11

server1# (7) ipmitool -I lanplus -H server2.l -U root -f /tmp/f power status
Chassis Power is on
server1# (8) ipmitool -I lanplus -H server2.l -U root -f /tmp/f sol activate
Error activating SOL payload: Invalid data field in request

v1.8.12

server1# (9) /opt/ipmitool/bin/ipmitool -I lanplus -H server2.l -U root -f /tmp/f power status
Chassis Power is on
server1# (10) /opt/ipmitool/bin/ipmitool -I lanplus -H server2.l -U root -f /tmp/f sol activate
[SOL Session operational.  Use ~? for help]

Private Data Network - Disconnect IMMEDIATELY if not authorised.

server2 console login: ~. [terminated ipmitool]

-- 
Citrus IT Limited | +44 (0)870 199 8000 | enquiries at citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123


From tobi at oetiker.ch  Mon Jun 10 05:17:04 2013
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Mon, 10 Jun 2013 11:17:04 +0200 (CEST)
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
Message-ID: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>

Folks,

We are trying to implement a fileserver using OmniOS. The customer
has been on Linux until now, but ZFS seems VERY tempting.

The first problem we ran into is that OmniOS seems to limit the
number of groups per user to 16 by default. Setting ngroups_max to
128 in /etc/system seemd to take care of this.

Today we tried to 'go live' and had to abort because the system was
behaving erratically. Users who clearly do belong to a certain
group were refused access to a directory. While other users a
slighly different (larger) set of groups memberships could access
the directory just fine.

we will be happy to take out a support contract with OmniTI if this
will help  us get the system to work as a file server for a user
population with up to 40 group memberships per person.

Below is some 'evidence':
----------------------------------------
elliott at fugu:/share>/bin/uname -a
SunOS fugu 5.11 omnios-d3950d8 i86pc i386 i86pc

----------------------------------------
elliott at fugu:/share>cat /etc/release
  OmniOS v11 r151006
  Copyright 2012-2013 OmniTI Computer Consulting, Inc. All rights
  reserved.
  Use is subject to license terms.

----------------------------------------
elliott at fugu:/share>/bin/id -a
uid=18204(elliott) gid=18904(speag) groups=18904(speag),18900(itis),18901(itis_ad),18906(speag_ad),18907(net_ad),18908(speag_sc),18909(lists),18910(models),18912(zmt),18916(isar_core),18021(support),18023(korea),18026(itis_temp),18030(netstor5_users),18031(netstor4_timemachine),18033(tmc_speag),18917(vpn),18036(netstor5_admin),18046(fugu-admins),18062(sandbox),18075(support-bldg),18076(support-it)

---------------------------------------
elliott at fugu:/share>/bin/ls itis-test
itis-test: Permission denied

---------------------------------------
elliott at fugu:/share>/bin/ls -dlv itis-test
drwxr-x---   2 root     itis           2 Jun 10 09:47 itis-test

0:owner@:list_directory/read_data/add_file/write_data/add_subdirectory
         /append_data/read_xattr/write_xattr/execute/read_attributes
         /write_attributes/read_acl/write_acl/write_owner/synchronize:allow
     1:group@:list_directory/read_data/read_xattr/execute/read_attributes
         /read_acl/synchronize:allow
     2:everyone@:read_xattr/read_attributes/read_acl/synchronize:allow

---------------------------------------
elliott at fugu:/share>/bin/ls -lv itis-admin
itis-admin: Permission denied

---------------------------------------
elliott at fugu:/share>/bin/ls -dlv itis-admin
drwxrws---+  4 root     itis-admin       7 Jun 10 09:05 itis-admin

0:group:fugu-admins:list_directory/read_data/read_xattr/execute
         /read_attributes/read_acl:allow
     1:group:itis:list_directory/read_data/read_xattr/execute/read_attributes
         /read_acl:allow
     2:owner@:list_directory/read_data/add_file/write_data/add_subdirectory
         /append_data/read_xattr/write_xattr/execute/read_attributes
         /write_attributes/read_acl/write_acl/write_owner/synchronize:allow
     3:group@:list_directory/read_data/add_file/write_data/add_subdirectory
         /append_data/read_xattr/execute/read_attributes/read_acl
         /synchronize:allow
     4:everyone@:read_xattr/read_attributes/read_acl/synchronize:allow


-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900



From tobi at oetiker.ch  Mon Jun 10 08:37:30 2013
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Mon, 10 Jun 2013 14:37:30 +0200 (CEST)
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <CAAPGDwJ=Mn5Za=NurdM1eNcH37s13FynHZAE4o+GtR5qD-LBjg@mail.gmail.com>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
	<CAAPGDwJ=Mn5Za=NurdM1eNcH37s13FynHZAE4o+GtR5qD-LBjg@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1306101435560.3317@froburg.oetiker.ch>

Today Ira Cooper wrote:

> Actually, just set ngroups_max to 1024 in /etc/system, there is an outside
> chance of a user having 128 groups in some AD environments.  1024 seems
> less likely.

so you suggest that setting ngroups_max to 128 is bad ? while
setting it to 1024 would be good ? in our setup a single user has
at most 40 groups.

cheers
tobi


-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900

From tobi at oetiker.ch  Mon Jun 10 08:48:51 2013
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Mon, 10 Jun 2013 14:48:51 +0200 (CEST)
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <CAAPGDwK28D-vhGKVLG8FOnXe4zgcV3XRo7nwqnz5hGkgBnj9PQ@mail.gmail.com>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
	<CAAPGDwJ=Mn5Za=NurdM1eNcH37s13FynHZAE4o+GtR5qD-LBjg@mail.gmail.com>
	<alpine.DEB.2.02.1306101435560.3317@froburg.oetiker.ch>
	<CAAPGDwK28D-vhGKVLG8FOnXe4zgcV3XRo7nwqnz5hGkgBnj9PQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1306101447430.19981@froburg.oetiker.ch>

Today Ira Cooper wrote:

> If it works, use it.
>
> I'm merely stating from experience in situations with even more groups, the
> max is 1024, and people may wish to be aware of it / use it.  I personally
> use it just so I don't have to worry about increasing it.  But that's me.

in testing it worked, but as soon as lots of people started using
the system, it started to fail for some of the user accounts ...

cheers
tobi

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900

From tobi at oetiker.ch  Mon Jun 10 05:17:04 2013
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Mon, 10 Jun 2013 11:17:04 +0200 (CEST)
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
Message-ID: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>

Folks,

We are trying to implement a fileserver using OmniOS. The customer
has been on Linux until now, but ZFS seems VERY tempting.

The first problem we ran into is that OmniOS seems to limit the
number of groups per user to 16 by default. Setting ngroups_max to
128 in /etc/system seemd to take care of this.

Today we tried to 'go live' and had to abort because the system was
behaving erratically. Users who clearly do belong to a certain
group were refused access to a directory. While other users a
slighly different (larger) set of groups memberships could access
the directory just fine.

we will be happy to take out a support contract with OmniTI if this
will help  us get the system to work as a file server for a user
population with up to 40 group memberships per person.

Below is some 'evidence':
----------------------------------------
elliott at fugu:/share>/bin/uname -a
SunOS fugu 5.11 omnios-d3950d8 i86pc i386 i86pc

----------------------------------------
elliott at fugu:/share>cat /etc/release
  OmniOS v11 r151006
  Copyright 2012-2013 OmniTI Computer Consulting, Inc. All rights
  reserved.
  Use is subject to license terms.

----------------------------------------
elliott at fugu:/share>/bin/id -a
uid=18204(elliott) gid=18904(speag) groups=18904(speag),18900(itis),18901(itis_ad),18906(speag_ad),18907(net_ad),18908(speag_sc),18909(lists),18910(models),18912(zmt),18916(isar_core),18021(support),18023(korea),18026(itis_temp),18030(netstor5_users),18031(netstor4_timemachine),18033(tmc_speag),18917(vpn),18036(netstor5_admin),18046(fugu-admins),18062(sandbox),18075(support-bldg),18076(support-it)

---------------------------------------
elliott at fugu:/share>/bin/ls itis-test
itis-test: Permission denied

---------------------------------------
elliott at fugu:/share>/bin/ls -dlv itis-test
drwxr-x---   2 root     itis           2 Jun 10 09:47 itis-test

0:owner@:list_directory/read_data/add_file/write_data/add_subdirectory
         /append_data/read_xattr/write_xattr/execute/read_attributes
         /write_attributes/read_acl/write_acl/write_owner/synchronize:allow
     1:group@:list_directory/read_data/read_xattr/execute/read_attributes
         /read_acl/synchronize:allow
     2:everyone@:read_xattr/read_attributes/read_acl/synchronize:allow

---------------------------------------
elliott at fugu:/share>/bin/ls -lv itis-admin
itis-admin: Permission denied

---------------------------------------
elliott at fugu:/share>/bin/ls -dlv itis-admin
drwxrws---+  4 root     itis-admin       7 Jun 10 09:05 itis-admin

0:group:fugu-admins:list_directory/read_data/read_xattr/execute
         /read_attributes/read_acl:allow
     1:group:itis:list_directory/read_data/read_xattr/execute/read_attributes
         /read_acl:allow
     2:owner@:list_directory/read_data/add_file/write_data/add_subdirectory
         /append_data/read_xattr/write_xattr/execute/read_attributes
         /write_attributes/read_acl/write_acl/write_owner/synchronize:allow
     3:group@:list_directory/read_data/add_file/write_data/add_subdirectory
         /append_data/read_xattr/execute/read_attributes/read_acl
         /synchronize:allow
     4:everyone@:read_xattr/read_attributes/read_acl/synchronize:allow


-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900

From tobi at oetiker.ch  Mon Jun 10 16:48:09 2013
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Mon, 10 Jun 2013 22:48:09 +0200 (CEST)
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
Message-ID: <alpine.DEB.2.02.1306102246560.19981@froburg.oetiker.ch>

Today Tobias Oetiker wrote:

> Folks,
>
> We are trying to implement a fileserver using OmniOS. The customer
> has been on Linux until now, but ZFS seems VERY tempting.
>
> The first problem we ran into is that OmniOS seems to limit the
> number of groups per user to 16 by default. Setting ngroups_max to
> 128 in /etc/system seemd to take care of this.
>
> Today we tried to 'go live' and had to abort because the system was
> behaving erratically. Users who clearly do belong to a certain
> group were refused access to a directory. While other users a
> slighly different (larger) set of groups memberships could access
> the directory just fine.
>
> we will be happy to take out a support contract with OmniTI if this
> will help  us get the system to work as a file server for a user
> population with up to 40 group memberships per person.

answering my own question ...

the problem seems to be this

  https://www.illumos.org/issues/3691

and

  https://www.illumos.org/issues/3577

anyone working on this ? seems pretty nasty ...

cheers
tobi

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900

From henson at acm.org  Mon Jun 10 17:23:43 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 10 Jun 2013 14:23:43 -0700
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <alpine.DEB.2.02.1306102246560.19981@froburg.oetiker.ch>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
	<alpine.DEB.2.02.1306102246560.19981@froburg.oetiker.ch>
Message-ID: <51B643DF.8050008@acm.org>

On 6/10/2013 1:48 PM, Tobias Oetiker wrote:

> answering my own question ...
>
> the problem seems to be this
>
>    https://www.illumos.org/issues/3691

I hadn't had a chance to reply to your original message yet, but I had 
this exact problem under S10U10 ? as the ticket says, they switched to a 
binary search for finding groups, but neglected to sort the groups 8-/.

Unfortunately I guess Oracle took their toys home before their fix for 
that found its way into OpenSolaris :(.

I'll take a look at it, but my previous OI-based illumos dev environment 
disappeared on me when we had a SAN failure at work, so I don't 
currently have one. I really don't want to have to build another OI box, 
ideally I'd like to start doing upstream illumos dev work under omnios. 
There's been some talk of supporting that, but there's some base level 
of work that needs to be done first...

I'll check on the illumos dev list, that's a pretty nasty bug, maybe 
somebody's already got a fix for it but hasn't pushed it back yet.


From ira at wakeful.net  Mon Jun 10 17:44:22 2013
From: ira at wakeful.net (Ira Cooper)
Date: Mon, 10 Jun 2013 17:44:22 -0400
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <51B643DF.8050008@acm.org>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
	<alpine.DEB.2.02.1306102246560.19981@froburg.oetiker.ch>
	<51B643DF.8050008@acm.org>
Message-ID: <CAAPGDwLiS=ncSZxVj85FgMoKDae4A-OfBA4vFM6E61-BeuVdig@mail.gmail.com>

On Mon, Jun 10, 2013 at 5:23 PM, Paul B. Henson <henson at acm.org> wrote:

> On 6/10/2013 1:48 PM, Tobias Oetiker wrote:
>
>  answering my own question ...
>>
>> the problem seems to be this
>>
>>    https://www.illumos.org/**issues/3691<https://www.illumos.org/issues/3691>
>>
>
> I hadn't had a chance to reply to your original message yet, but I had
> this exact problem under S10U10 ? as the ticket says, they switched to a
> binary search for finding groups, but neglected to sort the groups 8-/.
>
> Unfortunately I guess Oracle took their toys home before their fix for
> that found its way into OpenSolaris :(.
>
> I'll take a look at it, but my previous OI-based illumos dev environment
> disappeared on me when we had a SAN failure at work, so I don't currently
> have one. I really don't want to have to build another OI box, ideally I'd
> like to start doing upstream illumos dev work under omnios. There's been
> some talk of supporting that, but there's some base level of work that
> needs to be done first...
>
> I'll check on the illumos dev list, that's a pretty nasty bug, maybe
> somebody's already got a fix for it but hasn't pushed it back yet.


If it is the "sort" and you're getting the data from setgroups.  I wrote a
patch for that today, it came up on the samba-technical list.

If it is NFS not doing things right, or other things... that's a whole
'nother ball of wax.  What application is triggering this?

Thanks,

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

From tobi at oetiker.ch  Mon Jun 10 18:25:11 2013
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Tue, 11 Jun 2013 00:25:11 +0200 (CEST)
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <CAAPGDwLiS=ncSZxVj85FgMoKDae4A-OfBA4vFM6E61-BeuVdig@mail.gmail.com>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
	<alpine.DEB.2.02.1306102246560.19981@froburg.oetiker.ch>
	<51B643DF.8050008@acm.org>
	<CAAPGDwLiS=ncSZxVj85FgMoKDae4A-OfBA4vFM6E61-BeuVdig@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1306110022080.19981@froburg.oetiker.ch>

Ira,

Yesterday Ira Cooper wrote:

> On Mon, Jun 10, 2013 at 5:23 PM, Paul B. Henson <henson at acm.org> wrote:
>
> > On 6/10/2013 1:48 PM, Tobias Oetiker wrote:
> >
> >  answering my own question ...
> >>
> >> the problem seems to be this
> >>
> >>    https://www.illumos.org/**issues/3691<https://www.illumos.org/issues/3691>
> >>
> >
> > I hadn't had a chance to reply to your original message yet, but I had
> > this exact problem under S10U10 ? as the ticket says, they switched to a
> > binary search for finding groups, but neglected to sort the groups 8-/.
> >
> > Unfortunately I guess Oracle took their toys home before their fix for
> > that found its way into OpenSolaris :(.
> >
> > I'll take a look at it, but my previous OI-based illumos dev environment
> > disappeared on me when we had a SAN failure at work, so I don't currently
> > have one. I really don't want to have to build another OI box, ideally I'd
> > like to start doing upstream illumos dev work under omnios. There's been
> > some talk of supporting that, but there's some base level of work that
> > needs to be done first...
> >
> > I'll check on the illumos dev list, that's a pretty nasty bug, maybe
> > somebody's already got a fix for it but hasn't pushed it back yet.
>
>
> If it is the "sort" and you're getting the data from setgroups.  I wrote a
> patch for that today, it came up on the samba-technical list.

no external application required ... (look at my original post). It
all can be reproduced directly on zfs using standard unix
command-line tools simply create a user with more than 16 group
memberships and then create one directory for each group and try to
access it ... for some of the directories you will get access
denied ...

cheers
tobi

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900

From henson at acm.org  Mon Jun 10 18:42:03 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 10 Jun 2013 15:42:03 -0700
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <CAAPGDwLiS=ncSZxVj85FgMoKDae4A-OfBA4vFM6E61-BeuVdig@mail.gmail.com>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
	<alpine.DEB.2.02.1306102246560.19981@froburg.oetiker.ch>
	<51B643DF.8050008@acm.org>
	<CAAPGDwLiS=ncSZxVj85FgMoKDae4A-OfBA4vFM6E61-BeuVdig@mail.gmail.com>
Message-ID: <51B6563B.7070501@acm.org>

On 6/10/2013 2:44 PM, Ira Cooper wrote:

> If it is the "sort" and you're getting the data from setgroups.  I wrote
> a patch for that today, it came up on the samba-technical list.
>
> If it is NFS not doing things right, or other things... that's a whole
> 'nother ball of wax.  What application is triggering this?

It's really an underlying issue in the base OS; you can work around it 
for a particular application by overriding the setgroups libc call to 
make it sort the groups before setting them (I actually did that for 
samba under S10), but the root cause fix needs to be in the OS to 
account for cases such as over NFS where you don't really have a way to 
get in between the OS and the group list.



From henson at acm.org  Mon Jun 10 19:37:50 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 10 Jun 2013 16:37:50 -0700
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <CAAPGDwJTtVHVf3K=FAiWX+YFoDupVsALJ25Xph5FEQTqK3MUQA@mail.gmail.com>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
	<alpine.DEB.2.02.1306102246560.19981@froburg.oetiker.ch>
	<51B643DF.8050008@acm.org>
	<CAAPGDwLiS=ncSZxVj85FgMoKDae4A-OfBA4vFM6E61-BeuVdig@mail.gmail.com>
	<51B6563B.7070501@acm.org>
	<CAAPGDwJTtVHVf3K=FAiWX+YFoDupVsALJ25Xph5FEQTqK3MUQA@mail.gmail.com>
Message-ID: <51B6634E.2070305@acm.org>

On 6/10/2013 4:01 PM, Ira Cooper wrote:

> I patched in it illumos.
>
> And it passes the tests.  But I wouldn't assume it fixes NFS.
>
> Fixing one path of error, doesn't mean all paths are fixed.

The error in this case is one part of the code doing a binary search 
(assuming the group list is sorted), and another part of the code 
setting the group list without sorting it.

In any case, let's follow up on the thread on the illumos dev list 
rather than having two separate ones :).


From johan.kragsterman at capvert.se  Tue Jun 11 07:14:05 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Tue, 11 Jun 2013 13:14:05 +0200
Subject: [OmniOS-discuss] KVM & virtio
Message-ID: <OF08983E7B.90BEA5EB-ONC1257B87.003DB709-C1257B87.003DB70D@inse.com>

Hi!

I'm going to start to work with KVM on OmniOS now, and I googled around for possibilities to use virtio as disk=if instead of ide, but I don't find much. Much of what I find is complaining about bad performance on OpenIndiana.

Anyone can enlighten me about the issue/situation...?

Rgrds Johan


From ira at wakeful.net  Mon Jun 10 19:01:50 2013
From: ira at wakeful.net (Ira Cooper)
Date: Mon, 10 Jun 2013 19:01:50 -0400
Subject: [OmniOS-discuss] group membership trouble (ngroups_max)
In-Reply-To: <51B6563B.7070501@acm.org>
References: <alpine.DEB.2.02.1306101105380.3317@froburg.oetiker.ch>
	<alpine.DEB.2.02.1306102246560.19981@froburg.oetiker.ch>
	<51B643DF.8050008@acm.org>
	<CAAPGDwLiS=ncSZxVj85FgMoKDae4A-OfBA4vFM6E61-BeuVdig@mail.gmail.com>
	<51B6563B.7070501@acm.org>
Message-ID: <CAAPGDwJTtVHVf3K=FAiWX+YFoDupVsALJ25Xph5FEQTqK3MUQA@mail.gmail.com>

On Mon, Jun 10, 2013 at 6:42 PM, Paul B. Henson <henson at acm.org> wrote:

> On 6/10/2013 2:44 PM, Ira Cooper wrote:
>
>  If it is the "sort" and you're getting the data from setgroups.  I wrote
>> a patch for that today, it came up on the samba-technical list.
>>
>> If it is NFS not doing things right, or other things... that's a whole
>> 'nother ball of wax.  What application is triggering this?
>>
>
> It's really an underlying issue in the base OS; you can work around it for
> a particular application by overriding the setgroups libc call to make it
> sort the groups before setting them (I actually did that for samba under
> S10), but the root cause fix needs to be in the OS to account for cases
> such as over NFS where you don't really have a way to get in between the OS
> and the group list.
>

Umnn...

I patched in it illumos.

And it passes the tests.  But I wouldn't assume it fixes NFS.

Fixing one path of error, doesn't mean all paths are fixed.

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

From esproul at omniti.com  Tue Jun 11 09:52:29 2013
From: esproul at omniti.com (Eric Sproul)
Date: Tue, 11 Jun 2013 09:52:29 -0400
Subject: [OmniOS-discuss] KVM & virtio
In-Reply-To: <OF08983E7B.90BEA5EB-ONC1257B87.003DB709-C1257B87.003DB70D@inse.com>
References: <OF08983E7B.90BEA5EB-ONC1257B87.003DB709-C1257B87.003DB70D@inse.com>
Message-ID: <CA+QY2RQQ+Q9KkV6g4Y4ohESP1nzoc+t_5a0zK7OHLD1GJqT9=A@mail.gmail.com>

Johan,
We run many Linux KVM guests with virtio both for net (model=virtio)
and drive (if=virtio).  None of our use cases call for extreme
performance, but what we've seen is certainly adequate.

Eric

On Tue, Jun 11, 2013 at 7:14 AM, Johan Kragsterman
<johan.kragsterman at capvert.se> wrote:
> Hi!
>
> I'm going to start to work with KVM on OmniOS now, and I googled around for possibilities to use virtio as disk=if instead of ide, but I don't find much. Much of what I find is complaining about bad performance on OpenIndiana.
>
> Anyone can enlighten me about the issue/situation...?
>
> Rgrds Johan
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From esproul at omniti.com  Tue Jun 11 13:47:19 2013
From: esproul at omniti.com (Eric Sproul)
Date: Tue, 11 Jun 2013 13:47:19 -0400
Subject: [OmniOS-discuss] KVM & virtio
In-Reply-To: <OFFD91793D.1E44E8D0-ONC1257B87.005CD515-C1257B87.005CD519@inse.com>
References: <OF08983E7B.90BEA5EB-ONC1257B87.003DB709-C1257B87.003DB70D@inse.com>
	<CA+QY2RQQ+Q9KkV6g4Y4ohESP1nzoc+t_5a0zK7OHLD1GJqT9=A@mail.gmail.com>
	<OFFD91793D.1E44E8D0-ONC1257B87.005CD515-C1257B87.005CD519@inse.com>
Message-ID: <CA+QY2RRGnOQmhdv8MCxsLSD0y7FUBd9ddXdeR834oRz=ZiLV7Q@mail.gmail.com>

On Tue, Jun 11, 2013 at 12:53 PM, Johan Kragsterman
<johan.kragsterman at capvert.se> wrote:
> Thanks, Eric, we tried it with a ubuntu, and it went actually smooth, can't believe it, first time right away!
>
> We will do some tests and see how we can let SMF manage start and stop, I saw someone on the web did that.
>
> But right now, how in the f--k do I start and stop the VM? Stop it is of coarse no probs, but how do I start it again?
>

Have a look at http://omnios.omniti.com/wiki.php/VirtualMachinesKVM
for ideas.  Basically you start a VM by calling
/usr/bin/qemu-system-x86_64 with all the appropriate arguments.
Typically folks will encapsulate that in a script of some sort to make
it easier to manage.  I've just added a sample SMF manifest to that
wiki page.

Eric

From ramquick at gmail.com  Wed Jun 12 06:36:37 2013
From: ramquick at gmail.com (Ram Chander)
Date: Wed, 12 Jun 2013 16:06:37 +0530
Subject: [OmniOS-discuss] Boot failure
Message-ID: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>

Hi,


All of a sudden Omni box crashed and after reboot it halts at below error
wtihout coming up.
Any way to fix other than reclone ?  Thanks.


Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
svc:/system/early-manifest-import:default exited with status 1

Enter user name for system maintenance (control-d to bypass):


Regards,
Ram
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130612/1c4a1100/attachment.html>

From fabio at fabiorabelo.wiki.br  Wed Jun 12 08:07:41 2013
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Wed, 12 Jun 2013 09:07:41 -0300
Subject: [OmniOS-discuss] Supermicro board with LSI 2008
Message-ID: <CAEekY65TKBMHtwhPTAksbmfuHzKSnkv=U7b0s6-H9m8+ojiR8w@mail.gmail.com>

Hi to all

Did someone tested any recent Supermicro motherboard with "Integrated LSI
200" SAS ?

Like this :

http://www.supermicro.com/Aplus/motherboard/Opteron6000/SR56x0/H8DG6-F.cfm

http://www.supermicro.com/Aplus/motherboard/Opteron4000/SR56x0/H8DCL-6F.cfm

http://www.supermicro.com/products/motherboard/Xeon/C600/X9DR7-TF_.cfm

This LSI 2008 works with OminOS as it comes, ?

Or it needs some firmware change ??

Thanks in advance ...


F?bio Rabelo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130612/f0485c85/attachment.html>

From skiselkov.ml at gmail.com  Wed Jun 12 08:12:16 2013
From: skiselkov.ml at gmail.com (Saso Kiselkov)
Date: Wed, 12 Jun 2013 13:12:16 +0100
Subject: [OmniOS-discuss] Supermicro board with LSI 2008
In-Reply-To: <CAEekY65TKBMHtwhPTAksbmfuHzKSnkv=U7b0s6-H9m8+ojiR8w@mail.gmail.com>
References: <CAEekY65TKBMHtwhPTAksbmfuHzKSnkv=U7b0s6-H9m8+ojiR8w@mail.gmail.com>
Message-ID: <51B865A0.3020407@gmail.com>

On 12/06/2013 13:07, F?bio Rabelo wrote:
> Hi to all
> 
> Did someone tested any recent Supermicro motherboard with "Integrated
> LSI 200" SAS ?
> 
> Like this :
> 
> http://www.supermicro.com/Aplus/motherboard/Opteron6000/SR56x0/H8DG6-F.cfm
> 
> http://www.supermicro.com/Aplus/motherboard/Opteron4000/SR56x0/H8DCL-6F.cfm
> 
> http://www.supermicro.com/products/motherboard/Xeon/C600/X9DR7-TF_.cfm
> 
> This LSI 2008 works with OminOS as it comes, ?

I didn't test any of the boards, but the LSI SAS2008 chip is supported
and should support JBOD.

Cheers,
-- 
Saso

From jesus at omniti.com  Wed Jun 12 08:44:28 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 12 Jun 2013 08:44:28 -0400
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
Message-ID: <CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>

You're going to have to start by logging in as root and poking around.


On Wed, Jun 12, 2013 at 6:36 AM, Ram Chander <ramquick at gmail.com> wrote:

> Hi,
>
>
> All of a sudden Omni box crashed and after reboot it halts at below error
> wtihout coming up.
> Any way to fix other than reclone ?  Thanks.
>
>
> Requesting System Maintenance Mode
> (See /lib/svc/share/README for more information.)
> svc:/system/early-manifest-import:default exited with status 1
>
> Enter user name for system maintenance (control-d to bypass):
>
>
> Regards,
> Ram
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>


-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130612/61b66868/attachment.html>

From ramquick at gmail.com  Wed Jun 12 09:24:21 2013
From: ramquick at gmail.com (Ram Chander)
Date: Wed, 12 Jun 2013 18:54:21 +0530
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
	<CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
Message-ID: <CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>

No luck on logging in. Filesystem not mounted, no logs/dmesg.   Just stuck


On Wed, Jun 12, 2013 at 6:14 PM, Theo Schlossnagle <jesus at omniti.com> wrote:

> You're going to have to start by logging in as root and poking around.
>
>
> On Wed, Jun 12, 2013 at 6:36 AM, Ram Chander <ramquick at gmail.com> wrote:
>
>> Hi,
>>
>>
>> All of a sudden Omni box crashed and after reboot it halts at below error
>> wtihout coming up.
>> Any way to fix other than reclone ?  Thanks.
>>
>>
>> Requesting System Maintenance Mode
>> (See /lib/svc/share/README for more information.)
>> svc:/system/early-manifest-import:default exited with status 1
>>
>> Enter user name for system maintenance (control-d to bypass):
>>
>>
>> Regards,
>> Ram
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>>
>
>
> --
>
> Theo Schlossnagle
>
> http://omniti.com/is/theo-schlossnagle
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss 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/20130612/95421557/attachment.html>

From esproul at omniti.com  Wed Jun 12 09:25:20 2013
From: esproul at omniti.com (Eric Sproul)
Date: Wed, 12 Jun 2013 09:25:20 -0400
Subject: [OmniOS-discuss] Supermicro board with LSI 2008
In-Reply-To: <CAEekY65TKBMHtwhPTAksbmfuHzKSnkv=U7b0s6-H9m8+ojiR8w@mail.gmail.com>
References: <CAEekY65TKBMHtwhPTAksbmfuHzKSnkv=U7b0s6-H9m8+ojiR8w@mail.gmail.com>
Message-ID: <CA+QY2RRUBSH0Ahy0TUayKA6jLkrz0U=-HRNBPAUUGcnGxXvvBQ@mail.gmail.com>

On Wed, Jun 12, 2013 at 8:07 AM, F?bio Rabelo <fabio at fabiorabelo.wiki.br> wrote:
> This LSI 2008 works with OminOS as it comes, ?
>
> Or it needs some firmware change ??

The LSI 2008 is supported by either mr_sas(7D) or mpt_sas(7D),
depending on the firmware.  The default on most Supermicro boards (and
LSI HBAs in general) is "IR", or RAID-mode, firmware.  This is what
mr_sas attaches to.  If you re-flash the chip with "IT", or non-RAID
mode, firmware, then mpt_sas will attach.  There are a couple of SKUs
that Supermicro ships that already have IT firmware in the onboard SAS
chip.  The SKUs end in "-JBOD" and they use the 2308, not the 2008,
but mpt_sas is still the driver that supports it.

http://www.supermicro.com/products/motherboard/Xeon/C600/X9DR7-LN4F-JBOD.cfm
http://www.supermicro.com/products/motherboard/Xeon/C600/X9DRD-7LN4F-JBOD.cfm

These are known informally to the community as the "ZFS Special".  :)

Even if you opt for one of the other boards with a 2008 chip, you
should still be able to find IT firmware bundles on Supermicro's FTP
site.

Eric

From jesus at omniti.com  Wed Jun 12 10:05:04 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 12 Jun 2013 10:05:04 -0400
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
	<CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
	<CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>
Message-ID: <CACLsApshTEe8kcZynoGP54eTog=V45TtoNuf36YpYDYQuwUCjw@mail.gmail.com>

You could try booting Firefly and figuring out what's wrong with the host:

http://alexeremin.blogspot.com/2013/05/firefly-failsafe-image-for-illumos.html


On Wed, Jun 12, 2013 at 9:24 AM, Ram Chander <ramquick at gmail.com> wrote:

> No luck on logging in. Filesystem not mounted, no logs/dmesg.   Just stuck
>
>
> On Wed, Jun 12, 2013 at 6:14 PM, Theo Schlossnagle <jesus at omniti.com>wrote:
>
>> You're going to have to start by logging in as root and poking around.
>>
>>
>> On Wed, Jun 12, 2013 at 6:36 AM, Ram Chander <ramquick at gmail.com> wrote:
>>
>>> Hi,
>>>
>>>
>>> All of a sudden Omni box crashed and after reboot it halts at below
>>> error wtihout coming up.
>>> Any way to fix other than reclone ?  Thanks.
>>>
>>>
>>> Requesting System Maintenance Mode
>>> (See /lib/svc/share/README for more information.)
>>> svc:/system/early-manifest-import:default exited with status 1
>>>
>>> Enter user name for system maintenance (control-d to bypass):
>>>
>>>
>>> Regards,
>>> Ram
>>>
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>>
>>>
>>
>>
>> --
>>
>> Theo Schlossnagle
>>
>> http://omniti.com/is/theo-schlossnagle
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>>
>


-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130612/b56c0aa6/attachment-0001.html>

From fabio at fabiorabelo.wiki.br  Wed Jun 12 10:09:00 2013
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Wed, 12 Jun 2013 11:09:00 -0300
Subject: [OmniOS-discuss] Supermicro board with LSI 2008
In-Reply-To: <CA+QY2RRUBSH0Ahy0TUayKA6jLkrz0U=-HRNBPAUUGcnGxXvvBQ@mail.gmail.com>
References: <CAEekY65TKBMHtwhPTAksbmfuHzKSnkv=U7b0s6-H9m8+ojiR8w@mail.gmail.com>
	<CA+QY2RRUBSH0Ahy0TUayKA6jLkrz0U=-HRNBPAUUGcnGxXvvBQ@mail.gmail.com>
Message-ID: <CAEekY665E-sXYKwZsUPcXP2sB4auCcoE3_ucxo0KX5ydJWp2_A@mail.gmail.com>

Yes, I found it :

ftp://ftp.supermicro.com/Driver/SAS/LSI/

So, after I flash this controllers with IT firmware, it works like IBM 1015
?!?

And, thanks a lot ...


F?bio Rabelo


2013/6/12 Eric Sproul <esproul at omniti.com>

> On Wed, Jun 12, 2013 at 8:07 AM, F?bio Rabelo <fabio at fabiorabelo.wiki.br>
> wrote:
> > This LSI 2008 works with OminOS as it comes, ?
> >
> > Or it needs some firmware change ??
>
> The LSI 2008 is supported by either mr_sas(7D) or mpt_sas(7D),
> depending on the firmware.  The default on most Supermicro boards (and
> LSI HBAs in general) is "IR", or RAID-mode, firmware.  This is what
> mr_sas attaches to.  If you re-flash the chip with "IT", or non-RAID
> mode, firmware, then mpt_sas will attach.  There are a couple of SKUs
> that Supermicro ships that already have IT firmware in the onboard SAS
> chip.  The SKUs end in "-JBOD" and they use the 2308, not the 2008,
> but mpt_sas is still the driver that supports it.
>
>
> http://www.supermicro.com/products/motherboard/Xeon/C600/X9DR7-LN4F-JBOD.cfm
>
> http://www.supermicro.com/products/motherboard/Xeon/C600/X9DRD-7LN4F-JBOD.cfm
>
> These are known informally to the community as the "ZFS Special".  :)
>
> Even if you opt for one of the other boards with a 2008 chip, you
> should still be able to find IT firmware bundles on Supermicro's FTP
> site.
>
> Eric
> _______________________________________________
> 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/20130612/b63b05d2/attachment.html>

From henson at acm.org  Wed Jun 12 15:04:47 2013
From: henson at acm.org (Paul B. Henson)
Date: Wed, 12 Jun 2013 12:04:47 -0700
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <CACLsApshTEe8kcZynoGP54eTog=V45TtoNuf36YpYDYQuwUCjw@mail.gmail.com>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
	<CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
	<CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>
	<CACLsApshTEe8kcZynoGP54eTog=V45TtoNuf36YpYDYQuwUCjw@mail.gmail.com>
Message-ID: <51B8C64F.507@acm.org>

On 6/12/2013 7:05 AM, Theo Schlossnagle wrote:
> You could try booting Firefly and figuring out what's wrong with the host:
>
> http://alexeremin.blogspot.com/2013/05/firefly-failsafe-image-for-illumos.html

Cool; I'll have to make a note of that, that could be useful in the future.

Have there been any thoughts on restoring the failsafe boot option in 
grub that Solaris has and be able to do a recovery boot without needing 
other media (and one that uses the same versions as you currently have 
installed, rather than a third party ISO that might not match your 
system)? Unfortunately I'm not that familiar with the methodology, but 
it seems you'd just have to generate the equivalent of 
/boot/x86.miniroot-safe for omnios? Would that be a distribution level 
thing, or an upstream illumos thing?


From jesus at omniti.com  Wed Jun 12 15:23:10 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 12 Jun 2013 15:23:10 -0400
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <51B8C64F.507@acm.org>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
	<CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
	<CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>
	<CACLsApshTEe8kcZynoGP54eTog=V45TtoNuf36YpYDYQuwUCjw@mail.gmail.com>
	<51B8C64F.507@acm.org>
Message-ID: <CACLsApt6Jt+3qqZGn-DdwLNScgCdOPwGENP5mZwLsA4m4bH0HA@mail.gmail.com>

Distribution level, though upstream could provide some basics.

Patches welcome on that! I think having a failsafe built-in would be super.


On Wed, Jun 12, 2013 at 3:04 PM, Paul B. Henson <henson at acm.org> wrote:

> On 6/12/2013 7:05 AM, Theo Schlossnagle wrote:
>
>> You could try booting Firefly and figuring out what's wrong with the host:
>>
>> http://alexeremin.blogspot.**com/2013/05/firefly-failsafe-**
>> image-for-illumos.html<http://alexeremin.blogspot.com/2013/05/firefly-failsafe-image-for-illumos.html>
>>
>
> Cool; I'll have to make a note of that, that could be useful in the future.
>
> Have there been any thoughts on restoring the failsafe boot option in grub
> that Solaris has and be able to do a recovery boot without needing other
> media (and one that uses the same versions as you currently have installed,
> rather than a third party ISO that might not match your system)?
> Unfortunately I'm not that familiar with the methodology, but it seems
> you'd just have to generate the equivalent of /boot/x86.miniroot-safe for
> omnios? Would that be a distribution level thing, or an upstream illumos
> thing?
>
>
> ______________________________**_________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.**com <OmniOS-discuss at lists.omniti.com>
> http://lists.omniti.com/**mailman/listinfo/omnios-**discuss<http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>



-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130612/57508030/attachment.html>

From henson at acm.org  Wed Jun 12 15:39:53 2013
From: henson at acm.org (Paul B. Henson)
Date: Wed, 12 Jun 2013 12:39:53 -0700
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <CACLsApt6Jt+3qqZGn-DdwLNScgCdOPwGENP5mZwLsA4m4bH0HA@mail.gmail.com>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
	<CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
	<CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>
	<CACLsApshTEe8kcZynoGP54eTog=V45TtoNuf36YpYDYQuwUCjw@mail.gmail.com>
	<51B8C64F.507@acm.org>
	<CACLsApt6Jt+3qqZGn-DdwLNScgCdOPwGENP5mZwLsA4m4bH0HA@mail.gmail.com>
Message-ID: <51B8CE89.7070904@acm.org>

On 6/12/2013 12:23 PM, Theo Schlossnagle wrote:
> Distribution level, though upstream could provide some basics.
>
> Patches welcome on that! I think having a failsafe built-in would be super.

I'll add it to my (growing) list of things to look at once I get an 
illumos dev box going again?

Out of curiosity, what are you using for your illumos development? I've 
seen you post various webrevs on the dev list, do you have a separate 
OpenIndiana box for that, or have you shoehorned illumos development 
onto omnios? I'd prefer to use omnios, but based on the last discussion 
on the dev list it can't currently compile illumos successfully. If 
you've got workarounds for that I'd be interested in trying them :).

Thanks?


From jesus at omniti.com  Wed Jun 12 15:42:09 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 12 Jun 2013 15:42:09 -0400
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <51B8CE89.7070904@acm.org>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
	<CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
	<CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>
	<CACLsApshTEe8kcZynoGP54eTog=V45TtoNuf36YpYDYQuwUCjw@mail.gmail.com>
	<51B8C64F.507@acm.org>
	<CACLsApt6Jt+3qqZGn-DdwLNScgCdOPwGENP5mZwLsA4m4bH0HA@mail.gmail.com>
	<51B8CE89.7070904@acm.org>
Message-ID: <CACLsApuuw_oK18kPmmXkLNEWxdrWrk202U8qw6z1EijDF84FBA@mail.gmail.com>

I do my development on illumos-omnios.  It is so remarkably close to
illumos-gate that I even generate my webrevs from the "upstream" branch of
that (which is illumos-gate master).  If it doesn't something that hasn't
changed between the two, I leave it at that.  If there's a questions, I'll
ask someone with an OI box to build it.


On Wed, Jun 12, 2013 at 3:39 PM, Paul B. Henson <henson at acm.org> wrote:

> On 6/12/2013 12:23 PM, Theo Schlossnagle wrote:
>
>> Distribution level, though upstream could provide some basics.
>>
>> Patches welcome on that! I think having a failsafe built-in would be
>> super.
>>
>
> I'll add it to my (growing) list of things to look at once I get an
> illumos dev box going again?
>
> Out of curiosity, what are you using for your illumos development? I've
> seen you post various webrevs on the dev list, do you have a separate
> OpenIndiana box for that, or have you shoehorned illumos development onto
> omnios? I'd prefer to use omnios, but based on the last discussion on the
> dev list it can't currently compile illumos successfully. If you've got
> workarounds for that I'd be interested in trying them :).
>
> Thanks?
>
>


-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130612/447a3c24/attachment.html>

From henson at acm.org  Wed Jun 12 20:41:46 2013
From: henson at acm.org (Paul B. Henson)
Date: Wed, 12 Jun 2013 17:41:46 -0700
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <CACLsApuuw_oK18kPmmXkLNEWxdrWrk202U8qw6z1EijDF84FBA@mail.gmail.com>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
	<CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
	<CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>
	<CACLsApshTEe8kcZynoGP54eTog=V45TtoNuf36YpYDYQuwUCjw@mail.gmail.com>
	<51B8C64F.507@acm.org>
	<CACLsApt6Jt+3qqZGn-DdwLNScgCdOPwGENP5mZwLsA4m4bH0HA@mail.gmail.com>
	<51B8CE89.7070904@acm.org>
	<CACLsApuuw_oK18kPmmXkLNEWxdrWrk202U8qw6z1EijDF84FBA@mail.gmail.com>
Message-ID: <51B9154A.70401@acm.org>

On 6/12/2013 12:42 PM, Theo Schlossnagle wrote:
> I do my development on illumos-omnios.  It is so remarkably close to
> illumos-gate that I even generate my webrevs from the "upstream" branch
> of that (which is illumos-gate master).  If it doesn't something that
> hasn't changed between the two, I leave it at that.  If there's a
> questions, I'll ask someone with an OI box to build it.

Cool, I took a quick look through

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

and that seems a lot simpler than what I remember doing to get my OI box 
to work :).

I'll give it a try, thanks.

Did I misunderstand Garrett when he said there were a couple of 
components of illumos-gate that simply wouldn't compile under omnios, or 
does omnios-build just skip them?

From jesus at omniti.com  Wed Jun 12 22:15:27 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Wed, 12 Jun 2013 22:15:27 -0400
Subject: [OmniOS-discuss] Boot failure
In-Reply-To: <51B9154A.70401@acm.org>
References: <CAMRGQbPsAiz99OO1yEEzq4Ucf2UfF-5Lq3R7H15DX67UiQAWvQ@mail.gmail.com>
	<CACLsApuON5d1=ywW7THdtRvDUaciEs-uUtWmqE8muiP8jEPhqw@mail.gmail.com>
	<CAMRGQbMK7o0OXj9beymRTd0y9FOokvntCg4k+MG4Pwh332c+Ag@mail.gmail.com>
	<CACLsApshTEe8kcZynoGP54eTog=V45TtoNuf36YpYDYQuwUCjw@mail.gmail.com>
	<51B8C64F.507@acm.org>
	<CACLsApt6Jt+3qqZGn-DdwLNScgCdOPwGENP5mZwLsA4m4bH0HA@mail.gmail.com>
	<51B8CE89.7070904@acm.org>
	<CACLsApuuw_oK18kPmmXkLNEWxdrWrk202U8qw6z1EijDF84FBA@mail.gmail.com>
	<51B9154A.70401@acm.org>
Message-ID: <CACLsApvcGkNsHXJasVDz0ZzpChG4ep96bauvhObG201Gqi2a8A@mail.gmail.com>

We build illumos-omnios, not illumos-gate. They are close, but Garrett is
correct.
On Jun 12, 2013 8:41 PM, "Paul B. Henson" <henson at acm.org> wrote:

> On 6/12/2013 12:42 PM, Theo Schlossnagle wrote:
>
>> I do my development on illumos-omnios.  It is so remarkably close to
>> illumos-gate that I even generate my webrevs from the "upstream" branch
>> of that (which is illumos-gate master).  If it doesn't something that
>> hasn't changed between the two, I leave it at that.  If there's a
>> questions, I'll ask someone with an OI box to build it.
>>
>
> Cool, I took a quick look through
>
> http://omnios.omniti.com/wiki.**php/BuildInstructions<http://omnios.omniti.com/wiki.php/BuildInstructions>
>
> and that seems a lot simpler than what I remember doing to get my OI box
> to work :).
>
> I'll give it a try, thanks.
>
> Did I misunderstand Garrett when he said there were a couple of components
> of illumos-gate that simply wouldn't compile under omnios, or does
> omnios-build just skip them?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130612/6d762516/attachment.html>

From daleg at omniti.com  Thu Jun 13 12:14:26 2013
From: daleg at omniti.com (Dale Ghent)
Date: Thu, 13 Jun 2013 12:14:26 -0400
Subject: [OmniOS-discuss] New system/zones/brand/ipkg package released
Message-ID: <24624653-6CC1-46B6-9FE3-2919432C7378@omniti.com>


A update to system/zones/brand/ipkg was released today which addresses the zone cloning issues detailed in http://omnios.omniti.com/ticket.php/11

If you've been vexed by this problem, here's your fix. 

http://pkg.omniti.com/omnios/release/info/0/pkg%3A%2F%2Fomnios%2Fsystem%2Fzones%2Fbrand%2Fipkg%400.5.11%2C5.11-0.151006%3A20130613T155331Z

/dale

From esproul at omniti.com  Thu Jun 13 13:29:15 2013
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 13 Jun 2013 13:29:15 -0400
Subject: [OmniOS-discuss] Updated release: r151006g
Message-ID: <CA+QY2RSsDUKudzR1n4gjYyoS5GbM1jy0dOhUhoGjbig1zt7kzA@mail.gmail.com>

Weekly release r151006g fixes zone cloning and updates pci.ids:

http://omnios.omniti.com/wiki.php/ReleaseNotes#r151006g

From rafibeyli at gmail.com  Fri Jun 14 03:08:43 2013
From: rafibeyli at gmail.com (Hafiz Rafibeyli)
Date: Fri, 14 Jun 2013 10:08:43 +0300 (EEST)
Subject: [OmniOS-discuss] SLC SSD  connected via SAS expander
In-Reply-To: <16997037.4794025.1371192667048.JavaMail.root@cantekstil.com.tr>
Message-ID: <27086425.4794979.1371193723429.JavaMail.root@cantekstil.com.tr>

Hello ,i'm running omnios(d3950d8) as a NAS  base with napp-it,

hardware is Supermicro SC846E26-R1200B+LSI SAS 9211-8i HBA(IT mode enabled with last firmware)

everything working great,but i'm getting errors with my Intel SLC SSD 32GB(zil log).

SLC SSD connected to system backplane  via supermicro 2,5 to 3,5 converter.

I read somewhere Intel's SLC SSD not supported when  connected via SAS expander,anyway to solve this problem?

messages from /var/adm/messages

Jun 14 10:03:45 canomnios scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:03:45 canomnios 	Disconnected command timeout for Target 16
Jun 14 10:03:45 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:03:45 canomnios 	Log info 0x31140000 received for target 16.
Jun 14 10:03:45 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
Jun 14 10:03:45 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:03:45 canomnios 	Log info 0x31140000 received for target 16.
Jun 14 10:03:45 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
Jun 14 10:06:15 canomnios scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:06:15 canomnios 	Disconnected command timeout for Target 16
Jun 14 10:06:15 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
Jun 14 10:06:15 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc



From skiselkov.ml at gmail.com  Fri Jun 14 03:27:55 2013
From: skiselkov.ml at gmail.com (Saso Kiselkov)
Date: Fri, 14 Jun 2013 08:27:55 +0100
Subject: [OmniOS-discuss] SLC SSD  connected via SAS expander
In-Reply-To: <27086425.4794979.1371193723429.JavaMail.root@cantekstil.com.tr>
References: <27086425.4794979.1371193723429.JavaMail.root@cantekstil.com.tr>
Message-ID: <51BAC5FB.2090001@gmail.com>

On 14/06/2013 08:08, Hafiz Rafibeyli wrote:
> Hello ,i'm running omnios(d3950d8) as a NAS  base with napp-it,
> 
> hardware is Supermicro SC846E26-R1200B+LSI SAS 9211-8i HBA(IT mode enabled with last firmware)
> [..snip..]
> Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc

If it's a SATA SSD, I'd recommend attaching it via a SAS interposer
(AOC-LSISS9252). Running the SATA over a SAS backplane is just asking
for trouble (without one I've had expander lockups necessitating a full
powercycle of the machine). You may need to do some drilling and
mechanical adjustments of your 2.5-to-3.5 adapter plates in order to
accommodate the interposer, but it can be done.

Cheers,
-- 
Saso

From rafibeyli at gmail.com  Fri Jun 14 14:50:21 2013
From: rafibeyli at gmail.com (Hafiz Rafibeyli)
Date: Fri, 14 Jun 2013 21:50:21 +0300 (EEST)
Subject: [OmniOS-discuss] OmniOS-discuss Digest, Vol 15, Issue 17
In-Reply-To: <mailman.1.1371225601.2558.omnios-discuss@lists.omniti.com>
Message-ID: <26531237.4810669.1371235821740.JavaMail.root@cantekstil.com.tr>

Saso thank you for help,

yes SSD is Sata(Intel X25-E Series 32 GB),i will look for LSI interposer,

I have also Intel 520 Series 120 GB Sata SSD for Read Cache(L2ARC),but they work with SAS expander without any problem.

regards

Hafiz





----- Orijinal Mesaj -----
Kimden: omnios-discuss-request at lists.omniti.com
Kime: omnios-discuss at lists.omniti.com
G?nderilenler: 14 Haziran Cuma 2013 19:00:01
Konu: OmniOS-discuss Digest, Vol 15, Issue 17

Send OmniOS-discuss mailing list submissions to
	omnios-discuss at lists.omniti.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.omniti.com/mailman/listinfo/omnios-discuss
or, via email, send a message with subject or body 'help' to
	omnios-discuss-request at lists.omniti.com

You can reach the person managing the list at
	omnios-discuss-owner at lists.omniti.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of OmniOS-discuss digest..."


Today's Topics:

   1. New system/zones/brand/ipkg package released (Dale Ghent)
   2. Updated release: r151006g (Eric Sproul)
   3. SLC SSD  connected via SAS expander (Hafiz Rafibeyli)
   4. Re: SLC SSD  connected via SAS expander (Saso Kiselkov)


----------------------------------------------------------------------

Message: 1
Date: Thu, 13 Jun 2013 12:14:26 -0400
From: Dale Ghent <daleg at omniti.com>
To: "omnios-discuss at lists.omniti.com"
	<omnios-discuss at lists.omniti.com>
Subject: [OmniOS-discuss] New system/zones/brand/ipkg package released
Message-ID: <24624653-6CC1-46B6-9FE3-2919432C7378 at omniti.com>
Content-Type: text/plain; charset=us-ascii


A update to system/zones/brand/ipkg was released today which addresses the zone cloning issues detailed in http://omnios.omniti.com/ticket.php/11

If you've been vexed by this problem, here's your fix. 

http://pkg.omniti.com/omnios/release/info/0/pkg%3A%2F%2Fomnios%2Fsystem%2Fzones%2Fbrand%2Fipkg%400.5.11%2C5.11-0.151006%3A20130613T155331Z

/dale

------------------------------

Message: 2
Date: Thu, 13 Jun 2013 13:29:15 -0400
From: Eric Sproul <esproul at omniti.com>
To: omnios-discuss <omnios-discuss at lists.omniti.com>
Subject: [OmniOS-discuss] Updated release: r151006g
Message-ID:
	<CA+QY2RSsDUKudzR1n4gjYyoS5GbM1jy0dOhUhoGjbig1zt7kzA at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Weekly release r151006g fixes zone cloning and updates pci.ids:

http://omnios.omniti.com/wiki.php/ReleaseNotes#r151006g


------------------------------

Message: 3
Date: Fri, 14 Jun 2013 10:08:43 +0300 (EEST)
From: Hafiz Rafibeyli <rafibeyli at gmail.com>
To: omnios-discuss at lists.omniti.com
Subject: [OmniOS-discuss] SLC SSD  connected via SAS expander
Message-ID:
	<27086425.4794979.1371193723429.JavaMail.root at cantekstil.com.tr>
Content-Type: text/plain; charset=windows-1254

Hello ,i'm running omnios(d3950d8) as a NAS  base with napp-it,

hardware is Supermicro SC846E26-R1200B+LSI SAS 9211-8i HBA(IT mode enabled with last firmware)

everything working great,but i'm getting errors with my Intel SLC SSD 32GB(zil log).

SLC SSD connected to system backplane  via supermicro 2,5 to 3,5 converter.

I read somewhere Intel's SLC SSD not supported when  connected via SAS expander,anyway to solve this problem?

messages from /var/adm/messages

Jun 14 10:03:45 canomnios scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:03:45 canomnios 	Disconnected command timeout for Target 16
Jun 14 10:03:45 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:03:45 canomnios 	Log info 0x31140000 received for target 16.
Jun 14 10:03:45 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
Jun 14 10:03:45 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:03:45 canomnios 	Log info 0x31140000 received for target 16.
Jun 14 10:03:45 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
Jun 14 10:06:15 canomnios scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:06:15 canomnios 	Disconnected command timeout for Target 16
Jun 14 10:06:15 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
Jun 14 10:06:15 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc




------------------------------

Message: 4
Date: Fri, 14 Jun 2013 08:27:55 +0100
From: Saso Kiselkov <skiselkov.ml at gmail.com>
To: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] SLC SSD  connected via SAS expander
Message-ID: <51BAC5FB.2090001 at gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On 14/06/2013 08:08, Hafiz Rafibeyli wrote:
> Hello ,i'm running omnios(d3950d8) as a NAS  base with napp-it,
> 
> hardware is Supermicro SC846E26-R1200B+LSI SAS 9211-8i HBA(IT mode enabled with last firmware)
> [..snip..]
> Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc

If it's a SATA SSD, I'd recommend attaching it via a SAS interposer
(AOC-LSISS9252). Running the SATA over a SAS backplane is just asking
for trouble (without one I've had expander lockups necessitating a full
powercycle of the machine). You may need to do some drilling and
mechanical adjustments of your 2.5-to-3.5 adapter plates in order to
accommodate the interposer, but it can be done.

Cheers,
-- 
Saso


------------------------------

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


End of OmniOS-discuss Digest, Vol 15, Issue 17
**********************************************



From richard.elling at richardelling.com  Fri Jun 14 16:47:03 2013
From: richard.elling at richardelling.com (Richard Elling)
Date: Fri, 14 Jun 2013 13:47:03 -0700
Subject: [OmniOS-discuss] SLC SSD  connected via SAS expander
In-Reply-To: <27086425.4794979.1371193723429.JavaMail.root@cantekstil.com.tr>
References: <27086425.4794979.1371193723429.JavaMail.root@cantekstil.com.tr>
Message-ID: <5FAA178C-9904-45A8-83F3-4347AD18A16A@RichardElling.com>

On Jun 14, 2013, at 12:08 AM, Hafiz Rafibeyli <rafibeyli at gmail.com> wrote:

> Hello ,i'm running omnios(d3950d8) as a NAS  base with napp-it,
> 
> hardware is Supermicro SC846E26-R1200B+LSI SAS 9211-8i HBA(IT mode enabled with last firmware)
> 
> everything working great,but i'm getting errors with my Intel SLC SSD 32GB(zil log).
> 
> SLC SSD connected to system backplane  via supermicro 2,5 to 3,5 converter.
> 
> I read somewhere Intel's SLC SSD not supported when  connected via SAS expander,anyway to solve this problem?

It is not an SLC SSD issue. More likely, it is a SATA issue. Since we don't know the 
model of SSD, it can be hard to say for sure.

> 
> messages from /var/adm/messages

These are the result of the disk being reset. The timeout happens, the disk is reset and
any in-flight operations are aborted (can decode this from the ioc_status). Ultimately,
you will need to replace the SSD, though it may be possible to upgrade the SSD firmware
as some older Intel SATA SSDs had some firmware fixes available.

> 
> Jun 14 10:03:45 canomnios scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:03:45 canomnios 	Disconnected command timeout for Target 16

command timed out, reset sent...

> Jun 14 10:03:45 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:03:45 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:03:45 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
> Jun 14 10:03:45 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:03:45 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:03:45 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc

... two I/Os were aborted by the disk.

> Jun 14 10:06:15 canomnios scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:06:15 canomnios 	Disconnected command timeout for Target 16

rinse, repeat

> Jun 14 10:06:15 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
> Jun 14 10:06:15 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc

The reason people suggest using a SATA/SAS interposer instead of STP for these cases
is because we have experienced cases where the reset/recovery can take out everything
on the expander. There is a lot of proprietary firmware in the mix: HBAs, expanders, and 
disks. Mixing native SAS with STP just adds to the complexity and unintended consequences
can result. By using a SATA/SAS interposer, you can eliminate STP from the mix and keep
the protocol translation confined to one SAS target.
 -- richard

--

Richard.Elling at RichardElling.com
+1-760-896-4422



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

From richard.elling at richardelling.com  Fri Jun 14 16:53:11 2013
From: richard.elling at richardelling.com (Richard Elling)
Date: Fri, 14 Jun 2013 13:53:11 -0700
Subject: [OmniOS-discuss] OmniOS-discuss Digest, Vol 15, Issue 17
In-Reply-To: <26531237.4810669.1371235821740.JavaMail.root@cantekstil.com.tr>
References: <26531237.4810669.1371235821740.JavaMail.root@cantekstil.com.tr>
Message-ID: <1EAA6691-6FFC-48ED-9062-43BD0EF79C5C@RichardElling.com>


On Jun 14, 2013, at 11:50 AM, Hafiz Rafibeyli <rafibeyli at gmail.com> wrote:

> Saso thank you for help,
> 
> yes SSD is Sata(Intel X25-E Series 32 GB),i will look for LSI interposer,

There was a firmware change between the X25-E gen1 and gen2 that also enters
the equation. The older SSDs were particularly susceptible to problems that 
ultimately cause a timeout/reset.
 -- richard

> 
> I have also Intel 520 Series 120 GB Sata SSD for Read Cache(L2ARC),but they work with SAS expander without any problem.
> 
> regards
> 
> Hafiz
> 
> 
> 
> 
> 
> ----- Orijinal Mesaj -----
> Kimden: omnios-discuss-request at lists.omniti.com
> Kime: omnios-discuss at lists.omniti.com
> G?nderilenler: 14 Haziran Cuma 2013 19:00:01
> Konu: OmniOS-discuss Digest, Vol 15, Issue 17
> 
> Send OmniOS-discuss mailing list submissions to
> 	omnios-discuss at lists.omniti.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.omniti.com/mailman/listinfo/omnios-discuss
> or, via email, send a message with subject or body 'help' to
> 	omnios-discuss-request at lists.omniti.com
> 
> You can reach the person managing the list at
> 	omnios-discuss-owner at lists.omniti.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OmniOS-discuss digest..."
> 
> 
> Today's Topics:
> 
>   1. New system/zones/brand/ipkg package released (Dale Ghent)
>   2. Updated release: r151006g (Eric Sproul)
>   3. SLC SSD  connected via SAS expander (Hafiz Rafibeyli)
>   4. Re: SLC SSD  connected via SAS expander (Saso Kiselkov)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Thu, 13 Jun 2013 12:14:26 -0400
> From: Dale Ghent <daleg at omniti.com>
> To: "omnios-discuss at lists.omniti.com"
> 	<omnios-discuss at lists.omniti.com>
> Subject: [OmniOS-discuss] New system/zones/brand/ipkg package released
> Message-ID: <24624653-6CC1-46B6-9FE3-2919432C7378 at omniti.com>
> Content-Type: text/plain; charset=us-ascii
> 
> 
> A update to system/zones/brand/ipkg was released today which addresses the zone cloning issues detailed in http://omnios.omniti.com/ticket.php/11
> 
> If you've been vexed by this problem, here's your fix. 
> 
> http://pkg.omniti.com/omnios/release/info/0/pkg%3A%2F%2Fomnios%2Fsystem%2Fzones%2Fbrand%2Fipkg%400.5.11%2C5.11-0.151006%3A20130613T155331Z
> 
> /dale
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 13 Jun 2013 13:29:15 -0400
> From: Eric Sproul <esproul at omniti.com>
> To: omnios-discuss <omnios-discuss at lists.omniti.com>
> Subject: [OmniOS-discuss] Updated release: r151006g
> Message-ID:
> 	<CA+QY2RSsDUKudzR1n4gjYyoS5GbM1jy0dOhUhoGjbig1zt7kzA at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Weekly release r151006g fixes zone cloning and updates pci.ids:
> 
> http://omnios.omniti.com/wiki.php/ReleaseNotes#r151006g
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Fri, 14 Jun 2013 10:08:43 +0300 (EEST)
> From: Hafiz Rafibeyli <rafibeyli at gmail.com>
> To: omnios-discuss at lists.omniti.com
> Subject: [OmniOS-discuss] SLC SSD  connected via SAS expander
> Message-ID:
> 	<27086425.4794979.1371193723429.JavaMail.root at cantekstil.com.tr>
> Content-Type: text/plain; charset=windows-1254
> 
> Hello ,i'm running omnios(d3950d8) as a NAS  base with napp-it,
> 
> hardware is Supermicro SC846E26-R1200B+LSI SAS 9211-8i HBA(IT mode enabled with last firmware)
> 
> everything working great,but i'm getting errors with my Intel SLC SSD 32GB(zil log).
> 
> SLC SSD connected to system backplane  via supermicro 2,5 to 3,5 converter.
> 
> I read somewhere Intel's SLC SSD not supported when  connected via SAS expander,anyway to solve this problem?
> 
> messages from /var/adm/messages
> 
> Jun 14 10:03:45 canomnios scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:03:45 canomnios 	Disconnected command timeout for Target 16
> Jun 14 10:03:45 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:03:45 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:03:45 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
> Jun 14 10:03:45 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:03:45 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:03:45 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
> Jun 14 10:06:15 canomnios scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:06:15 canomnios 	Disconnected command timeout for Target 16
> Jun 14 10:06:15 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
> Jun 14 10:06:15 canomnios scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,340e at 7/pci1000,3020 at 0 (mpt_sas0):
> Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
> Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Fri, 14 Jun 2013 08:27:55 +0100
> From: Saso Kiselkov <skiselkov.ml at gmail.com>
> To: omnios-discuss at lists.omniti.com
> Subject: Re: [OmniOS-discuss] SLC SSD  connected via SAS expander
> Message-ID: <51BAC5FB.2090001 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On 14/06/2013 08:08, Hafiz Rafibeyli wrote:
>> Hello ,i'm running omnios(d3950d8) as a NAS  base with napp-it,
>> 
>> hardware is Supermicro SC846E26-R1200B+LSI SAS 9211-8i HBA(IT mode enabled with last firmware)
>> [..snip..]
>> Jun 14 10:06:15 canomnios 	Log info 0x31140000 received for target 16.
>> Jun 14 10:06:15 canomnios 	scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
> 
> If it's a SATA SSD, I'd recommend attaching it via a SAS interposer
> (AOC-LSISS9252). Running the SATA over a SAS backplane is just asking
> for trouble (without one I've had expander lockups necessitating a full
> powercycle of the machine). You may need to do some drilling and
> mechanical adjustments of your 2.5-to-3.5 adapter plates in order to
> accommodate the interposer, but it can be done.
> 
> Cheers,
> -- 
> Saso
> 
> 
> ------------------------------
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
> 
> End of OmniOS-discuss Digest, Vol 15, Issue 17
> **********************************************
> 
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

--

Richard.Elling at RichardElling.com
+1-760-896-4422



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

From henson at acm.org  Fri Jun 14 19:02:23 2013
From: henson at acm.org (Paul B. Henson)
Date: Fri, 14 Jun 2013 16:02:23 -0700
Subject: [OmniOS-discuss] Building illumos-omnios
Message-ID: <51BBA0FF.6030003@acm.org>

I'm trying to get set up to do some forward development on illumos-gate 
(using Theo's method of working with illumos-omnios).

I checked out the stable branch of omnios-build (as the master branch 
doesn't work with stable, and as this isn't omnios distribution 
development, I'd prefer to do it under stable). I then checked out by 
hand the master branch of illumos-omnios (rather than letting 
omnios-build automatically check out the corresponding stable branch), 
and did a test build.

For the most part, it seemed to work well; with the exception of the 
following errors:

==== package build errors (non-DEBUG) ====

dmake: Warning: Command failed for target 
`packages.i386/developer-dtrace.dep'
dmake: Warning: Command failed for target 
`packages.i386/service-network-dns-mdns.dep'
dmake: Warning: Command failed for target 
`packages.i386/system-boot-network.dep'
dmake: Warning: Target `install' not remade because of errors


==== Validating manifests against proto area ====

Entries present in manifests but not proto area:
         file NOHASH group=other mode=0644 owner=root 
path=usr/share/lib/java/javadoc/
dnssd/api/resources/background.gif
         file NOHASH group=other mode=0644 owner=root 
path=usr/share/lib/java/javadoc/
dnssd/api/resources/tab.gif
         file NOHASH group=other mode=0644 owner=root 
path=usr/share/lib/java/javadoc/
dnssd/api/resources/titlebar.gif
         file NOHASH group=other mode=0644 owner=root 
path=usr/share/lib/java/javadoc/
dnssd/api/resources/titlebar_end.gif
         file NOHASH group=other mode=0644 owner=root 
path=usr/share/lib/java/javadoc/
dtrace/api/resources/background.gif
         file NOHASH group=other mode=0644 owner=root 
path=usr/share/lib/java/javadoc/dtrace/api/resources/tab.gif
         file NOHASH group=other mode=0644 owner=root 
path=usr/share/lib/java/javadoc/dtrace/api/resources/titlebar.gif
         file NOHASH group=other mode=0644 owner=root 
path=usr/share/lib/java/javadoc/dtrace/api/resources/titlebar_end.gif

Entries present in proto area but not manifests:
         file usr/share/lib/java/javadoc/dnssd/api/resources/inherit.gif 
group=group mode=0644 owner=owner 
path=usr/share/lib/java/javadoc/dnssd/api/resources/inherit.gif
         file 
usr/share/lib/java/javadoc/dtrace/api/resources/inherit.gif group=group 
mode=0644 owner=owner 
path=usr/share/lib/java/javadoc/dtrace/api/resources/inherit.gif



It looks like the problems are related per the nightly log:

Generating dependencies for developer-dtrace.mog
Couldn't find 
'usr/share/lib/java/javadoc/dtrace/api/resources/background.gif' in any
  of the specified search directories:
         /code/omnios-151006/illumos-omnios/proto/root_i386-nd


Is this a known issue? Did I do something wrong? Is this from the cross 
pollination of stable omnios-build and master illumos-omnios?

Thanks?

From daleg at omniti.com  Sun Jun 16 23:00:25 2013
From: daleg at omniti.com (Dale Ghent)
Date: Sun, 16 Jun 2013 23:00:25 -0400
Subject: [OmniOS-discuss] Building illumos-omnios
In-Reply-To: <51BBA0FF.6030003@acm.org>
References: <51BBA0FF.6030003@acm.org>
Message-ID: <3AC91EF9-42B2-4A9F-8F65-B400E62F361B@omniti.com>


Are you not building this on Bloody?

Building the master branch requires Bloody - and now even moreso because openjdk 7 replaced Sun JDK 6 in Bloody recently, and illumos-omnios had to be adjusted to match - which is what your errors are related to.

/dale

On Jun 14, 2013, at 7:02 PM, "Paul B. Henson" <henson at acm.org> wrote:

> I'm trying to get set up to do some forward development on illumos-gate (using Theo's method of working with illumos-omnios).
> 
> I checked out the stable branch of omnios-build (as the master branch doesn't work with stable, and as this isn't omnios distribution development, I'd prefer to do it under stable). I then checked out by hand the master branch of illumos-omnios (rather than letting omnios-build automatically check out the corresponding stable branch), and did a test build.
> 
> For the most part, it seemed to work well; with the exception of the following errors:
> 
> ==== package build errors (non-DEBUG) ====
> 
> dmake: Warning: Command failed for target `packages.i386/developer-dtrace.dep'
> dmake: Warning: Command failed for target `packages.i386/service-network-dns-mdns.dep'
> dmake: Warning: Command failed for target `packages.i386/system-boot-network.dep'
> dmake: Warning: Target `install' not remade because of errors
> 
> 
> ==== Validating manifests against proto area ====
> 
> Entries present in manifests but not proto area:
>        file NOHASH group=other mode=0644 owner=root path=usr/share/lib/java/javadoc/
> dnssd/api/resources/background.gif
>        file NOHASH group=other mode=0644 owner=root path=usr/share/lib/java/javadoc/
> dnssd/api/resources/tab.gif
>        file NOHASH group=other mode=0644 owner=root path=usr/share/lib/java/javadoc/
> dnssd/api/resources/titlebar.gif
>        file NOHASH group=other mode=0644 owner=root path=usr/share/lib/java/javadoc/
> dnssd/api/resources/titlebar_end.gif
>        file NOHASH group=other mode=0644 owner=root path=usr/share/lib/java/javadoc/
> dtrace/api/resources/background.gif
>        file NOHASH group=other mode=0644 owner=root path=usr/share/lib/java/javadoc/dtrace/api/resources/tab.gif
>        file NOHASH group=other mode=0644 owner=root path=usr/share/lib/java/javadoc/dtrace/api/resources/titlebar.gif
>        file NOHASH group=other mode=0644 owner=root path=usr/share/lib/java/javadoc/dtrace/api/resources/titlebar_end.gif
> 
> Entries present in proto area but not manifests:
>        file usr/share/lib/java/javadoc/dnssd/api/resources/inherit.gif group=group mode=0644 owner=owner path=usr/share/lib/java/javadoc/dnssd/api/resources/inherit.gif
>        file usr/share/lib/java/javadoc/dtrace/api/resources/inherit.gif group=group mode=0644 owner=owner path=usr/share/lib/java/javadoc/dtrace/api/resources/inherit.gif
> 
> 
> 
> It looks like the problems are related per the nightly log:
> 
> Generating dependencies for developer-dtrace.mog
> Couldn't find 'usr/share/lib/java/javadoc/dtrace/api/resources/background.gif' in any
> of the specified search directories:
>        /code/omnios-151006/illumos-omnios/proto/root_i386-nd
> 
> 
> Is this a known issue? Did I do something wrong? Is this from the cross pollination of stable omnios-build and master illumos-omnios?
> 
> Thanks?
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From cnehren at omniti.com  Fri Jun 14 19:51:11 2013
From: cnehren at omniti.com (Chris Nehren)
Date: Fri, 14 Jun 2013 19:51:11 -0400
Subject: [OmniOS-discuss] Building illumos-omnios
In-Reply-To: <51BBA0FF.6030003@acm.org>
References: <51BBA0FF.6030003@acm.org>
Message-ID: <20130614235110.GM9700@eschaton.local>

On Fri, Jun 14, 2013 at 16:02:23 -0700 , Paul B. Henson wrote:
> I'm trying to get set up to do some forward development on illumos-gate 
> (using Theo's method of working with illumos-omnios).
> 
> I checked out the stable branch of omnios-build (as the master branch 
> doesn't work with stable, and as this isn't omnios distribution 
> development, I'd prefer to do it under stable). I then checked out by 
> hand the master branch of illumos-omnios (rather than letting 
> omnios-build automatically check out the corresponding stable branch), 
> and did a test build.
>
> [snip]
> 
> Is this a known issue? Did I do something wrong? Is this from the cross 
> pollination of stable omnios-build and master illumos-omnios?

Quite probably. You'll want to match the version you're running with the
version you're building. Check the branches in the repo you checked
out--you should see e.g. r151004, r151006. Check out the one you're
running on and try building again.

-- 
Chris Nehren

From garrett at damore.org  Mon Jun 17 05:23:03 2013
From: garrett at damore.org (Garrett D'Amore)
Date: Mon, 17 Jun 2013 13:23:03 +0400
Subject: [OmniOS-discuss] Python 2.7?
Message-ID: <535051A8-3C58-4378-B8F2-C6B4075DDF14@icloud.com>

Not sure if this is asked (new here, didn't see it in the archives); am thinking about switching to OmniOS for hosting our own build infrastructure (we use OI for now), and would be especially keen to know if Python 2.7 is available?  We've got a bunch of python code that makes use of 2.7 features not available in 2.6 (or at least not the version of 2.6 in OI), so having it available natively would be a very nice thing indeed.

	- Garrett


From esproul at omniti.com  Mon Jun 17 09:55:09 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 17 Jun 2013 09:55:09 -0400
Subject: [OmniOS-discuss] Python 2.7?
In-Reply-To: <535051A8-3C58-4378-B8F2-C6B4075DDF14@icloud.com>
References: <535051A8-3C58-4378-B8F2-C6B4075DDF14@icloud.com>
Message-ID: <CA+QY2RT=w-Z=te1ghEY+c=LKoUWOya46B3uSGVPdZhYHzAxuvQ@mail.gmail.com>

Hi Garrett,
We don't yet have python 2.7 builds.  It likely won't appear in the
OmniOS core unless/until illumos-gate requires it.  It's more likely
that it would appear in the ms.omniti.com repo (the one we use for our
own managed services platform).  Our "layer cake" approach to package
delivery is well-suited to this sort of add-on; you could take a look
at http://omnios.omniti.com/wiki.php/Packaging and the template branch
of omnios-build:
https://github.com/omniti-labs/omnios-build/tree/template

Pulling in the existing 2.6 build script would be a good starting
point for a 2.7 build.  We're happy to help if need be.

Eric

On Mon, Jun 17, 2013 at 5:23 AM, Garrett D'Amore <garrett at damore.org> wrote:
> Not sure if this is asked (new here, didn't see it in the archives); am thinking about switching to OmniOS for hosting our own build infrastructure (we use OI for now), and would be especially keen to know if Python 2.7 is available?  We've got a bunch of python code that makes use of 2.7 features not available in 2.6 (or at least not the version of 2.6 in OI), so having it available natively would be a very nice thing indeed.
>
>         - Garrett
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From garrett.damore at dey-sys.com  Mon Jun 17 13:42:10 2013
From: garrett.damore at dey-sys.com (Garrett D'Amore)
Date: Mon, 17 Jun 2013 21:42:10 +0400
Subject: [OmniOS-discuss] Python 2.7?
In-Reply-To: <CA+QY2RT=w-Z=te1ghEY+c=LKoUWOya46B3uSGVPdZhYHzAxuvQ@mail.gmail.com>
References: <535051A8-3C58-4378-B8F2-C6B4075DDF14@icloud.com>
	<CA+QY2RT=w-Z=te1ghEY+c=LKoUWOya46B3uSGVPdZhYHzAxuvQ@mail.gmail.com>
Message-ID: <CAEE760B-BBD6-454D-927C-105D0938DCB1@dey-sys.com>

I will look.  I'm not particular about how this appears but it would make my life easier if I could easily get it on the install. I don't particularly like any further python burdens on illumos though. 

Sent from my iPhone

On Jun 17, 2013, at 5:55 PM, Eric Sproul <esproul at omniti.com> wrote:

> Hi Garrett,
> We don't yet have python 2.7 builds.  It likely won't appear in the
> OmniOS core unless/until illumos-gate requires it.  It's more likely
> that it would appear in the ms.omniti.com repo (the one we use for our
> own managed services platform).  Our "layer cake" approach to package
> delivery is well-suited to this sort of add-on; you could take a look
> at http://omnios.omniti.com/wiki.php/Packaging and the template branch
> of omnios-build:
> https://github.com/omniti-labs/omnios-build/tree/template
> 
> Pulling in the existing 2.6 build script would be a good starting
> point for a 2.7 build.  We're happy to help if need be.
> 
> Eric
> 
> On Mon, Jun 17, 2013 at 5:23 AM, Garrett D'Amore <garrett at damore.org> wrote:
>> Not sure if this is asked (new here, didn't see it in the archives); am thinking about switching to OmniOS for hosting our own build infrastructure (we use OI for now), and would be especially keen to know if Python 2.7 is available?  We've got a bunch of python code that makes use of 2.7 features not available in 2.6 (or at least not the version of 2.6 in OI), so having it available natively would be a very nice thing indeed.
>> 
>>        - Garrett
>> 
>> _______________________________________________
>> 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 henson at acm.org  Mon Jun 17 15:00:53 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 17 Jun 2013 12:00:53 -0700
Subject: [OmniOS-discuss] Building illumos-omnios
In-Reply-To: <3AC91EF9-42B2-4A9F-8F65-B400E62F361B@omniti.com>
References: <51BBA0FF.6030003@acm.org>
	<3AC91EF9-42B2-4A9F-8F65-B400E62F361B@omniti.com>
Message-ID: <51BF5CE5.6000509@acm.org>

On 6/16/2013 8:00 PM, Dale Ghent wrote:

> Are you not building this on Bloody?

No; if I were developing omnios itself, I probably would be. But at the 
moment I'm trying to leverage omnios as a development platform for 
upstream illumos-gate work, and I'd prefer a stable system for that as 
opposed to dealing with any quirks that might pop up in bloody. As 
illumos-gate won't currently compile under omnios, I was going to try 
Theo's method of doing upstream work based on illumos-omnios and see how 
it worked out.

> Building the master branch requires Bloody - and now even moreso
> because openjdk 7 replaced Sun JDK 6 in Bloody recently, and
> illumos-omnios had to be adjusted to match - which is what your
> errors are related to.

At this point it looks like I'll either have to try bloody for upstream 
development, convince illumos-dev to go ahead and drop those bits of the 
gate that won't compile under omnios so I can use illumos-gate directly 
rather than illumos-omnios, or give up and just build another OI box <sigh>?

Thanks?


From henson at acm.org  Mon Jun 17 15:04:12 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 17 Jun 2013 12:04:12 -0700
Subject: [OmniOS-discuss] Building illumos-omnios
In-Reply-To: <20130614235110.GM9700@eschaton.local>
References: <51BBA0FF.6030003@acm.org> <20130614235110.GM9700@eschaton.local>
Message-ID: <51BF5DAC.9010908@acm.org>

On 6/14/2013 4:51 PM, Chris Nehren wrote:

>> Is this a known issue? Did I do something wrong? Is this from the cross
>> pollination of stable omnios-build and master illumos-omnios?
>
> Quite probably. You'll want to match the version you're running with the
> version you're building. Check the branches in the repo you checked
> out--you should see e.g. r151004, r151006. Check out the one you're
> running on and try building again.

Unfortunately, working with the stable branch of illumos-onmnios isn't 
going to meet my needs, as it is surely already or will be soon too far 
out of sync with upstream illumos-gate to be a good basis for working on 
changes to that.

I guess I'll probably just have to build another OI box until someday 
illumos-gate supports building under omnios or there's another purpose 
built reference platform for illumos development.

Thanks?



From henson at acm.org  Mon Jun 17 15:06:06 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 17 Jun 2013 12:06:06 -0700
Subject: [OmniOS-discuss] Python 2.7?
In-Reply-To: <535051A8-3C58-4378-B8F2-C6B4075DDF14@icloud.com>
References: <535051A8-3C58-4378-B8F2-C6B4075DDF14@icloud.com>
Message-ID: <51BF5E1E.6010509@acm.org>

On 6/17/2013 2:23 AM, Garrett D'Amore wrote:
> Not sure if this is asked (new here, didn't see it in the archives);
> am thinking about switching to OmniOS for hosting our own build
> infrastructure (we use OI for now)

So I'm assuming you guys ripped out the parts of illumos-gate that won't 
compile on omnios for your internal fork, just like omniti did with 
illumos-omnios? Sure would be nice to get those changes into 
illumos-gate itself, too bad there's such a political nightmare about 
doing so?

From garrett.damore at dey-sys.com  Mon Jun 17 15:47:58 2013
From: garrett.damore at dey-sys.com (Garrett D'Amore)
Date: Mon, 17 Jun 2013 23:47:58 +0400
Subject: [OmniOS-discuss] Building illumos-omnios
In-Reply-To: <51BF5DAC.9010908@acm.org>
References: <51BBA0FF.6030003@acm.org> <20130614235110.GM9700@eschaton.local>
	<51BF5DAC.9010908@acm.org>
Message-ID: <4A9DA71D-F08B-4494-BAA8-93BD7F3B72B7@dey-sys.com>

Is it possible to work on illumos for upstream?  I figured it was impossible to build illumos on omnios (it used to be) because of dependencies in illumos gate that omnios has reasonably removed.  If that situation has changed, I'll be very happy indeed.  

	- Garrett

On Jun 17, 2013, at 11:04 PM, Paul B. Henson <henson at acm.org> wrote:

> On 6/14/2013 4:51 PM, Chris Nehren wrote:
> 
>>> Is this a known issue? Did I do something wrong? Is this from the cross
>>> pollination of stable omnios-build and master illumos-omnios?
>> 
>> Quite probably. You'll want to match the version you're running with the
>> version you're building. Check the branches in the repo you checked
>> out--you should see e.g. r151004, r151006. Check out the one you're
>> running on and try building again.
> 
> Unfortunately, working with the stable branch of illumos-onmnios isn't going to meet my needs, as it is surely already or will be soon too far out of sync with upstream illumos-gate to be a good basis for working on changes to that.
> 
> I guess I'll probably just have to build another OI box until someday illumos-gate supports building under omnios or there's another purpose built reference platform for illumos development.
> 
> Thanks?
> 
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From henson at acm.org  Mon Jun 17 15:58:25 2013
From: henson at acm.org (Paul B. Henson)
Date: Mon, 17 Jun 2013 12:58:25 -0700
Subject: [OmniOS-discuss] Building illumos-omnios
In-Reply-To: <4A9DA71D-F08B-4494-BAA8-93BD7F3B72B7@dey-sys.com>
References: <51BBA0FF.6030003@acm.org> <20130614235110.GM9700@eschaton.local>
	<51BF5DAC.9010908@acm.org>
	<4A9DA71D-F08B-4494-BAA8-93BD7F3B72B7@dey-sys.com>
Message-ID: <51BF6A61.9080105@acm.org>

On 6/17/2013 12:47 PM, Garrett D'Amore wrote:
> Is it possible to work on illumos for upstream?  I figured it was
> impossible to build illumos on omnios (it used to be) because of
> dependencies in illumos gate that omnios has reasonably removed.  If
> that situation has changed, I'll be very happy indeed.

My understanding is that it is still impossible to build illumos-gate 
under omnios.

However, the illumos-omnios fork is very close to illumos-gate, and Theo 
says he actually does most of his illumos-gate upstream development 
using illumos-omnios. I was going to give that a try, but it looks like 
I would have to run the unstable development version of omnios in order 
to compile the head of illumos-omnios, which I'd rather not do as I'd 
prefer not to run into potential omnios issues while trying to do 
illumos development.

I guess I'll probably end up spinning up another OI box, which is kind 
of annoying and somewhat of a deterrent <sigh> 8-/.

I was saying it would kind of be nice if the pieces dropped in 
illumos-omnios could also be dropped in illumos-gate, allowing 
illumos-gate itself to be directly compiled with omnios. But I don't 
think I want to pick up the torch to try to make that happen myself ;).

From johan.kragsterman at capvert.se  Tue Jun 18 01:35:06 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Tue, 18 Jun 2013 07:35:06 +0200
Subject: [OmniOS-discuss] Pfsense KVM guest complaining about DAD ipv6
Message-ID: <OF79EAEB09.13F0F55B-ONC1257B8E.001EAE02-C1257B8E.001EAE06@inse.com>

Hi there!

We are now in process of learning KVM on OmniOS, and our first tests have been fine!

However, when we try to install Pfsense 2.0.3 as a KVM guest, we run into trouble. During installation it complains about DAD(Duplicate Address Discovery) ipv6, and the installation stalls. We are using normal em0, em1, and em2 if. 

Could this be conflicting with OmniOS assigning ipv6 addresses in some way? I don't see those ipv6 addresses assigned when I run ipadm show-addr.

We also use etherstubs for internal communication between two of the Pfsense if's and the other VM's that should connect to it, but not for the wan if, which is assigned to a phys if, so it couldn't really have something with that to do.

Anyone get som ideas? I could of coarse turn off address autoconfiguration in ndpd.conf, but I'm not sure that would be the right way of doing it...?

I'm also asking about this on the Pfsense forum.

Rgrds Johan



From raenac at gmail.com  Wed Jun 19 13:30:11 2013
From: raenac at gmail.com (Moises Medina)
Date: Wed, 19 Jun 2013 13:30:11 -0400
Subject: [OmniOS-discuss] OmniOS/OpenSM
Message-ID: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>

Hi All, new to the list.  Question I had is has anyone successfully ran
OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not have
a switch at all.

Thanks,

Raenac
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130619/515692eb/attachment.html>

From palmertime at gmail.com  Wed Jun 19 16:07:04 2013
From: palmertime at gmail.com (Michael Palmer)
Date: Wed, 19 Jun 2013 13:07:04 -0700
Subject: [OmniOS-discuss] OmniOS/OpenSM
In-Reply-To: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
References: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
Message-ID: <CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>

I believe that OpenSM is included in OmniOS but i'm not sure if VMware ESXi
5.x and above supports it.  If you are using ESXi 4.0 then some vendors
might have drivers for infiniband on ESXi.

Thanks,
Michael


On Wed, Jun 19, 2013 at 10:30 AM, Moises Medina <raenac at gmail.com> wrote:

> Hi All, new to the list.  Question I had is has anyone successfully ran
> OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not have
> a switch at all.
>
> Thanks,
>
> Raenac
>
> _______________________________________________
> 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/20130619/c092b0b1/attachment.html>

From raenac at gmail.com  Wed Jun 19 21:29:42 2013
From: raenac at gmail.com (Moises Medina)
Date: Wed, 19 Jun 2013 21:29:42 -0400
Subject: [OmniOS-discuss] OmniOS/OpenSM
In-Reply-To: <CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>
References: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
	<CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>
Message-ID: <CACZ7scSv7Vut-hg_Mgui6tM2OdEY6P2HYh=Vubyva5RXoSaHKw@mail.gmail.com>

Hi Michael, thanks for the response.  I tried the usual opensm command,
returned nothing, and searched for it in pkg, maybe its named something
else?

Moises


On Wed, Jun 19, 2013 at 4:07 PM, Michael Palmer <palmertime at gmail.com>wrote:

> I believe that OpenSM is included in OmniOS but i'm not sure if VMware
> ESXi 5.x and above supports it.  If you are using ESXi 4.0 then some
> vendors might have drivers for infiniband on ESXi.
>
> Thanks,
> Michael
>
>
> On Wed, Jun 19, 2013 at 10:30 AM, Moises Medina <raenac at gmail.com> wrote:
>
>> Hi All, new to the list.  Question I had is has anyone successfully ran
>> OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not have
>> a switch at all.
>>
>> Thanks,
>>
>> Raenac
>>
>> _______________________________________________
>> 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/20130619/7e7160f7/attachment.html>

From narayan.desai at gmail.com  Wed Jun 19 22:25:52 2013
From: narayan.desai at gmail.com (Narayan Desai)
Date: Wed, 19 Jun 2013 21:25:52 -0500
Subject: [OmniOS-discuss] OmniOS/OpenSM
In-Reply-To: <CACZ7scSv7Vut-hg_Mgui6tM2OdEY6P2HYh=Vubyva5RXoSaHKw@mail.gmail.com>
References: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
	<CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>
	<CACZ7scSv7Vut-hg_Mgui6tM2OdEY6P2HYh=Vubyva5RXoSaHKw@mail.gmail.com>
Message-ID: <CABweQmLLQv-etrJ6PXowGCgfGBGSjPxCB1wVDDh-qRtWG-kQOw@mail.gmail.com>

It looks like someone has managed to get things working on OI:
http://syoyo.wordpress.com/category/infiniband/

Just fyi, there don't seem to be many people running IB with omniOS or OI,
in general. We are, but aren't getting the performance we get with the same
hardware on linux.
 -nld


On Wed, Jun 19, 2013 at 8:29 PM, Moises Medina <raenac at gmail.com> wrote:

> Hi Michael, thanks for the response.  I tried the usual opensm command,
> returned nothing, and searched for it in pkg, maybe its named something
> else?
>
> Moises
>
>
> On Wed, Jun 19, 2013 at 4:07 PM, Michael Palmer <palmertime at gmail.com>wrote:
>
>> I believe that OpenSM is included in OmniOS but i'm not sure if VMware
>> ESXi 5.x and above supports it.  If you are using ESXi 4.0 then some
>> vendors might have drivers for infiniband on ESXi.
>>
>> Thanks,
>> Michael
>>
>>
>> On Wed, Jun 19, 2013 at 10:30 AM, Moises Medina <raenac at gmail.com> wrote:
>>
>>> Hi All, new to the list.  Question I had is has anyone successfully ran
>>> OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not have
>>> a switch at all.
>>>
>>> Thanks,
>>>
>>> Raenac
>>>
>>> _______________________________________________
>>> 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/20130619/c928ca0d/attachment.html>

From turbo124 at gmail.com  Wed Jun 19 23:01:12 2013
From: turbo124 at gmail.com (David Bomba)
Date: Thu, 20 Jun 2013 13:01:12 +1000
Subject: [OmniOS-discuss] OmniOS/OpenSM
In-Reply-To: <CABweQmLLQv-etrJ6PXowGCgfGBGSjPxCB1wVDDh-qRtWG-kQOw@mail.gmail.com>
References: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
	<CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>
	<CACZ7scSv7Vut-hg_Mgui6tM2OdEY6P2HYh=Vubyva5RXoSaHKw@mail.gmail.com>
	<CABweQmLLQv-etrJ6PXowGCgfGBGSjPxCB1wVDDh-qRtWG-kQOw@mail.gmail.com>
Message-ID: <BAB00A37-DC4D-4AB3-B970-44AD0F4E02FB@gmail.com>

We run 10G Infiniband on OmniOS using the ComSTAR iscsi target.

We can flood the network easily between two OmniOS machines.

We are about to upgrade to 40Gb/s HCAs, and i would expect similar performance.

Dave

On 20/06/2013, at 12:25 PM, Narayan Desai wrote:

> It looks like someone has managed to get things working on OI:
> http://syoyo.wordpress.com/category/infiniband/
> 
> Just fyi, there don't seem to be many people running IB with omniOS or OI, in general. We are, but aren't getting the performance we get with the same hardware on linux. 
>  -nld
> 
> 
> On Wed, Jun 19, 2013 at 8:29 PM, Moises Medina <raenac at gmail.com> wrote:
> Hi Michael, thanks for the response.  I tried the usual opensm command, returned nothing, and searched for it in pkg, maybe its named something else?
> 
> Moises
> 
> 
> On Wed, Jun 19, 2013 at 4:07 PM, Michael Palmer <palmertime at gmail.com> wrote:
> I believe that OpenSM is included in OmniOS but i'm not sure if VMware ESXi 5.x and above supports it.  If you are using ESXi 4.0 then some vendors might have drivers for infiniband on ESXi.
> 
> Thanks,
> Michael
> 
> 
> On Wed, Jun 19, 2013 at 10:30 AM, Moises Medina <raenac at gmail.com> wrote:
> Hi All, new to the list.  Question I had is has anyone successfully ran OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not have a switch at all.
> 
> Thanks,
> 
> Raenac
> 
> _______________________________________________
> 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/20130620/3a3a3487/attachment.html>

From narayan.desai at gmail.com  Thu Jun 20 00:09:50 2013
From: narayan.desai at gmail.com (Narayan Desai)
Date: Wed, 19 Jun 2013 23:09:50 -0500
Subject: [OmniOS-discuss] OmniOS/OpenSM
In-Reply-To: <BAB00A37-DC4D-4AB3-B970-44AD0F4E02FB@gmail.com>
References: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
	<CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>
	<CACZ7scSv7Vut-hg_Mgui6tM2OdEY6P2HYh=Vubyva5RXoSaHKw@mail.gmail.com>
	<CABweQmLLQv-etrJ6PXowGCgfGBGSjPxCB1wVDDh-qRtWG-kQOw@mail.gmail.com>
	<BAB00A37-DC4D-4AB3-B970-44AD0F4E02FB@gmail.com>
Message-ID: <CABweQmJPW7TUe5V5niJ8xSm9r0SKo6+bbdi7kZxbazdnrqXJSQ@mail.gmail.com>

I'm curious to hear what performance you end up seeing. We've got QDR
connectX 2 cards, and only seen ~2300 MB/s out of them, compared with ~3100
on linux with the same hardware. (this is even just the completely local bw
tests to the cards)

Our of curiosity, are you using ipoib or iSER? We've seen much better
performance with the latter, topping out around 1800 MB/s, compared with
~300 on ipoib without much tuning. (single clients, in both cases) We can't
hit the RDMA benchmark bandwidths with a single client, even though we have
sufficient spindles on the back end.
 -nld


On Wed, Jun 19, 2013 at 10:01 PM, David Bomba <turbo124 at gmail.com> wrote:

> We run 10G Infiniband on OmniOS using the ComSTAR iscsi target.
>
> We can flood the network easily between two OmniOS machines.
>
> We are about to upgrade to 40Gb/s HCAs, and i would expect similar
> performance.
>
> Dave
>
> On 20/06/2013, at 12:25 PM, Narayan Desai wrote:
>
> It looks like someone has managed to get things working on OI:
> http://syoyo.wordpress.com/category/infiniband/
>
> Just fyi, there don't seem to be many people running IB with omniOS or OI,
> in general. We are, but aren't getting the performance we get with the same
> hardware on linux.
>  -nld
>
>
> On Wed, Jun 19, 2013 at 8:29 PM, Moises Medina <raenac at gmail.com> wrote:
>
>> Hi Michael, thanks for the response.  I tried the usual opensm command,
>> returned nothing, and searched for it in pkg, maybe its named something
>> else?
>>
>> Moises
>>
>>
>> On Wed, Jun 19, 2013 at 4:07 PM, Michael Palmer <palmertime at gmail.com>wrote:
>>
>>> I believe that OpenSM is included in OmniOS but i'm not sure if VMware
>>> ESXi 5.x and above supports it.  If you are using ESXi 4.0 then some
>>> vendors might have drivers for infiniband on ESXi.
>>>
>>> Thanks,
>>> Michael
>>>
>>>
>>> On Wed, Jun 19, 2013 at 10:30 AM, Moises Medina <raenac at gmail.com>wrote:
>>>
>>>> Hi All, new to the list.  Question I had is has anyone successfully ran
>>>> OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not have
>>>> a switch at all.
>>>>
>>>> Thanks,
>>>>
>>>> Raenac
>>>>
>>>> _______________________________________________
>>>> 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/20130619/65e92e4b/attachment-0001.html>

From turbo124 at gmail.com  Thu Jun 20 00:15:17 2013
From: turbo124 at gmail.com (David Bomba)
Date: Thu, 20 Jun 2013 14:15:17 +1000
Subject: [OmniOS-discuss] OmniOS/OpenSM
In-Reply-To: <CABweQmJPW7TUe5V5niJ8xSm9r0SKo6+bbdi7kZxbazdnrqXJSQ@mail.gmail.com>
References: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
	<CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>
	<CACZ7scSv7Vut-hg_Mgui6tM2OdEY6P2HYh=Vubyva5RXoSaHKw@mail.gmail.com>
	<CABweQmLLQv-etrJ6PXowGCgfGBGSjPxCB1wVDDh-qRtWG-kQOw@mail.gmail.com>
	<BAB00A37-DC4D-4AB3-B970-44AD0F4E02FB@gmail.com>
	<CABweQmJPW7TUe5V5niJ8xSm9r0SKo6+bbdi7kZxbazdnrqXJSQ@mail.gmail.com>
Message-ID: <CACS0AjGmi_avi552DQ0x4GPRWY4cekKSz8xM_82bpb8a8SwZMw@mail.gmail.com>

We use both IPoIB and iSER. iSER can flood the HCA.

With IPoIB because TCP is done in software we only see around 450MB/s,
using connected mode with 65k MTU and some tuning with ndd for larger frame
sizes.

With 40Gb/s equipment the bottleneck will be the PCIe 2.0 BUS, so I doubt
we will be able to get over 3Gb/s..

What protocols are you using for your testing? SRP , iSER or NFSoRDMA?


On 20 June 2013 14:09, Narayan Desai <narayan.desai at gmail.com> wrote:

> I'm curious to hear what performance you end up seeing. We've got QDR
> connectX 2 cards, and only seen ~2300 MB/s out of them, compared with ~3100
> on linux with the same hardware. (this is even just the completely local bw
> tests to the cards)
>
> Our of curiosity, are you using ipoib or iSER? We've seen much better
> performance with the latter, topping out around 1800 MB/s, compared with
> ~300 on ipoib without much tuning. (single clients, in both cases) We can't
> hit the RDMA benchmark bandwidths with a single client, even though we have
> sufficient spindles on the back end.
>  -nld
>
>
> On Wed, Jun 19, 2013 at 10:01 PM, David Bomba <turbo124 at gmail.com> wrote:
>
>> We run 10G Infiniband on OmniOS using the ComSTAR iscsi target.
>>
>> We can flood the network easily between two OmniOS machines.
>>
>> We are about to upgrade to 40Gb/s HCAs, and i would expect similar
>> performance.
>>
>> Dave
>>
>> On 20/06/2013, at 12:25 PM, Narayan Desai wrote:
>>
>> It looks like someone has managed to get things working on OI:
>> http://syoyo.wordpress.com/category/infiniband/
>>
>> Just fyi, there don't seem to be many people running IB with omniOS or
>> OI, in general. We are, but aren't getting the performance we get with the
>> same hardware on linux.
>>  -nld
>>
>>
>> On Wed, Jun 19, 2013 at 8:29 PM, Moises Medina <raenac at gmail.com> wrote:
>>
>>> Hi Michael, thanks for the response.  I tried the usual opensm command,
>>> returned nothing, and searched for it in pkg, maybe its named something
>>> else?
>>>
>>> Moises
>>>
>>>
>>> On Wed, Jun 19, 2013 at 4:07 PM, Michael Palmer <palmertime at gmail.com>wrote:
>>>
>>>> I believe that OpenSM is included in OmniOS but i'm not sure if VMware
>>>> ESXi 5.x and above supports it.  If you are using ESXi 4.0 then some
>>>> vendors might have drivers for infiniband on ESXi.
>>>>
>>>> Thanks,
>>>> Michael
>>>>
>>>>
>>>> On Wed, Jun 19, 2013 at 10:30 AM, Moises Medina <raenac at gmail.com>wrote:
>>>>
>>>>> Hi All, new to the list.  Question I had is has anyone successfully
>>>>> ran OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not
>>>>> have a switch at all.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Raenac
>>>>>
>>>>> _______________________________________________
>>>>> 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/20130620/84d05fd0/attachment.html>

From narayan.desai at gmail.com  Thu Jun 20 07:33:33 2013
From: narayan.desai at gmail.com (Narayan Desai)
Date: Thu, 20 Jun 2013 06:33:33 -0500
Subject: [OmniOS-discuss] OmniOS/OpenSM
In-Reply-To: <CACS0AjGmi_avi552DQ0x4GPRWY4cekKSz8xM_82bpb8a8SwZMw@mail.gmail.com>
References: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
	<CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>
	<CACZ7scSv7Vut-hg_Mgui6tM2OdEY6P2HYh=Vubyva5RXoSaHKw@mail.gmail.com>
	<CABweQmLLQv-etrJ6PXowGCgfGBGSjPxCB1wVDDh-qRtWG-kQOw@mail.gmail.com>
	<BAB00A37-DC4D-4AB3-B970-44AD0F4E02FB@gmail.com>
	<CABweQmJPW7TUe5V5niJ8xSm9r0SKo6+bbdi7kZxbazdnrqXJSQ@mail.gmail.com>
	<CACS0AjGmi_avi552DQ0x4GPRWY4cekKSz8xM_82bpb8a8SwZMw@mail.gmail.com>
Message-ID: <CABweQmK5kGRMdw1z9YnOcKuLNmO39gWY_ab86k41h2KbFAH0Xg@mail.gmail.com>

We're primarily using iSER. We had similar problems using iscsi with tcp
over the ipoib. We're using the system as openstack block storage, so
iscsi+iSER was the simplest protocol to use.

Depending on the depending on the PCIe chipset, we see up to about 3200
MB/s with a connectX2 on gen2 PCIe (on linux). ConnectX3's are gen3 so
those wouldn't be bus limited with a single port card on a system with gen3
PCIe.
 -nld


On Wed, Jun 19, 2013 at 11:15 PM, David Bomba <turbo124 at gmail.com> wrote:

> We use both IPoIB and iSER. iSER can flood the HCA.
>
> With IPoIB because TCP is done in software we only see around 450MB/s,
> using connected mode with 65k MTU and some tuning with ndd for larger frame
> sizes.
>
> With 40Gb/s equipment the bottleneck will be the PCIe 2.0 BUS, so I doubt
> we will be able to get over 3Gb/s..
>
> What protocols are you using for your testing? SRP , iSER or NFSoRDMA?
>
>
> On 20 June 2013 14:09, Narayan Desai <narayan.desai at gmail.com> wrote:
>
>> I'm curious to hear what performance you end up seeing. We've got QDR
>> connectX 2 cards, and only seen ~2300 MB/s out of them, compared with ~3100
>> on linux with the same hardware. (this is even just the completely local bw
>> tests to the cards)
>>
>> Our of curiosity, are you using ipoib or iSER? We've seen much better
>> performance with the latter, topping out around 1800 MB/s, compared with
>> ~300 on ipoib without much tuning. (single clients, in both cases) We can't
>> hit the RDMA benchmark bandwidths with a single client, even though we have
>> sufficient spindles on the back end.
>>  -nld
>>
>>
>> On Wed, Jun 19, 2013 at 10:01 PM, David Bomba <turbo124 at gmail.com> wrote:
>>
>>> We run 10G Infiniband on OmniOS using the ComSTAR iscsi target.
>>>
>>> We can flood the network easily between two OmniOS machines.
>>>
>>> We are about to upgrade to 40Gb/s HCAs, and i would expect similar
>>> performance.
>>>
>>> Dave
>>>
>>> On 20/06/2013, at 12:25 PM, Narayan Desai wrote:
>>>
>>> It looks like someone has managed to get things working on OI:
>>> http://syoyo.wordpress.com/category/infiniband/
>>>
>>> Just fyi, there don't seem to be many people running IB with omniOS or
>>> OI, in general. We are, but aren't getting the performance we get with the
>>> same hardware on linux.
>>>  -nld
>>>
>>>
>>> On Wed, Jun 19, 2013 at 8:29 PM, Moises Medina <raenac at gmail.com> wrote:
>>>
>>>> Hi Michael, thanks for the response.  I tried the usual opensm command,
>>>> returned nothing, and searched for it in pkg, maybe its named something
>>>> else?
>>>>
>>>> Moises
>>>>
>>>>
>>>> On Wed, Jun 19, 2013 at 4:07 PM, Michael Palmer <palmertime at gmail.com>wrote:
>>>>
>>>>> I believe that OpenSM is included in OmniOS but i'm not sure if VMware
>>>>> ESXi 5.x and above supports it.  If you are using ESXi 4.0 then some
>>>>> vendors might have drivers for infiniband on ESXi.
>>>>>
>>>>> Thanks,
>>>>> Michael
>>>>>
>>>>>
>>>>> On Wed, Jun 19, 2013 at 10:30 AM, Moises Medina <raenac at gmail.com>wrote:
>>>>>
>>>>>> Hi All, new to the list.  Question I had is has anyone successfully
>>>>>> ran OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not
>>>>>> have a switch at all.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Raenac
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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/20130620/d06feff8/attachment.html>

From raenac at gmail.com  Thu Jun 20 08:43:05 2013
From: raenac at gmail.com (Moises Medina)
Date: Thu, 20 Jun 2013 08:43:05 -0400
Subject: [OmniOS-discuss] Fwd:  OmniOS/OpenSM
In-Reply-To: <CACZ7scTsDXdCZ_HnCbrDb974maB8ik1i7kBBNJY2aJQn3WT99A@mail.gmail.com>
References: <CACZ7scRwEy7jtBjBk2VMm1r5aU9drq7qAGmc=G-Qrrcrcp1LWw@mail.gmail.com>
	<CABpYwfcWiaAWjaXCHmRLX4M_gofmJy6M8O59XkcS_BH79qc6hw@mail.gmail.com>
	<CACZ7scSv7Vut-hg_Mgui6tM2OdEY6P2HYh=Vubyva5RXoSaHKw@mail.gmail.com>
	<CABweQmLLQv-etrJ6PXowGCgfGBGSjPxCB1wVDDh-qRtWG-kQOw@mail.gmail.com>
	<CACZ7scTsDXdCZ_HnCbrDb974maB8ik1i7kBBNJY2aJQn3WT99A@mail.gmail.com>
Message-ID: <CACZ7scQzvZfc-xj50Sog_OGc1zoEiykZ5eNvcSxCQD+DeOvY1Q@mail.gmail.com>

Forgot to send to list ;)

---------- Forwarded message ----------
From: Moises Medina <raenac at gmail.com>
Date: Thu, Jun 20, 2013 at 8:42 AM
Subject: Re: [OmniOS-discuss] OmniOS/OpenSM
To: Narayan Desai <narayan.desai at gmail.com>


Hi Narayan, Yes I've seen that blog and might have to try to compile openSM
on OmniOS.  I was able to get IB up with OmniOS with MS Server 2012 on
other end running OpenSM there, but wanted to see about getting SRP working
with ESXi and OmniOS.

That or I'll have to wait until I can get a QDR switch that has SM on it.


On Wed, Jun 19, 2013 at 10:25 PM, Narayan Desai <narayan.desai at gmail.com>wrote:

> It looks like someone has managed to get things working on OI:
> http://syoyo.wordpress.com/category/infiniband/
>
> Just fyi, there don't seem to be many people running IB with omniOS or OI,
> in general. We are, but aren't getting the performance we get with the same
> hardware on linux.
>  -nld
>
>
> On Wed, Jun 19, 2013 at 8:29 PM, Moises Medina <raenac at gmail.com> wrote:
>
>> Hi Michael, thanks for the response.  I tried the usual opensm command,
>> returned nothing, and searched for it in pkg, maybe its named something
>> else?
>>
>> Moises
>>
>>
>> On Wed, Jun 19, 2013 at 4:07 PM, Michael Palmer <palmertime at gmail.com>wrote:
>>
>>> I believe that OpenSM is included in OmniOS but i'm not sure if VMware
>>> ESXi 5.x and above supports it.  If you are using ESXi 4.0 then some
>>> vendors might have drivers for infiniband on ESXi.
>>>
>>> Thanks,
>>> Michael
>>>
>>>
>>> On Wed, Jun 19, 2013 at 10:30 AM, Moises Medina <raenac at gmail.com>wrote:
>>>
>>>> Hi All, new to the list.  Question I had is has anyone successfully ran
>>>> OpenSM on OmniOS?  Trying to use this as ZFS server to ESXI but do not have
>>>> a switch at all.
>>>>
>>>> Thanks,
>>>>
>>>> Raenac
>>>>
>>>> _______________________________________________
>>>> 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/20130620/5721e052/attachment-0001.html>

From felix.nielsen at gmail.com  Fri Jun 21 09:10:51 2013
From: felix.nielsen at gmail.com (Felix Nielsen)
Date: Fri, 21 Jun 2013 15:10:51 +0200
Subject: [OmniOS-discuss] slow system
Message-ID: <CAOPMS7Zw1PYCNu+TRFsV7bwO-8RB=+dRNN_SJD8Z_ZjJAyOWZw@mail.gmail.com>

Hi All,

I am new to the omnios system, but have been using nexenta for a while.

I have an HP Z800 workstation, 96GB ram, integrated LSI controller with IT
firmware, 6 x 2TB SAS 7200 disks, 2 x 750GB OS mirror, 1 x SSD ARC 160GB
Intel, 1 x OZ SSD for ZIL - OmniOS and napp-it to handle the ZFS functions.

I started to replicate some snapshots from my Nexenta - 5-8TB in total, and
I was playing around with compression, dedup to see what gain I would get.

Then suddenly it took for ever to destroy and create new zfs filesystems,
and replication was really slow.

So I deleted all my replicated volumes and rebooted the system - nothing
happened, so I was watching the console and it took 4100 sec to shutdown,
and then it started file system sync, which I am not sure how long will
take.

What could be the issue?

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

From esproul at omniti.com  Fri Jun 21 09:53:51 2013
From: esproul at omniti.com (Eric Sproul)
Date: Fri, 21 Jun 2013 09:53:51 -0400
Subject: [OmniOS-discuss] slow system
In-Reply-To: <CAOPMS7Zw1PYCNu+TRFsV7bwO-8RB=+dRNN_SJD8Z_ZjJAyOWZw@mail.gmail.com>
References: <CAOPMS7Zw1PYCNu+TRFsV7bwO-8RB=+dRNN_SJD8Z_ZjJAyOWZw@mail.gmail.com>
Message-ID: <CA+QY2RSZTssXRY63wdJeS+wdsDeva8cRhE8B1_pwzN1ikmjb2Q@mail.gmail.com>

Hi Felix,
This sounds like the characteristics of a dedup table (DDT) that will
not fit in RAM.  The consequences this produces are well-documented
and can be found easily via Google.  Constantin Gonzalez has a pretty
good summary here:
http://constantin.glez.de/blog/2011/07/zfs-dedupe-or-not-dedupe

Your options are basically: wait it out It will eventually grind
through all the DDT de-referencing of the freed blocks, or destroy the
pool and start over.

You've learned the hard way that dedup has a dark side.  :)
Eric


On Fri, Jun 21, 2013 at 9:10 AM, Felix Nielsen <felix.nielsen at gmail.com> wrote:
> Hi All,
>
> I am new to the omnios system, but have been using nexenta for a while.
>
> I have an HP Z800 workstation, 96GB ram, integrated LSI controller with IT
> firmware, 6 x 2TB SAS 7200 disks, 2 x 750GB OS mirror, 1 x SSD ARC 160GB
> Intel, 1 x OZ SSD for ZIL - OmniOS and napp-it to handle the ZFS functions.
>
> I started to replicate some snapshots from my Nexenta - 5-8TB in total, and
> I was playing around with compression, dedup to see what gain I would get.
>
> Then suddenly it took for ever to destroy and create new zfs filesystems,
> and replication was really slow.
>
> So I deleted all my replicated volumes and rebooted the system - nothing
> happened, so I was watching the console and it took 4100 sec to shutdown,
> and then it started file system sync, which I am not sure how long will
> take.
>
> What could be the issue?
>
> Thanks
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From tobi at oetiker.ch  Sat Jun 22 02:11:24 2013
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Sat, 22 Jun 2013 08:11:24 +0200 (CEST)
Subject: [OmniOS-discuss] could you please merge the setgroups fix
Message-ID: <alpine.DEB.2.02.1306220809140.19981@froburg.oetiker.ch>

We are in the process of deploying omnios for a large customer with
a complex group setup ... only to find that support for more than
16 groups per user was broken ... this got fixed upstream in the
mean time ...

could you please merge the fix ?

 https://github.com/illumos/illumos-gate/commit/b77dfcc8362f3695ece944d5bb504276753a40f9

if yousers can not access their data, this whole thing is dead in
the water ...

cheers
tobi


-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900

From jesus at omniti.com  Sat Jun 22 02:23:18 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Sat, 22 Jun 2013 02:23:18 -0400
Subject: [OmniOS-discuss] could you please merge the setgroups fix
In-Reply-To: <alpine.DEB.2.02.1306220809140.19981@froburg.oetiker.ch>
References: <alpine.DEB.2.02.1306220809140.19981@froburg.oetiker.ch>
Message-ID: <CACLsApv3pFvVtbanKjDCjyBzE9a5c1doyKSeUNgt=1x5jB2u3A@mail.gmail.com>

I believe that is already merged.  It should be in bloody.
On Jun 21, 2013 11:16 PM, "Tobias Oetiker" <tobi at oetiker.ch> wrote:

> We are in the process of deploying omnios for a large customer with
> a complex group setup ... only to find that support for more than
> 16 groups per user was broken ... this got fixed upstream in the
> mean time ...
>
> could you please merge the fix ?
>
>
> https://github.com/illumos/illumos-gate/commit/b77dfcc8362f3695ece944d5bb504276753a40f9
>
> if yousers can not access their data, this whole thing is dead in
> the water ...
>
> cheers
> tobi
>
>
> --
> Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
> http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900
> _______________________________________________
> 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/20130622/09f5712b/attachment.html>

From henson at acm.org  Sat Jun 22 02:46:44 2013
From: henson at acm.org (Paul B. Henson)
Date: Fri, 21 Jun 2013 23:46:44 -0700
Subject: [OmniOS-discuss] could you please merge the setgroups fix
In-Reply-To: <CACLsApv3pFvVtbanKjDCjyBzE9a5c1doyKSeUNgt=1x5jB2u3A@mail.gmail.com>
References: <alpine.DEB.2.02.1306220809140.19981@froburg.oetiker.ch>
	<CACLsApv3pFvVtbanKjDCjyBzE9a5c1doyKSeUNgt=1x5jB2u3A@mail.gmail.com>
Message-ID: <5AC3A3F8-E946-4933-B489-FFBACF344D46@acm.org>

Were you guys going to backport that to stable? Seems like it might be an important enough fix to be worth it, and tiny enough not to have much risk. 

On Jun 21, 2013, at 11:23 PM, Theo Schlossnagle <jesus at omniti.com> wrote:

> I believe that is already merged.  It should be in bloody.
> 
> On Jun 21, 2013 11:16 PM, "Tobias Oetiker" <tobi at oetiker.ch> wrote:
>> We are in the process of deploying omnios for a large customer with
>> a complex group setup ... only to find that support for more than
>> 16 groups per user was broken ... this got fixed upstream in the
>> mean time ...
>> 
>> could you please merge the fix ?
>> 
>>  https://github.com/illumos/illumos-gate/commit/b77dfcc8362f3695ece944d5bb504276753a40f9
>> 
>> if yousers can not access their data, this whole thing is dead in
>> the water ...
>> 
>> cheers
>> tobi
>> 
>> 
>> --
>> Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
>> http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900
>> _______________________________________________
>> 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/20130621/6b7632ba/attachment.html>

From gc at birzan.org  Sat Jun 22 03:28:50 2013
From: gc at birzan.org (=?ISO-8859-1?Q?George=2DCristian_B=EErzan?=)
Date: Sat, 22 Jun 2013 10:28:50 +0300
Subject: [OmniOS-discuss] 802.3ad/LACP weirdness
Message-ID: <CAMxNYaZFKUJVNySONFFBjCcBULWV5gVGJfrR72vpqu2Y7JTU4A@mail.gmail.com>

We set up a machine the other day and had a very weird problem when trying
to aggregate a couple of NICs. The machine has 4*10GigE ports (2*2 cards)
but we only connected two to a Force10 switch. We enabled LACP and the port
channel was created on the switch, but we then spent the next 4 hours
trying to get ARP requests to work.

It turns out that, for our config, it is possible broadcast frames over
interfaces that are down. We have not seen any unicast doing this, and
we're not doing any multicast, I'm not 100% sure if having an L4 policy
looks at the IP requested in the ARP frame, but we've tested with ~30 and
they all went over the same, even with L4. It's also something that can
happen if the interface goes down after the aggr interface was created, as
we shutdown the two operational interfaces one by and ARP requests were
still trying to go over the one that was down.

Obviously, our setup is not just that, on top of the aggr1 interface, we
have two VLANs (and the problem manifests itself on both). I cannot test
right now, as the machine is in production, but we'll be getting an
identical setup on Monday to play with for a bit. Anyway, some of the stuff
I looked at (was talking to esproul in the IRC channel):

dladm show-aggr -si while trying to get the MAC of an IP with all 4 ifaces
in (I removed the irrelevant ones so the headers match :) ):

LINK        PORT      IPACKETS RBYTES OPACKETS OBYTES IPKTDIST OPKTDIST
aggr1       --        6521    2804    2       294     --       --
--          ixgbe0    0       0       0       46      0.0      0.0
--          ixgbe1    5616    252     1       124     86.1     50.0
--          ixgbe2    0       0       0       0       0.0      0.0
--          ixgbe3    905     2552    1       124     13.9     50.0

dladm show-aggr -x:

LINK        PORT           SPEED DUPLEX   STATE     ADDRESS
 PORTSTATE
aggr1       --             10000Mb full   up        90:e2:ba:3f:d2:38  --
            ixgbe0         0Mb  unknown   down      90:e2:ba:3f:d2:38
 standby
            ixgbe1         10000Mb full   up        90:e2:ba:3f:d2:39
 attached
            ixgbe2         0Mb  unknown   down      90:e2:ba:3f:d0:50
 standby
            ixgbe3         10000Mb full   up        90:e2:ba:3f:d0:51
 attached


A tcpdump running on ixgbe0 at the same time:

# /opt/omni/sbin/tcpdump -ni ixgbe0 ether host 90:e2:ba:3f:d2:38
tcpdump: WARNING: SIOCGIFADDR: ixgbe0: No such device or address
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ixgbe0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:42:30.025630 ARP, Request who-has 10.0.64.105 (ff:ff:ff:ff:ff:ff) tell
10.0.64.131, length 28
14:42:30.520063 ARP, Request who-has 10.0.64.105 (ff:ff:ff:ff:ff:ff) tell
10.0.64.131, length 28
14:42:31.020049 ARP, Request who-has 10.0.64.105 (ff:ff:ff:ff:ff:ff) tell
10.0.64.131, length 28
14:42:32.020122 ARP, Request who-has 10.0.64.105 (ff:ff:ff:ff:ff:ff) tell
10.0.64.131, length 28
14:42:32.520041 ARP, Request who-has 10.0.64.105 (ff:ff:ff:ff:ff:ff) tell
10.0.64.131, length 28


While the machine will be mostly accessed from other hosts, not the other
way around, this won't really be an issue, if an external machine sends an
ARP request, the reply will go over unicast and it will be on the correct
interface (i.e. one that is up), and we can just add static ARP entries
(i.e. the log host and default gateway), going forward this might be quite
a problem, and wanted to know if:

a) I did something stupid (quite likely, I have absolutely no experience
with OmniOS or Solaris except for the two weeks spent playing around with
it)
b) it's a bug (I took a look at aggr_send.c and couldn't see anything
obviously wrong, and I cannot see why broadcast packets would be treated
differently)
c) anyone has seen this behaviour before

-- 
George-Cristian B?rzan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130622/2357bca6/attachment.html>

From tobi at oetiker.ch  Sat Jun 22 04:06:42 2013
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Sat, 22 Jun 2013 10:06:42 +0200
Subject: [OmniOS-discuss] could you please merge the setgroups fix
In-Reply-To: <5AC3A3F8-E946-4933-B489-FFBACF344D46@acm.org>
References: <alpine.DEB.2.02.1306220809140.19981@froburg.oetiker.ch>
	<CACLsApv3pFvVtbanKjDCjyBzE9a5c1doyKSeUNgt=1x5jB2u3A@mail.gmail.com>
	<5AC3A3F8-E946-4933-B489-FFBACF344D46@acm.org>
Message-ID: <AAD9D3BF-5A22-4262-9906-D1FD94433E67@oetiker.ch>

I was thinking about stable too, running bloody in production des not seem optimal.

Tobias Oetiker

On 22.06.2013, at 08:46, "Paul B. Henson" <henson at acm.org> wrote:

> Were you guys going to backport that to stable? Seems like it might be an important enough fix to be worth it, and tiny enough not to have much risk. 
> 
> On Jun 21, 2013, at 11:23 PM, Theo Schlossnagle <jesus at omniti.com> wrote:
> 
>> I believe that is already merged.  It should be in bloody.
>> 
>> On Jun 21, 2013 11:16 PM, "Tobias Oetiker" <tobi at oetiker.ch> wrote:
>>> We are in the process of deploying omnios for a large customer with
>>> a complex group setup ... only to find that support for more than
>>> 16 groups per user was broken ... this got fixed upstream in the
>>> mean time ...
>>> 
>>> could you please merge the fix ?
>>> 
>>>  https://github.com/illumos/illumos-gate/commit/b77dfcc8362f3695ece944d5bb504276753a40f9
>>> 
>>> if yousers can not access their data, this whole thing is dead in
>>> the water ...
>>> 
>>> cheers
>>> tobi
>>> 
>>> 
>>> --
>>> Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
>>> http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900
>>> _______________________________________________
>>> 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/20130622/a7236644/attachment-0001.html>

From robin at smidsrod.no  Sun Jun 23 07:12:06 2013
From: robin at smidsrod.no (=?UTF-8?B?Um9iaW4gU21pZHNyw7hk?=)
Date: Sun, 23 Jun 2013 13:12:06 +0200
Subject: [OmniOS-discuss] kstat -p gives segfault on OmniOS r151006
Message-ID: <51C6D806.4090404@smidsrod.no>

Hi everyone,

I'm having a problem with kstat -p segfaulting on me.

I've included the output from truss here:
https://gist.github.com/robinsmidsrod/5844493

A user on irc (gcbirzan) confirmed that he did not get a segfault on a
clean install of r151006, so it seems this might be related to some
stmf_tgt-related configuration which is confusing kstat. He also
confirmed that he got the same segfault on his system that has some
iscsi targets setup. This is his exact uttering:

"<gcbirzan> I get the same :) but I always assumed it's because I hacked
libiscsit to have more than 255 targets"

I have not hacked anything on my system, running standard versions of
all software.

Any chance of a fix and a backport to stable?

Not sure what kind of info you'd need to debug things further, but ask
and I shall provide.

-- Robin

From richard.elling at richardelling.com  Sun Jun 23 21:32:49 2013
From: richard.elling at richardelling.com (Richard Elling)
Date: Sun, 23 Jun 2013 18:32:49 -0700
Subject: [OmniOS-discuss] kstat -p gives segfault on OmniOS r151006
In-Reply-To: <51C6D806.4090404@smidsrod.no>
References: <51C6D806.4090404@smidsrod.no>
Message-ID: <2B3D20AC-FBD9-43C8-ADD0-422C0BA7367C@RichardElling.com>

On Jun 23, 2013, at 4:12 AM, Robin Smidsr?d <robin at smidsrod.no> wrote:

> Hi everyone,
> 
> I'm having a problem with kstat -p segfaulting on me.
> 
> I've included the output from truss here:
> https://gist.github.com/robinsmidsrod/5844493
> 
> A user on irc (gcbirzan) confirmed that he did not get a segfault on a
> clean install of r151006, so it seems this might be related to some
> stmf_tgt-related configuration which is confusing kstat. He also
> confirmed that he got the same segfault on his system that has some
> iscsi targets setup. This is his exact uttering:
> 
> "<gcbirzan> I get the same :) but I always assumed it's because I hacked
> libiscsit to have more than 255 targets"

More likely, you don't have an alias for the target. This leaves a null pointer
where kstat expects a string. Simple fix that Theo already submitted.

> 
> I have not hacked anything on my system, running standard versions of
> all software.
> 
> Any chance of a fix and a backport to stable?

This is a very low risk, only affects the kstat command itself.
 -- richard

> 
> Not sure what kind of info you'd need to debug things further, but ask
> and I shall provide.
> 
> -- Robin
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

--

Richard.Elling at RichardElling.com
+1-760-896-4422



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

From robin at smidsrod.no  Mon Jun 24 02:55:56 2013
From: robin at smidsrod.no (=?UTF-8?B?Um9iaW4gU21pZHNyw7hk?=)
Date: Mon, 24 Jun 2013 08:55:56 +0200
Subject: [OmniOS-discuss] kstat -p gives segfault on OmniOS r151006
In-Reply-To: <2B3D20AC-FBD9-43C8-ADD0-422C0BA7367C@RichardElling.com>
References: <51C6D806.4090404@smidsrod.no>
	<2B3D20AC-FBD9-43C8-ADD0-422C0BA7367C@RichardElling.com>
Message-ID: <51C7ED7C.7080705@smidsrod.no>

On 24.06.2013 03:32, Richard Elling wrote:
> On Jun 23, 2013, at 4:12 AM, Robin Smidsr?d <robin at smidsrod.no
> <mailto:robin at smidsrod.no>> wrote:
>>
>> I'm having a problem with kstat -p segfaulting on me.
>>
>> I've included the output from truss here:
>> https://gist.githubcom/robinsmidsrod/5844493
>> <https://gist.github.com/robinsmidsrod/5844493>
>>
>> A user on irc (gcbirzan) confirmed that he did not get a segfault on a
>> clean install of r151006, so it seems this might be related to some
>> stmf_tgt-related configuration which is confusing kstat. He also
>> confirmed that he got the same segfault on his system that has some
>> iscsi targets setup. This is his exact uttering:
>>
>> "<gcbirzan> I get the same :) but I always assumed it's because I hacked
>> libiscsit to have more than 255 targets"
> 
> More likely, you don't have an alias for the target. This leaves a null
> pointer
> where kstat expects a string. Simple fix that Theo already submitted.

After I provided Theo with a core file he was able to come up with a fix
that I have already verified worked on my system. He said he would push
it upstream.

>> Any chance of a fix and a backport to stable?
> 
> This is a very low risk, only affects the kstat command itself.

Yeah, that was what Theo said as well, so I'm eager to see it in stable.

Thank you for a quick fix!

-- Robin


From ramquick at gmail.com  Mon Jun 24 10:00:02 2013
From: ramquick at gmail.com (Ram Chander)
Date: Mon, 24 Jun 2013 19:30:02 +0530
Subject: [OmniOS-discuss] Bonding Nics
Message-ID: <CAMRGQbPWA-GTanKD21Suw=mPNfAT+_z7Hf=yQOSkGT-zoJT4jg@mail.gmail.com>

Hi,

I have  below 4 interfaces connected two switch. I want to create bonding
where bnx0, bnx1 group are  active and failsover to bnx2, bnx3 group when
primary switch is down.
Please help on how to create using ipmp.

 bnx0 + bnx1 ( interfaces are connected to primary switch A )

 bnx2 + bnx3 (  interfaces are connected to secondary switch B)

Regards,
Ram
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130624/4b1476f7/attachment.html>

From ben at fluffy.co.uk  Mon Jun 24 10:16:22 2013
From: ben at fluffy.co.uk (Ben Summers)
Date: Mon, 24 Jun 2013 15:16:22 +0100
Subject: [OmniOS-discuss] Bonding Nics
In-Reply-To: <CAMRGQbPWA-GTanKD21Suw=mPNfAT+_z7Hf=yQOSkGT-zoJT4jg@mail.gmail.com>
References: <CAMRGQbPWA-GTanKD21Suw=mPNfAT+_z7Hf=yQOSkGT-zoJT4jg@mail.gmail.com>
Message-ID: <C71B2F56-B4F3-4F47-BDBA-D474712D9249@fluffy.co.uk>


On 24 Jun 2013, at 15:00, Ram Chander <ramquick at gmail.com> wrote:

> Hi,
> 
> I have  below 4 interfaces connected two switch. I want to create bonding where bnx0, bnx1 group are  active and failsover to bnx2, bnx3 group when primary switch is down.
> Please help on how to create using ipmp.
> 
>  bnx0 + bnx1 ( interfaces are connected to primary switch A )
> 
>  bnx2 + bnx3 (  interfaces are connected to secondary switch B)


You have to use the old-school Solaris networking config rather than dladm & ipadm.

Here's an example config, for a host called "phy5". You'll need to tweak the addresses and which of the interfaces you're using.

It's slightly complicated because the 'dmz' subnet is small, so we use another overlap subnet for the test addresses.

Ben


cat >> /etc/hosts <<EOF
10.11.0.175 phy5
10.88.0.175     phy5p loghost
10.88.0.15  phy5pt1
10.88.0.25  phy5pt3
10.99.0.15    phy5t0
10.99.0.25    phy5t2
EOF

cat >> /etc/inet/netmasks <<EOF
10.11.0.160 255.255.255.224
10.88.0.0 255.255.255.0
10.99.0.0 255.255.255.0
EOF

echo "ipmp phy5 up" > /etc/hostname.dmz0
echo "ipmp phy5p up" > /etc/hostname.private0

echo "phy5t0 netmask + broadcast + -failover group dmz0 up" > /etc/hostname.bnx0
echo "phy5t2 netmask + broadcast + -failover group dmz0 standby up" > /etc/hostname.bnx2
echo "phy5pt1 netmask + broadcast + -failover group private0 up" > /etc/hostname.bnx1
echo "phy5pt3 netmask + broadcast + -failover group private0 standby up" > /etc/hostname.bnx3

echo 10.11.0.161 > /etc/defaultrouter

init 6




--
http://bens.me.uk


From garrett.damore at dey-sys.com  Sun Jun 23 07:38:45 2013
From: garrett.damore at dey-sys.com (Garrett D'Amore)
Date: Sun, 23 Jun 2013 17:38:45 +0600
Subject: [OmniOS-discuss] kstat -p gives segfault on OmniOS r151006
In-Reply-To: <51C6D806.4090404@smidsrod.no>
References: <51C6D806.4090404@smidsrod.no>
Message-ID: <E7A59186-0D59-46AA-B7C2-7B446077C2EF@dey-sys.com>

I've noticed lately that kstat seems to segfault when asked for a non existent stat. I have not had time to investigate further and I can't yet confirm that this problem exists in current illumos.  I will look soon though.  

Sent from my iPhone

On Jun 23, 2013, at 5:12 PM, Robin Smidsr?d <robin at smidsrod.no> wrote:

> Hi everyone,
> 
> I'm having a problem with kstat -p segfaulting on me.
> 
> I've included the output from truss here:
> https://gist.github.com/robinsmidsrod/5844493
> 
> A user on irc (gcbirzan) confirmed that he did not get a segfault on a
> clean install of r151006, so it seems this might be related to some
> stmf_tgt-related configuration which is confusing kstat. He also
> confirmed that he got the same segfault on his system that has some
> iscsi targets setup. This is his exact uttering:
> 
> "<gcbirzan> I get the same :) but I always assumed it's because I hacked
> libiscsit to have more than 255 targets"
> 
> I have not hacked anything on my system, running standard versions of
> all software.
> 
> Any chance of a fix and a backport to stable?
> 
> Not sure what kind of info you'd need to debug things further, but ask
> and I shall provide.
> 
> -- Robin
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From johan.kragsterman at capvert.se  Tue Jun 25 01:46:28 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Tue, 25 Jun 2013 07:46:28 +0200
Subject: [OmniOS-discuss] Pfsense KVM guest complaining about DAD ipv6
In-Reply-To: <1781842371.7137.1372106399551.JavaMail.root@blackdot.be>
References: <1781842371.7137.1372106399551.JavaMail.root@blackdot.be>
Message-ID: <OF8CF1C0AE.27DEAF81-ONC1257B95.001FB893-C1257B95.001FB898@inse.com>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130625/c5de2016/attachment.html>

From johan.kragsterman at capvert.se  Tue Jun 25 02:40:50 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Tue, 25 Jun 2013 08:40:50 +0200
Subject: [OmniOS-discuss] Pfsense KVM guest complaining about DAD ipv6
In-Reply-To: <61BDC4FB-411E-4BF6-BE29-2504151ABE1B@blackdot.be>
References: <61BDC4FB-411E-4BF6-BE29-2504151ABE1B@blackdot.be>,
	<1781842371.7137.1372106399551.JavaMail.root@blackdot.be>
	<OF8CF1C0AE.27DEAF81-ONC1257B95.001FB893-C1257B95.001FB898@inse.com>
Message-ID: <OF4EF88961.7E53C36C-ONC1257B95.0024B2D1-C1257B95.0024B2D6@inse.com>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130625/4b0a0ca4/attachment.html>

From jorge at blackdot.be  Tue Jun 25 02:30:31 2013
From: jorge at blackdot.be (Jorge Schrauwen)
Date: Tue, 25 Jun 2013 08:30:31 +0200 (CEST)
Subject: [OmniOS-discuss] Pfsense KVM guest complaining about DAD ipv6
In-Reply-To: <OF8CF1C0AE.27DEAF81-ONC1257B95.001FB893-C1257B95.001FB898@inse.com>
References: <1781842371.7137.1372106399551.JavaMail.root@blackdot.be>
	<OF8CF1C0AE.27DEAF81-ONC1257B95.001FB893-C1257B95.001FB898@inse.com>
Message-ID: <61BDC4FB-411E-4BF6-BE29-2504151ABE1B@blackdot.be>

Unfortunately I have experienced issues with both Arch Linux, CentOS and Ubuntu. Although they just silently refuse to bind the IPv6 Addr and print one line in message.

I've hit other problems with multicast traffic too. (mdns for example).

If IPv6 is not important you could install in vbox/vmware and convert the disk image. But that is a bit cumbersum.

Regards

Jorge

On 25 Jun 2013, at 07:47, "Johan Kragsterman" <johan.kragsterman at capvert.se> wrote:

> Thanks very much, Jorge! Wouldn't have discovering this without your help!
> 
> I don't have any problems with this in Linux, never seen the problem there whatsoever, but with Pfsense it gets fatal, since it doesn't install.
> 
> I will post this also on smartos-discuss.
> 
> Rgrds Johan
> 
> -----Jorge Schrauwen <jorge at blackdot.be> skrev: -----
> Till: johan.kragsterman at capvert.se
> Fr?n: Jorge Schrauwen <jorge at blackdot.be>
> Datum: 2013.06.24 22:39
> ?rende: Re: [OmniOS-discuss] Pfsense KVM guest complaining about DAD ipv6
> 
> Hi Johan,
> 
> I don't subscribe to the OmniOS-discuss list but I follow it via the archive when I have some free time.
> It's a bit late and this is an out of list reply but... the problem you are seeing is a generic KVM on Solaris problem
> 
> It is described here: https://github.com/joyent/illumos-kvm-cmd/issues/13
> Unfortunately there does not seem to be much motivation from Joyent to fix it.
> 
> Hope this was at least somewhat helpful.
> 
> Regards
> 
> Jorge
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130625/91e4d610/attachment.html>

From rm at joyent.com  Tue Jun 25 08:50:17 2013
From: rm at joyent.com (Robert Mustacchi)
Date: Tue, 25 Jun 2013 05:50:17 -0700
Subject: [OmniOS-discuss] [smartos-discuss] Re: Pfsense KVM guest
 complaining about DAD ipv6
In-Reply-To: <OF8CF1C0AE.27DEAF81-ONC1257B95.001FB893-C1257B95.001FB898@inse.com>
References: <1781842371.7137.1372106399551.JavaMail.root@blackdot.be>
	<OF8CF1C0AE.27DEAF81-ONC1257B95.001FB893-C1257B95.001FB898@inse.com>
Message-ID: <51C99209.3030700@joyent.com>

On 06/24/2013 10:46 PM, Johan Kragsterman wrote:
> Thanks very much, Jorge! Wouldn't have discovering this without your help!
> 
> I don't have any problems with this in Linux, never seen the problem there 
> whatsoever, but with Pfsense it gets fatal, since it doesn't install.
> 
> I will post this also on smartos-discuss.
> 
> Rgrds Johan
> 
> -----Jorge Schrauwen <jorge at blackdot.be> skrev: -----
> Till: johan.kragsterman at capvert.se
> Fr?n: Jorge Schrauwen <jorge at blackdot.be>
> Datum: 2013.06.24 22:39
> ?rende: Re: [OmniOS-discuss] Pfsense KVM guest complaining about DAD ipv6
> 
> Hi Johan,
> 
> I don't subscribe to the OmniOS-discuss list but I follow it via the archive 
> when I have some free time.
> It's a bit late and this is an out of list reply but... the problem you are 
> seeing is a generic KVM on Solaris problem
> 
> It is described here: https://github.com/joyent/illumos-kvm-cmd/issues/13
> Unfortunately there does not seem to be much motivation from Joyent to fix it.

I understand the problem here and am happy to help talk someone through
what needs to be done to fix this in the core OS. Unfortunately it just
takes time and I have had to prioritize other work first. It requires
adding a bit of plumbing up through the stack and exposing something new
in dlpi.

If someone would like to do it ahead of me getting cycles, I'm happy to
talk them through privately what needs to be done.

Robert

From jesus at omniti.com  Tue Jun 25 10:03:47 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Tue, 25 Jun 2013 10:03:47 -0400
Subject: [OmniOS-discuss] [smartos-discuss] Re: Pfsense KVM guest
 complaining about DAD ipv6
In-Reply-To: <51C99209.3030700@joyent.com>
References: <1781842371.7137.1372106399551.JavaMail.root@blackdot.be>
	<OF8CF1C0AE.27DEAF81-ONC1257B95.001FB893-C1257B95.001FB898@inse.com>
	<51C99209.3030700@joyent.com>
Message-ID: <CACLsApvRwOj--FG0BNJ7Jp02FtYHpJNvOu9uEwN+QjVtd-haxA@mail.gmail.com>

Robert, can you articulate the API you intended to add to DLPI?  From
there, I think connecting the dots would be quite straight forward.


On Tue, Jun 25, 2013 at 8:50 AM, Robert Mustacchi <rm at joyent.com> wrote:

> On 06/24/2013 10:46 PM, Johan Kragsterman wrote:
> > Thanks very much, Jorge! Wouldn't have discovering this without your
> help!
> >
> > I don't have any problems with this in Linux, never seen the problem
> there
> > whatsoever, but with Pfsense it gets fatal, since it doesn't install.
> >
> > I will post this also on smartos-discuss.
> >
> > Rgrds Johan
> >
> > -----Jorge Schrauwen <jorge at blackdot.be> skrev: -----
> > Till: johan.kragsterman at capvert.se
> > Fr?n: Jorge Schrauwen <jorge at blackdot.be>
> > Datum: 2013.06.24 22:39
> > ?rende: Re: [OmniOS-discuss] Pfsense KVM guest complaining about DAD ipv6
> >
> > Hi Johan,
> >
> > I don't subscribe to the OmniOS-discuss list but I follow it via the
> archive
> > when I have some free time.
> > It's a bit late and this is an out of list reply but... the problem you
> are
> > seeing is a generic KVM on Solaris problem
> >
> > It is described here:
> https://github.com/joyent/illumos-kvm-cmd/issues/13
> > Unfortunately there does not seem to be much motivation from Joyent to
> fix it.
>
> I understand the problem here and am happy to help talk someone through
> what needs to be done to fix this in the core OS. Unfortunately it just
> takes time and I have had to prioritize other work first. It requires
> adding a bit of plumbing up through the stack and exposing something new
> in dlpi.
>
> If someone would like to do it ahead of me getting cycles, I'm happy to
> talk them through privately what needs to be done.
>
> Robert
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>



-- 

Theo Schlossnagle

http://omniti.com/is/theo-schlossnagle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130625/0556fa6a/attachment.html>

From nuno at diogonet.com  Tue Jun 25 15:06:51 2013
From: nuno at diogonet.com (Nuno Diogo)
Date: Tue, 25 Jun 2013 15:06:51 -0400
Subject: [OmniOS-discuss] kernel smb server SPNEGO support
Message-ID: <CANJD8ncc_zLcs8AnPEJX-8=nvKgXiWVcaqLePMZ9SRkNe61rUw@mail.gmail.com>

Gurus,
When I attempt to access a share via FQDN I get "The account is not
authorized to log in from this station" error message.  When accessing via
IP or host name everything works as expected.
I've read that there's an ongoing bug (sing 2009?) regarding SPNEGO support
in the built in smb server.(https://www.illumos.org/issues/1122) which
causes this.

Is this still being worked on?
Also, are there plans to keep the built in SMB server component up to date
with MS implementations? (SMB v2.1 and v3 etc)

Thank you for all for what is now my go to server OS (can't beat ZFS with
built in NFS/SMB sharing for ESX datastores!)

-----------------
Nuno Diogo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130625/97403f9a/attachment.html>

From gate03 at landcroft.co.uk  Sun Jun 30 10:09:33 2013
From: gate03 at landcroft.co.uk (Michael Mounteney)
Date: Sun, 30 Jun 2013 20:09:33 +1000
Subject: [OmniOS-discuss] lofs filesystem not seen inside zone
Message-ID: <20130630200933.6ed76b59@dickless.landy.net>

Hello, my zones setup appears to be inconsistent and inexplicable
(polite word for wrong) in its treatment of filesystems imported into
zones.

The system has a rpool/home ZFS which is just a container for five
'child' volumes, thus:

    root at mundo:~# zfs list | grep -w home
    rpool/home                  46.3G   134G    37K  /home
    rpool/home/business          288M   134G   288M  /home/business
    rpool/home/common           11.6G   134G  11.6G  /home/common
    rpool/home/installs         40.1M   134G  40.1M  /home/installs
    rpool/home/mounty           33.4G   134G  33.4G  /home/mounty
    rpool/home/sheila           1009M   134G  1009M  /home/sheila

What does work correctly is importing /home into a zone:

    root at mundo:~# zonecfg -z person export
    ...
    add fs
    set dir=/home
    set special=/home
    set type=lofs
    end
    ...

and that makes all five 'child' volumes appear at /home in the zone.
But what doesn't is importing the 'child' volumes directly, it appears:

    root at mundo:~# zonecfg -z zamba export
    ...
    add fs
    set dir=/home/common
    set special=/home/common
    set type=lofs
    end
    add fs
    set dir=/home/sheila
    set special=/home/sheila
    set type=lofs
    end
    ...

but the two volumes are not seen:

    root at mundo:~# zlogin zamba
    [Connected to zone 'zamba' pts/3]
    Last login: Sun Jun 30 02:23:32 on pts/3
    OmniOS 5.11	omnios-8d266aa	2013.05.04
    root at zamba:~# ls -la /home
    total 2
    dr-xr-xr-x  1 root root  1 Jun 30 02:12 .
    drwxr-xr-x 19 root root 21 Jun 16 08:35 ..

Even more wierdly, from the global zone it seems that they ARE present:

    root at zamba:~# shutdown -g0 -i5 -y

    Shutdown started.    Sun Jun 30 10:07:41 UTC 2013

    Changing to init state 5 - please wait
    Broadcast Message from root (pts/3) on zamba Sun Jun 30 10:07:41...
    THE SYSTEM zamba IS BEING SHUT DOWN NOW ! ! !
    Log off now or risk your files being damaged

    root at zamba:~# 
    [Connection to zone 'zamba' pts/3 closed]
    root at mundo:/# ls -l /zone/zamba/root/home/
    total 3
    drwxr-xr-x 2 root root 2 Jun 30 20:06 common
    drwxr-xr-x 2 root root 2 Jun 30 20:06 sheila

Any idea why ?  Thanks in expectation.

Michael.

From ben at fluffy.co.uk  Sun Jun 30 10:17:04 2013
From: ben at fluffy.co.uk (Ben Summers)
Date: Sun, 30 Jun 2013 11:17:04 +0100
Subject: [OmniOS-discuss] lofs filesystem not seen inside zone
In-Reply-To: <20130630200933.6ed76b59@dickless.landy.net>
References: <20130630200933.6ed76b59@dickless.landy.net>
Message-ID: <495FE2E7-15C5-4B40-9439-EB98F630E70B@fluffy.co.uk>


On 30 Jun 2013, at 11:09, Michael Mounteney <gate03 at landcroft.co.uk> wrote:

> Hello, my zones setup appears to be inconsistent and inexplicable
> (polite word for wrong) in its treatment of filesystems imported into
> zones.
> 
> 
> What does work correctly is importing /home into a zone:
> 
>    root at mundo:~# zonecfg -z person export
>    ...
>    add fs
>    set dir=/home
>    set special=/home
>    set type=lofs
>    end
>    ...


Is there a reason why you're not just delegating the ZFS filesystem to the zone?

  add dataset
  set name=rpool/home
  end

Then doing all the admin of the child filesystems inside the zone?

Ben




--
http://bens.me.uk


From vab at bb-c.de  Sun Jun 30 10:32:48 2013
From: vab at bb-c.de (Volker A. Brandt)
Date: Sun, 30 Jun 2013 12:32:48 +0200
Subject: [OmniOS-discuss] lofs filesystem not seen inside zone
In-Reply-To: <20130630200933.6ed76b59@dickless.landy.net>
References: <20130630200933.6ed76b59@dickless.landy.net>
Message-ID: <20944.2384.421236.677563@glaurung.bb-c.de>

Michael Mounteney writes:
[...]
> and that makes all five 'child' volumes appear at /home in the zone.
> But what doesn't is importing the 'child' volumes directly, it
> appears:
> 
>     root at mundo:~# zonecfg -z zamba export
>     ...
>     add fs
>     set dir=/home/common
>     set special=/home/common
>     set type=lofs
>     end
>     add fs
>     set dir=/home/sheila
>     set special=/home/sheila
>     set type=lofs
>     end
>     ...
> 
> but the two volumes are not seen:

Have you disabled the automounter map for the home directories?
At least in the zone you should do that.


Best 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 jon.koslung at gmail.com  Sun Jun 30 13:21:01 2013
From: jon.koslung at gmail.com (Jon Koslung)
Date: Sun, 30 Jun 2013 17:21:01 +0400
Subject: [OmniOS-discuss] ESXi,
 OmniOS VM and problem with portforwarding (TCP_NODELAY: Invalid
 argument)
Message-ID: <F5757C505A3B4A5FB06AB79417D9CF7D@gmail.com>

Hi, I'm trying to SSH with portforwarding to the OmniOS VM (with two aggregated passthrough NICs) on ESXi, but I keep getting "sshd[695]: [ID 800047 auth.error] error: setsockopt TCP_NODELAY: Invalid argument" in messages. Normal SSH works fine.  

Anyone have any tips/advice?

Thank you.

Please see below for details.


Client ssh command:
"ssh -L 4200:localhost:4243 username at server.hostname"

It seems to connect normal, but when my CrashPlan clients try to connect I get this in messages:
"Jun 29 22:42:43 hostname sshd[695]: [ID 800047 auth.error] error: setsockopt TCP_NODELAY: Invalid argument
Jun 29 22:45:35 hostname last message repeated 1 time
Jun 29 22:52:50 hostname sshd[1081]: [ID 800047 auth.error] error: setsockopt TCP_NODELAY: Invalid argument"

The CrashPlan service is running fine and listening on port 4242.
"#ps aux |grep java
root       566  0.0  4.1152228126744 ?        S 01:55:21  0:25 /usr/bin/java -Dfi ? "

"#netstat -na | grep LISTEN | grep 42
      *.4242               *.*                0      0 65880      0 LISTEN
::ffff:127.0.0.1.4243                   *.*                             0      0 128000      0 LISTEN
      *.4242                            *.*                             0      0 65880      0 LISTEN"


I have tried setting this in sshd_config, but did not work:
"AllowTcpPortforwarding yes  
GatewayPorts yes"


This is my sshd_config:

#
# Copyright (c) 2001, 2010, Oracle and/or its affiliates. All rights reserved.
#
# Configuration file for sshd(1m) (see also sshd_config(4))
#

# Protocol versions supported
#
# The sshd shipped in this release of Solaris has support for major versions
# 1 and 2.  It is recommended due to security weaknesses in the v1 protocol
# that sites run only v2 if possible. Support for v1 is provided to help sites
# with existing ssh v1 clients/servers to transition.  
# Support for v1 may not be available in a future release of Solaris.
#
# To enable support for v1 an RSA1 key must be created with ssh-keygen(1).
# RSA and DSA keys for protocol v2 are created by /etc/init.d/sshd if they
# do not already exist, RSA1 keys for protocol v1 are not automatically created.

# Uncomment ONLY ONE of the following Protocol statements.

# Only v2 (recommended)
Protocol 2

# Both v1 and v2 (not recommended)
#Protocol 2,1

# Only v1 (not recommended)
#Protocol 1

# Listen port (the IANA registered port number for ssh is 22)
Port 22

# The default listen address is all interfaces, this may need to be changed
# if you wish to restrict the interfaces sshd listens on for a multi homed host.
# Multiple ListenAddress entries are allowed.

# IPv4 only
ListenAddress 0.0.0.0
# IPv4 & IPv6
#ListenAddress ::

# If port forwarding is enabled (default), specify if the server can bind to
# INADDR_ANY.  
# This allows the local port forwarding to work when connections are received
# from any remote host.
#GatewayPorts no #default
GatewayPorts yes

# X11 tunneling options
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes

# The maximum number of concurrent unauthenticated connections to sshd.
# start:rate:full see sshd(1) for more information.
# The default is 10 unauthenticated clients.
#MaxStartups 10:30:60

# Banner to be printed before authentication starts.
Banner /etc/issue

# Should sshd print the /etc/motd file and check for mail.
# On Solaris it is assumed that the login shell will do these (eg /etc/profile).
PrintMotd no

# KeepAlive specifies whether keep alive messages are sent to the client.
# See sshd(1) for detailed description of what this means.
# Note that the client may also be sending keep alive messages to the server.
KeepAlive yes

# Syslog facility and level  
SyslogFacility auth
LogLevel info

#
# Authentication configuration
#  

# Host private key files
# Must be on a local disk and readable only by the root user (root:sys 600).
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key

# Length of the server key
# Default 768, Minimum 512
ServerKeyBits 768

# sshd regenerates the key every KeyRegenerationInterval seconds.
# The key is never stored anywhere except the memory of sshd.
# The default is 1 hour (3600 seconds).
KeyRegenerationInterval 3600

# Ensure secure permissions on users .ssh directory.
StrictModes yes

# Length of time in seconds before a client that hasn't completed
# authentication is disconnected.
# Default is 600 seconds. 0 means no time limit.
LoginGraceTime 600

# Maximum number of retries for authentication
# Default is 6. Default (if unset) for MaxAuthTriesLog is MaxAuthTries / 2
MaxAuthTries  ?  6
MaxAuthTriesLog  ?  3

# Are logins to accounts with empty passwords allowed.
# If PermitEmptyPasswords is no, pass PAM_DISALLOW_NULL_AUTHTOK  
# to pam_authenticate(3PAM).
PermitEmptyPasswords no

# To disable tunneled clear text passwords, change PasswordAuthentication to no.
PasswordAuthentication yes

# Are root logins permitted using sshd.
# Note that sshd uses pam_authenticate(3PAM) so the root (or any other) user
# maybe denied access by a PAM module regardless of this setting.
# Valid options are yes, without-password, no.
PermitRootLogin no

# sftp subsystem
Subsystem  ?  sftp  ?  internal-sftp


# SSH protocol v1 specific options
#
# The following options only apply to the v1 protocol and provide
# some form of backwards compatibility with the very weak security
# of /usr/bin/rsh.  Their use is not recommended and the functionality
# will be removed when support for v1 protocol is removed.

# Should sshd use .rhosts and .shosts for password less authentication.
IgnoreRhosts yes
RhostsAuthentication no

# Rhosts RSA Authentication
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts.
# If the user on the client side is not root then this won't work on
# Solaris since /usr/bin/ssh is not installed setuid.
RhostsRSAAuthentication no

# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication.
#IgnoreUserKnownHosts yes

# Is pure RSA authentication allowed.
# Default is yes
RSAAuthentication yes

#portforwarding #non-default
AllowTcpForwarding yes



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

