From steve at linuxsuite.org  Fri Feb  1 10:26:35 2013
From: steve at linuxsuite.org (steve at linuxsuite.org)
Date: Fri, 1 Feb 2013 10:26:35 -0500
Subject: [OmniOS-discuss] Fault detection
Message-ID: <92e38fc99adc538b88dcea3e47ec2a3f.squirrel@emailmg.netfirms.com>


  Howdy!

        I am trying to test the fault management system, so I yanked out
one of the disks in the mirrored rpool. It detects the failure and resilvers
the hot spare, syslogs the condition ,, but the fault management system
doesn't seem
to notice (as per fmadm faulty -a see below) and I don't get a
notification...
Shouldn't fm facility see this "error"? Or how can I test for failed disk
detection/notification, removing one of the disks in a mirrored volume should
be enough?

root at live-dfs-2:~# zpool status rpool
  pool: rpool
 state: DEGRADED
status: One or more devices has been removed by the administrator.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Online the device using 'zpool online' or replace the device with
        'zpool replace'.
  scan: resilvered 13.9G in 0h2m with 0 errors on Thu Jan 31 11:54:40 2013
config:

        NAME            STATE     READ WRITE CKSUM
        rpool           DEGRADED     0     0     0
          mirror-0      DEGRADED     0     0     0
            c1t0d0s0    ONLINE       0     0     0
            spare-1     DEGRADED     0     0     0
              c1t1d0s0  REMOVED      0     0     0
              c1t2d0s0  ONLINE       0     0     0
        spares
          c1t2d0s0      INUSE     currently in use

errors: No known data errors


  fmadm sees only historical rsync fault.. ??? in which I did get a
notification.


root at live-dfs-2:~# fmadm faulty -a
--------------- ------------------------------------  --------------
---------
TIME            EVENT-ID                              MSG-ID         SEVERITY
--------------- ------------------------------------  --------------
---------
Jan 28 11:52:22 2d48eac3-ce73-e0f0-9487-b2aee3fbeb74  SMF-8000-YX    major

Host        : dfs2
Platform    : PowerEdge-R710    Chassis_id  : 93FCWL1
Product_sn  :

Fault class : defect.sunos.smf.svc.maintenance
Affects     : svc:///network/rsyncd:default
                  ok and in service
Problem in  : svc:///network/rsyncd:default
                  repair attempted

Description : A service failed - a method is failing in a retryable manner
but
              too often.
              Refer to http://illumos.org/msg/SMF-8000-YX for more
information.

Response    : The service has been placed into the maintenance state.

Impact      : svc:/network/rsyncd:default is unavailable.

Action      : Run 'svcs -xv svc:/network/rsyncd:default' to determine the
              generic reason why the service failed, the location of any
              logfiles, and a list of other services impacted.





From GAlbitz at albitz.biz  Fri Feb  1 14:45:09 2013
From: GAlbitz at albitz.biz (Grant Albitz)
Date: Fri, 1 Feb 2013 19:45:09 +0000
Subject: [OmniOS-discuss] Dell H310 in R720
In-Reply-To: <0B8E74B73A30D941847CF77E766E365C126100D2@ALPHA.PSC.Net>
References: <0B8E74B73A30D941847CF77E766E365C126100D2@ALPHA.PSC.Net>
Message-ID: <0B8E74B73A30D941847CF77E766E365C126100E7@ALPHA.PSC.Net>



I know this item has been discussed before but i am not able to find a solution. I am trying to install omnios on a r720 with a h310 raid controller. The drives are in jbod mode but are not detected. I have seen some articles which lead me to believe i can use this card if I use update_drv and add the pcie id of the raid card. Those articles tend to use scanpci which does not exist in omnios.

The h310 is the mini type which may ultimately be an issue, from what i originally read i did not think i would need to flash the h310 though.

From tbingen at homeshore.be  Sat Feb  2 02:20:16 2013
From: tbingen at homeshore.be (Thierry Bingen)
Date: Sat, 2 Feb 2013 08:20:16 +0100
Subject: [OmniOS-discuss] BIND DNS server
Message-ID: <92E0A86F-D2E1-4A12-8823-887A79EAA4E5@homeshore.be>

I can't complete the installation of my DNS server. 
I installed the following packages: 
 - pkg:/omniti/server/dns/bind at 9.9.2.1-0.151004
 - pkg:/network/dns/bind at 9.9.2.1-0.151004
Comparing with another Illumos distro, it looks as if I were missing a package such as:
 - pkg:/service/network/dns/bind
Thanks for your hints!
T.

From GAlbitz at albitz.biz  Sat Feb  2 08:50:05 2013
From: GAlbitz at albitz.biz (Grant Albitz)
Date: Sat, 2 Feb 2013 13:50:05 +0000
Subject: [OmniOS-discuss] Perc h310 (mini)
Message-ID: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>

I know the perc h310 has been discussed before. From what I can tell you can use a h310 if you flash it to the LSI firmware. Does anyone know if you can get the h310 mini to work? It already supports jbod (as did the original perc h310). I have come across some posts saying you can use update_drv with other cards. I was not able to identify the card to try this. Is there a scanpci type of command in omnios? Any input would be appreciated. I can scrap the h310 mini if I have to, but the current chassis cabling will not work with any other card. I would live to keep it as is if possible.




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

From tbingen at homeshore.be  Sat Feb  2 10:16:41 2013
From: tbingen at homeshore.be (Thierry Bingen)
Date: Sat, 2 Feb 2013 16:16:41 +0100
Subject: [OmniOS-discuss] BIND DNS server
In-Reply-To: <AD579A3B-4A4C-4D13-9E91-2FF50F6E3871@uni-ulm.de>
References: <92E0A86F-D2E1-4A12-8823-887A79EAA4E5@homeshore.be>
	<AD579A3B-4A4C-4D13-9E91-2FF50F6E3871@uni-ulm.de>
Message-ID: <1D62B551-5D52-4359-9699-E240963231AA@homeshore.be>

Hi Steffen, 

Excellent advice, and it worked like a charm. 

Curiously ms.omniti.com locates "named" in /opt/omni/sbin/ while your uulm.mawi locates it in /usr/local/sbin/. 
The main advantage of your package over that of Omniti is that you also provide the SMF manifest; most pleasant for Solaris addicts... 

Thanks, 
T. 

The URL of your repository on the page http://omnios.omniti.com/wiki.php/Packaging is a bit short; I had to add a "release" at the end to add you as a publisher. 

On 2 Feb 2013, at 15:32, Steffen Fritzsche <steffen.fritzsche at uni-ulm.de> wrote:

> Hi Thierry,
> 
> current stable and bloody only contains the client side bind tools, not the server. You can find the server packages in the ms.omniti.com or my uulm.mawi package providers. See the wiki and the linked package listings for details.
> 
> Cheers,
> Steffen
> 
> 
> Am 02.02.2013 um 08:20 schrieb Thierry Bingen <tbingen at homeshore.be>:
> 
>> I can't complete the installation of my DNS server. 
>> I installed the following packages: 
>> - pkg:/omniti/server/dns/bind at 9.9.2.1-0.151004
>> - pkg:/network/dns/bind at 9.9.2.1-0.151004
>> Comparing with another Illumos distro, it looks as if I were missing a package such as:
>> - pkg:/service/network/dns/bind
>> Thanks for your hints!
>> T.


From esproul at omniti.com  Sat Feb  2 10:47:38 2013
From: esproul at omniti.com (Eric Sproul)
Date: Sat, 2 Feb 2013 10:47:38 -0500
Subject: [OmniOS-discuss] Perc h310 (mini)
In-Reply-To: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>
References: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>
Message-ID: <CA+QY2RRz-Sq5tSqTMALA3gMq1P-5-uVEvcroibknTtQb8LH=rw@mail.gmail.com>

>From the installer shell you can use prtconf -pv and look for "scsi"
devices.  You can see the vendor and device ids within. We have pciutils
(lspci & friends) available after install. There is an open ticket to get
that added to the installer environments.

On Saturday, February 2, 2013, Grant Albitz wrote:

>  I know the perc h310 has been discussed before. From what I can tell you
> can use a h310 if you flash it to the LSI firmware. Does anyone know if
> you can get the h310 mini to work? It already supports jbod (as did the
> original perc h310). I have come across some posts saying you can
> use update_drv with other cards. I was not able to identify the card to
> try this. Is there a scanpci type of command in omnios? Any input would
> be appreciated. I can scrap the h310 mini if I have to, but the current
> chassis cabling will not work with any other card. I would live to keep it
> as is if possible.
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130202/cf22c828/attachment.html>

From GAlbitz at albitz.biz  Sat Feb  2 11:06:15 2013
From: GAlbitz at albitz.biz (Grant Albitz)
Date: Sat, 2 Feb 2013 16:06:15 +0000
Subject: [OmniOS-discuss] Perc h310 (mini)
In-Reply-To: <CA+QY2RRz-Sq5tSqTMALA3gMq1P-5-uVEvcroibknTtQb8LH=rw@mail.gmail.com>
References: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>,
	<CA+QY2RRz-Sq5tSqTMALA3gMq1P-5-uVEvcroibknTtQb8LH=rw@mail.gmail.com>
Message-ID: <0B8E74B73A30D941847CF77E766E365C12611298@ALPHA.PSC.Net>

here is what it came back with, based on this any recommendations for what i can try? format shows no disks attached, i have 3 disks as jbod attached to the controller at the moment.



compatible: 'pciex1000,73.1028.1f51.3' + 'pciex1000,73.1028.1f51' + 'pciex1000,73.3' + 'pciex1000,73' + pciexclass,010400' + 'pciexclass,0104' + 'pci1000,73.1028.1f51.3' + 'pci1000,73.1028.1f51' + 'pci1028,1f51' + 'pci1000,73.3' + 'pci1000,73' + 'pciclass,010400' + 'pciclass,0104'

model: "Raid controller'
subsystem-vendor-id: 00001028
subsystem-id: 00001f51
vendor-id: 00001000
device-id: 00000073
name: 'pci1028,1f51'

________________________________
From: Eric Sproul [esproul at omniti.com]
Sent: Saturday, February 02, 2013 10:47 AM
To: Grant Albitz
Cc: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] Perc h310 (mini)

>From the installer shell you can use prtconf -pv and look for "scsi" devices.  You can see the vendor and device ids within. We have pciutils (lspci & friends) available after install. There is an open ticket to get that added to the installer environments.

On Saturday, February 2, 2013, Grant Albitz wrote:

I know the perc h310 has been discussed before. From what I can tell you can use a h310 if you flash it to the LSI firmware. Does anyone know if you can get the h310 mini to work? It already supports jbod (as did the original perc h310). I have come across some posts saying you can use update_drv with other cards. I was not able to identify the card to try this. Is there a scanpci type of command in omnios? Any input would be appreciated. I can scrap the h310 mini if I have to, but the current chassis cabling will not work with any other card. I would live to keep it as is if possible.




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

From esproul at omniti.com  Sat Feb  2 16:22:36 2013
From: esproul at omniti.com (Eric Sproul)
Date: Sat, 2 Feb 2013 16:22:36 -0500
Subject: [OmniOS-discuss] Perc h310 (mini)
In-Reply-To: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>
References: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>
Message-ID: <CA+QY2RTVT1ABfRRoeBtUd838Vw2Jox7O3-GLo5q7aUieNx+rDQ@mail.gmail.com>

>From the installer shell you can use prtconf -pv and look for "scsi"
devices.  You can see the vendor and device ids within. We have pciutils
(lspci

On Saturday, February 2, 2013, Grant Albitz wrote:

I know the perc h310 has been discussed before. From what I can tell you
can use a h310 if you flash it to the LSI firmware. Does anyone know if you
can get the h310 mini to work? It already supports jbod (as did the
original perc h310). I have come across some posts saying you can
use update_drv with other cards. I was not able to identify the card to try
this. Is there a scanpci type of command in omnios? Any input would be
appreciated. I can scrap the h310 mini if I have to, but the current
chassis cabling will not work with any other card. I would live to keep it
as is if possible.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130202/890c9ff9/attachment.html>

From esproul at omniti.com  Sat Feb  2 17:21:29 2013
From: esproul at omniti.com (Eric Sproul)
Date: Sat, 2 Feb 2013 17:21:29 -0500
Subject: [OmniOS-discuss] Perc h310 (mini)
In-Reply-To: <0B8E74B73A30D941847CF77E766E365C12611298@ALPHA.PSC.Net>
References: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>
	<CA+QY2RRz-Sq5tSqTMALA3gMq1P-5-uVEvcroibknTtQb8LH=rw@mail.gmail.com>
	<0B8E74B73A30D941847CF77E766E365C12611298@ALPHA.PSC.Net>
Message-ID: <CA+QY2RT4xY87UecnJ1U7YAVNJe4s4Btdurii4z8yT7fkw+RwAw@mail.gmail.com>

pciex1000,73 is most likely going to be mr_sas. It's also likely supported
out of the box on bloody. Might be nice to see if that's the case if that's
possible.
On Feb 2, 2013 11:08 AM, "Grant Albitz" <GAlbitz at albitz.biz> wrote:

>  here is what it came back with, based on this any recommendations for
> what i can try? format shows no disks attached, i have 3 disks as jbodattached to the controller at the moment.
>
>
>
> compatible: 'pciex1000,73.1028.1f51.3' + 'pciex1000,73.1028.1f51' +
> 'pciex1000,73.3' + 'pciex1000,73' + pciexclass,010400' + 'pciexclass,0104'
> + 'pci1000,73.1028.1f51.3' + 'pci1000,73.1028.1f51' + 'pci1028,1f51' +
> 'pci1000,73.3' + 'pci1000,73' + 'pciclass,010400' + 'pciclass,0104'
>
> model: "Raid controller'
> subsystem-vendor-id: 00001028
> subsystem-id: 00001f51
> vendor-id: 00001000
> device-id: 00000073
> name: 'pci1028,1f51'
>  ------------------------------
> *From:* Eric Sproul [esproul at omniti.com]
> *Sent:* Saturday, February 02, 2013 10:47 AM
> *To:* Grant Albitz
> *Cc:* omnios-discuss at lists.omniti.com
> *Subject:* Re: [OmniOS-discuss] Perc h310 (mini)
>
>  From the installer shell you can use prtconf -pv and look for "scsi"
> devices.  You can see the vendor and device ids within. We have pciutils
> (lspci & friends) available after install. There is an open ticket to get
> that added to the installer environments.
>
> On Saturday, February 2, 2013, Grant Albitz wrote:
>
>>  I know the perc h310 has been discussed before. From what I can tell
>> you can use a h310 if you flash it to the LSI firmware. Does anyone know
>> if you can get the h310 mini to work? It already supports jbod (as did
>> the original perc h310). I have come across some posts saying you can
>> use update_drv with other cards. I was not able to identify the card to
>> try this. Is there a scanpci type of command in omnios? Any input would
>> be appreciated. I can scrap the h310 mini if I have to, but the current
>> chassis cabling will not work with any other card. I would live to keep it
>> as is if possible.
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130202/e1e3a96d/attachment.html>

From GAlbitz at albitz.biz  Sat Feb  2 18:34:16 2013
From: GAlbitz at albitz.biz (Grant Albitz)
Date: Sat, 2 Feb 2013 23:34:16 +0000
Subject: [OmniOS-discuss] Perc h310 (mini)
In-Reply-To: <CA+QY2RT4xY87UecnJ1U7YAVNJe4s4Btdurii4z8yT7fkw+RwAw@mail.gmail.com>
References: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>
	<CA+QY2RRz-Sq5tSqTMALA3gMq1P-5-uVEvcroibknTtQb8LH=rw@mail.gmail.com>
	<0B8E74B73A30D941847CF77E766E365C12611298@ALPHA.PSC.Net>,
	<CA+QY2RT4xY87UecnJ1U7YAVNJe4s4Btdurii4z8yT7fkw+RwAw@mail.gmail.com>
Message-ID: <0B8E74B73A30D941847CF77E766E365C12611361@ALPHA.PSC.Net>

i am running the latest bloody with no success. update_drv with pciex1000,73 also didnt work so i am not sure.

________________________________
From: Eric Sproul [esproul at omniti.com]
Sent: Saturday, February 02, 2013 5:21 PM
To: Grant Albitz
Cc: omnios-discuss at lists.omniti.com
Subject: RE: [OmniOS-discuss] Perc h310 (mini)


pciex1000,73 is most likely going to be mr_sas. It's also likely supported out of the box on bloody. Might be nice to see if that's the case if that's possible.

On Feb 2, 2013 11:08 AM, "Grant Albitz" <GAlbitz at albitz.biz<mailto:GAlbitz at albitz.biz>> wrote:

here is what it came back with, based on this any recommendations for what i can try? format shows no disks attached, i have 3 disks as jbod attached to the controller at the moment.



compatible: 'pciex1000,73.1028.1f51.3' + 'pciex1000,73.1028.1f51' + 'pciex1000,73.3' + 'pciex1000,73' + pciexclass,010400' + 'pciexclass,0104' + 'pci1000,73.1028.1f51.3' + 'pci1000,73.1028.1f51' + 'pci1028,1f51' + 'pci1000,73.3' + 'pci1000,73' + 'pciclass,010400' + 'pciclass,0104'

model: "Raid controller'
subsystem-vendor-id: 00001028
subsystem-id: 00001f51
vendor-id: 00001000
device-id: 00000073
name: 'pci1028,1f51'

________________________________
From: Eric Sproul [esproul at omniti.com<mailto:esproul at omniti.com>]
Sent: Saturday, February 02, 2013 10:47 AM
To: Grant Albitz
Cc: omnios-discuss at lists.omniti.com<mailto:omnios-discuss at lists.omniti.com>
Subject: Re: [OmniOS-discuss] Perc h310 (mini)

>From the installer shell you can use prtconf -pv and look for "scsi" devices.  You can see the vendor and device ids within. We have pciutils (lspci & friends) available after install. There is an open ticket to get that added to the installer environments.

On Saturday, February 2, 2013, Grant Albitz wrote:

I know the perc h310 has been discussed before. From what I can tell you can use a h310 if you flash it to the LSI firmware. Does anyone know if you can get the h310 mini to work? It already supports jbod (as did the original perc h310). I have come across some posts saying you can use update_drv with other cards. I was not able to identify the card to try this. Is there a scanpci type of command in omnios? Any input would be appreciated. I can scrap the h310 mini if I have to, but the current chassis cabling will not work with any other card. I would live to keep it as is if possible.




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

From esproul at omniti.com  Sat Feb  2 21:46:32 2013
From: esproul at omniti.com (Eric Sproul)
Date: Sat, 2 Feb 2013 21:46:32 -0500
Subject: [OmniOS-discuss] Perc h310 (mini)
In-Reply-To: <0B8E74B73A30D941847CF77E766E365C12611361@ALPHA.PSC.Net>
References: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>
	<CA+QY2RRz-Sq5tSqTMALA3gMq1P-5-uVEvcroibknTtQb8LH=rw@mail.gmail.com>
	<0B8E74B73A30D941847CF77E766E365C12611298@ALPHA.PSC.Net>
	<CA+QY2RT4xY87UecnJ1U7YAVNJe4s4Btdurii4z8yT7fkw+RwAw@mail.gmail.com>
	<0B8E74B73A30D941847CF77E766E365C12611361@ALPHA.PSC.Net>
Message-ID: <CA+QY2RQhuHzWkY=0W9bm9UzRkv-pYJSu9NDNh39XFb-vN=YAuQ@mail.gmail.com>

I knew that ID sounded familiar: https://www.illumos.org/issues/3500

Support for the H310 is coming, pending this integration. Hit up Dan
McDonald on irc (danmcd) or join the thread on illumos-developer if you're
interested in testing his code. Once it does integrate it will shortly be
available in bloody.

Eric

On Saturday, February 2, 2013, Grant Albitz wrote:

>  i am running the latest bloody with no success. update_drvwith pciex1000,73also didntwork so iam not sure.
>  ------------------------------
> *From:* Eric Sproul [esproul at omniti.com <javascript:_e({}, 'cvml',
> 'esproul at omniti.com');>]
> *Sent:* Saturday, February 02, 2013 5:21 PM
> *To:* Grant Albitz
> *Cc:* omnios-discuss at lists.omniti.com <javascript:_e({}, 'cvml',
> 'omnios-discuss at lists.omniti.com');>
> *Subject:* RE: [OmniOS-discuss] Perc h310 (mini)
>
>   pciex1000,73 is most likely going to be mr_sas. It's also likely
> supported out of the box on bloody. Might be nice to see if that's the case
> if that's possible.
> On Feb 2, 2013 11:08 AM, "Grant Albitz" <GAlbitz at albitz.biz<javascript:_e({}, 'cvml', 'GAlbitz at albitz.biz');>>
> wrote:
>
>>  here is what it came back with, based on this any recommendations for
>> what i can try? format shows no disks attached, i have 3 disks as jbodattached to the controller at the moment.
>>
>>
>>
>> compatible: 'pciex1000,73.1028.1f51.3' + 'pciex1000,73.1028.1f51' +
>> 'pciex1000,73.3' + 'pciex1000,73' + pciexclass,010400' + 'pciexclass,0104'
>> + 'pci1000,73.1028.1f51.3' + 'pci1000,73.1028.1f51' + 'pci1028,1f51' +
>> 'pci1000,73.3' + 'pci1000,73' + 'pciclass,010400' + 'pciclass,0104'
>>
>> model: "Raid controller'
>> subsystem-vendor-id: 00001028
>> subsystem-id: 00001f51
>> vendor-id: 00001000
>> device-id: 00000073
>> name: 'pci1028,1f51'
>>  ------------------------------
>> *From:* Eric Sproul [esproul at omniti.com <javascript:_e({}, 'cvml',
>> 'esproul at omniti.com');>]
>> *Sent:* Saturday, February 02, 2013 10:47 AM
>> *To:* Grant Albitz
>> *Cc:* omnios-discuss at lists.omniti.com <javascript:_e({}, 'cvml',
>> 'omnios-discuss at lists.omniti.com');>
>> *Subject:* Re: [OmniOS-discuss] Perc h310 (mini)
>>
>>  From the installer shell you can use prtconf -pv and look for "scsi"
>> devices.  You can see the vendor and device ids within. We have pciutils
>> (lspci & friends) available after install. There is an open ticket to get
>> that added to the installer environments.
>>
>> On Saturday, February 2, 2013, Grant Albitz wrote:
>>
>>>  I know the perc h310 has been discussed before. From what I can tell
>>> you can use a h310 if you flash it to the LSI firmware. Does anyone
>>> know if you can get the h310 mini to work? It already supports jbod (as
>>> did the original perc h310). I have come across some posts saying you
>>> can use update_drv with other cards. I was not able to identify the
>>> card to try this. Is there a scanpci type of command in omnios? Any
>>> input would be appreciated. I can scrap the h310 mini if I have to, but
>>> the current chassis cabling will not work with any other card. I would live
>>> to keep it as is if possible.
>>>
>>>
>>>
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130202/27c2048c/attachment-0001.html>

From GAlbitz at albitz.biz  Sat Feb  2 22:53:00 2013
From: GAlbitz at albitz.biz (Grant Albitz)
Date: Sun, 3 Feb 2013 03:53:00 +0000
Subject: [OmniOS-discuss] Perc h310 (mini)
In-Reply-To: <CA+QY2RQhuHzWkY=0W9bm9UzRkv-pYJSu9NDNh39XFb-vN=YAuQ@mail.gmail.com>
References: <0B8E74B73A30D941847CF77E766E365C12611249@ALPHA.PSC.Net>
	<CA+QY2RRz-Sq5tSqTMALA3gMq1P-5-uVEvcroibknTtQb8LH=rw@mail.gmail.com>
	<0B8E74B73A30D941847CF77E766E365C12611298@ALPHA.PSC.Net>
	<CA+QY2RT4xY87UecnJ1U7YAVNJe4s4Btdurii4z8yT7fkw+RwAw@mail.gmail.com>
	<0B8E74B73A30D941847CF77E766E365C12611361@ALPHA.PSC.Net>,
	<CA+QY2RQhuHzWkY=0W9bm9UzRkv-pYJSu9NDNh39XFb-vN=YAuQ@mail.gmail.com>
Message-ID: <0B8E74B73A30D941847CF77E766E365C12611398@ALPHA.PSC.Net>

ok i will see what i can get from him. if i use update_drv to add
update_drv -a -i 'pciex1000,73' mr_sas



it results in mr_sas invalid device detected.

________________________________
From: Eric Sproul [esproul at omniti.com]
Sent: Saturday, February 02, 2013 9:46 PM
To: Grant Albitz
Cc: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] Perc h310 (mini)

I knew that ID sounded familiar: https://www.illumos.org/issues/3500

Support for the H310 is coming, pending this integration. Hit up Dan McDonald on irc (danmcd) or join the thread on illumos-developer if you're interested in testing his code. Once it does integrate it will shortly be available in bloody.

Eric

On Saturday, February 2, 2013, Grant Albitz wrote:

i am running the latest bloody with no success. update_drv with pciex1000,73 also didnt work so i am not sure.

________________________________
From: Eric Sproul [esproul at omniti.com<http://www.cryptz.com/owa/UrlBlockedError.aspx>]
Sent: Saturday, February 02, 2013 5:21 PM
To: Grant Albitz
Cc: omnios-discuss at lists.omniti.com<http://www.cryptz.com/owa/UrlBlockedError.aspx>
Subject: RE: [OmniOS-discuss] Perc h310 (mini)


pciex1000,73 is most likely going to be mr_sas. It's also likely supported out of the box on bloody. Might be nice to see if that's the case if that's possible.

On Feb 2, 2013 11:08 AM, "Grant Albitz" <GAlbitz at albitz.biz<http://www.cryptz.com/owa/UrlBlockedError.aspx>> wrote:

here is what it came back with, based on this any recommendations for what i can try? format shows no disks attached, i have 3 disks as jbod attached to the controller at the moment.



compatible: 'pciex1000,73.1028.1f51.3' + 'pciex1000,73.1028.1f51' + 'pciex1000,73.3' + 'pciex1000,73' + pciexclass,010400' + 'pciexclass,0104' + 'pci1000,73.1028.1f51.3' + 'pci1000,73.1028.1f51' + 'pci1028,1f51' + 'pci1000,73.3' + 'pci1000,73' + 'pciclass,010400' + 'pciclass,0104'

model: "Raid controller'
subsystem-vendor-id: 00001028
subsystem-id: 00001f51
vendor-id: 00001000
device-id: 00000073
name: 'pci1028,1f51'

________________________________
From: Eric Sproul [esproul at omniti.com<http://www.cryptz.com/owa/UrlBlockedError.aspx>]
Sent: Saturday, February 02, 2013 10:47 AM
To: Grant Albitz
Cc: omnios-discuss at lists.omniti.com<http://www.cryptz.com/owa/UrlBlockedError.aspx>
Subject: Re: [OmniOS-discuss] Perc h310 (mini)

>From the installer shell you can use prtconf -pv and look for "scsi" devices.  You can see the vendor and device ids within. We have pciutils (lspci & friends) available after install. There is an open ticket to get that added to the installer environments.

On Saturday, February 2, 2013, Grant Albitz wrote:

I know the perc h310 has been discussed before. From what I can tell you can use a h310 if you flash it to the LSI firmware. Does anyone know if you can get the h310 mini to work? It already supports jbod (as did the original perc h310). I have come across some posts saying you can use update_drv with other cards. I was not able to identify the card to try this. Is there a scanpci type of command in omnios? Any input would be appreciated. I can scrap the h310 mini if I have to, but the current chassis cabling will not work with any other card. I would live to keep it as is if possible.




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

From johan.kragsterman at capvert.se  Tue Feb  5 03:01:39 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Tue, 5 Feb 2013 09:01:39 +0100
Subject: [OmniOS-discuss] remove old e1000g if...?
Message-ID: <OFB0227C8F.49D1C624-ONC1257B09.002C189F-C1257B09.002C18A7@inse.com>

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

From staf.wagemakers at gmail.com  Tue Feb  5 05:34:13 2013
From: staf.wagemakers at gmail.com (Staf Wagemakers)
Date: Tue, 5 Feb 2013 11:34:13 +0100
Subject: [OmniOS-discuss] remove old e1000g if...?
Message-ID: <CAOkCUXiSBLV=UuiO16Mkw5GnjuhFh=L1af-w1YHQA_J4MrJq5A@mail.gmail.com>

>
>  I tried ipadm and dladm to look for how to remove the old config, but
didn't find a way to do it.
>
> Can anyone help me out here? I don't want to configure the new nic before
I get rid of the old one.
>

Normally "dladm show-phys -P" and "dladm delete-phys" should do the trick.

regards,

--
staf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130205/2bb74e35/attachment.html>

From johan.kragsterman at capvert.se  Tue Feb  5 06:48:40 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Tue, 5 Feb 2013 12:48:40 +0100
Subject: [OmniOS-discuss] Vbf: Ang: Re:  remove old e1000g if...?
Message-ID: <OFB4FE1252.C2159817-ONC1257B09.0040E16F-C1257B09.0040E173@inse.com>

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

From staf.wagemakers at gmail.com  Tue Feb  5 08:05:13 2013
From: staf.wagemakers at gmail.com (Staf Wagemakers)
Date: Tue, 5 Feb 2013 14:05:13 +0100
Subject: [OmniOS-discuss] remove old e1000g if...?
In-Reply-To: <OFC4D96F79.DC6BEC98-ONC1257B09.003EDB95-C1257B09.003EDB99@inse.com>
References: <CAOkCUXiSBLV=UuiO16Mkw5GnjuhFh=L1af-w1YHQA_J4MrJq5A@mail.gmail.com>
	<OFC4D96F79.DC6BEC98-ONC1257B09.003EDB95-C1257B09.003EDB99@inse.com>
Message-ID: <CAOkCUXiFy0Br0Q0RvzHKjSAKAqVG8c4vRiWYoZjo4KQbg-sxNA@mail.gmail.com>

On Tue, Feb 5, 2013 at 12:26 PM, Johan Kragsterman <
johan.kragsterman at capvert.se> wrot:

>
>
> Though, I removed first e1000g0 and 1, and then also 2, 3, 4 and 5, to get
> it start all over again with e1000g0, nothing shows up on dladm...?
>
>  I restarted between, without any nic in, to let the system clean out the
> old config, and then restarted with the new nic in, but then, as I said, no
> interface/phys shows up...?
>
> Any more tips?
>

Try to run "devfsadm ", "dladm show-phys" and "ifconfig -a plumb",
"ifconfig"

hope this helps...

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

From aszeszo at gmail.com  Tue Feb  5 08:16:16 2013
From: aszeszo at gmail.com (Andrzej Szeszo)
Date: Tue, 5 Feb 2013 14:16:16 +0100
Subject: [OmniOS-discuss] remove old e1000g if...?
In-Reply-To: <OFB0227C8F.49D1C624-ONC1257B09.002C189F-C1257B09.002C18A7@inse.com>
References: <OFB0227C8F.49D1C624-ONC1257B09.002C189F-C1257B09.002C18A7@inse.com>
Message-ID: <E83D8C97-7D33-4D8F-965D-703C04587C36@gmail.com>

This is what I was running in the past to shut the system down before moving the disk to a different box with e1000g nic:


$ cat ~/bin/reset-e1000g-config.sh
#!/bin/sh

SUDO=sudo

$SUDO /usr/gnu/bin/sed -i /e1000g/d /etc/path_to_inst
$SUDO rm /dev/e1000g[0-9]
$SUDO touch /reconfigure
$SUDO bootadm update-archive
$SUDO init 5
$ 

Cheers

Andrzej


On 5 Feb 2013, at 09:01, Johan Kragsterman <johan.kragsterman at capvert.se> wrote:

>  Hi all!
> 
>  I needed to remove an Intel nic with two e1000g if's, e1000g0 and e1000g1. I  I didn't remove any config before I removed the nic. After that, I put in a new Intel nic with 4 if's. They show up as e1000g2, 3, 4, and 5. For me that means that there is an old configuration remaining, belonging to the old nic, somewhere, that is not removed.
> 
>  I tried ipadm and dladm to look for how to remove the old config, but didn't find a way to do it.
> 
>  Can anyone help me out here? I don't want to configure the new nic before I get rid of the old one.
> 
> Rgrds Johan
> _______________________________________________
> 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/20130205/99317f4d/attachment.html>

From ramquick at gmail.com  Wed Feb  6 01:54:00 2013
From: ramquick at gmail.com (Ram Chander)
Date: Wed, 6 Feb 2013 12:24:00 +0530
Subject: [OmniOS-discuss] Zfs import fails
Message-ID: <CAMRGQbOx01C2kouieTXSW9jAwYH554CW5y4j_v5oTXxZeoFVEA@mail.gmail.com>

Hi,


I had a  zpool thats exported on another system and when i try to import,
it fails on Omni. Any idea how to recover ?

"format" shows all the disks.


root at host:~# zpool import -FfX pool1
cannot import 'pool1': one or more devices is currently unavailable

root at host:~# zpool import -f  pool1
cannot import 'pool1': I/O error
       Destroy and re-create the pool from
       a backup source.


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

From Floris at houseofancients.nl  Wed Feb  6 15:10:54 2013
From: Floris at houseofancients.nl (Floris van Essen ..:: House of Ancients Amstafs ::..)
Date: Wed, 6 Feb 2013 20:10:54 +0000
Subject: [OmniOS-discuss] VAAI Support into Stable
Message-ID: <356582D1FC91784992ABB4265A16ED480133834F@vEX01.mindstorm-internet.local>

Hi ,

Does anyone know when or why not the (open) VAAI support Developped by Joerg Goltermann will be available in COMSTAR ?


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

From gate03 at landcroft.co.uk  Thu Feb  7 19:02:29 2013
From: gate03 at landcroft.co.uk (Michael Mounteney)
Date: Fri, 8 Feb 2013 10:02:29 +1000
Subject: [OmniOS-discuss] preservation of permissions and ownership of zvols
	in child zone
Message-ID: <20130208100229.3357926b1392d3c762b85032@landcroft.co.uk>

The way that zvols work in child zones is a bit counter-intuitive, it seems to me, or counter to my intuition at least.

A while ago I posted a message that it simply wasn't working.  That is, if your zonecfg has:

    add device
    set match=/dev/zvol/dsk/rpool/vol/Gentoo1
    end

where that matches:

    zfs create -V 15G rpool/vol/Gentoo1

then inside the zone:

    # ls -l /dev/zvol/dsk/rpool/vol

matches nothing.  But if instead:

    # ls -l /dev/zvol/dsk/rpool/vol/Gentoo1

then the volume appears.  However, defeat is snatched from the jaws of victory because I want this volume for a VirtualBox file system, so in the global zone:

    # chown 573:100 /dev/zvol/dsk/rpool/vol/Gentoo1

however, in the child zone:

    # ls -l /dev/zvol/dsk/rpool/vol/Gentoo1
    brw------- 1 root sys 95, 3 Feb  7 23:48 /dev/zvol/dsk/rpool/vol/Gentoo1

that is, ownership somehow is lost.  You can chown again in the child zone and it works but the ownership is lost when the child zone is rebooted.  All of the foregoing about chown applies to chmod.  This matter is discussed in

    http://www.archivum.info/openindiana-discuss at openindiana.org/2012-10/00257/%28OpenIndiana-discuss%29-ZVOL-%28et-al%29-device-node-access-rights.html

but there is no conclusion, yet.  I wonder if a bodge-fix is to write a service that chmods the zvols on boot, and if so, what would the manifest be ?  I have no experience of writing manifests.

-- 
Michael Mounteney <gate03 at landcroft.co.uk>

From ramquick at gmail.com  Fri Feb  8 05:26:57 2013
From: ramquick at gmail.com (Ram Chander)
Date: Fri, 8 Feb 2013 15:56:57 +0530
Subject: [OmniOS-discuss] Hardware compaibility list
Message-ID: <CAMRGQbNx6=u2ya6GURzCsxNSV=fQ32-s6Z=b7KAmguGeJ3RZHw@mail.gmail.com>

Hi,


Is there a  hardware compatibility list  for OmniOS ? ( List of hardware
that works on Omni )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130208/3766e04d/attachment.html>

From nagele at wildbit.com  Fri Feb  8 09:47:22 2013
From: nagele at wildbit.com (Chris Nagele)
Date: Fri, 8 Feb 2013 09:47:22 -0500
Subject: [OmniOS-discuss] Hardware compaibility list
In-Reply-To: <CAMRGQbNx6=u2ya6GURzCsxNSV=fQ32-s6Z=b7KAmguGeJ3RZHw@mail.gmail.com>
References: <CAMRGQbNx6=u2ya6GURzCsxNSV=fQ32-s6Z=b7KAmguGeJ3RZHw@mail.gmail.com>
Message-ID: <CAHfYOdUAcg+70Q6u7czCB+hQngkdsV_Z7SHa9R6AAUhGvw3ckg@mail.gmail.com>

Hi Ram,

Since it is based on Illumos, I am pretty sure you can reference this list:

  http://illumos.org/hcl/

We just recently built a few servers for OmniOS, so feel free to ask
any questions about particular hardware or requirements as well.

Chris

From esproul at omniti.com  Fri Feb  8 09:53:16 2013
From: esproul at omniti.com (Eric Sproul)
Date: Fri, 8 Feb 2013 09:53:16 -0500
Subject: [OmniOS-discuss] Hardware compaibility list
In-Reply-To: <CAMRGQbNx6=u2ya6GURzCsxNSV=fQ32-s6Z=b7KAmguGeJ3RZHw@mail.gmail.com>
References: <CAMRGQbNx6=u2ya6GURzCsxNSV=fQ32-s6Z=b7KAmguGeJ3RZHw@mail.gmail.com>
Message-ID: <CA+QY2RSOHjy8UZRmO_4r-PK4RjJeMYRbwnrNKOcUK-He3HRJGg@mail.gmail.com>

You can use the illumos HCL: http://illumos.org/hcl

OmniOS does not add or change any hardware drivers from upstream illumos-gate.

On Fri, Feb 8, 2013 at 5:26 AM, Ram Chander <ramquick at gmail.com> wrote:
> Hi,
>
>
> Is there a  hardware compatibility list  for OmniOS ? ( List of hardware
> that works on Omni )
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From esproul at omniti.com  Fri Feb  8 09:56:18 2013
From: esproul at omniti.com (Eric Sproul)
Date: Fri, 8 Feb 2013 09:56:18 -0500
Subject: [OmniOS-discuss] Hardware compaibility list
In-Reply-To: <CAHfYOdUAcg+70Q6u7czCB+hQngkdsV_Z7SHa9R6AAUhGvw3ckg@mail.gmail.com>
References: <CAMRGQbNx6=u2ya6GURzCsxNSV=fQ32-s6Z=b7KAmguGeJ3RZHw@mail.gmail.com>
	<CAHfYOdUAcg+70Q6u7czCB+hQngkdsV_Z7SHa9R6AAUhGvw3ckg@mail.gmail.com>
Message-ID: <CA+QY2RSsy6gt03LvFEETOkvXH=nvJZ4sP6X6XLp2nCoJrJwzTQ@mail.gmail.com>

Thanks Chris.  I've just updated
http://omnios.omniti.com/wiki.php/Installation with a link to the HCL
so this info will be easier to find.

Eric

On Fri, Feb 8, 2013 at 9:47 AM, Chris Nagele <nagele at wildbit.com> wrote:
> Hi Ram,
>
> Since it is based on Illumos, I am pretty sure you can reference this list:
>
>   http://illumos.org/hcl/
>
> We just recently built a few servers for OmniOS, so feel free to ask
> any questions about particular hardware or requirements as well.
>
> Chris
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From ramquick at gmail.com  Mon Feb 11 07:39:34 2013
From: ramquick at gmail.com (Ram Chander)
Date: Mon, 11 Feb 2013 18:09:34 +0530
Subject: [OmniOS-discuss] Hardware compaibility list
In-Reply-To: <CA+QY2RSsy6gt03LvFEETOkvXH=nvJZ4sP6X6XLp2nCoJrJwzTQ@mail.gmail.com>
References: <CAMRGQbNx6=u2ya6GURzCsxNSV=fQ32-s6Z=b7KAmguGeJ3RZHw@mail.gmail.com>
	<CAHfYOdUAcg+70Q6u7czCB+hQngkdsV_Z7SHa9R6AAUhGvw3ckg@mail.gmail.com>
	<CA+QY2RSsy6gt03LvFEETOkvXH=nvJZ4sP6X6XLp2nCoJrJwzTQ@mail.gmail.com>
Message-ID: <CAMRGQbOFapmn_LGJYOkSrGzqDYz5aoSxg3UK2oTQfDyaH6HU4Q@mail.gmail.com>

Thanks all !!


On Fri, Feb 8, 2013 at 8:26 PM, Eric Sproul <esproul at omniti.com> wrote:

> Thanks Chris.  I've just updated
> http://omnios.omniti.com/wiki.php/Installation with a link to the HCL
> so this info will be easier to find.
>
> Eric
>
> On Fri, Feb 8, 2013 at 9:47 AM, Chris Nagele <nagele at wildbit.com> wrote:
> > Hi Ram,
> >
> > Since it is based on Illumos, I am pretty sure you can reference this
> list:
> >
> >   http://illumos.org/hcl/
> >
> > We just recently built a few servers for OmniOS, so feel free to ask
> > any questions about particular hardware or requirements as well.
> >
> > Chris
> > _______________________________________________
> > 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/20130211/c8f5dbc4/attachment.html>

From ramquick at gmail.com  Mon Feb 11 07:48:52 2013
From: ramquick at gmail.com (Ram Chander)
Date: Mon, 11 Feb 2013 18:18:52 +0530
Subject: [OmniOS-discuss] Slow zfs writes
Message-ID: <CAMRGQbPHkciBVGd+SvsOc3-OQtSharyoydCZ5Lj0HixurcwgLA@mail.gmail.com>

Hi,

My OI box is expreiencing slow zfs writes ( around 30 times slower ).
iostat reports below error though pool is healthy. This is happening in
past 4 days though no change was done to system. Is the hard disks faulty ?
Please help.


# zpool status -v
root at host:~# zpool status -v
  pool: test
 state: ONLINE
status: The pool is formatted using a legacy on-disk format.  The pool can
        still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'.  Once this is done, the
        pool will no longer be accessible on software that does not support
feature flags.
config:

        NAME         STATE     READ WRITE CKSUM
        test       ONLINE       0     0     0
          raidz1-0   ONLINE       0     0     0
            c2t0d0   ONLINE       0     0     0
            c2t1d0   ONLINE       0     0     0
            c2t2d0   ONLINE       0     0     0
            c2t3d0   ONLINE       0     0     0
            c2t4d0   ONLINE       0     0     0
          raidz1-1   ONLINE       0     0     0
            c2t5d0   ONLINE       0     0     0
            c2t6d0   ONLINE       0     0     0
            c2t7d0   ONLINE       0     0     0
            c2t8d0   ONLINE       0     0     0
            c2t9d0   ONLINE       0     0     0
          raidz1-3   ONLINE       0     0     0
            c2t12d0  ONLINE       0     0     0
            c2t13d0  ONLINE       0     0     0
            c2t14d0  ONLINE       0     0     0
            c2t15d0  ONLINE       0     0     0
            c2t16d0  ONLINE       0     0     0
            c2t17d0  ONLINE       0     0     0
            c2t18d0  ONLINE       0     0     0
            c2t19d0  ONLINE       0     0     0
            c2t20d0  ONLINE       0     0     0
            c2t21d0  ONLINE       0     0     0
            c2t22d0  ONLINE       0     0     0
            c2t23d0  ONLINE       0     0     0
          raidz1-4   ONLINE       0     0     0
            c2t24d0  ONLINE       0     0     0
            c2t25d0  ONLINE       0     0     0
            c2t26d0  ONLINE       0     0     0
            c2t27d0  ONLINE       0     0     0
            c2t28d0  ONLINE       0     0     0
            c2t29d0  ONLINE       0     0     0
            c2t30d0  ONLINE       0     0     0
          raidz1-5   ONLINE       0     0     0
            c2t31d0  ONLINE       0     0     0
            c2t32d0  ONLINE       0     0     0
            c2t33d0  ONLINE       0     0     0
            c2t34d0  ONLINE       0     0     0
            c2t35d0  ONLINE       0     0     0
            c2t36d0  ONLINE       0     0     0
            c2t37d0  ONLINE       0     0     0
          raidz1-6   ONLINE       0     0     0
            c2t38d0  ONLINE       0     0     0
            c2t39d0  ONLINE       0     0     0
            c2t40d0  ONLINE       0     0     0
            c2t41d0  ONLINE       0     0     0
            c2t42d0  ONLINE       0     0     0
            c2t43d0  ONLINE       0     0     0
            c2t44d0  ONLINE       0     0     0
        spares
          c5t10d0    AVAIL
          c5t11d0    AVAIL
          c2t45d0    AVAIL
          c2t46d0    AVAIL
          c2t47d0    AVAIL



# iostat -En

c4t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
Vendor: iDRAC    Product: Virtual CD       Revision: 0323 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0
c3t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: iDRAC    Product: LCDRIVE          Revision: 0323 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c4t0d1           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: iDRAC    Product: Virtual Floppy   Revision: 0323 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0


root at host:~# fmadm faulty
--------------- ------------------------------------  --------------
---------
TIME            EVENT-ID                              MSG-ID
SEVERITY
--------------- ------------------------------------  --------------
---------
Jan 05 08:21:09 7af1ab3c-83c2-602d-d4b9-f9040db6944a  ZFS-8000-HC
Major

Host        : host
Platform    : PowerEdge-R810
Product_sn  :

Fault class : fault.fs.zfs.io_failure_wait
Affects     : zfs://pool=test
                  faulted but still in service
Problem in  : zfs://pool=test
                  faulted but still in service

Description : The ZFS pool has experienced currently unrecoverable I/O
                    failures.  Refer to http://illumos.org/msg/ZFS-8000-HCfor
              more information.

Response    : No automated response will be taken.

Impact      : Read and write I/Os cannot be serviced.

Action      : Make sure the affected devices are connected, then run
                    'zpool clear'.


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

From esproul at omniti.com  Mon Feb 11 09:44:59 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 11 Feb 2013 09:44:59 -0500
Subject: [OmniOS-discuss] Slow zfs writes
In-Reply-To: <CAMRGQbPHkciBVGd+SvsOc3-OQtSharyoydCZ5Lj0HixurcwgLA@mail.gmail.com>
References: <CAMRGQbPHkciBVGd+SvsOc3-OQtSharyoydCZ5Lj0HixurcwgLA@mail.gmail.com>
Message-ID: <CA+QY2RRiEaxcxUoabQnuQbMFXTb1v8LDiUJuFbxBvbBNv0UsQg@mail.gmail.com>

On Mon, Feb 11, 2013 at 7:48 AM, Ram Chander <ramquick at gmail.com> wrote:
> Hi,
>
> My OI box is expreiencing slow zfs writes ( around 30 times slower ). iostat
> reports below error though pool is healthy. This is happening in past 4 days
> though no change was done to system. Is the hard disks faulty ?
> Please help.

How have you measured this 30x drop in performance?  You haven't
provided any data.


> c4t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
> Vendor: iDRAC    Product: Virtual CD       Revision: 0323 Serial No:
> Size: 0.00GB <0 bytes>
> Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
> Illegal Request: 1 Predictive Failure Analysis: 0

I wouldn't worry about errors here.  This is a virtual device provided
by your server's lights-out management system.


> root at host:~# fmadm faulty
> --------------- ------------------------------------  --------------
> ---------
> TIME            EVENT-ID                              MSG-ID
> SEVERITY
> --------------- ------------------------------------  --------------
> ---------
> Jan 05 08:21:09 7af1ab3c-83c2-602d-d4b9-f9040db6944a  ZFS-8000-HC    Major
>
> Host        : host
> Platform    : PowerEdge-R810
> Product_sn  :
>
> Fault class : fault.fs.zfs.io_failure_wait
> Affects     : zfs://pool=test
>                   faulted but still in service
> Problem in  : zfs://pool=test
>                   faulted but still in service
>
> Description : The ZFS pool has experienced currently unrecoverable I/O
>                     failures.  Refer to http://illumos.org/msg/ZFS-8000-HC
> for
>               more information.
>
> Response    : No automated response will be taken.
>
> Impact      : Read and write I/Os cannot be serviced.
>
> Action      : Make sure the affected devices are connected, then run
>                     'zpool clear'.

What has happened since January 5?  The pool appears fine now.  Did
you run a scrub?  Replace devices?  Reboot?  It looks like ZFS
encountered an underlying problem with the hardware.

Eric

From esproul at omniti.com  Mon Feb 11 10:03:55 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 11 Feb 2013 10:03:55 -0500
Subject: [OmniOS-discuss] Updated release: r151004n
Message-ID: <CA+QY2RRe9kfXycag8mf-a5uzCeJpkkWkcwc=tSxZr-wjGk_AtA@mail.gmail.com>

This was announced on Friday via IRC and Twitter, but I forgot to post
to the discuss list. Sorry!

Weekly release r151004n fixes an OpenSSL security vulnerability:
 * http://www.openssl.org/news/secadv_20130205.txt
 * http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0169

An updated omnios-userland incorporation is required in order to
update openssl.  See the release notes for details:
http://omnios.omniti.com/wiki.php/ReleaseNotes#r151004n

Updated installation media are now available, including ISO and USB
images as well as Kayak ZFS. Note that the file name of the Kayak ZFS
image remains the same to ensure compatibility with existing GRUB
configuration.

This release also updates pci.ids to the 2013-02-05 snapshot.

From ramquick at gmail.com  Mon Feb 11 11:33:04 2013
From: ramquick at gmail.com (Ram Chander)
Date: Mon, 11 Feb 2013 22:03:04 +0530
Subject: [OmniOS-discuss] Slow zfs writes
In-Reply-To: <CA+QY2RRiEaxcxUoabQnuQbMFXTb1v8LDiUJuFbxBvbBNv0UsQg@mail.gmail.com>
References: <CAMRGQbPHkciBVGd+SvsOc3-OQtSharyoydCZ5Lj0HixurcwgLA@mail.gmail.com>
	<CA+QY2RRiEaxcxUoabQnuQbMFXTb1v8LDiUJuFbxBvbBNv0UsQg@mail.gmail.com>
Message-ID: <CAMRGQbNR_uT4Wn0_=1crNA6Xb2Bzbk-+-K9mutrsEfY3B_3o_w@mail.gmail.com>

I am not sure what happened on Jan 5. I havent run scrub or replaced
devices for more than 3 months. The underlying hardware is Dell Md1200
which has 48 disks.
How to recover from this ? I had tried rebooting  but issue comes back.


On Mon, Feb 11, 2013 at 8:14 PM, Eric Sproul <esproul at omniti.com> wrote:

> On Mon, Feb 11, 2013 at 7:48 AM, Ram Chander <ramquick at gmail.com> wrote:
> > Hi,
> >
> > My OI box is expreiencing slow zfs writes ( around 30 times slower ).
> iostat
> > reports below error though pool is healthy. This is happening in past 4
> days
> > though no change was done to system. Is the hard disks faulty ?
> > Please help.
>
> How have you measured this 30x drop in performance?  You haven't
> provided any data.
>
>
> > c4t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
> > Vendor: iDRAC    Product: Virtual CD       Revision: 0323 Serial No:
> > Size: 0.00GB <0 bytes>
> > Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
> > Illegal Request: 1 Predictive Failure Analysis: 0
>
> I wouldn't worry about errors here.  This is a virtual device provided
> by your server's lights-out management system.
>
>
> > root at host:~# fmadm faulty
> > --------------- ------------------------------------  --------------
> > ---------
> > TIME            EVENT-ID                              MSG-ID
> > SEVERITY
> > --------------- ------------------------------------  --------------
> > ---------
> > Jan 05 08:21:09 7af1ab3c-83c2-602d-d4b9-f9040db6944a  ZFS-8000-HC
>  Major
> >
> > Host        : host
> > Platform    : PowerEdge-R810
> > Product_sn  :
> >
> > Fault class : fault.fs.zfs.io_failure_wait
> > Affects     : zfs://pool=test
> >                   faulted but still in service
> > Problem in  : zfs://pool=test
> >                   faulted but still in service
> >
> > Description : The ZFS pool has experienced currently unrecoverable I/O
> >                     failures.  Refer to
> http://illumos.org/msg/ZFS-8000-HC
> > for
> >               more information.
> >
> > Response    : No automated response will be taken.
> >
> > Impact      : Read and write I/Os cannot be serviced.
> >
> > Action      : Make sure the affected devices are connected, then run
> >                     'zpool clear'.
>
> What has happened since January 5?  The pool appears fine now.  Did
> you run a scrub?  Replace devices?  Reboot?  It looks like ZFS
> encountered an underlying problem with the hardware.
>
> 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/20130211/67131e5d/attachment-0001.html>

From esproul at omniti.com  Mon Feb 11 11:36:37 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 11 Feb 2013 11:36:37 -0500
Subject: [OmniOS-discuss] Slow zfs writes
In-Reply-To: <CAMRGQbNR_uT4Wn0_=1crNA6Xb2Bzbk-+-K9mutrsEfY3B_3o_w@mail.gmail.com>
References: <CAMRGQbPHkciBVGd+SvsOc3-OQtSharyoydCZ5Lj0HixurcwgLA@mail.gmail.com>
	<CA+QY2RRiEaxcxUoabQnuQbMFXTb1v8LDiUJuFbxBvbBNv0UsQg@mail.gmail.com>
	<CAMRGQbNR_uT4Wn0_=1crNA6Xb2Bzbk-+-K9mutrsEfY3B_3o_w@mail.gmail.com>
Message-ID: <CA+QY2RSsbRQ9J6aALR026fYHGBuRXd3nWpjhY5SwhdFrKq7kYA@mail.gmail.com>

You still haven't said how you know that performance has dropped 30x.
Where are the numbers?

On Mon, Feb 11, 2013 at 11:33 AM, Ram Chander <ramquick at gmail.com> wrote:
> I am not sure what happened on Jan 5. I havent run scrub or replaced devices
> for more than 3 months. The underlying hardware is Dell Md1200 which has 48
> disks.
> How to recover from this ? I had tried rebooting  but issue comes back.
>
>
> On Mon, Feb 11, 2013 at 8:14 PM, Eric Sproul <esproul at omniti.com> wrote:
>>
>> On Mon, Feb 11, 2013 at 7:48 AM, Ram Chander <ramquick at gmail.com> wrote:
>> > Hi,
>> >
>> > My OI box is expreiencing slow zfs writes ( around 30 times slower ).
>> > iostat
>> > reports below error though pool is healthy. This is happening in past 4
>> > days
>> > though no change was done to system. Is the hard disks faulty ?
>> > Please help.
>>
>> How have you measured this 30x drop in performance?  You haven't
>> provided any data.
>>
>>
>> > c4t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
>> > Vendor: iDRAC    Product: Virtual CD       Revision: 0323 Serial No:
>> > Size: 0.00GB <0 bytes>
>> > Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
>> > Illegal Request: 1 Predictive Failure Analysis: 0
>>
>> I wouldn't worry about errors here.  This is a virtual device provided
>> by your server's lights-out management system.
>>
>>
>> > root at host:~# fmadm faulty
>> > --------------- ------------------------------------  --------------
>> > ---------
>> > TIME            EVENT-ID                              MSG-ID
>> > SEVERITY
>> > --------------- ------------------------------------  --------------
>> > ---------
>> > Jan 05 08:21:09 7af1ab3c-83c2-602d-d4b9-f9040db6944a  ZFS-8000-HC
>> > Major
>> >
>> > Host        : host
>> > Platform    : PowerEdge-R810
>> > Product_sn  :
>> >
>> > Fault class : fault.fs.zfs.io_failure_wait
>> > Affects     : zfs://pool=test
>> >                   faulted but still in service
>> > Problem in  : zfs://pool=test
>> >                   faulted but still in service
>> >
>> > Description : The ZFS pool has experienced currently unrecoverable I/O
>> >                     failures.  Refer to
>> > http://illumos.org/msg/ZFS-8000-HC
>> > for
>> >               more information.
>> >
>> > Response    : No automated response will be taken.
>> >
>> > Impact      : Read and write I/Os cannot be serviced.
>> >
>> > Action      : Make sure the affected devices are connected, then run
>> >                     'zpool clear'.
>>
>> What has happened since January 5?  The pool appears fine now.  Did
>> you run a scrub?  Replace devices?  Reboot?  It looks like ZFS
>> encountered an underlying problem with the hardware.
>>
>> Eric
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>

From ramquick at gmail.com  Mon Feb 11 11:52:40 2013
From: ramquick at gmail.com (Ram Chander)
Date: Mon, 11 Feb 2013 22:22:40 +0530
Subject: [OmniOS-discuss] Slow zfs writes
In-Reply-To: <CA+QY2RSsbRQ9J6aALR026fYHGBuRXd3nWpjhY5SwhdFrKq7kYA@mail.gmail.com>
References: <CAMRGQbPHkciBVGd+SvsOc3-OQtSharyoydCZ5Lj0HixurcwgLA@mail.gmail.com>
	<CA+QY2RRiEaxcxUoabQnuQbMFXTb1v8LDiUJuFbxBvbBNv0UsQg@mail.gmail.com>
	<CAMRGQbNR_uT4Wn0_=1crNA6Xb2Bzbk-+-K9mutrsEfY3B_3o_w@mail.gmail.com>
	<CA+QY2RSsbRQ9J6aALR026fYHGBuRXd3nWpjhY5SwhdFrKq7kYA@mail.gmail.com>
Message-ID: <CAMRGQbNt7Q-Me+gDbr_zyh2uQP4S_e9UtDRCnFPLbf1JE0P3uQ@mail.gmail.com>

cp of 1Gb file takes 20min  to the pool whereas on normal disk it takes
35sec.


On Mon, Feb 11, 2013 at 10:06 PM, Eric Sproul <esproul at omniti.com> wrote:

> You still haven't said how you know that performance has dropped 30x.
> Where are the numbers?
>
> On Mon, Feb 11, 2013 at 11:33 AM, Ram Chander <ramquick at gmail.com> wrote:
> > I am not sure what happened on Jan 5. I havent run scrub or replaced
> devices
> > for more than 3 months. The underlying hardware is Dell Md1200 which has
> 48
> > disks.
> > How to recover from this ? I had tried rebooting  but issue comes back.
> >
> >
> > On Mon, Feb 11, 2013 at 8:14 PM, Eric Sproul <esproul at omniti.com> wrote:
> >>
> >> On Mon, Feb 11, 2013 at 7:48 AM, Ram Chander <ramquick at gmail.com>
> wrote:
> >> > Hi,
> >> >
> >> > My OI box is expreiencing slow zfs writes ( around 30 times slower ).
> >> > iostat
> >> > reports below error though pool is healthy. This is happening in past
> 4
> >> > days
> >> > though no change was done to system. Is the hard disks faulty ?
> >> > Please help.
> >>
> >> How have you measured this 30x drop in performance?  You haven't
> >> provided any data.
> >>
> >>
> >> > c4t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
> >> > Vendor: iDRAC    Product: Virtual CD       Revision: 0323 Serial No:
> >> > Size: 0.00GB <0 bytes>
> >> > Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
> >> > Illegal Request: 1 Predictive Failure Analysis: 0
> >>
> >> I wouldn't worry about errors here.  This is a virtual device provided
> >> by your server's lights-out management system.
> >>
> >>
> >> > root at host:~# fmadm faulty
> >> > --------------- ------------------------------------  --------------
> >> > ---------
> >> > TIME            EVENT-ID                              MSG-ID
> >> > SEVERITY
> >> > --------------- ------------------------------------  --------------
> >> > ---------
> >> > Jan 05 08:21:09 7af1ab3c-83c2-602d-d4b9-f9040db6944a  ZFS-8000-HC
> >> > Major
> >> >
> >> > Host        : host
> >> > Platform    : PowerEdge-R810
> >> > Product_sn  :
> >> >
> >> > Fault class : fault.fs.zfs.io_failure_wait
> >> > Affects     : zfs://pool=test
> >> >                   faulted but still in service
> >> > Problem in  : zfs://pool=test
> >> >                   faulted but still in service
> >> >
> >> > Description : The ZFS pool has experienced currently unrecoverable I/O
> >> >                     failures.  Refer to
> >> > http://illumos.org/msg/ZFS-8000-HC
> >> > for
> >> >               more information.
> >> >
> >> > Response    : No automated response will be taken.
> >> >
> >> > Impact      : Read and write I/Os cannot be serviced.
> >> >
> >> > Action      : Make sure the affected devices are connected, then run
> >> >                     'zpool clear'.
> >>
> >> What has happened since January 5?  The pool appears fine now.  Did
> >> you run a scrub?  Replace devices?  Reboot?  It looks like ZFS
> >> encountered an underlying problem with the hardware.
> >>
> >> Eric
> >> _______________________________________________
> >> 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/20130211/4b5b94d1/attachment.html>

From denis at denisandyuki.net  Mon Feb 11 17:50:35 2013
From: denis at denisandyuki.net (Denis Cheong)
Date: Tue, 12 Feb 2013 09:50:35 +1100
Subject: [OmniOS-discuss] Slow zfs writes
In-Reply-To: <CAMRGQbNt7Q-Me+gDbr_zyh2uQP4S_e9UtDRCnFPLbf1JE0P3uQ@mail.gmail.com>
References: <CAMRGQbPHkciBVGd+SvsOc3-OQtSharyoydCZ5Lj0HixurcwgLA@mail.gmail.com>
	<CA+QY2RRiEaxcxUoabQnuQbMFXTb1v8LDiUJuFbxBvbBNv0UsQg@mail.gmail.com>
	<CAMRGQbNR_uT4Wn0_=1crNA6Xb2Bzbk-+-K9mutrsEfY3B_3o_w@mail.gmail.com>
	<CA+QY2RSsbRQ9J6aALR026fYHGBuRXd3nWpjhY5SwhdFrKq7kYA@mail.gmail.com>
	<CAMRGQbNt7Q-Me+gDbr_zyh2uQP4S_e9UtDRCnFPLbf1JE0P3uQ@mail.gmail.com>
Message-ID: <CABOCf+iAhk-d9XsDKYMj5wv0_TEczq1x3Lf9z=BxPmC6R=41mQ@mail.gmail.com>

You haven't enabled dedup on any zfs volumes?  That will drop performance
by 30x to 300x especially on an array that size unless you have an insane
amount of memory.




On Tue, Feb 12, 2013 at 3:52 AM, Ram Chander <ramquick at gmail.com> wrote:

> cp of 1Gb file takes 20min  to the pool whereas on normal disk it takes
> 35sec.
>
>
> On Mon, Feb 11, 2013 at 10:06 PM, Eric Sproul <esproul at omniti.com> wrote:
>
>> You still haven't said how you know that performance has dropped 30x.
>> Where are the numbers?
>>
>> On Mon, Feb 11, 2013 at 11:33 AM, Ram Chander <ramquick at gmail.com> wrote:
>> > I am not sure what happened on Jan 5. I havent run scrub or replaced
>> devices
>> > for more than 3 months. The underlying hardware is Dell Md1200 which
>> has 48
>> > disks.
>> > How to recover from this ? I had tried rebooting  but issue comes back.
>> >
>> >
>> > On Mon, Feb 11, 2013 at 8:14 PM, Eric Sproul <esproul at omniti.com>
>> wrote:
>> >>
>> >> On Mon, Feb 11, 2013 at 7:48 AM, Ram Chander <ramquick at gmail.com>
>> wrote:
>> >> > Hi,
>> >> >
>> >> > My OI box is expreiencing slow zfs writes ( around 30 times slower ).
>> >> > iostat
>> >> > reports below error though pool is healthy. This is happening in
>> past 4
>> >> > days
>> >> > though no change was done to system. Is the hard disks faulty ?
>> >> > Please help.
>> >>
>> >> How have you measured this 30x drop in performance?  You haven't
>> >> provided any data.
>> >>
>> >>
>> >> > c4t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
>> >> > Vendor: iDRAC    Product: Virtual CD       Revision: 0323 Serial No:
>> >> > Size: 0.00GB <0 bytes>
>> >> > Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
>> >> > Illegal Request: 1 Predictive Failure Analysis: 0
>> >>
>> >> I wouldn't worry about errors here.  This is a virtual device provided
>> >> by your server's lights-out management system.
>> >>
>> >>
>> >> > root at host:~# fmadm faulty
>> >> > --------------- ------------------------------------  --------------
>> >> > ---------
>> >> > TIME            EVENT-ID                              MSG-ID
>> >> > SEVERITY
>> >> > --------------- ------------------------------------  --------------
>> >> > ---------
>> >> > Jan 05 08:21:09 7af1ab3c-83c2-602d-d4b9-f9040db6944a  ZFS-8000-HC
>> >> > Major
>> >> >
>> >> > Host        : host
>> >> > Platform    : PowerEdge-R810
>> >> > Product_sn  :
>> >> >
>> >> > Fault class : fault.fs.zfs.io_failure_wait
>> >> > Affects     : zfs://pool=test
>> >> >                   faulted but still in service
>> >> > Problem in  : zfs://pool=test
>> >> >                   faulted but still in service
>> >> >
>> >> > Description : The ZFS pool has experienced currently unrecoverable
>> I/O
>> >> >                     failures.  Refer to
>> >> > http://illumos.org/msg/ZFS-8000-HC
>> >> > for
>> >> >               more information.
>> >> >
>> >> > Response    : No automated response will be taken.
>> >> >
>> >> > Impact      : Read and write I/Os cannot be serviced.
>> >> >
>> >> > Action      : Make sure the affected devices are connected, then run
>> >> >                     'zpool clear'.
>> >>
>> >> What has happened since January 5?  The pool appears fine now.  Did
>> >> you run a scrub?  Replace devices?  Reboot?  It looks like ZFS
>> >> encountered an underlying problem with the hardware.
>> >>
>> >> Eric
>> >> _______________________________________________
>> >> 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/20130212/e561f38d/attachment.html>

From Kevin.Swab at ColoState.EDU  Mon Feb 11 17:57:02 2013
From: Kevin.Swab at ColoState.EDU (Kevin Swab)
Date: Mon, 11 Feb 2013 15:57:02 -0700
Subject: [OmniOS-discuss] Upgrade from OpenIndiana to OmniOS?
Message-ID: <5119773E.3020401@ColoState.EDU>

Hello,

	We're thinking of making the switch from OpenIndiana to OmniOS. In
order to minimize downtime, we'd like to be able to install OmniOS to an
alternate boot environment, if possible.  I tried (unsuccessfully) to
use a procedure similar to the one outlined on the OpenIndiana wiki for
upgrading OpenSolaris to OpenIndiana:

http://wiki.openindiana.org/oi/Upgrading+from+OpenSolaris

This is how it went:

# uname -v
oi_151a7
# pkg set-publisher -P -g http://pkg.omniti.com/omnios/release/ omnios
# pkg publisher
PUBLISHER                             TYPE     STATUS   URI
omnios                                origin   online
http://pkg.omniti.com/omnios/release/
openindiana.org                       origin   online
http://pkg.openindiana.org/dev/
# pkg list -af entire
NAME (PUBLISHER)                                  VERSION
     IFO
entire                                            11-0.151004
     ---
entire                                            11-0.151002
     ---
entire                                            11-0.151002
     ---
entire (openindiana.org)                          0.5.11-0.151.1.7
     i--
entire (openindiana.org)                          0.5.11-0.151.1.6
     ---
entire (openindiana.org)                          0.5.11-0.151.1.5
     ---
entire (openindiana.org)                          0.5.11-0.151.1.4
     ---
entire (openindiana.org)                          0.5.11-0.151.1.3
     ---
entire (openindiana.org)                          0.5.11-0.151.1.2
     ---
entire (openindiana.org)                          0.5.11-0.151.1.1
     ---
entire (openindiana.org)                          0.5.11-0.151.1
     ---
entire (openindiana.org)                          0.5.11-0.148
     ---
entire (openindiana.org)                          0.5.11-0.147
     ---
# pkg update -f --be-name omnios entire at 11-0.151004
Creating Plan
pkg update: The following patterns only matched packages that are from
publishers other than that which supplied the already installed version
of this package
        entire at 11-0.151004: omnios


I get the same results trying "pkg install ..." instead of "pkg update ..."

Is it possible to do this?  If so, what do I need to do?


Thanks for your help,
Kevin


From ramquick at gmail.com  Tue Feb 12 00:09:32 2013
From: ramquick at gmail.com (Ram Chander)
Date: Tue, 12 Feb 2013 10:39:32 +0530
Subject: [OmniOS-discuss] Slow zfs writes
In-Reply-To: <CABOCf+iAhk-d9XsDKYMj5wv0_TEczq1x3Lf9z=BxPmC6R=41mQ@mail.gmail.com>
References: <CAMRGQbPHkciBVGd+SvsOc3-OQtSharyoydCZ5Lj0HixurcwgLA@mail.gmail.com>
	<CA+QY2RRiEaxcxUoabQnuQbMFXTb1v8LDiUJuFbxBvbBNv0UsQg@mail.gmail.com>
	<CAMRGQbNR_uT4Wn0_=1crNA6Xb2Bzbk-+-K9mutrsEfY3B_3o_w@mail.gmail.com>
	<CA+QY2RSsbRQ9J6aALR026fYHGBuRXd3nWpjhY5SwhdFrKq7kYA@mail.gmail.com>
	<CAMRGQbNt7Q-Me+gDbr_zyh2uQP4S_e9UtDRCnFPLbf1JE0P3uQ@mail.gmail.com>
	<CABOCf+iAhk-d9XsDKYMj5wv0_TEczq1x3Lf9z=BxPmC6R=41mQ@mail.gmail.com>
Message-ID: <CAMRGQbMRwwTF_zHL-gRZTEzHV8L=HEwG7WeVSYgW4htxari=yQ@mail.gmail.com>

So it looks like re-distribution issue. Initially  there were two Vdev with
24 disks ( disk 0-23 ) for close to year. After which  which we added 24
more disks and created additional vdevs. The initial vdevs are filled up
and so write speed declined. Now  how to find files that are present in a
Vdev or a disk. That way I can remove and re-copy back to distribute data.
Any other way to solve this ?

Total capacity of pool - 98Tb
Used - 44Tb
Free - 54 Tb

root at host:# zpool iostat -v
                capacity     operations    bandwidth
pool         alloc   free   read  write   read  write
-----------  -----  -----  -----  -----  -----  -----
test       54.0T  62.7T     52  1.12K  2.16M  5.78M
  raidz1     11.2T  2.41T     13     30   176K   146K
    c2t0d0       -      -      5     18  42.1K  39.0K
    c2t1d0       -      -      5     18  42.2K  39.0K
    c2t2d0       -      -      5     18  42.5K  39.0K
    c2t3d0       -      -      5     18  42.9K  39.0K
    c2t4d0       -      -      5     18  42.6K  39.0K
  raidz1     13.3T   308G     13    100   213K   521K
    c2t5d0       -      -      5     94  50.8K   135K
    c2t6d0       -      -      5     94  51.0K   135K
    c2t7d0       -      -      5     94  50.8K   135K
    c2t8d0       -      -      5     94  51.1K   135K
    c2t9d0       -      -      5     94  51.1K   135K
  raidz1     13.4T  19.1T      9    455   743K  2.31M
    c2t12d0      -      -      3    137  69.6K   235K
    c2t13d0      -      -      3    129  69.4K   227K
    c2t14d0      -      -      3    139  69.6K   235K
    c2t15d0      -      -      3    131  69.6K   227K
    c2t16d0      -      -      3    141  69.6K   235K
    c2t17d0      -      -      3    132  69.5K   227K
    c2t18d0      -      -      3    142  69.6K   235K
    c2t19d0      -      -      3    133  69.6K   227K
    c2t20d0      -      -      3    143  69.6K   235K
    c2t21d0      -      -      3    133  69.5K   227K
    c2t22d0      -      -      3    143  69.6K   235K
    c2t23d0      -      -      3    133  69.5K   227K
  raidz1     2.44T  16.6T      5    103   327K   485K
    c2t24d0      -      -      2     48  50.8K  87.4K
    c2t25d0      -      -      2     49  50.7K  87.4K
    c2t26d0      -      -      2     49  50.8K  87.3K
    c2t27d0      -      -      2     49  50.8K  87.3K
    c2t28d0      -      -      2     49  50.8K  87.3K
    c2t29d0      -      -      2     49  50.8K  87.3K
    c2t30d0      -      -      2     49  50.8K  87.3K
  raidz1     8.18T  10.8T      5    295   374K  1.54M
    c2t31d0      -      -      2    131  58.2K   279K
    c2t32d0      -      -      2    131  58.1K   279K
    c2t33d0      -      -      2    131  58.2K   279K
    c2t34d0      -      -      2    132  58.2K   279K
    c2t35d0      -      -      2    132  58.1K   279K
    c2t36d0      -      -      2    133  58.3K   279K
    c2t37d0      -      -      2    133  58.2K   279K
  raidz1     5.42T  13.6T      5    163   383K   823K
    c2t38d0      -      -      2     61  59.4K   146K
    c2t39d0      -      -      2     61  59.3K   146K
    c2t40d0      -      -      2     61  59.4K   146K
    c2t41d0      -      -      2     61  59.4K   146K
    c2t42d0      -      -      2     61  59.3K   146K
    c2t43d0      -      -      2     62  59.2K   146K
    c2t44d0      -      -      2     62  59.3K   146K


On Tue, Feb 12, 2013 at 4:20 AM, Denis Cheong <denis at denisandyuki.net>wrote:

> You haven't enabled dedup on any zfs volumes?  That will drop performance
> by 30x to 300x especially on an array that size unless you have an insane
> amount of memory.
>
>
>
>
> On Tue, Feb 12, 2013 at 3:52 AM, Ram Chander <ramquick at gmail.com> wrote:
>
>> cp of 1Gb file takes 20min  to the pool whereas on normal disk it takes
>> 35sec.
>>
>>
>> On Mon, Feb 11, 2013 at 10:06 PM, Eric Sproul <esproul at omniti.com> wrote:
>>
>>> You still haven't said how you know that performance has dropped 30x.
>>> Where are the numbers?
>>>
>>> On Mon, Feb 11, 2013 at 11:33 AM, Ram Chander <ramquick at gmail.com>
>>> wrote:
>>> > I am not sure what happened on Jan 5. I havent run scrub or replaced
>>> devices
>>> > for more than 3 months. The underlying hardware is Dell Md1200 which
>>> has 48
>>> > disks.
>>> > How to recover from this ? I had tried rebooting  but issue comes back.
>>> >
>>> >
>>> > On Mon, Feb 11, 2013 at 8:14 PM, Eric Sproul <esproul at omniti.com>
>>> wrote:
>>> >>
>>> >> On Mon, Feb 11, 2013 at 7:48 AM, Ram Chander <ramquick at gmail.com>
>>> wrote:
>>> >> > Hi,
>>> >> >
>>> >> > My OI box is expreiencing slow zfs writes ( around 30 times slower
>>> ).
>>> >> > iostat
>>> >> > reports below error though pool is healthy. This is happening in
>>> past 4
>>> >> > days
>>> >> > though no change was done to system. Is the hard disks faulty ?
>>> >> > Please help.
>>> >>
>>> >> How have you measured this 30x drop in performance?  You haven't
>>> >> provided any data.
>>> >>
>>> >>
>>> >> > c4t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
>>> >> > Vendor: iDRAC    Product: Virtual CD       Revision: 0323 Serial No:
>>> >> > Size: 0.00GB <0 bytes>
>>> >> > Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
>>> >> > Illegal Request: 1 Predictive Failure Analysis: 0
>>> >>
>>> >> I wouldn't worry about errors here.  This is a virtual device provided
>>> >> by your server's lights-out management system.
>>> >>
>>> >>
>>> >> > root at host:~# fmadm faulty
>>> >> > --------------- ------------------------------------  --------------
>>> >> > ---------
>>> >> > TIME            EVENT-ID                              MSG-ID
>>> >> > SEVERITY
>>> >> > --------------- ------------------------------------  --------------
>>> >> > ---------
>>> >> > Jan 05 08:21:09 7af1ab3c-83c2-602d-d4b9-f9040db6944a  ZFS-8000-HC
>>> >> > Major
>>> >> >
>>> >> > Host        : host
>>> >> > Platform    : PowerEdge-R810
>>> >> > Product_sn  :
>>> >> >
>>> >> > Fault class : fault.fs.zfs.io_failure_wait
>>> >> > Affects     : zfs://pool=test
>>> >> >                   faulted but still in service
>>> >> > Problem in  : zfs://pool=test
>>> >> >                   faulted but still in service
>>> >> >
>>> >> > Description : The ZFS pool has experienced currently unrecoverable
>>> I/O
>>> >> >                     failures.  Refer to
>>> >> > http://illumos.org/msg/ZFS-8000-HC
>>> >> > for
>>> >> >               more information.
>>> >> >
>>> >> > Response    : No automated response will be taken.
>>> >> >
>>> >> > Impact      : Read and write I/Os cannot be serviced.
>>> >> >
>>> >> > Action      : Make sure the affected devices are connected, then run
>>> >> >                     'zpool clear'.
>>> >>
>>> >> What has happened since January 5?  The pool appears fine now.  Did
>>> >> you run a scrub?  Replace devices?  Reboot?  It looks like ZFS
>>> >> encountered an underlying problem with the hardware.
>>> >>
>>> >> Eric
>>> >> _______________________________________________
>>> >> 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
>>
>>
>
> _______________________________________________
> 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/20130212/a75ea4f0/attachment-0001.html>

From steve at linuxsuite.org  Tue Feb 12 13:13:21 2013
From: steve at linuxsuite.org (steve at linuxsuite.org)
Date: Tue, 12 Feb 2013 13:13:21 -0500
Subject: [OmniOS-discuss] Setting service max file descriptors on OmniOS
Message-ID: <c40b6773845ba27d88d0d56e5c9fe491.squirrel@emailmg.netfirms.com>


   Howdy!

          I need to up the max number of file descriptors of the
network/http:lighttpd14
service

     plimit can do it after the service is up, but what is the correct way
to have this set when the service is started? Is there some "property"
that can be changed with svccfg? I can find some reference to
 ${PROPERTY_GROUP}/fd_limit but doesn't seem to exist in lighttpd ?

     This must be a common need. What is the correct way to
do this on OmnOS?


          thanx - steve


From jared at basho.com  Tue Feb 12 14:21:33 2013
From: jared at basho.com (Jared Morrow)
Date: Tue, 12 Feb 2013 12:21:33 -0700
Subject: [OmniOS-discuss] Setting service max file descriptors on OmniOS
In-Reply-To: <c40b6773845ba27d88d0d56e5c9fe491.squirrel@emailmg.netfirms.com>
References: <c40b6773845ba27d88d0d56e5c9fe491.squirrel@emailmg.netfirms.com>
Message-ID: <CACUSOvefkyf+dzYO99PTUTuC01fU+_07ku35Js50co9N7P0XOg@mail.gmail.com>

Steve,

I don't have lighttpd installed, but it should work like anything else that
is a proper service.

You can add a project associated with lighttpd if there isn't already one,
and set the max open file descriptors for that project.

Here's an example:

$ projadd -c "lighttpd settings" -U <username> -G <groupname> -K
"process.max-file-descriptor=(basic,65535,deny)" lighttpdproj
$ svccfg -s network/http:lighttpd14 setprop
'method_context/project=lighttpdproj'
$  svcadm disable network/http:lighttpd
$  svcadm enable network/http:lighttpd


That *should* do the trick.  I'll let someone from OmniOS correct me if I'm
wrong, but that's what we do with our service (Riak) that needs a ton of
file descriptors.

-Jared



On Tue, Feb 12, 2013 at 11:13 AM, <steve at linuxsuite.org> wrote:

>
>    Howdy!
>
>           I need to up the max number of file descriptors of the
> network/http:lighttpd14
> service
>
>      plimit can do it after the service is up, but what is the correct way
> to have this set when the service is started? Is there some "property"
> that can be changed with svccfg? I can find some reference to
>  ${PROPERTY_GROUP}/fd_limit but doesn't seem to exist in lighttpd ?
>
>      This must be a common need. What is the correct way to
> do this on OmnOS?
>
>
>           thanx - steve
>
> _______________________________________________
> 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/20130212/e45a862f/attachment.html>

From jared at basho.com  Tue Feb 12 14:24:33 2013
From: jared at basho.com (Jared Morrow)
Date: Tue, 12 Feb 2013 12:24:33 -0700
Subject: [OmniOS-discuss] Setting service max file descriptors on OmniOS
In-Reply-To: <CACUSOvefkyf+dzYO99PTUTuC01fU+_07ku35Js50co9N7P0XOg@mail.gmail.com>
References: <c40b6773845ba27d88d0d56e5c9fe491.squirrel@emailmg.netfirms.com>
	<CACUSOvefkyf+dzYO99PTUTuC01fU+_07ku35Js50co9N7P0XOg@mail.gmail.com>
Message-ID: <CACUSOvdyooC_PvcH_KRAAAR3Wcz_oQ6BU3=i6RBTnf=1u7fBbA@mail.gmail.com>

Sorry, I meant to add a link to the documentation on projects:

http://docs.oracle.com/cd/E19683-01/817-1592/6mhahuoie/index.html



On Tue, Feb 12, 2013 at 12:21 PM, Jared Morrow <jared at basho.com> wrote:

> Steve,
>
> I don't have lighttpd installed, but it should work like anything else
> that is a proper service.
>
> You can add a project associated with lighttpd if there isn't already one,
> and set the max open file descriptors for that project.
>
> Here's an example:
>
> $ projadd -c "lighttpd settings" -U <username> -G <groupname> -K "process.max-file-descriptor=(basic,65535,deny)" lighttpdproj
> $ svccfg -s network/http:lighttpd14 setprop 'method_context/project=lighttpdproj'
> $  svcadm disable network/http:lighttpd
> $  svcadm enable network/http:lighttpd
>
>
> That *should* do the trick.  I'll let someone from OmniOS correct me if
> I'm wrong, but that's what we do with our service (Riak) that needs a ton
> of file descriptors.
>
> -Jared
>
>
>
> On Tue, Feb 12, 2013 at 11:13 AM, <steve at linuxsuite.org> wrote:
>
>>
>>    Howdy!
>>
>>           I need to up the max number of file descriptors of the
>> network/http:lighttpd14
>> service
>>
>>      plimit can do it after the service is up, but what is the correct way
>> to have this set when the service is started? Is there some "property"
>> that can be changed with svccfg? I can find some reference to
>>  ${PROPERTY_GROUP}/fd_limit but doesn't seem to exist in lighttpd ?
>>
>>      This must be a common need. What is the correct way to
>> do this on OmnOS?
>>
>>
>>           thanx - steve
>>
>> _______________________________________________
>> 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/20130212/c5f7b233/attachment.html>

From ramquick at gmail.com  Wed Feb 13 00:01:57 2013
From: ramquick at gmail.com (Ram Chander)
Date: Wed, 13 Feb 2013 10:31:57 +0530
Subject: [OmniOS-discuss] Lftp package
Message-ID: <CAMRGQbP7wVo2jfFzidPv-f-XjiQFg0Eouh=nizEtFO4oPLbrEQ@mail.gmail.com>

Hi,

Currently there is no lftp package in the omnis repository. . Can we please
add this ?
Csw version of lftp doesnt work and hangs.


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

From ano at bestmx.ru  Wed Feb 13 04:39:42 2013
From: ano at bestmx.ru (Andrey N. Oktyabrski)
Date: Wed, 13 Feb 2013 13:39:42 +0400
Subject: [OmniOS-discuss] Lftp package
In-Reply-To: <CAMRGQbP7wVo2jfFzidPv-f-XjiQFg0Eouh=nizEtFO4oPLbrEQ@mail.gmail.com>
References: <CAMRGQbP7wVo2jfFzidPv-f-XjiQFg0Eouh=nizEtFO4oPLbrEQ@mail.gmail.com>
Message-ID: <511B5F5E.6000906@bestmx.ru>

On 13.02.13 09:01, Ram Chander wrote:
> Currently there is no lftp package in the omnis repository. . Can we
> please add this ?
> Csw version of lftp doesnt work and hangs.
lftp from pkgsrc works well.


From steve at linuxsuite.org  Wed Feb 13 10:36:57 2013
From: steve at linuxsuite.org (steve at linuxsuite.org)
Date: Wed, 13 Feb 2013 10:36:57 -0500
Subject: [OmniOS-discuss] Setting service max file descriptors on OmniOS
In-Reply-To: <CACUSOvefkyf+dzYO99PTUTuC01fU+_07ku35Js50co9N7P0XOg@mail.gmail.com>
References: <c40b6773845ba27d88d0d56e5c9fe491.squirrel@emailmg.netfirms.com>
	<CACUSOvefkyf+dzYO99PTUTuC01fU+_07ku35Js50co9N7P0XOg@mail.gmail.com>
Message-ID: <5211c370c0380d6b843f15ce0d99bfbe.squirrel@emailmg.netfirms.com>

> Steve,
>
> I don't have lighttpd installed, but it should work like anything else
> that
> is a proper service.

       Ok, I'm a newbee on Solaris, but why can't something like this be
possible, have a property like this

root at live-dfs-2:~# svccfg -s network/http:lighttpd14 listprop
general/fd_limit
general/fd_limit              count    8192

      And this would set this service up with this parameter
max-file-descriptor=8192

        Setting resource limits on services like http are a common
requirement. If there
is an alternative to editing the method script and simply adding "ulimit
-n 8192"
then perhaps a property is needed?

      Is the above possible? How do I implement it?

   I found reference to the following for a printer service


# svccfg
svc:> select svc:/application/print/server
svc:/application/print/server> setprop lpsched/num_filters = count: 1
svc:/application/print/server> setprop lpsched/num_notifiers = count: 1
svc:/application/print/server> setprop lpsched/fd_limit = count: 4096
svc:/application/print/server> setprop lpsched/reserved_fds = count: 2
svc:/application/print/server> quit


>
> You can add a project associated with lighttpd if there isn't already one,
> and set the max open file descriptors for that project.
>
> Here's an example:
>
> $ projadd -c "lighttpd settings" -U <username> -G <groupname> -K
> "process.max-file-descriptor=(basic,65535,deny)" lighttpdproj
> $ svccfg -s network/http:lighttpd14 setprop
> 'method_context/project=lighttpdproj'
> $  svcadm disable network/http:lighttpd
> $  svcadm enable network/http:lighttpd
>
>
> That *should* do the trick.

       I get complaint about no such property

svccfg: No such property group "method_context"

         Need to create a property group?

      Must be an easier way? Setting max fd's is a common need....
I want to do something like this

    svccfg -s network/http:lighttpd14  setprop general/fd_limit = count: 8192

      possible? How?


    -steve

>
> -Jared
>
>
>
> On Tue, Feb 12, 2013 at 11:13 AM, <steve at linuxsuite.org> wrote:
>
>>
>>    Howdy!
>>
>>           I need to up the max number of file descriptors of the
>> network/http:lighttpd14
>> service
>>
>>      plimit can do it after the service is up, but what is the correct
>> way
>> to have this set when the service is started? Is there some "property"
>> that can be changed with svccfg? I can find some reference to
>>  ${PROPERTY_GROUP}/fd_limit but doesn't seem to exist in lighttpd ?
>>
>>      This must be a common need. What is the correct way to
>> do this on OmnOS?
>>
>>
>>           thanx - steve
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>



From cnehren at omniti.com  Wed Feb 13 10:52:49 2013
From: cnehren at omniti.com (Chris Nehren)
Date: Wed, 13 Feb 2013 10:52:49 -0500
Subject: [OmniOS-discuss] Lftp package
In-Reply-To: <CAMRGQbP7wVo2jfFzidPv-f-XjiQFg0Eouh=nizEtFO4oPLbrEQ@mail.gmail.com>
References: <CAMRGQbP7wVo2jfFzidPv-f-XjiQFg0Eouh=nizEtFO4oPLbrEQ@mail.gmail.com>
Message-ID: <20130213155248.GH7098@eschaton.local>

On Wed, Feb 13, 2013 at 10:31:57 +0530 , Ram Chander wrote:
> Hi,
> 
> Currently there is no lftp package in the omnis repository. . Can we please
> add this ?
> Csw version of lftp doesnt work and hangs.

>From my FreeBSD machine: 

$ pkg info -d lftp
lftp-4.4.1 depends on:
expat-2.0.1_2
gettext-0.18.1.1
libiconv-1.14

$

All of these packages exist either in core OmniOS or in the omniti-ms
publisher (which OmniTI maintains). This suggests that the dependencies
are in place for lftp. A pain point, however, may be that lftp is
written in C++. You should be able to install the dependencies listed
above and at least give it a try using the instructions found here:
http://omnios.omniti.com/wiki.php/PackagingForOmniOS. Please feel free
to ask questions about that document so that we can improve it.

-- 
Chris Nehren
Site Reliability Engineer, OmniTI

From cnehren at omniti.com  Thu Feb 14 12:40:32 2013
From: cnehren at omniti.com (Chris Nehren)
Date: Thu, 14 Feb 2013 12:40:32 -0500
Subject: [OmniOS-discuss] Lftp package
In-Reply-To: <20130213155248.GH7098@eschaton.local>
References: <CAMRGQbP7wVo2jfFzidPv-f-XjiQFg0Eouh=nizEtFO4oPLbrEQ@mail.gmail.com>
	<20130213155248.GH7098@eschaton.local>
Message-ID: <20130214174031.GI7098@eschaton.local>

On Wed, Feb 13, 2013 at 10:52:49 -0500 , Chris Nehren wrote:
> On Wed, Feb 13, 2013 at 10:31:57 +0530 , Ram Chander wrote:
> > Hi,
> > 
> > Currently there is no lftp package in the omnis repository. . Can we please
> > add this ?
> > Csw version of lftp doesnt work and hangs.
> 
> From my FreeBSD machine: 
> 
> $ pkg info -d lftp
> lftp-4.4.1 depends on:
> expat-2.0.1_2
> gettext-0.18.1.1
> libiconv-1.14
> 
> $
> 
> All of these packages exist either in core OmniOS or in the omniti-ms
> publisher (which OmniTI maintains). This suggests that the dependencies
> are in place for lftp. A pain point, however, may be that lftp is
> written in C++. You should be able to install the dependencies listed
> above and at least give it a try using the instructions found here:
> http://omnios.omniti.com/wiki.php/PackagingForOmniOS. Please feel free
> to ask questions about that document so that we can improve it.

Following on from this, I tried building it on my VPS before work this
morning and got pretty far. This is the only error I encountered:

/bin/sh ../libtool --silent --tag=CXX    --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../lib -I../lib -I../trio       -O2 -Wall -Wwrite-strings
-Woverloaded-virtual -fno-exceptions -fno-rtti -fno-implement-inlines -MT
buffer.lo -MD -MP -MF .deps/buffer.Tpo -c -o buffer.lo buffer.cc
buffer.cc: In member function ?virtual void DataRecoder::PutTranslated(Buffer*,
const char*, int)?: buffer.cc:277:83: error: invalid conversion from ?const
char**? to ?char**? [-fpermissive] /usr/include/iconv.h:44:15: error:
initializing argument 2 of ?size_t iconv(iconv_t, char**, size_t*, char**,
size_t*)? [-fpermissive]

As the output suggests, using -fpermissive fixes the build. Once it's
built, it seems to actually work, too, suggesting there aren't any ABI
issues. I haven't had time to create a proper code patch, but at first
glance it appears to be a simple fix. I'll try to have a package
available tonight.

-- 
Chris Nehren
Site Reliability Engineer, OmniTI

From GAlbitz at albitz.biz  Sat Feb 16 11:14:11 2013
From: GAlbitz at albitz.biz (Grant Albitz)
Date: Sat, 16 Feb 2013 16:14:11 +0000
Subject: [OmniOS-discuss] ISCSI SSD Performance
Message-ID: <0B8E74B73A30D941847CF77E766E365C126A924D@ALPHA.PSC.Net>

Hi I am trying to track down a performance issue with my setup.

I have 24 ssds in 6 vdevs (4 drives per) that are then striped. Essentially a raid50. Originally I had a perc h310 and saw similar numbers. I have since switched to a perch h710 and have each drive in raid 0 and presented to the os. In both cases the numbers are the same. I also tried 8 devices per vdev with only 3 vdevs and the numbers were also the same.I am thinking I am tracking down a zfs tunable but I am not sure what to try. My reads are ? of my writes. Given a raid 50 I was expecting the opposite. The volume is being presented as an iscsi lun. The benchmarks below were run from a vmware guest. The esxi host is connected to the iscsi target via a 10g interface (direct connection).

There is no l2arche, but the entire pool is ssd..


-----------------------------------------------------------------------
CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

           Sequential Read :   361.519 MB/s
          Sequential Write :   690.307 MB/s
         Random Read 512KB :   298.297 MB/s
        Random Write 512KB :   517.125 MB/s
    Random Read 4KB (QD=1) :    19.731 MB/s [  4817.0 IOPS]
   Random Write 4KB (QD=1) :    18.025 MB/s [  4400.7 IOPS]
   Random Read 4KB (QD=32) :   174.766 MB/s [ 42667.5 IOPS]
  Random Write 4KB (QD=32) :   209.150 MB/s [ 51061.9 IOPS]

  Test : 50 MB [C: 10.8% (32.3/299.7 GB)] (x1) <0Fill>
  Date : 2013/02/16 11:07:10
    OS : Windows 8 Professional [6.2 Build 9200] (x64)



-----------------------------------------------------------------------
CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

           Sequential Read :   351.646 MB/s
          Sequential Write :   652.356 MB/s
         Random Read 512KB :   287.946 MB/s
        Random Write 512KB :   468.861 MB/s
    Random Read 4KB (QD=1) :    19.915 MB/s [  4862.2 IOPS]
   Random Write 4KB (QD=1) :    17.263 MB/s [  4214.7 IOPS]
   Random Read 4KB (QD=32) :   169.849 MB/s [ 41466.9 IOPS]
  Random Write 4KB (QD=32) :   189.730 MB/s [ 46320.8 IOPS]

  Test : 100 MB [C: 10.8% (32.2/299.7 GB)] (x1) <0Fill>
  Date : 2013/02/16 11:05:07
    OS : Windows 8 Professional [6.2 Build 9200] (x64)

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

From palmertime at gmail.com  Sat Feb 16 11:42:29 2013
From: palmertime at gmail.com (Michael Palmer)
Date: Sat, 16 Feb 2013 08:42:29 -0800
Subject: [OmniOS-discuss] ISCSI SSD Performance
In-Reply-To: <0B8E74B73A30D941847CF77E766E365C126A924D@ALPHA.PSC.Net>
References: <0B8E74B73A30D941847CF77E766E365C126A924D@ALPHA.PSC.Net>
Message-ID: <7487479444555085024@unknownmsgid>

What ssd are you using?

Sent from my iPhone

On Feb 16, 2013, at 8:18 AM, Grant Albitz <GAlbitz at albitz.biz> wrote:

  Hi I am trying to track down a performance issue with my setup.



I have 24 ssds in 6 vdevs (4 drives per) that are then striped. Essentially
a raid50. Originally I had a perc h310 and saw similar numbers. I have
since switched to a perch h710 and have each drive in raid 0 and presented
to the os. In both cases the numbers are the same. I also tried 8 devices
per vdev with only 3 vdevs and the numbers were also the same.I am thinking
I am tracking down a zfs tunable but I am not sure what to try. My reads
are ? of my writes. Given a raid 50 I was expecting the opposite. The
volume is being presented as an iscsi lun. The benchmarks below were run
from a vmware guest. The esxi host is connected to the iscsi target via a
10g interface (direct connection).



There is no l2arche, but the entire pool is ssd..





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

CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo

                           Crystal Dew World : http://crystalmark.info/

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

* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]



           Sequential Read :   361.519 MB/s

          Sequential Write :   690.307 MB/s

         Random Read 512KB :   298.297 MB/s

        Random Write 512KB :   517.125 MB/s

    Random Read 4KB (QD=1) :    19.731 MB/s [  4817.0 IOPS]

   Random Write 4KB (QD=1) :    18.025 MB/s [  4400.7 IOPS]

   Random Read 4KB (QD=32) :   174.766 MB/s [ 42667.5 IOPS]

  Random Write 4KB (QD=32) :   209.150 MB/s [ 51061.9 IOPS]



  Test : 50 MB [C: 10.8% (32.3/299.7 GB)] (x1) <0Fill>

  Date : 2013/02/16 11:07:10

    OS : Windows 8 Professional [6.2 Build 9200] (x64)







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

CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo

                           Crystal Dew World : http://crystalmark.info/

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

* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]



           Sequential Read :   351.646 MB/s

          Sequential Write :   652.356 MB/s

         Random Read 512KB :   287.946 MB/s

        Random Write 512KB :   468.861 MB/s

    Random Read 4KB (QD=1) :    19.915 MB/s [  4862.2 IOPS]

   Random Write 4KB (QD=1) :    17.263 MB/s [  4214.7 IOPS]

   Random Read 4KB (QD=32) :   169.849 MB/s [ 41466.9 IOPS]

  Random Write 4KB (QD=32) :   189.730 MB/s [ 46320.8 IOPS]



  Test : 100 MB [C: 10.8% (32.2/299.7 GB)] (x1) <0Fill>

  Date : 2013/02/16 11:05:07

    OS : Windows 8 Professional [6.2 Build 9200] (x64)



_______________________________________________
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/20130216/7bb88c15/attachment.html>

From GAlbitz at albitz.biz  Sat Feb 16 12:18:08 2013
From: GAlbitz at albitz.biz (Grant Albitz)
Date: Sat, 16 Feb 2013 17:18:08 +0000
Subject: [OmniOS-discuss] ISCSI SSD Performance
Message-ID: <0B8E74B73A30D941847CF77E766E365C126AA2A6@ALPHA.PSC.Net>




Hi I am trying to track down a performance issue with my setup.

I have 24 ssds in 6 vdevs (4 drives per) that are then striped. Essentially a raid50. Originally I had a perc h310 and saw similar numbers. I have since switched to a perch h710 and have each drive in raid 0 and presented to the os. In both cases the numbers are the same. I also tried 8 devices per vdev with only 3 vdevs and the numbers were also the same.I am thinking I am tracking down a zfs tunable but I am not sure what to try. My reads are ? of my writes. Given a raid 50 I was expecting the opposite. The volume is being presented as an iscsi lun. The benchmarks below were run from a vmware guest. The esxi host is connected to the iscsi target via a 10g interface (direct connection).

There is no l2arche, but the entire pool is ssd..


-----------------------------------------------------------------------
CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

           Sequential Read :   361.519 MB/s
          Sequential Write :   690.307 MB/s
         Random Read 512KB :   298.297 MB/s
        Random Write 512KB :   517.125 MB/s
    Random Read 4KB (QD=1) :    19.731 MB/s [  4817.0 IOPS]
   Random Write 4KB (QD=1) :    18.025 MB/s [  4400.7 IOPS]
   Random Read 4KB (QD=32) :   174.766 MB/s [ 42667.5 IOPS]
  Random Write 4KB (QD=32) :   209.150 MB/s [ 51061.9 IOPS]

  Test : 50 MB [C: 10.8% (32.3/299.7 GB)] (x1) <0Fill>
  Date : 2013/02/16 11:07:10
    OS : Windows 8 Professional [6.2 Build 9200] (x64)



-----------------------------------------------------------------------
CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

           Sequential Read :   351.646 MB/s
          Sequential Write :   652.356 MB/s
         Random Read 512KB :   287.946 MB/s
        Random Write 512KB :   468.861 MB/s
    Random Read 4KB (QD=1) :    19.915 MB/s [  4862.2 IOPS]
   Random Write 4KB (QD=1) :    17.263 MB/s [  4214.7 IOPS]
   Random Read 4KB (QD=32) :   169.849 MB/s [ 41466.9 IOPS]
  Random Write 4KB (QD=32) :   189.730 MB/s [ 46320.8 IOPS]

  Test : 100 MB [C: 10.8% (32.2/299.7 GB)] (x1) <0Fill>
  Date : 2013/02/16 11:05:07
    OS : Windows 8 Professional [6.2 Build 9200] (x64)

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

From johan.kragsterman at capvert.se  Sat Feb 16 12:42:49 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Sat, 16 Feb 2013 18:42:49 +0100
Subject: [OmniOS-discuss] Ang:  ISCSI SSD Performance
In-Reply-To: <0B8E74B73A30D941847CF77E766E365C126A924D@ALPHA.PSC.Net>
References: <0B8E74B73A30D941847CF77E766E365C126A924D@ALPHA.PSC.Net>
Message-ID: <OFD05FDB70.8C0EE791-ONC1257B14.00614DE2-C1257B14.00614DE9@inse.com>

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

From Fred_Liu at issi.com  Sat Feb 16 23:42:09 2013
From: Fred_Liu at issi.com (Fred Liu)
Date: Sat, 16 Feb 2013 20:42:09 -0800
Subject: [OmniOS-discuss] [zfs-discuss] zfs-discuss mailing list &
	opensolaris EOL
In-Reply-To: <51201931.8060903@cos.ru>
References: <D1B1A95FBDCF7341AC8EB0A97FCCC4771EF7BB55@SN2PRD0410MB372.namprd04.prod.outlook.com>
	<CAEW8MaWrKNbSTMNdfy7JPUw_0xAigYaBF1MQ7=1+-O_AMkzSzw@mail.gmail.com>
	<51201931.8060903@cos.ru>
Message-ID: <A5A6EA4AE9DCC44F8E7FCB4D6317B1D2022B1B08E680@SH-MAIL.ISSI.COM>

Is it possible to replicate the whole opensolaris site to illumos/openindiana/smartos/omnios site in a sub-catalog as archive?

>-----Original Message-----
>From: zfs-discuss-bounces at opensolaris.org
>[mailto:zfs-discuss-bounces at opensolaris.org] On Behalf Of Jim Klimov
>Sent: Sunday, February 17, 2013 7:42 AM
>To: zfs-discuss at opensolaris.org
>Subject: Re: [zfs-discuss] zfs-discuss mailing list & opensolaris EOL
>
>Hello Cindy,
>
>Are there any plans to preserve the official mailing lists' archives, or will they
>go the way of Jive forums and the future digs for bits of knowledge would rely
>on alternate mirrors and caches?
>
>I understand that Oracle has some business priorities, but retiring hardware
>causes site shutdown? They've gotta be kidding, with all the buzz about clouds
>and virtualization ;)
>
>I'd guess, you also are not authorized to say whether Oracle might permit
>re-use (re-hosting) of current OpenSolaris.Org materials or even give away
>the site and domain for community steering and rid itself of more black PR by
>shooting down another public project of the Sun legacy (hint: if the site does
>wither and die in community's hands - it is not Oracle's fault; and if it lives on -
>Oracle did something good for karma... win-win, at no price).
>
>Thanks for your helpfulness in the past years, //Jim
>_______________________________________________
>zfs-discuss mailing list
>zfs-discuss at opensolaris.org
>http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


From johan.kragsterman at capvert.se  Sun Feb 17 03:19:23 2013
From: johan.kragsterman at capvert.se (Johan Kragsterman)
Date: Sun, 17 Feb 2013 09:19:23 +0100
Subject: [OmniOS-discuss] kvm in zones
Message-ID: <OFDA5516F9.B6CEC10F-ONC1257B15.002DB895-C1257B15.002DB898@inse.com>

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

From kent at watsen.net  Fri Feb 22 09:07:58 2013
From: kent at watsen.net (Kent Watsen)
Date: Fri, 22 Feb 2013 09:07:58 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
Message-ID: <51277BBE.6030108@watsen.net>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130222/8dd09054/attachment-0001.html>

From jesus at omniti.com  Fri Feb 22 09:27:29 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Fri, 22 Feb 2013 09:27:29 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <51277BBE.6030108@watsen.net>
References: <51277BBE.6030108@watsen.net>
Message-ID: <CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>

You have two choices and both should work equally well:

If you want to run latest stable (that happens to be r151004) you'll need
to use the r151004 branch of omnios-build: git clone -b r151004
anon at src.omniti.com:~omnios/core/omnios-build

If you want to dev stuff, it may be better to use bloody. Bloody is...
well... bloody. And as you've noticed has some issues handling an upgrade
from 151004 that have not been fixed yet.  So, you'll need to directly
install it or work some IPS trickery to get bloody installed.  The "master"
branch of omnios-build is bloody.

On Fri, Feb 22, 2013 at 9:07 AM, Kent Watsen <kent at watsen.net> wrote:

>
> I'm trying to compile the AMD fork of illumos-kvm<https://github.com/arekinath/illumos-kvm/blob/master/README.md>,
> the build instructions for which say " set the path for the KERNEL_SOURCEdirectory to point to the root of a checked out and built illumos
> directory".
>
> I figured that compiling OmniOS would be one way to get a checked out and
> built illumos directory, so I decided to give  OmniOS's Build Instructions<http://omnios.omniti.com/wiki.php/BuildInstructions>a go, which I I struggled through.
>
> Currently I'm stuck on the ` # ./buildctl list` command, but I want to
> recount all my so that this document can be enhanced.
>
> Environment: OmniOS stable, updated to most recent release.
>                      Created a non-global zone for this compiling activity
>                       (I put all services into zones, leaving the global
> zone in its most minimal state)
>
>
> Following the instructions, the "Closed Tools" section didn't seems to
> provide any actions, so I skipped it.
> The "How-to" section has a very nice block of commands to cut-n-paste,
> here's how it went:
>
> STEP 1
> ====
>
> *root at compiler:~# git clone anon at src.omniti.com:~omnios/core/omnios-build*
> -bash: git: command not found
> *root at compiler:~# pkg install pkg:/developer/versioning/git     (Add an
> instruction to install git?)*
>            Packages to install:  1
>        Create boot environment: No
> Create backup boot environment: No
>
> DOWNLOAD                                  PKGS       FILES    XFER (MB)
> Completed                                  1/1     353/353    10.4/10.4$<3>
>
> PHASE                                        ACTIONS
> Install Phase                                635/635
>
> PHASE                                          ITEMS
> Package State Update Phase                       1/1
> Image State Update Phase                         2/2
> *root at compiler:~# git clone anon at src.omniti.com:~omnios/core/omnios-build*
> *
> *Cloning into 'omnios-build'...
> The authenticity of host 'src.omniti.com (199.15.226.39)' can't be
> established.
> RSA key fingerprint is 51:bb:7a:4a:3a:de:ff:dc:0a:87:8b:4f:d4:63:b0:d2.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'src.omniti.com,199.15.226.39' (RSA) to the
> list of known hosts.
> remote: Counting objects: 6243, done.
> remote: Compressing objects: 100% (5116/5116), done.
> remote: Total 6243 (delta 2924), reused 1441 (delta 679)
> Receiving objects: 100% (6243/6243), 25.84 MiB | 1.85 MiB/s, done.
> Resolving deltas: 100% (2924/2924), done.
>
> STEP 2
> ====
>
> *root at compiler:~# cd omnios-build/build**
> *
>
> STEP 3
> ====
>
> *root at compiler:~/omnios-build/build# ./buildctl list**
> *You appear to be missing some basic build requirements.
> To fix this run:
>
>   sudo pkg install developer/gcc47 developer/object-file
> developer/build/gnu-make system/header system/library/math/header-math
>
> An Error occured in the build. Do you wish to continue anyway? (y/n) n
> ===== Build aborted =====
> *root at compiler:~/omnios-build/build# pkg install developer/gcc47
> developer/object-file developer/build/gnu-make system/header
> system/library/math/header-math**
> *Creating Plan
> pkg install: The following pattern(s) did not match any allowable
> packages.  Try
> using a different matching pattern, or refreshing publisher information:
>
>     developer/gcc47
>
> *root at compiler:~/omnios-build/build# pkg set-publisher -G '*' -g
> http://pkg.omniti.com/omnios/bloody/ omnios
> (Add an instruction to install bloody?)
> ****root at compiler:~/omnios-build/build# pkg publisher**
> *PUBLISHER                             TYPE     STATUS   URI
> omnios                                origin   online
> http://pkg.omniti.com/omnios/bloody/
> *root at compiler:~/omnios-build/build# pkg update**
> *            Packages to update:   5
>        Create boot environment:  No
> Create backup boot environment: Yes
>
> DOWNLOAD                                  PKGS       FILES    XFER (MB)
> Completed                                  5/5       63/63    53.6/53.6$<3>
>
> PHASE                                        ACTIONS
> Update Phase                                   76/76
>
> PHASE                                          ITEMS
> Package State Update Phase                     10/10
> Package Cache Update Phase                       5/5
> Image State Update Phase                         2/2
>
> ---------------------------------------------------------------------------
> NOTE: Please review release notes posted at:
>
> http://omnios.omniti.com/ReleaseNotes
> ---------------------------------------------------------------------------
>
> *root at compiler:~/omnios-build/build# ./buildctl list**
> *You appear to be missing some basic build requirements.
> To fix this run:
>
>   sudo pkg install developer/gcc47 developer/object-file
> developer/build/gnu-make system/header system/library/math/header-math
>
> An Error occured in the build. Do you wish to continue anyway? (y/n) n
> ===== Build aborted =====
> *root at compiler:~/omnios-build/build# pkg install developer/gcc47
> developer/object-file developer/build/gnu-make system/header
> system/library/math/header-math**
> *Creating Plan /
> pkg install: No matching version of system/library/math/header-math can be
> installed:
>   Reject:
> pkg://omnios/system/library/math/header-math at 0.5.11,5.11-0.151002:20120401T180415Z
>
> pkg://omnios/system/library/math/header-math at 0.5.11,5.11-0.151005:20121031T183225Z
>   Reason:  This version is excluded by installed incorporation
> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.151004:20130208T215446Z
> No matching version of developer/build/gnu-make can be installed:
>   Reject:
> pkg://omnios/developer/build/gnu-make at 3.82,5.11-0.151002:20120401T174135Z
>
> pkg://omnios/developer/build/gnu-make at 3.82,5.11-0.151005:20121031T155036Z
>   Reason:  This version is excluded by installed incorporation
> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.151004:20130208T215446Z
> No matching version of developer/object-file can be installed:
>   Reject:
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120401T174415Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120418T163114Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120418T225330Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120509T022251Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120518T203209Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120522T010146Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120529T141500Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120611T191626Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120614T103701Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120628T043959Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120705T162018Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120719T230832Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120726T140607Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120807T211706Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120813T150123Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120827T190440Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120831T134351Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120912T140322Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120914T135506Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120920T221650Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120926T053938Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20121004T184549Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121102T203643Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121105T213146Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121107T173024Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121112T150347Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121210T220409Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121228T023348Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130105T180723Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130116T230003Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130117T170208Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130124T225816Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130129T221145Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130208T145400Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130220T191556Z
>   Reason:  This version is excluded by installed incorporation
> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151004:20121011T223920Z
>            This version is excluded by installed incorporation
> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.151004:20121023T161839Z
> No matching version of system/header can be installed:
>   Reject:
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120401T180118Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120418T164413Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120418T225419Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120509T022340Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120518T203257Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120522T010234Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120529T141549Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120611T191715Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120614T103750Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120628T044048Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120705T162106Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120719T230920Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120726T140655Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120807T211754Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120813T150211Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120827T190528Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120831T134439Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120912T140411Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120914T135555Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120920T221738Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120926T054026Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151002:20121004T184637Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121102T203731Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121105T213234Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121107T173112Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121112T150435Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121210T220457Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121228T023436Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130105T180811Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130116T230051Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130117T170257Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130124T225904Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130129T221233Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130208T145448Z
>
> pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130220T191644Z
>   Reason:  This version is excluded by installed incorporation
> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151004:20121011T223920Z
>            This version is excluded by installed incorporation
> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.151004:20121023T161839Z
>
> *root at compiler:~/omnios-build/build# ./buildctl list**
> *You appear to be missing some basic build requirements.
> To fix this run:
>
>   sudo pkg install developer/gcc47 developer/object-file
> developer/build/gnu-make system/header system/library/math/header-math
>
> An Error occured in the build. Do you wish to continue anyway? (y/n) n
> ===== Build aborted =====
>
>
> Now what?
>
>
> Thanks,
> Kent
>
>
>
> _______________________________________________
> 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/20130222/8daa3532/attachment-0001.html>

From esproul at omniti.com  Fri Feb 22 09:53:43 2013
From: esproul at omniti.com (Eric Sproul)
Date: Fri, 22 Feb 2013 09:53:43 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <51277BBE.6030108@watsen.net>
References: <51277BBE.6030108@watsen.net>
Message-ID: <CA+QY2RSP-vdK3Q37f3=FzGAo5nz5qsEjmsygn-qA6TnpaSZZgQ@mail.gmail.com>

Hi Kent,
We need to spruce up the build instructions; as you've noted, they are
a little sparse in places.  Generally when we (OmniTI) are building
new illumos bits, we are doing so on bloody.  The master branch of the
build repo assumes you're on bloody, which is why it's indicating
gcc47 instead of gcc46.

You've also noted that there are issues upgrading from r151004 to
bloody, which we're aware of and working through as we prep for the
next stable release.  There have been more changes in this cycle than
in the previous one.  For now, your best bet would be to do a fresh
install directly to bloody.

I'll look at getting the docs updated to be more clear.
Eric


On Fri, Feb 22, 2013 at 9:07 AM, Kent Watsen <kent at watsen.net> wrote:
>
> I'm trying to compile the AMD fork of illumos-kvm, the build instructions
> for which say " set the path for the KERNEL_SOURCE directory to point to the
> root of a checked out and built illumos directory".
>
> I figured that compiling OmniOS would be one way to get a checked out and
> built illumos directory, so I decided to give  OmniOS's Build Instructions a
> go, which I I struggled through.
>
> Currently I'm stuck on the ` # ./buildctl list` command, but I want to
> recount all my so that this document can be enhanced.
>
> Environment: OmniOS stable, updated to most recent release.
>                      Created a non-global zone for this compiling activity
>                       (I put all services into zones, leaving the global
> zone in its most minimal state)
>
>
> Following the instructions, the "Closed Tools" section didn't seems to
> provide any actions, so I skipped it.
> The "How-to" section has a very nice block of commands to cut-n-paste,
> here's how it went:
>
> STEP 1
> ====
>
> root at compiler:~# git clone anon at src.omniti.com:~omnios/core/omnios-build
> -bash: git: command not found
> root at compiler:~# pkg install pkg:/developer/versioning/git     (Add an
> instruction to install git?)
>            Packages to install:  1
>        Create boot environment: No
> Create backup boot environment: No
>
> DOWNLOAD                                  PKGS       FILES    XFER (MB)
> Completed                                  1/1     353/353    10.4/10.4$<3>
>
> PHASE                                        ACTIONS
> Install Phase                                635/635
>
> PHASE                                          ITEMS
> Package State Update Phase                       1/1
> Image State Update Phase                         2/2
> root at compiler:~# git clone anon at src.omniti.com:~omnios/core/omnios-build
> Cloning into 'omnios-build'...
> The authenticity of host 'src.omniti.com (199.15.226.39)' can't be
> established.
> RSA key fingerprint is 51:bb:7a:4a:3a:de:ff:dc:0a:87:8b:4f:d4:63:b0:d2.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'src.omniti.com,199.15.226.39' (RSA) to the list
> of known hosts.
> remote: Counting objects: 6243, done.
> remote: Compressing objects: 100% (5116/5116), done.
> remote: Total 6243 (delta 2924), reused 1441 (delta 679)
> Receiving objects: 100% (6243/6243), 25.84 MiB | 1.85 MiB/s, done.
> Resolving deltas: 100% (2924/2924), done.
>
> STEP 2
> ====
>
> root at compiler:~# cd omnios-build/build
>
>
> STEP 3
> ====
>
> root at compiler:~/omnios-build/build# ./buildctl list
> You appear to be missing some basic build requirements.
> To fix this run:
>
>   sudo pkg install developer/gcc47 developer/object-file
> developer/build/gnu-make system/header system/library/math/header-math
>
> An Error occured in the build. Do you wish to continue anyway? (y/n) n
> ===== Build aborted =====
> root at compiler:~/omnios-build/build# pkg install developer/gcc47
> developer/object-file developer/build/gnu-make system/header
> system/library/math/header-math
> Creating Plan
> pkg install: The following pattern(s) did not match any allowable packages.
> Try
> using a different matching pattern, or refreshing publisher information:
>
>     developer/gcc47
>
> root at compiler:~/omnios-build/build# pkg set-publisher -G '*' -g
> http://pkg.omniti.com/omnios/bloody/ omnios
> (Add an instruction to install bloody?)
> root at compiler:~/omnios-build/build# pkg publisher
> PUBLISHER                             TYPE     STATUS   URI
> omnios                                origin   online
> http://pkg.omniti.com/omnios/bloody/
> root at compiler:~/omnios-build/build# pkg update
>             Packages to update:   5
>        Create boot environment:  No
> Create backup boot environment: Yes
>
> DOWNLOAD                                  PKGS       FILES    XFER (MB)
> Completed                                  5/5       63/63    53.6/53.6$<3>
>
> PHASE                                        ACTIONS
> Update Phase                                   76/76
>
> PHASE                                          ITEMS
> Package State Update Phase                     10/10
> Package Cache Update Phase                       5/5
> Image State Update Phase                         2/2
>
> ---------------------------------------------------------------------------
> NOTE: Please review release notes posted at:
>
> http://omnios.omniti.com/ReleaseNotes
> ---------------------------------------------------------------------------
>
> root at compiler:~/omnios-build/build# ./buildctl list
> You appear to be missing some basic build requirements.
> To fix this run:
>
>   sudo pkg install developer/gcc47 developer/object-file
> developer/build/gnu-make system/header system/library/math/header-math
>
> An Error occured in the build. Do you wish to continue anyway? (y/n) n
> ===== Build aborted =====
> root at compiler:~/omnios-build/build# pkg install developer/gcc47
> developer/object-file developer/build/gnu-make system/header
> system/library/math/header-math
> Creating Plan /
> pkg install: No matching version of system/library/math/header-math can be
> installed:
>   Reject:
> pkg://omnios/system/library/math/header-math at 0.5.11,5.11-0.151002:20120401T180415Z
>
> pkg://omnios/system/library/math/header-math at 0.5.11,5.11-0.151005:20121031T183225Z
>   Reason:  This version is excluded by installed incorporation
> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.151004:20130208T215446Z
> No matching version of developer/build/gnu-make can be installed:
>   Reject:
> pkg://omnios/developer/build/gnu-make at 3.82,5.11-0.151002:20120401T174135Z
>
> pkg://omnios/developer/build/gnu-make at 3.82,5.11-0.151005:20121031T155036Z
>   Reason:  This version is excluded by installed incorporation
> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.151004:20130208T215446Z
> No matching version of developer/object-file can be installed:
>   Reject:
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120401T174415Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120418T163114Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120418T225330Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120509T022251Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120518T203209Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120522T010146Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120529T141500Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120611T191626Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120614T103701Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120628T043959Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120705T162018Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120719T230832Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120726T140607Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120807T211706Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120813T150123Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120827T190440Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120831T134351Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120912T140322Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120914T135506Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120920T221650Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20120926T053938Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151002:20121004T184549Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121102T203643Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121105T213146Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121107T173024Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121112T150347Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121210T220409Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20121228T023348Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130105T180723Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130116T230003Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130117T170208Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130124T225816Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130129T221145Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130208T145400Z
>
> pkg://omnios/developer/object-file at 0.5.11,5.11-0.151005:20130220T191556Z
>   Reason:  This version is excluded by installed incorporation
> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151004:20121011T223920Z
>            This version is excluded by installed incorporation
> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.151004:20121023T161839Z
> No matching version of system/header can be installed:
>   Reject:  pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120401T180118Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120418T164413Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120418T225419Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120509T022340Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120518T203257Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120522T010234Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120529T141549Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120611T191715Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120614T103750Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120628T044048Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120705T162106Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120719T230920Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120726T140655Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120807T211754Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120813T150211Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120827T190528Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120831T134439Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120912T140411Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120914T135555Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120920T221738Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20120926T054026Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151002:20121004T184637Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121102T203731Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121105T213234Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121107T173112Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121112T150435Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121210T220457Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20121228T023436Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130105T180811Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130116T230051Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130117T170257Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130124T225904Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130129T221233Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130208T145448Z
>            pkg://omnios/system/header at 0.5.11,5.11-0.151005:20130220T191644Z
>   Reason:  This version is excluded by installed incorporation
> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151004:20121011T223920Z
>            This version is excluded by installed incorporation
> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.151004:20121023T161839Z
>
> root at compiler:~/omnios-build/build# ./buildctl list
> You appear to be missing some basic build requirements.
> To fix this run:
>
>   sudo pkg install developer/gcc47 developer/object-file
> developer/build/gnu-make system/header system/library/math/header-math
>
> An Error occured in the build. Do you wish to continue anyway? (y/n) n
> ===== Build aborted =====
>
>
> Now what?
>
>
> Thanks,
> Kent
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From kent at watsen.net  Fri Feb 22 11:29:13 2013
From: kent at watsen.net (Kent Watsen)
Date: Fri, 22 Feb 2013 11:29:13 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
Message-ID: <51279CD9.8080508@watsen.net>

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

From alka at hfg-gmuend.de  Fri Feb 22 15:09:38 2013
From: alka at hfg-gmuend.de (alka)
Date: Fri, 22 Feb 2013 21:09:38 +0100
Subject: [OmniOS-discuss] Preconfigured distributable OmniOS NAS with
	mirrorred USB sticks
Message-ID: <2EDC7C4A-0CC1-4E39-AE49-4ACB67F78542@hfg-gmuend.de>

about a ready to use mirrorred USB based NAS/SAN

OmniOS is more and more my first choice for a NAS or SAN solution.
With newer and faster USB sticks and disabled atime there is nearly no difference to a disk booted NAS or SAN.

I have now started "napp-it to go", a solution for a preconfigured ZFS File, SAN or media-.server running from USB sticks.:
I put together all needed things like cloning tools or support for mirroring in the Web-UI to allow

- booting a distributeable ready to use solution on USB sticks  (insert stick, boot and manage the preconfigured SAN via Web-UI), 
- no Unix skills needed for basic management 
- add a second stick to mirror rpool (Web-UI  Disk - mirror rpool)


Howto and Tools to clone such a ready to use stick (preconfigured for a special hardware like HP Microserver or a SM mainboard line)
http://www.napp-it.org/manuals/to-go_en.html


Gea
napp-it.org

-  


From esproul at omniti.com  Fri Feb 22 15:29:48 2013
From: esproul at omniti.com (Eric Sproul)
Date: Fri, 22 Feb 2013 15:29:48 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <51279CD9.8080508@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
Message-ID: <CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>

buildctl has rather bit-rotted-- we don't really use it much
internally.  Nevertheless, what buildctl expects for names is the
package FMRI, e.g. "developer/build/autoconf", because it has scraped
those from the PKG variable in each build.sh file.  So what you might
do is 'for i in $(./buildctl list) ; do ./buildctl $i ; done'

Eric

On Fri, Feb 22, 2013 at 11:29 AM, Kent Watsen <kent at watsen.net> wrote:
>
>
>
> On 2/22/13 9:27 AM, Theo Schlossnagle wrote:
>
> You have two choices and both should work equally well:
>
> If you want to run latest stable (that happens to be r151004) you'll need to
> use the r151004 branch of omnios-build: git clone -b r151004
> anon at src.omniti.com:~omnios/core/omnios-build
>
>
>
> Rerunning the instructions using the stable repo got me much further!  (now
> I'm stuck on `./buildctl build`)
>
> This is on a fresh zone:
>
> root at compiler:~# git clone -b r151004
> anon at src.omniti.com:~omnios/core/omnios-build
>
> -bash: git: command not found
> root at compiler:~# pkg install pkg:/developer/versioning/git (Add an
> instruction to install git?)
>            Packages to install:  1
>        Create boot environment: No
> Create backup boot environment: No
>
> DOWNLOAD                                  PKGS       FILES    XFER (MB)
> Completed                                  1/1     353/353    10.4/10.4$<3>
>
> PHASE                                        ACTIONS
> Install Phase                                635/635
>
> PHASE                                          ITEMS
> Package State Update Phase                       1/1
> Image State Update Phase                         2/2
> root at compiler:~# git clone -b r151004
> anon at src.omniti.com:~omnios/core/omnios-build
>
> Cloning into 'omnios-build'...
> The authenticity of host 'src.omniti.com (199.15.226.39)' can't be
> established.
> RSA key fingerprint is 51:bb:7a:4a:3a:de:ff:dc:0a:87:8b:4f:d4:63:b0:d2.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'src.omniti.com,199.15.226.39' (RSA) to the list
> of known hosts.
> remote: Counting objects: 6243, done.
> remote: Compressing objects: 100% (5116/5116), done.
> remote: Total 6243 (delta 2929), reused 1444 (delta 679)
> Receiving objects: 100% (6243/6243), 25.81 MiB | 1.66 MiB/s, done.
> Resolving deltas: 100% (2929/2929), done.
> root at compiler:~# cd omnios-build/build
>
> root at compiler:~/omnios-build/build# ./buildctl list
> You appear to be missing some basic build requirements.
> To fix this run:
>
>   sudo pkg install developer/gcc46 developer/object-file
> developer/build/gnu-make system/header system/library/math/header-math
>
>
> An Error occured in the build. Do you wish to continue anyway? (y/n) n
> ===== Build aborted =====
> root at compiler:~/omnios-build/build# pkg install developer/gcc46
> developer/object-file developer/build/gnu-make system/header
> system/library/math/header-math
> Creating Plan
>            Packages to install:  9
>        Create boot environment: No
> Create backup boot environment: No
>
> DOWNLOAD                                  PKGS       FILES    XFER (MB)
> Completed                                  9/9   2732/2732    99.3/99.3$<3>
>
> PHASE                                        ACTIONS
> Install Phase                              3204/3204
>
> PHASE                                          ITEMS
> Package State Update Phase                       9/9
> Image State Update Phase                         2/2
> root at compiler:~/omnios-build/build# ./buildctl build
> --- You cannot run this as root  (Add an instruction to install git?)
> An Error occured in the build. Do you wish to continue anyway? (y/n) n
> ===== Build aborted =====
> root at compiler:~/omnios-build/build# svcadm disable autofs
> root at compiler:~/omnios-build/build# useradd -m -b /home  -c "Kent Watsen"
> kent
> 64 blocks
> root at compiler:~/omnios-build/build# passwd kent
> New Password:
> Re-enter new Password:
> passwd: password successfully changed for kent
>
>
> Logging in again as "kent":
>
> kent at compiler:/home/kent$ git clone -b r151004
> anon at src.omniti.com:~omnios/core/omnios-build
>
> Cloning into 'omnios-build'...
> The authenticity of host 'src.omniti.com (199.15.226.39)' can't be
> established.
> RSA key fingerprint is 51:bb:7a:4a:3a:de:ff:dc:0a:87:8b:4f:d4:63:b0:d2.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'src.omniti.com,199.15.226.39' (RSA) to the list
> of known hosts.
> remote: Counting objects: 6243, done.
> remote: Compressing objects: 100% (5116/5116), done.
> remote: Total 6243 (delta 2929), reused 1441 (delta Receiving objects679)
> Receiving objects: 100% (6243/6243), 25.83 MiB | 1.34 MiB/s, done.
> Resolving deltas: 100% (2929/2929), done.
> kent at compiler:/home/kent$ cd omnios-build/build
> kent at compiler:/home/kent/omnios-build/build$ ./buildctl list
>  * archiver/gnu-tar
>  * caiman
>  * compress/bzip2
>  * compress/gzip
>  * compress/p7zip
>  * compress/unzip
>  * compress/xz
>  * compress/zip
>  * data/iso-codes
>  * database/sqlite-3
>  * developer/build/autoconf
>  * developer/build/automake-111
>  * developer/build/automake-19
>  * developer/build/gnu-make
>  * developer/build/libtool
>  * developer/build/make
>  * developer/dtrace/toolkit
>  * developer/gcc44
>  * developer/gcc44/libgmp-gcc44
>  * developer/gcc44/libmpc-gcc44
>  * developer/gcc44/libmpfr-gcc44
>  * developer/gcc46
>  * developer/gcc46/libgmp-gcc46
>  * developer/gcc46/libmpc-gcc46
>  * developer/gcc46/libmpfr-gcc46
>  * developer/gnu-binutils
>  * developer/lexer/flex
>  * developer/macro/cpp
>  * developer/macro/gnu-m4
>  * developer/parser/bison
>  * developer/solstudio12.2
>  * developer/sunstudio12.1
>  * developer/swig
>  * developer/versioning/git
>  * developer/versioning/mercurial
>  * driver/virtualization/kvm
>  * editor/vim
>  * entire
>  * file/gnu-coreutils
>  * file/gnu-findutils
>  * illumos-gate
>  * incorporation/jeos/illumos-gate
>  * incorporation/jeos/omnios-userland
>  * libgcc_s
>  * library/c++/sigcpp
>  * library/expat
>  * library/glib2
>  * library/gmp
>  * library/gnutls
>  * library/idnkit
>  * library/idnkit/header-idnkit
>  * library/libffi
>  * library/libidn
>  * library/libtasn1
>  * library/libtool/libltdl
>  * library/libxml2
>  * library/libxslt
>  * library/ncurses
>  * library/nspr
>  * library/nspr/header-nspr
>  * library/pcre
>  * library/perl-5/xml-parser
>  * library/popt
>  * library/python-2/cherrypy
>  * library/python-2/lxml-26
>  * library/python-2/m2crypto
>  * library/python-2/mako
>  * library/python-2/numpy-26
>  * library/python-2/ply
>  * library/python-2/pybonjour
>  * library/python-2/pycurl
>  * library/python-2/pyopenssl-26
>  * library/python-2/pyrex-26
>  * library/python-2/python-extra-26
>  * library/python-2/setuptools-26
>  * library/python-2/simplejson-26
>  * library/readline
>  * library/security/libgpg-error
>  * library/security/nettle
>  * library/security/openssl
>  * library/security/trousers
>  * library/unixodbc
>  * library/zlib
>  * libstdc++
>  * media/cdrtools
>  * network/dns/bind
>  * network/dns/idnconv
>  * network/rsync
>  * package/pkg
>  * release/name
>  * release/notices
>  * runtime/perl-$NODOTVER
>  * runtime/perl-$NODOTVER-64
>  * runtime/perl-$NODOTVER/manual
>  * runtime/python-26
>  * security/sudo
>  * service/network/ntp
>  * shell/bash
>  * shell/pipe-viewer
>  * shell/tcsh
>  * shell/which
>  * shell/zsh
>  * system/install/kayak
>  * system/install/kayak-kernel
>  * system/install/locale
>  * system/kvm
>  * system/library/c++/sunpro
>  * system/library/dbus
>  * system/library/g++-4-runtime
>  * system/library/gcc-4-runtime
>  * system/library/iconv/extra
>  * system/library/iconv/unicode
>  * system/library/iconv/utf-8
>  * system/library/iconv/utf-8/manual
>  * system/library/iconv/xsh4/latin
>  * system/library/libdbus
>  * system/library/libdbus-glib
>  * system/library/math
>  * system/library/math/header-math
>  * system/library/mozilla-nss
>  * system/library/mozilla-nss/header-nss
>  * system/library/pcap
>  * system/library/security/libgcrypt
>  * system/management/ec2-api-tools
>  * system/management/ec2-credential
>  * system/management/ipmitool
>  * system/management/snmp/net-snmp
>  * system/pciutils
>  * system/pciutils/pci.ids
>  * system/prerequisite/gnu
>  * system/zones/brand/ipkg
>  * terminal/screen
>  * terminal/tmux
>  * text/auto_ef
>  * text/gawk
>  * text/gnu-diffutils
>  * text/gnu-gettext
>  * text/gnu-grep
>  * text/gnu-patch
>  * text/gnu-sed
>  * text/groff
>  * text/less
>  * text/texinfo
>  * web/ca-bundle
>  * web/curl
>  * web/wget
> kent at compiler:/home/kent/omnios-build/build$ ./buildctl build
> kent at compiler:/home/kent/omnios-build/build$   (nothing happened?)
>
> OK, let's pass a list of packages in...
>
> kent at compiler:/home/kent/omnios-build/build$ for i in *; do
>> echo $i
>> ./buildctl build $i
>> done
> autoconf
> Unknown package: autoconf
> automake-111
> Unknown package: automake-111
> automake-19
> Unknown package: automake-19
> bash
> Unknown package: bash
> bind
> Unknown package: bind
> binutils
> Unknown package: binutils
> bison
> Unknown package: bison
> buildctl
> Unknown package: buildctl
> bzip2
> Unknown package: bzip2
> ca-bundle
> Unknown package: ca-bundle
> caiman
> ^C
>
> No dice either.  I've examined the buildctl script and it seems that the way
> it builds up its "targets" variable is incompatible with the comparison that
> happens later:
>
>     if [[ -z "${targets[$1]}" ]]; then
>         bail "Unknown package: $1"
>     fi
>
>
> Or am I doing something wrong?
>
> Thanks again,
> Kent
>
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From jesus at omniti.com  Fri Feb 22 15:31:31 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Fri, 22 Feb 2013 15:31:31 -0500
Subject: [OmniOS-discuss] Preconfigured distributable OmniOS NAS with
 mirrorred USB sticks
In-Reply-To: <2EDC7C4A-0CC1-4E39-AE49-4ACB67F78542@hfg-gmuend.de>
References: <2EDC7C4A-0CC1-4E39-AE49-4ACB67F78542@hfg-gmuend.de>
Message-ID: <CACLsApvYWUCUaSGOsho7CyxpyCgMhGsoY2pqqtrV+sbfq9Ec1Q@mail.gmail.com>

This sounds really nice.

On Fri, Feb 22, 2013 at 3:09 PM, alka <alka at hfg-gmuend.de> wrote:

> about a ready to use mirrorred USB based NAS/SAN
>
> OmniOS is more and more my first choice for a NAS or SAN solution.
> With newer and faster USB sticks and disabled atime there is nearly no
> difference to a disk booted NAS or SAN.
>
> I have now started "napp-it to go", a solution for a preconfigured ZFS
> File, SAN or media-.server running from USB sticks.:
> I put together all needed things like cloning tools or support for
> mirroring in the Web-UI to allow
>
> - booting a distributeable ready to use solution on USB sticks  (insert
> stick, boot and manage the preconfigured SAN via Web-UI),
> - no Unix skills needed for basic management
> - add a second stick to mirror rpool (Web-UI  Disk - mirror rpool)
>
>
> Howto and Tools to clone such a ready to use stick (preconfigured for a
> special hardware like HP Microserver or a SM mainboard line)
> http://www.napp-it.org/manuals/to-go_en.html
>
>
> Gea
> napp-it.org
>
> -
>
> _______________________________________________
> 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/20130222/5ef1031f/attachment.html>

From Rob at Logan.com  Fri Feb 22 16:37:07 2013
From: Rob at Logan.com (Rob Logan)
Date: Fri, 22 Feb 2013 16:37:07 -0500
Subject: [OmniOS-discuss] [SPAM] Re: Preconfigured distributable OmniOS
 NAS with mirrorred USB sticks
In-Reply-To: <CACLsApvYWUCUaSGOsho7CyxpyCgMhGsoY2pqqtrV+sbfq9Ec1Q@mail.gmail.com>
References: <2EDC7C4A-0CC1-4E39-AE49-4ACB67F78542@hfg-gmuend.de>
	<CACLsApvYWUCUaSGOsho7CyxpyCgMhGsoY2pqqtrV+sbfq9Ec1Q@mail.gmail.com>
Message-ID: <5127E503.5090609@Logan.com>

 > about a ready to use mirrorred USB based NAS/SAN

cool... I did that too
http://rob.com/lancair/2013.01/usb.jpg

but for USB write leveling

we might want research what files to link to /tmp (ramdisk)

/var/adm/messages
/var/adm/wtmpx

				Rob

From alka at hfg-gmuend.de  Fri Feb 22 17:14:34 2013
From: alka at hfg-gmuend.de (alka)
Date: Fri, 22 Feb 2013 23:14:34 +0100
Subject: [OmniOS-discuss] [SPAM] Re: Preconfigured distributable OmniOS
	NAS with mirrorred USB sticks
In-Reply-To: <5127E503.5090609@Logan.com>
References: <2EDC7C4A-0CC1-4E39-AE49-4ACB67F78542@hfg-gmuend.de>
	<CACLsApvYWUCUaSGOsho7CyxpyCgMhGsoY2pqqtrV+sbfq9Ec1Q@mail.gmail.com>
	<5127E503.5090609@Logan.com>
Message-ID: <99055A16-8618-4321-818C-A5DAF992CA8B@hfg-gmuend.de>

I avoided USB with Solaris for a long time due to performance and reliability problems. 
Modern USB sticks are fast and reliable especially when combined to a ZFS mirror

Now I am more and more convinced, that booting a ZFS SAN is best done via mirrorred USB sticks.
No other method is as flexible and serious boot problems can be fixed without delay using a spare stick.

Even updates are painles. Use a spare stick, configure on a spare machine and updates are only a reboot with another stick.

With modern sticks, I do not see the need of a redirect of folders with some write activity  to RAM like SmartOS or EON are doing.
Keep it simple, keep it default.


Am 22.02.2013 um 22:37 schrieb Rob Logan:

> > about a ready to use mirrorred USB based NAS/SAN
> 
> cool... I did that too
> http://rob.com/lancair/2013.01/usb.jpg
> 
> but for USB write leveling
> 
> we might want research what files to link to /tmp (ramdisk)
> 
> /var/adm/messages
> /var/adm/wtmpx
> 
> 				Rob
> _______________________________________________
> 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/20130222/2dd71dae/attachment.html>

From kent at watsen.net  Fri Feb 22 20:18:07 2013
From: kent at watsen.net (Kent Watsen)
Date: Fri, 22 Feb 2013 20:18:07 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
Message-ID: <512818CF.3030406@watsen.net>

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

From jesus at omniti.com  Fri Feb 22 21:35:40 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Fri, 22 Feb 2013 21:35:40 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <512818CF.3030406@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
Message-ID: <CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>

Kent, you are indeed close. If you are just trying to build Illumos, you
only want to build the illumos directory in the build system. Skip buildctl
and just:

cd illumos
./build.sh

That package server is where you want to publish your built packages after
they are built, so a public one wouldn't do, there is documentation on the
public omnios wiki on how to set up your own package server. The various
stuff in the build system is for building all the supporting parts of
omnios; "Illumos" is just the kernel.

Luckily, you can get a complete build and local IPS packaging of just the
gate bits from the above mentioned command.
On Feb 22, 2013 8:47 PM, "Kent Watsen" <kent at watsen.net> wrote:

>
>
> On 2/22/13 3:29 PM, Eric Sproul wrote:
>
> buildctl has rather bit-rotted-- we don't really use it much
> internally.  Nevertheless, what buildctl expects for names is the
> package FMRI, e.g. "developer/build/autoconf", because it has scraped
> those from the PKG variable in each build.sh file.  So what you might
> do is 'for i in $(./buildctl list) ; do ./buildctl $i ; done'
>
> Eric
>
>
>
> OK, we're getting closer:
>
>  *kent at compiler:/home/kent/omnios-build/build$* for i in $(./buildctl
> list | awk '{print $2}'); do
>  > ./buildctl build $i
>  > done
>  ===== Build started at Fri Feb 22 20:09:47 UTC 2013 =====
>  Package name: archiver/gnu-tar
>  Selected flavor: None (use -f to specify a flavor)
>  Selected build arch: 32
>  Extra dependency: None (use -d to specify a version)
>  The PKGSRVR (http://omnios.int.omniti.net:10002/) isn't available. *All
> is doomed*.  (emphasis mine :-)
>  An Error occured in the build. Do you wish to continue anyway? (y/n) n
>  ===== Build aborted =====
>
>
> This server's name makes it sound like its internal...
>   - if so, is there an external server with the packages on it?
>
> Or I give up now and try to compile illumos using these instructions<http://wiki.illumos.org/display/illumos/How+To+Build+illumos>instead?
>
>
> Thanks,
> Kent
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130222/2bb1c9f2/attachment.html>

From kent at watsen.net  Fri Feb 22 22:22:18 2013
From: kent at watsen.net (Kent Watsen)
Date: Fri, 22 Feb 2013 22:22:18 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
Message-ID: <512835EA.2080608@watsen.net>

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

From jesus at omniti.com  Fri Feb 22 23:22:21 2013
From: jesus at omniti.com (Theo Schlossnagle)
Date: Fri, 22 Feb 2013 23:22:21 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <512835EA.2080608@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
Message-ID: <CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>

You'll need to install developer/astdev and any other build dependency
required.

pkg install developer/astdev
On Feb 22, 2013 10:22 PM, "Kent Watsen" <kent at watsen.net> wrote:

>  On 2/22/13 9:35 PM, Theo Schlossnagle wrote:
>
> Kent, you are indeed close. If you are just trying to build Illumos, you
> only want to build the illumos directory in the build system. Skip buildctl
> and just:
>
> cd illumos
> ./build.sh
>
> That package server is where you want to publish your built packages after
> they are built, so a public one wouldn't do, there is documentation on the
> public omnios wiki on how to set up your own package server. The various
> stuff in the build system is for building all the supporting parts of
> omnios; "Illumos" is just the kernel.
>
> Luckily, you can get a complete build and local IPS packaging of just the
> gate bits from the above mentioned command.
>
>
>
> Thanks for all the help so far.  In part I'm eager to get illumos
> compiled, but I'm also trying to help you understand what's not working, in
> case you want to fix it someday.   Here's the latest:
>
> *kent at compiler:/home/kent/omnios-build/build$ cd illumos*
> *kent at compiler:/home/kent/omnios-build/build/illumos$ ./build.sh*
> ===== Build started at Fri Feb 22 22:15:11 UTC 2013 =====
> Package name: illumos-gate
> Selected flavor: None (use -f to specify a flavor)
> Selected build arch: both
> Extra dependency: None (use -d to specify a version)
> The PKGSRVR (http://omnios.int.omniti.net:10002/) isn't available. All is
> doomed.
> An Error occured in the build. Do you wish to continue anyway? (y/n) *y*
> (I tried to ignore the error)
> ===== User elected to continue after prompt. =====
> Verifying dependencies
> --- Build-time dependency developer/astdev not found
> An Error occured in the build. Do you wish to continue anyway? (y/n) *n*
> (this looks more serious...)
> ===== Build aborted =====
>
>
> Any other ideas - or should I give the illumos build instructions a whirl?
>
> Thanks again,
> Kent
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130222/a880b9b2/attachment.html>

From kent at watsen.net  Sat Feb 23 08:39:31 2013
From: kent at watsen.net (Kent Watsen)
Date: Sat, 23 Feb 2013 08:39:31 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
Message-ID: <5128C693.6040107@watsen.net>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130223/8fa75374/attachment-0001.html>

From esproul at omniti.com  Sun Feb 24 11:12:41 2013
From: esproul at omniti.com (Eric Sproul)
Date: Sun, 24 Feb 2013 11:12:41 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <512A35AF.90101@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
Message-ID: <CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>

(adding list address back in-- my mistake to direct-reply last night)

In https://github.com/omniti-labs/omnios-build/commit/fa210762018b66f066c5a0991c7633cea0d1b0eb
I added some error handling and a comment on the TMPDIR setting.  It's
only "hard-coded" in the sense that it's set near the top of the
script as opposed to somewhere like site.sh.

I've also updated http://omnios.omniti.com/wiki.php/BuildInstructions
with your previous suggestions as well as a note about TMPDIR for the
illumos build.

Glad things are working for you!
Eric

On Sun, Feb 24, 2013 at 10:45 AM, Kent Watsen <kent at watsen.net> wrote:
>
> Right you are.   My bad for not seeing that the "/code/omnios-151004: No
> such file or directory" error happened first.    The "how to build illumos"
> doc uses "/code" in its examples, but it also says that the directory can be
> anything, though it seems the OmniOS build hardcodes this value.  A
> directory-existence check followed by a nice error message would be nice -
> especially given that the script requires being built by a user other than
> "root" and yet creating a directory in '/' requires root-permissions.
> Another nice add, to docs or scripts, would be to mention that detailed
> output from the can be monitored in
> /code/omnios\-151004/illumos\-omnios/log/nightly.log...
>
> Anyway, after creating /code and chmod-ing it to have good perms, the build
> has been running error-free for ~10-15 minutes - yeah!   Hopefully, with
> 12-cores and 24GB, I'll have a result in a couple hours...
>
> Thanks for all the help so far!
>
>
>
>
> On 2/24/13 12:31 AM, Eric Sproul wrote:
>
> After the deps are done the first error is the missing /code/... directory.
> I would check to make sure you have write permission to that directory. It
> also seems like we need better error handling around the dir creation.
>
> Eric
>
>

From kent at watsen.net  Sun Feb 24 12:22:52 2013
From: kent at watsen.net (Kent Watsen)
Date: Sun, 24 Feb 2013 12:22:52 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
Message-ID: <512A4C6C.5010305@watsen.net>

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

From esproul at omniti.com  Mon Feb 25 09:41:52 2013
From: esproul at omniti.com (Eric Sproul)
Date: Mon, 25 Feb 2013 09:41:52 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <512A4C6C.5010305@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
Message-ID: <CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>

Have a look at the "mail_msg" file in the log directory for your
build, which should contain a concise summary of the build, looking
especially at the sections for various errors.  If those are non-empty
you can grep for those errors from nightly.log to drill down to root
causes.

Eric

On Sun, Feb 24, 2013 at 12:22 PM, Kent Watsen <kent at watsen.net> wrote:
>
> Hi Eric,
>
> I'm glad that I've been able to helped the project out   :)
>
> So, the build completed, but I'm unsure if it succeeded....
>
> In the window where I executed ./build.sh, I see:
>
> kent at compiler:/home/kent/omnios-build/build/illumos$ ./build.sh
> ===== Build started at Sun Feb 24 10:14:58 UTC 2013 =====
>
> Package name: illumos-gate
> Selected flavor: None (use -f to specify a flavor)
> Selected build arch: both
> Extra dependency: None (use -d to specify a version)
> The PKGSRVR (http://omnios.int.omniti.net:10002/) isn't available. All is
> doomed.
> An Error occured in the build. Do you wish to continue anyway? (y/n) y
> ===== User elected to continue after prompt. =====
> Verifying dependencies
> Preparing for build
> --- Creating temporary install dir
> Ensuring that Sun Studio is where Illumos thinks it is...
> --- fake SUNWspro link exists, good
> Creating build dir /code/omnios-151004
> Entering /code/omnios-151004
> Cloning OMNI Illumos Source...
> /code/omnios-151004/illumos-omnios /code/omnios-151004
> ~/omnios-build/build/illumos
>
> VERSION=\'omnios\-75e1472'
> Leaving /code/omnios-151004
> Entering /code/omnios-151004/illumos-omnios
>
> Changing illumos.sh variables to what we want them to be...
> Leaving /code/omnios-151004/illumos-omnios
> Entering /code/omnios-151004/illumos-omnios
>
> Getting Closed Source Bins...
> Leaving /code/omnios-151004/illumos-omnios
> Entering /code/omnios-151004/illumos-omnios
>
> Building extra tools needed for illumos pkgs...
> Leaving /code/omnios-151004/illumos-omnios
> Entering /code/omnios-151004/illumos-omnios
>
> Building illumos pkgs...
> Nightly failed
> An Error occured in the build. Do you wish to continue anyway? (y/n)  (how
> should I answer?)
>
> But /code/omnios-151004/illumos-omnios/log/nightly.log says:
>
> <SNIP/>
> sh /code/omnios-151004/illumos-omnios/usr/src/cmd/sgs/tools/chkmsg.sh -m
> ../common/elfedit.msg  ../common/elfedit.c ../common/sys.c ../common/util.c
> ../common/elfconst.c  ../common/elfedit_machelf.c ../common/util_machelf.c
> msg.c
>
> ==== Find core files ====
>
>
> ==== Check lists of files ====
>
> ==== Nightly distributed build completed: Sun Feb 24 10:46:25 UTC 2013 ====
>
> ==== Total build time ====
>
> real    0:27:18
>
>
> It says it completed - what gives?
>
> Also, comparing my compile-time to known Illumos build times, it seems
> comparable to the 2 x Xeon E5620  (total of 8 cores/16 threads @ 2.4GHz),
> whereas I have 2 x Opteron 2419 (total of 12 cores/12 threads @ 1.8GHz) -
> does it seem reasonable?   I suppose disk-access could also be a factor, but
> assume that it's not a significant bottleneck for either case...
>
> Thoughts?  - especially with regards to the "do you wish to continue"
> prompt?
>
> Thanks again,
> Kent
>
>
>
>
> On 2/24/13 11:12 AM, Eric Sproul wrote:
>
> (adding list address back in-- my mistake to direct-reply last night)
>
> In
> https://github.com/omniti-labs/omnios-build/commit/fa210762018b66f066c5a0991c7633cea0d1b0eb
> I added some error handling and a comment on the TMPDIR setting.  It's
> only "hard-coded" in the sense that it's set near the top of the
> script as opposed to somewhere like site.sh.
>
> I've also updated http://omnios.omniti.com/wiki.php/BuildInstructions
> with your previous suggestions as well as a note about TMPDIR for the
> illumos build.
>
> Glad things are working for you!
> Eric
>
>
>

From ramquick at gmail.com  Tue Feb 26 06:30:30 2013
From: ramquick at gmail.com (Ram Chander)
Date: Tue, 26 Feb 2013 17:00:30 +0530
Subject: [OmniOS-discuss] "df" reports wrong value
Message-ID: <CAMRGQbNLR3U5WehvEPDB8NofaXMZEU9PYkUdxRbAGRC5b2N8MQ@mail.gmail.com>

Hi,


I have 547G parition and df  shows  only 97G used and 31G  available .
When checked with "du" it  also reports only 97G used. Where are the rest
of space ? And why is "df" reporting wrong available space.
There are no process holding deleted files.
*
-bash-4.2# df -h*
Filesystem             size   used  avail capacity  Mounted on
rpool/ROOT/omnios      547G    97G    31G    76%    /
/devices                 0K     0K     0K     0%    /devices
/dev                     0K     0K     0K     0%    /dev
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                  10.0G   300K  10.0G     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap1.so.1
                       128G    97G    31G    76%    /lib/libc.so.1
fd                       0K     0K     0K     0%    /dev/fd
swap                  10.0G     4K  10.0G     1%    /tmp
swap                  10.0G    40K  10.0G     1%    /var/run
rpool/export           547G    32K    31G     1%    /export
rpool/export/home      547G    31K    31G     1%    /export/home
rpool                  547G    36K    31G     1%    /rpool

*-bash-4.2# du -sch /**
512     bin
74M     boot
707K    dev
322K    devices
38M     etc
3.0K    export
512     home
112M    kernel
49M     lib
2.0K    media
1.5K    mnt
512     net
439M    opt
341M    platform
du: cannot access `proc/23443/fd/3': No such file or directory
du: cannot access `proc/23443/path/3': No such file or directory
4.0G    proc
5.7M    root
7.5K    rpool
1.8M    sbin
3.7M    system
1.5K    test
8.0K    tmp
906M    usr
91G     var
*97G     total*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130226/f14450f5/attachment.html>

From sergey57 at gmail.com  Tue Feb 26 07:05:08 2013
From: sergey57 at gmail.com (sergey ivanov)
Date: Tue, 26 Feb 2013 07:05:08 -0500
Subject: [OmniOS-discuss] "df" reports wrong value
In-Reply-To: <CAMRGQbNLR3U5WehvEPDB8NofaXMZEU9PYkUdxRbAGRC5b2N8MQ@mail.gmail.com>
References: <CAMRGQbNLR3U5WehvEPDB8NofaXMZEU9PYkUdxRbAGRC5b2N8MQ@mail.gmail.com>
Message-ID: <CAAv=BDGvh-L5v5346Oe2FY=X=DJoFtZRRp3RG5GGS9m3Ck92iA@mail.gmail.com>

Dear Ram Chandler,
I guess this space is used by snapshots. Also there is possibility it is
used by children (nested zfs filesystems) but then they must be unmounted
so that they are not reported in your du results. Or they are subvolumes?
If you are using zfs, then I would suggest using zfs tools to monitor it's
status. Like "zfs list" and "zfs get". You see, zfs is not just a
filesystem, - it combines in one things like filesytem, volume manager,
raid and may be others. And to find out what is using the space, I usually
do something like "zfs get all | grep used" Or, for example, on one of our
systems:
---
root at megaera:~# df -h /raid/data{,/subversion}

Filesystem            Size  Used Avail Use% Mounted on
raid/data             5.7T   88K  5.7T   1% /raid/data
raid/data/subversion  5.8T   39G  5.7T   1% /raid/data/subversion
root at megaera:~# zfs list  -o
name,used,usedbychildren,usedbysnapshots,available,compressratio,mountpoint
\

    raid/data{,/subversion}

NAME                   USED  USEDCHILD  USEDSNAP  AVAIL  RATIO  MOUNTPOINT
raid/data              222G       222G         0  5.70T  1.30x  /raid/data
raid/data/subversion   151G          0      113G  5.70T  1.09x
/raid/data/subversion

---

-- 

  Regards,

  Sergey Ivanov.



On Tue, Feb 26, 2013 at 6:30 AM, Ram Chander <ramquick at gmail.com> wrote:

> Hi,
>
>
> I have 547G parition and df  shows  only 97G used and 31G  available .
> When checked with "du" it  also reports only 97G used. Where are the rest
> of space ? And why is "df" reporting wrong available space.
> There are no process holding deleted files.
> *
> -bash-4.2# df -h*
> Filesystem             size   used  avail capacity  Mounted on
> rpool/ROOT/omnios      547G    97G    31G    76%    /
> /devices                 0K     0K     0K     0%    /devices
> /dev                     0K     0K     0K     0%    /dev
> ctfs                     0K     0K     0K     0%    /system/contract
> proc                     0K     0K     0K     0%    /proc
> mnttab                   0K     0K     0K     0%    /etc/mnttab
> swap                  10.0G   300K  10.0G     1%    /etc/svc/volatile
> objfs                    0K     0K     0K     0%    /system/object
> sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
> /usr/lib/libc/libc_hwcap1.so.1
>                        128G    97G    31G    76%    /lib/libc.so.1
> fd                       0K     0K     0K     0%    /dev/fd
> swap                  10.0G     4K  10.0G     1%    /tmp
> swap                  10.0G    40K  10.0G     1%    /var/run
> rpool/export           547G    32K    31G     1%    /export
> rpool/export/home      547G    31K    31G     1%    /export/home
> rpool                  547G    36K    31G     1%    /rpool
>
> *-bash-4.2# du -sch /**
> 512     bin
> 74M     boot
> 707K    dev
> 322K    devices
> 38M     etc
> 3.0K    export
> 512     home
> 112M    kernel
> 49M     lib
> 2.0K    media
> 1.5K    mnt
> 512     net
> 439M    opt
> 341M    platform
> du: cannot access `proc/23443/fd/3': No such file or directory
> du: cannot access `proc/23443/path/3': No such file or directory
> 4.0G    proc
> 5.7M    root
> 7.5K    rpool
> 1.8M    sbin
> 3.7M    system
> 1.5K    test
> 8.0K    tmp
> 906M    usr
> 91G     var
> *97G     total*
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>


-- 
Regards,
Sergey Ivanov | 443-844-6318 | sergey57 at gmail.com
http://www.linkedin.com/pub/sergey-ivanov/8/270/a09
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130226/07ea3c06/attachment.html>

From ramquick at gmail.com  Tue Feb 26 08:37:04 2013
From: ramquick at gmail.com (Ram Chander)
Date: Tue, 26 Feb 2013 19:07:04 +0530
Subject: [OmniOS-discuss] "df" reports wrong value
In-Reply-To: <CAAv=BDGvh-L5v5346Oe2FY=X=DJoFtZRRp3RG5GGS9m3Ck92iA@mail.gmail.com>
References: <CAMRGQbNLR3U5WehvEPDB8NofaXMZEU9PYkUdxRbAGRC5b2N8MQ@mail.gmail.com>
	<CAAv=BDGvh-L5v5346Oe2FY=X=DJoFtZRRp3RG5GGS9m3Ck92iA@mail.gmail.com>
Message-ID: <CAMRGQbMHjG8DxAcSRsOLwWQuq7eq5-DzTZ7M6deQF8eTZq2hcg@mail.gmail.com>

There are no nestes zfs sub volumes. Below are the snapshots used.  Should
i try deleting snaps ?

-bash-4.2#  zfs list  -o
name,used,usedbychildren,usedbysnapshots,available,compressratio,mountpoint
rpool
NAME    USED  USEDCHILD  USEDSNAP  AVAIL  RATIO  MOUNTPOINT
rpool   505G       505G         0  42.5G  1.00x  /rpool

-bash-4.2#  zfs list -r -t snapshot
NAME                                    USED  AVAIL  REFER  MOUNTPOINT
rpool/ROOT/omnios at install               277M      -  1.52G  -
rpool/ROOT/omnios at 2012-11-22-02:03:18   274K      -  35.6G  -
rpool/ROOT/omnios at 2012-11-22-02:04:02   406K      -  35.6G  -
rpool/ROOT/omnios at 2012-12-19-04:54:57   317G      -   318G  -


On Tue, Feb 26, 2013 at 5:35 PM, sergey ivanov <sergey57 at gmail.com> wrote:

> Dear Ram Chandler,
> I guess this space is used by snapshots. Also there is possibility it is
> used by children (nested zfs filesystems) but then they must be unmounted
> so that they are not reported in your du results. Or they are subvolumes?
> If you are using zfs, then I would suggest using zfs tools to monitor it's
> status. Like "zfs list" and "zfs get". You see, zfs is not just a
> filesystem, - it combines in one things like filesytem, volume manager,
> raid and may be others. And to find out what is using the space, I usually
> do something like "zfs get all | grep used" Or, for example, on one of our
> systems:
> ---
> root at megaera:~# df -h /raid/data{,/subversion}
>
> Filesystem            Size  Used Avail Use% Mounted on
> raid/data             5.7T   88K  5.7T   1% /raid/data
> raid/data/subversion  5.8T   39G  5.7T   1% /raid/data/subversion
> root at megaera:~# zfs list  -o name,used,usedbychildren,usedbysnapshots,available,compressratio,mountpoint \
>
>     raid/data{,/subversion}
>
> NAME                   USED  USEDCHILD  USEDSNAP  AVAIL  RATIO  MOUNTPOINT
> raid/data              222G       222G         0  5.70T  1.30x  /raid/data
> raid/data/subversion   151G          0      113G  5.70T  1.09x  /raid/data/subversion
>
> ---
>
> --
>
>   Regards,
>
>   Sergey Ivanov.
>
>
>
> On Tue, Feb 26, 2013 at 6:30 AM, Ram Chander <ramquick at gmail.com> wrote:
>
>> Hi,
>>
>>
>> I have 547G parition and df  shows  only 97G used and 31G  available .
>> When checked with "du" it  also reports only 97G used. Where are the rest
>> of space ? And why is "df" reporting wrong available space.
>> There are no process holding deleted files.
>> *
>> -bash-4.2# df -h*
>> Filesystem             size   used  avail capacity  Mounted on
>> rpool/ROOT/omnios      547G    97G    31G    76%    /
>> /devices                 0K     0K     0K     0%    /devices
>> /dev                     0K     0K     0K     0%    /dev
>> ctfs                     0K     0K     0K     0%    /system/contract
>> proc                     0K     0K     0K     0%    /proc
>> mnttab                   0K     0K     0K     0%    /etc/mnttab
>> swap                  10.0G   300K  10.0G     1%    /etc/svc/volatile
>> objfs                    0K     0K     0K     0%    /system/object
>> sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
>> /usr/lib/libc/libc_hwcap1.so.1
>>                        128G    97G    31G    76%    /lib/libc.so.1
>> fd                       0K     0K     0K     0%    /dev/fd
>> swap                  10.0G     4K  10.0G     1%    /tmp
>> swap                  10.0G    40K  10.0G     1%    /var/run
>> rpool/export           547G    32K    31G     1%    /export
>> rpool/export/home      547G    31K    31G     1%    /export/home
>> rpool                  547G    36K    31G     1%    /rpool
>>
>> *-bash-4.2# du -sch /**
>> 512     bin
>> 74M     boot
>> 707K    dev
>> 322K    devices
>> 38M     etc
>> 3.0K    export
>> 512     home
>> 112M    kernel
>> 49M     lib
>> 2.0K    media
>> 1.5K    mnt
>> 512     net
>> 439M    opt
>> 341M    platform
>> du: cannot access `proc/23443/fd/3': No such file or directory
>> du: cannot access `proc/23443/path/3': No such file or directory
>> 4.0G    proc
>> 5.7M    root
>> 7.5K    rpool
>> 1.8M    sbin
>> 3.7M    system
>> 1.5K    test
>> 8.0K    tmp
>> 906M    usr
>> 91G     var
>> *97G     total*
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>>
>
>
> --
> Regards,
> Sergey Ivanov | 443-844-6318 | sergey57 at gmail.com
> http://www.linkedin.com/pub/sergey-ivanov/8/270/a09
>
> _______________________________________________
> 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/20130226/ca56d909/attachment-0001.html>

From esproul at omniti.com  Tue Feb 26 09:30:23 2013
From: esproul at omniti.com (Eric Sproul)
Date: Tue, 26 Feb 2013 09:30:23 -0500
Subject: [OmniOS-discuss] "df" reports wrong value
In-Reply-To: <CAMRGQbMHjG8DxAcSRsOLwWQuq7eq5-DzTZ7M6deQF8eTZq2hcg@mail.gmail.com>
References: <CAMRGQbNLR3U5WehvEPDB8NofaXMZEU9PYkUdxRbAGRC5b2N8MQ@mail.gmail.com>
	<CAAv=BDGvh-L5v5346Oe2FY=X=DJoFtZRRp3RG5GGS9m3Ck92iA@mail.gmail.com>
	<CAMRGQbMHjG8DxAcSRsOLwWQuq7eq5-DzTZ7M6deQF8eTZq2hcg@mail.gmail.com>
Message-ID: <CA+QY2RSQv=6ehk1NDQh3Ua07POfo3bW1tq=pWbmWQaq8xuV3Fw@mail.gmail.com>

On Tue, Feb 26, 2013 at 8:37 AM, Ram Chander <ramquick at gmail.com> wrote:
> There are no nestes zfs sub volumes. Below are the snapshots used.  Should i
> try deleting snaps ?
>
> -bash-4.2#  zfs list  -o
> name,used,usedbychildren,usedbysnapshots,available,compressratio,mountpoint
> rpool
>
> NAME    USED  USEDCHILD  USEDSNAP  AVAIL  RATIO  MOUNTPOINT
> rpool   505G       505G         0  42.5G  1.00x  /rpool
>
> -bash-4.2#  zfs list -r -t snapshot
> NAME                                    USED  AVAIL  REFER  MOUNTPOINT
> rpool/ROOT/omnios at install               277M      -  1.52G  -
> rpool/ROOT/omnios at 2012-11-22-02:03:18   274K      -  35.6G  -
> rpool/ROOT/omnios at 2012-11-22-02:04:02   406K      -  35.6G  -
> rpool/ROOT/omnios at 2012-12-19-04:54:57   317G      -   318G  -

The @2012-12-19-04:54:57 is holding over 300G of space (the USED
value).  The "used" value represents the data exclusive to that
snapshot.  That's where your space went.

Eric

From maria at redmoon.es  Tue Feb 26 13:11:50 2013
From: maria at redmoon.es (Maria del Mar Perez)
Date: Tue, 26 Feb 2013 19:11:50 +0100
Subject: [OmniOS-discuss] Creating SMF service for Spread
Message-ID: <CABFrpu1XzdmD+Sr_jN7y7L5BZHexfhE-Ss9tkRMfz+3b2RW3UQ@mail.gmail.com>

Hi,
I'm trying to create an SMF service to Spread, because the service Wackamole
need as dependency.

The manifest I created is next, but when I try to enable the service says the
following error:

*root @ w2: ~ # svcs-xv
svc :/ network / spread: spread (?)
  State: offline since February 26, 2013 20:00:22 CET
Reason: Start method is running.
    See: http://illumos.org/msg/SMF-8000-C4
    See: / var / svc / log / network-spread: spread.log
Impact: This service is not running.*


Here below attached the manifest and the service log:
Any idea what can happen?


----------------------------------------------------------------------------------------------------------------------------------
Manifest
----------------------------------------------------------------------------------------------------------------------------------
*<?xml version='1.0'?>
<!DOCTYPE service_bundle SYSTEM '/usr/share/lib/xml/dtd/**
service_bundle.dtd.1'>
<service_bundle type='manifest' name='export'>
  <service name='network/spread' type='service' version='0'>
    <dependency name='filesystem_minimal' grouping='require_all'
restart_on='none' type='service'>
      <service_fmri value='svc:/system/filesystem/**minimal'/>
    </dependency>
    <dependency name='network' grouping='optional_all' restart_on='error'
type='service'>
      <service_fmri value='svc:/milestone/network'**/>
    </dependency>
    <exec_method name='stop' type='method' exec=':kill'
timeout_seconds='60'/>
    <property_group name='tm_common_name' type='template'/>
    <instance name='spread' enabled='false'>
      <dependency name='config_data' grouping='require_all'
restart_on='none' type='path'>
        <service_fmri value='file://localhost/opt/**omni/etc/spread.conf'/>
      </dependency>
      <exec_method name='start' type='method' exec='/opt/omni/sbin/spread'
timeout_seconds='60'/>
      <property_group name='general' type='framework'>
     <propval name="duration" type="astring" value="contract"/>
        <property name='action_authorization' type='astring'/>
        <property name='value_authorization' type='astring'/>
      </property_group>
    </instance>
    <stability value='Unstable'/>
  </service>
</service_bundle>
*
----------------------------------------------------------------------------------------------------------------------------------
Log
----------------------------------------------------------------------------------------------------------------------------------
*
[ Feb 26 20:00:22 Executing start method ("/opt/omni/sbin/spread"). ]
/===========================================================================\
| The Spread Toolkit.
|
| Copyright (c)    1993-2002 Spread Concepts
LLC                               |
| All rights reserved.
|
|
|
| The Spread toolkit is    licensed under the Spread Open-Source
License.      |
| You may only use this    software in compliance with the
License.            |
| A copy of the    license    can be found at
http://www.spread.org/license       |
|
|
| This product uses software developed by Spread Concepts LLC for use
|
| in the Spread    toolkit. For more information about
Spread,                 |
| see http://www.spread.org
|
|
|
| This software    is distributed on an "AS IS" basis, WITHOUT WARRANTY
OF     |
| ANY KIND, either express or implied.
|
|
|
| Spread is developed at Spread    Concepts LLC and the Center for
Networking  |
| and Distributed Systems, The Johns Hopkins University.
|
|
|
| Creators:
|
|    Yair Amir             yairamir at cs.jhu.edu
|
|    Michal Miskin-Amir       michal at spreadconcepts.com
|
|    Jonathan Stanton       jstanton at gwu.edu
|
|
|
| Major
Contributors:                                                       |
|    Cristina Nita-Rotaru crisn at cs.purdue.edu -    GC
security.                |
|    Theo Schlossnagle      jesus at omniti.com - Perl, skiplists,
autoconf.     |
|    Dan Schoenblum      dansch at cnds.jhu.edu -    Java
interface.             |
|    John Schultz      jschultz at d-fusion.net    - contribution to process
|
|                                       group membership.
|
|
|
| Special thanks to the    following for providing    ideas and/or
code:          |
|    Ken Birman, Danny Dolev, Mike Goodrich, Ben Laurie,
|
|    David Shaw, Robbert VanRenesse.
|
|
|
| Partial funding provided by the Defense Advanced Research Project Agency
|
| (DARPA) and the National Security Agency (NSA) since 2000. The Spread
|
| toolkit is not necessarily endorsed by DARPA or the NSA.
|
|
|
| For a    full list of contributors, see Readme.txt in the
distribution.      |
|
|
| WWW:       www.spread.org     www.cnds.jhu.edu      www.spreadconcepts.com
|
| Contact: spread at spread.org
|
|
|
| Version 3.17.03 Built
15/October/2004                                     |
\===========================================================================/
Conf_init: using file: /opt/omni/etc/spread.conf
Successfully configured    Segment    0 [10.56.33.255:4803] with 2 procs:
                   wackamole: 10.56.33.63
                          w2: 10.56.33.64
[ Feb 26 20:01:21 Method or service exit timed out.  Killing contract 115. ]


**
Regards,
Mar?a del Mar P?rez Fajardo.**
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130226/7c1dd339/attachment.html>

From alka at hfg-gmuend.de  Wed Feb 27 17:54:45 2013
From: alka at hfg-gmuend.de (alka)
Date: Wed, 27 Feb 2013 23:54:45 +0100
Subject: [OmniOS-discuss] Preconfigured distributable OmniOS NAS with
	mirrorred USB sticks
In-Reply-To: <99055A16-8618-4321-818C-A5DAF992CA8B@hfg-gmuend.de>
References: <2EDC7C4A-0CC1-4E39-AE49-4ACB67F78542@hfg-gmuend.de>
	<CACLsApvYWUCUaSGOsho7CyxpyCgMhGsoY2pqqtrV+sbfq9Ec1Q@mail.gmail.com>
	<5127E503.5090609@Logan.com>
	<99055A16-8618-4321-818C-A5DAF992CA8B@hfg-gmuend.de>
Message-ID: <4D1D818D-E5F0-48DD-9569-765A2A51D187@hfg-gmuend.de>

I uploaded a first trial version of my 'napp-it to go' ZFS Server + OmniOS newest bloody for HP Microserver.
(incl. LZ4 Compression- the new ZFS Highlight):

- download USB cloner, readme and USB Image  (16 GB, can take some time)
- Clone image to a fast 16 GB USB Stick 

- Boot it, use it (ready to use with Web-UI)
Downloads: [url=http://www.napp-it.org/manuals/to-go.html]napp-it.org[/url]




Am 22.02.2013 um 23:14 schrieb alka:

> I avoided USB with Solaris for a long time due to performance and reliability problems. 
> Modern USB sticks are fast and reliable especially when combined to a ZFS mirror
> 
> Now I am more and more convinced, that booting a ZFS SAN is best done via mirrorred USB sticks.
> No other method is as flexible and serious boot problems can be fixed without delay using a spare stick.
> 
> Even updates are painles. Use a spare stick, configure on a spare machine and updates are only a reboot with another stick.
> 
> With modern sticks, I do not see the need of a redirect of folders with some write activity  to RAM like SmartOS or EON are doing.
> Keep it simple, keep it default.
> 
> 
> Am 22.02.2013 um 22:37 schrieb Rob Logan:
> 
>> > about a ready to use mirrorred USB based NAS/SAN
>> 
>> cool... I did that too
>> http://rob.com/lancair/2013.01/usb.jpg
>> 
>> but for USB write leveling
>> 
>> we might want research what files to link to /tmp (ramdisk)
>> 
>> /var/adm/messages
>> /var/adm/wtmpx
>> 
>> 				Rob
>> _______________________________________________
>> 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/20130227/c186213e/attachment.html>

From kent at watsen.net  Thu Feb 28 03:11:17 2013
From: kent at watsen.net (Kent Watsen)
Date: Thu, 28 Feb 2013 03:11:17 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
	<CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
Message-ID: <512F1125.1070405@watsen.net>

An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20130228/1db38538/attachment-0001.html>

From ramquick at gmail.com  Thu Feb 28 06:25:25 2013
From: ramquick at gmail.com (Ram Chander)
Date: Thu, 28 Feb 2013 16:55:25 +0530
Subject: [OmniOS-discuss] "df" reports wrong value
In-Reply-To: <CA+QY2RSQv=6ehk1NDQh3Ua07POfo3bW1tq=pWbmWQaq8xuV3Fw@mail.gmail.com>
References: <CAMRGQbNLR3U5WehvEPDB8NofaXMZEU9PYkUdxRbAGRC5b2N8MQ@mail.gmail.com>
	<CAAv=BDGvh-L5v5346Oe2FY=X=DJoFtZRRp3RG5GGS9m3Ck92iA@mail.gmail.com>
	<CAMRGQbMHjG8DxAcSRsOLwWQuq7eq5-DzTZ7M6deQF8eTZq2hcg@mail.gmail.com>
	<CA+QY2RSQv=6ehk1NDQh3Ua07POfo3bW1tq=pWbmWQaq8xuV3Fw@mail.gmail.com>
Message-ID: <CAMRGQbPadTkwibSc7yg0ZciuAL2+YJ9Va-fARLz8NqmqtuKUBw@mail.gmail.com>

Thanks. It was snapshots that were taking space and deleted to recover
space.


On Tue, Feb 26, 2013 at 8:00 PM, Eric Sproul <esproul at omniti.com> wrote:

> On Tue, Feb 26, 2013 at 8:37 AM, Ram Chander <ramquick at gmail.com> wrote:
> > There are no nestes zfs sub volumes. Below are the snapshots used.
>  Should i
> > try deleting snaps ?
> >
> > -bash-4.2#  zfs list  -o
> >
> name,used,usedbychildren,usedbysnapshots,available,compressratio,mountpoint
> > rpool
> >
> > NAME    USED  USEDCHILD  USEDSNAP  AVAIL  RATIO  MOUNTPOINT
> > rpool   505G       505G         0  42.5G  1.00x  /rpool
> >
> > -bash-4.2#  zfs list -r -t snapshot
> > NAME                                    USED  AVAIL  REFER  MOUNTPOINT
> > rpool/ROOT/omnios at install               277M      -  1.52G  -
> > rpool/ROOT/omnios at 2012-11-22-02:03:18   274K      -  35.6G  -
> > rpool/ROOT/omnios at 2012-11-22-02:04:02   406K      -  35.6G  -
> > rpool/ROOT/omnios at 2012-12-19-04:54:57   317G      -   318G  -
>
> The @2012-12-19-04:54:57 is holding over 300G of space (the USED
> value).  The "used" value represents the data exclusive to that
> snapshot.  That's where your space went.
>
> 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/20130228/c50e0aec/attachment.html>

From esproul at omniti.com  Thu Feb 28 10:13:52 2013
From: esproul at omniti.com (Eric Sproul)
Date: Thu, 28 Feb 2013 10:13:52 -0500
Subject: [OmniOS-discuss] trouble compiling OmniOS
In-Reply-To: <512F1125.1070405@watsen.net>
References: <51277BBE.6030108@watsen.net>
	<CACLsApsoJmkdv4nOpYdkckKYoN_F+GPWF1G5st0+d6D2ZWSTcQ@mail.gmail.com>
	<51279CD9.8080508@watsen.net>
	<CA+QY2RRVpcGYM+Q0XHrSRko=YVUH1GFPRKMUWD12LTVBRFALEg@mail.gmail.com>
	<512818CF.3030406@watsen.net>
	<CACLsApv4JeK_SoXZWf6gGyU5Fi43b=swXpO=RmCb4zqx3L6FGg@mail.gmail.com>
	<512835EA.2080608@watsen.net>
	<CACLsAptmvseSSa-gOUdmPXxdbErcuCaFdwMX77iG6P-9oYwM7Q@mail.gmail.com>
	<5128C693.6040107@watsen.net>
	<CA+QY2RTVOin4WRe96-WVV=AO0Pg7GN=o6S2TH9ynhnAaM2ufzw@mail.gmail.com>
	<512A35AF.90101@watsen.net>
	<CA+QY2RS3OhZfOXO4WFKmOa7NN_LwBLjD0WixZmCf+PBrtu+deA@mail.gmail.com>
	<512A4C6C.5010305@watsen.net>
	<CA+QY2RS0gADCSFOrcrtQUv_mjnXb94Nhgq5HKxx4C3h0E4Uj7g@mail.gmail.com>
	<512F1125.1070405@watsen.net>
Message-ID: <CA+QY2RR6YU=1m67k6VsRTsw+bi5w-YWsAG-GWixWOJHoyHtskQ@mail.gmail.com>

Kent,
Do you mind if we review how you got to this point?  I recall that
earlier you said you wanted to try building in someone else's KVM
branch for AMD hardware virtualization support.  How are you getting
those code changes applied to what you're trying to build with the
OmniOS scripts?

How did you invoke the build that produced the log you've been showing us?

It might also be helpful to move the discussion to IRC if that's
something you're willing/able to do.  It would allow for a more
interactive conversation about your setup and the goal(s) you're
working to achieve.  The channels are either #omnios or #illumos on
Freenode.

Eric

On Thu, Feb 28, 2013 at 3:11 AM, Kent Watsen <kent at watsen.net> wrote:
>
>
> On 2/25/13 9:41 AM, Eric Sproul wrote:
>
> Have a look at the "mail_msg" file in the log directory for your
> build, which should contain a concise summary of the build, looking
> especially at the sections for various errors.  If those are non-empty
> you can grep for those errors from nightly.log to drill down to root
> causes.
>
>
>
> I found the mail_msg file, and I see some errors in it, but I'm sad to
> report that they're not very meaningful to me...
>
> Following is what the mail_msg file contains:
>
>
> ==== Nightly distributed build started:   Sun Feb 24 10:19:06 UTC 2013 ====
>
> ==== Nightly distributed build completed: Sun Feb 24 10:46:25 UTC 2013 ====
>
> ==== Total build time ====
>
> real    0:27:18
>
> ==== Build environment ====
>
> /usr/bin/uname
> SunOS compiler 5.11 omnios-33fdde4 i86pc i386 i86pc
>
> /opt/SUNWspro/bin/dmake
> dmake: Sun Distributed Make 7.9 SunOS_i386 2009/06/03
> number of concurrent jobs = 14
>
> 32-bit compiler
> /opt/onbld/bin/i386/cw -_gcc
> cw version 1.29 (SHADOW MODE DISABLED)
> primary: /opt/gcc-4.4.4/bin/gcc
> gcc (GCC) 4.4.4
>
> 64-bit compiler
> /opt/onbld/bin/i386/cw -_gcc
> cw version 1.29 (SHADOW MODE DISABLED)
> primary: /opt/gcc-4.4.4/bin/gcc
> gcc (GCC) 4.4.4
>
> /usr/java/bin/javac
> java full version "1.6.0_26-b03"
>
> /usr/bin/as
> as: Sun Compiler Common 12 SunOS_i386 snv_121 08/03/2009
>
> /usr/ccs/bin/ld
> ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1726
>
> Build project:  default
> Build taskid:   839
>
> ==== Nightly argument issues ====
>
>
> ==== Build version ====
>
> omnios-75e1472
>
> ==== Make clobber ERRORS ====
>
>
> ==== Make tools clobber ERRORS ====
>
>
> ==== Tools build errors ====
>
>
> ==== Build errors (non-DEBUG) ====
>
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Utils/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Kstat/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Intrs/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Project/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Task/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Lgrp/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Ucred/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/BSM/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Pg/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Privilege/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Exacct/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/PerlGcc/Makefile'
> dmake: Warning: Don't know how to make target `install'
> dmake: Warning: Target `install' not remade because of errors
> dmake: Warning: Target `install' not remade because of errors
> The following command caused the error:
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Utils/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Kstat/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Intrs/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Project/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Task/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Exacct/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Ucred/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Pg/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Lgrp/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/BSM/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/Privilege/Makefile'
> The following command caused the error:
> dmake: Warning: Command failed for target `Sun/Solaris/PerlGcc/Makefile'
> dmake: Warning: Don't know how to make target `install'
> dmake: Warning: Target `install' not remade because of errors
> dmake: Warning: Target `install' not remade because of errors
> The following command caused the error:
> dmake: Warning: Target `install' not remade because of errors
> The following command caused the error:
> dmake: Warning: Command failed for target `perl'
> dmake: Warning: Target `install' not remade because of errors
> The following command caused the error:
> dmake: Warning: Target `install' not remade because of errors
>
> ==== Build warnings (non-DEBUG) ====
>
> dmake: Warning: Command failed for target `Sun/Solaris/Utils/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Kstat/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Intrs/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Project/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Task/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Lgrp/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Ucred/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/BSM/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Pg/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Privilege/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Exacct/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/PerlGcc/Makefile'
> dmake: Warning: Don't know how to make target `install'
> dmake: Warning: Target `install' not remade because of errors
> dmake: Warning: Target `install' not remade because of errors
> dmake: Warning: Command failed for target `Sun/Solaris/Utils/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Kstat/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Intrs/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Project/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Task/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Exacct/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Ucred/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Pg/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Lgrp/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/BSM/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/Privilege/Makefile'
> dmake: Warning: Command failed for target `Sun/Solaris/PerlGcc/Makefile'
> dmake: Warning: Don't know how to make target `install'
> dmake: Warning: Target `install' not remade because of errors
> dmake: Warning: Target `install' not remade because of errors
> dmake: Warning: Target `install' not remade because of errors
> dmake: Warning: Command failed for target `perl'
> dmake: Warning: Target `install' not remade because of errors
> dmake: Warning: Target `install' not remade because of errors
>
> ==== Elapsed build time (non-DEBUG) ====
>
> real    24:40.1
> user  2:43:17.8
> sys     18:04.9
>
> ==== Build noise differences (non-DEBUG) ====
>
>
> ==== cstyle/hdrchk errors ====
>
>
>
> ==== Find core files ====
>
>
> ==== Check lists of files ====
>
>
> Does it mean anything to you?
>
> Thanks,
> Kent
>
>

