From alka at hfg-gmuend.de Wed Oct 2 07:39:49 2013 From: alka at hfg-gmuend.de (Guenther Alka) Date: Wed, 02 Oct 2013 09:39:49 +0200 Subject: [OmniOS-discuss] preconfigured ZFS/OmniOS All-IN-ONE appliance for ESXi 5.5 In-Reply-To: <9B3ECD07-3682-49EE-8B7C-376A8442FBB9@hfg-gmuend.de> References: <9B3ECD07-3682-49EE-8B7C-376A8442FBB9@hfg-gmuend.de> Message-ID: <524BCDC5.30600@hfg-gmuend.de> Update: I have stability problems when using e1000 on a default OmniOS VM under ESXi 5.5 It works either when using the VMXnet3 vnic or when adding the following lines to /kernel/drv/e1000g.conf (reboot required) #tcp offload disable tx_hcksum_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; lso_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; Maybe similar to this problem: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2058692 I uploaded a new appliance VM v 13b to adress this problem Gea Am 29.09.2013 02:44, schrieb alka: > I have published a ready to use OmniOS ZFS appliance for my All-In-One > idea > for ESXi 5.5 (without 32GB RAM Limit) with vmware tools installed > > If you want to test the appliance (best on ESXi with an additional LSI > SAS controller in pass-through mode, needs vt-d capable systems) > http://napp-it.org/downloads/ > > - download > - unzip (7Zip) > - upload to ESXi's local datastore (ESXi filebrowser) > this can last some time > > - import to inventory with right-click on the .vmx file (ESXi filebrowser) > - add storage controller to VM (via pass-through) > - boot, login as root (no pw) and use ifconfig to get serverip > - start and manage via browser http://serverip:81 > > It is a ready to use OmniOS ZFS storage appliance and includes > - e1000 and vmxnet3 vnics (dhcp) with ESXi 5.5 tools preinstalled > - working AFP, CIFS and iSCSI/FC > - napp-it Web-UI on latest stable OmniOS > > It is free to use (home and commercially). > With enough RAM it gives you a similar performance like a barebone > install. > > > Gea > napp-it.org > > > _______________________________________________ > 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: From johan.kragsterman at capvert.se Wed Oct 2 17:45:01 2013 From: johan.kragsterman at capvert.se (Johan Kragsterman) Date: Wed, 2 Oct 2013 19:45:01 +0200 Subject: [OmniOS-discuss] Brocade Fc HBA 825 Message-ID: Hi! Someone knows something about the Brocade Fc HBA 825? It's a dual port 8 Gbit HBA, and since I got hold of some of them, I wanted to test them. I thought they were either Emulex or Qlogic, or perhaps LSI, but they don't bind to any drivers, what I can see. Anyone got some experience of these? http://www.brocade.com/products/all/adapters/product-details/415-425-815-825-fibre-channel-hba/index.page Here I did some stuff to check things: root at omni:~# mdb -k Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp scsi_vhci zfs sata sd ip hook neti sockfs arp usba uhci stmf stmf_sbd md lofs mpt_sas random idm nfs crypto ptm cpc kvm smbsrv ufs logindmux nsmb ] Can't find any drivers loaded there... And as well: root at omni:~# fcinfo hba-port No Adapters Found. No adapters.... So I try: root at omni:~# prtconf -pv And here, at least, I can see that they are discoverd as fibre channel devices: ?Node 0x000026 ?? ? ? ? ? ? ? ?assigned-addresses: ?83220010.00000000.dfdc0000.00000000.00020000.83220018.00000000.dfdb8000.00000000.00004000 ?? ? ? ? ? ? ? ?reg: ?00220000.00000000.00000000.00000000.00000000.03220010.00000000.00000000.00000000.00020000.03220018.00000000.00000000.00000000.00004000 ?? ? ? ? ? ? ? ?compatible: 'pciex1657,13.1657.14.1' + 'pciex1657,13.1657.14' + 'pciex1657,13.1' + 'pciex1657,13' + 'pciexclass,0c0400' + 'pciexclass,0c04' + 'pci1657,13.1657.14.1' + 'pci1657,13.1657.14' + 'pci1657,14' + 'pci1657,13.1' + 'pci1657,13' + 'pciclass,0c0400' + 'pciclass,0c04' ?? ? ? ? ? ? ? ?model: ?'Fibre Channel' ?? ? ? ? ? ? ? ?power-consumption: ?00000001.00000001 ?? ? ? ? ? ? ? ?devsel-speed: ?00000000 ?? ? ? ? ? ? ? ?interrupts: ?00000001 ?? ? ? ? ? ? ? ?subsystem-vendor-id: ?00001657 ?? ? ? ? ? ? ? ?subsystem-id: ?00000014 ?? ? ? ? ? ? ? ?unit-address: ?'0' ?? ? ? ? ? ? ? ?class-code: ?000c0400 ?? ? ? ? ? ? ? ?revision-id: ?00000001 ?? ? ? ? ? ? ? ?vendor-id: ?00001657 ?? ? ? ? ? ? ? ?device-id: ?00000013 ?? ? ? ? ? ? ? ?name: ?'pci1657,14' ?? ? ? ? ? ?Node 0x000027 ?? ? ? ? ? ? ? ?assigned-addresses: ?83220110.00000000.dfde0000.00000000.00020000.83220118.00000000.dfdbc000.00000000.00004000 ?? ? ? ? ? ? ? ?reg: ?00220100.00000000.00000000.00000000.00000000.03220110.00000000.00000000.00000000.00020000.03220118.00000000.00000000.00000000.00004000 ?? ? ? ? ? ? ? ?compatible: 'pciex1657,13.1657.14.1' + 'pciex1657,13.1657.14' + 'pciex1657,13.1' + 'pciex1657,13' + 'pciexclass,0c0400' + 'pciexclass,0c04' + 'pci1657,13.1657.14.1' + 'pci1657,13.1657.14' + 'pci1657,14' + 'pci1657,13.1' + 'pci1657,13' + 'pciclass,0c0400' + 'pciclass,0c04' ?? ? ? ? ? ? ? ?model: ?'Fibre Channel' ?? ? ? ? ? ? ? ?power-consumption: ?00000001.00000001 ?? ? ? ? ? ? ? ?devsel-speed: ?00000000 ?? ? ? ? ? ? ? ?interrupts: ?00000002 ?? ? ? ? ? ? ? ?subsystem-vendor-id: ?00001657 ?? ? ? ? ? ? ? ?subsystem-id: ?00000014 ?? ? ? ? ? ? ? ?unit-address: ?'0,1' ?? ? ? ? ? ? ? ?class-code: ?000c0400 ?? ? ? ? ? ? ? ?revision-id: ?00000001 ?? ? ? ? ? ? ? ?vendor-id: ?00001657 ?? ? ? ? ? ? ? ?device-id: ?00000013 ?? ? ? ? ? ? ? ?name: ?'pci1657,14' They seem to have a downloadable driver f?r Solaris 10 x86, haven't tried it yet, don't want to put in too much work, perhaps they're not worth it...? Any info would be nice... Rgrds Johan From mir at miras.org Wed Oct 2 18:14:59 2013 From: mir at miras.org (Michael Rasmussen) Date: Wed, 2 Oct 2013 20:14:59 +0200 Subject: [OmniOS-discuss] Shared library error Message-ID: <20131002201459.690bdf6a@sleipner.datanom.net> Hi List, cat /etc/release OmniOS v11 r151007 Copyright 2013 OmniTI Computer Consulting, Inc. All rights reserved. Use is subject to license terms. mdb -k ld.so.1: mdb: fatal: relocation error: file /usr/bin/amd64/mdb: symbol kvm_namelist: referenced symbol not found Killed -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- When a fly lands on the ceiling, does it do a half roll or a half loop? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From ci4 at outlook.com Wed Oct 2 18:38:26 2013 From: ci4 at outlook.com (outlook) Date: Wed, 2 Oct 2013 19:38:26 +0100 Subject: [OmniOS-discuss] Shared library error Message-ID: It's been like that for quite sometime now. I pkg update my omnios bloody box weekly only to revert back. Hope 151008, which should be out midmonth, will be sorted. Bloody is expected to have that sort of problems from time to time. Chavdar --- Original Message --- From: "Michael Rasmussen" Sent: 2 October 2013 19:18 To: "omnios-discuss" Subject: [OmniOS-discuss] Shared library error Hi List, cat /etc/release OmniOS v11 r151007 Copyright 2013 OmniTI Computer Consulting, Inc. All rights reserved. Use is subject to license terms. mdb -k ld.so.1: mdb: fatal: relocation error: file /usr/bin/amd64/mdb: symbol kvm_namelist: referenced symbol not found Killed -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- When a fly lands on the ceiling, does it do a half roll or a half loop? -------------- next part -------------- _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss at lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss From fabior at gmx.net Thu Oct 3 08:13:12 2013 From: fabior at gmx.net (GMX) Date: Thu, 3 Oct 2013 09:13:12 +0100 Subject: [OmniOS-discuss] Brocade Fc HBA 825 In-Reply-To: References: Message-ID: <4B21E10D-47E3-4B4D-ADA8-3B0484E0A5A9@gmx.net> Hi Johan, I have a good few of these Brocade HBA cards working very well with a variety of OSes, including Windows, Linux (Red Hat and SUSE) and VMware ESXi servers. I've also done quite a bit with them on Solaris 10 and 11. In my environment they're usually connected to enterprise arrays (block) and we run POCs with them all year round. They're really grand, comparable to Emulex and QLogics. The only test I haven't done yet is with OpenSolaris or OmniOS. In all the other OSes I've mentioned, it does need the driver to be downloaded from Brocade and loaded, before you can do anything with them. I'm also using Brocade 1020 CNAs (10GbE) and they're the same. Yesterday I've completed a full NexentaStor community edition v3.1.5 install and it did not recognised my 1020 CNA. I might give a try with OmniOS as well and try to load the Solaris driver (now OmniTI guys, let me know if this would be unsupported from your perspective). I just don't have a timeframe for this yet. Anyway, with regarding quality, you're safe enough with the Brocade cards. I hope this helps! Cheers, --- Fabio Rodrigues On 2 Oct 2013, at 18:45, Johan Kragsterman wrote: > Hi! > > Someone knows something about the Brocade Fc HBA 825? It's a dual port 8 Gbit HBA, and since I got hold of some of them, I wanted to test them. I thought they were either Emulex or Qlogic, or perhaps LSI, but they don't bind to any drivers, what I can see. > > Anyone got some experience of these? > > http://www.brocade.com/products/all/adapters/product-details/415-425-815-825-fibre-channel-hba/index.page > > > > Here I did some stuff to check things: > > > root at omni:~# mdb -k > Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp scsi_vhci zfs sata sd ip hook neti sockfs arp usba uhci stmf stmf_sbd md lofs mpt_sas random idm nfs crypto ptm cpc kvm smbsrv ufs logindmux nsmb ] > > Can't find any drivers loaded there... > > > And as well: > > root at omni:~# fcinfo hba-port > No Adapters Found. > > > No adapters.... > > > So I try: > > root at omni:~# prtconf -pv > > > And here, at least, I can see that they are discoverd as fibre channel devices: > > > > Node 0x000026 > assigned-addresses: 83220010.00000000.dfdc0000.00000000.00020000.83220018.00000000.dfdb8000.00000000.00004000 > reg: 00220000.00000000.00000000.00000000.00000000.03220010.00000000.00000000.00000000.00020000.03220018.00000000.00000000.00000000.00004000 > compatible: 'pciex1657,13.1657.14.1' + 'pciex1657,13.1657.14' + 'pciex1657,13.1' + 'pciex1657,13' + 'pciexclass,0c0400' + 'pciexclass,0c04' + 'pci1657,13.1657.14.1' + 'pci1657,13.1657.14' + 'pci1657,14' + 'pci1657,13.1' + 'pci1657,13' + 'pciclass,0c0400' + 'pciclass,0c04' > model: 'Fibre Channel' > power-consumption: 00000001.00000001 > devsel-speed: 00000000 > interrupts: 00000001 > subsystem-vendor-id: 00001657 > subsystem-id: 00000014 > unit-address: '0' > class-code: 000c0400 > revision-id: 00000001 > vendor-id: 00001657 > device-id: 00000013 > name: 'pci1657,14' > > Node 0x000027 > assigned-addresses: 83220110.00000000.dfde0000.00000000.00020000.83220118.00000000.dfdbc000.00000000.00004000 > reg: 00220100.00000000.00000000.00000000.00000000.03220110.00000000.00000000.00000000.00020000.03220118.00000000.00000000.00000000.00004000 > compatible: 'pciex1657,13.1657.14.1' + 'pciex1657,13.1657.14' + 'pciex1657,13.1' + 'pciex1657,13' + 'pciexclass,0c0400' + 'pciexclass,0c04' + 'pci1657,13.1657.14.1' + 'pci1657,13.1657.14' + 'pci1657,14' + 'pci1657,13.1' + 'pci1657,13' + 'pciclass,0c0400' + 'pciclass,0c04' > model: 'Fibre Channel' > power-consumption: 00000001.00000001 > devsel-speed: 00000000 > interrupts: 00000002 > subsystem-vendor-id: 00001657 > subsystem-id: 00000014 > unit-address: '0,1' > class-code: 000c0400 > revision-id: 00000001 > vendor-id: 00001657 > device-id: 00000013 > name: 'pci1657,14' > > > They seem to have a downloadable driver f?r Solaris 10 x86, haven't tried it yet, don't want to put in too much work, perhaps they're not worth it...? > > Any info would be nice... > > Rgrds Johan > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From johan.kragsterman at capvert.se Thu Oct 3 16:13:21 2013 From: johan.kragsterman at capvert.se (Johan Kragsterman) Date: Thu, 3 Oct 2013 18:13:21 +0200 Subject: [OmniOS-discuss] Brocade Fc HBA 825 In-Reply-To: <4B21E10D-47E3-4B4D-ADA8-3B0484E0A5A9@gmx.net> References: <4B21E10D-47E3-4B4D-ADA8-3B0484E0A5A9@gmx.net>, Message-ID: Till: Johan Kragsterman Fr?n: GMX Datum: 2013.10.03 10:13 Kopia: omnios-discuss ?rende: Re: [OmniOS-discuss] Brocade Fc HBA 825 "Hi Johan, I have a good few of these Brocade HBA cards working very well with a variety of OSes, including Windows, Linux (Red Hat and SUSE) and VMware ESXi servers. I've also done quite a bit with them on Solaris 10 and 11. In my environment they're usually connected to enterprise arrays (block) and we run POCs with them all year round. They're really grand, comparable to Emulex and QLogics. The only test I haven't done yet is with OpenSolaris or OmniOS. In all the other OSes I've mentioned, it does need the driver to be downloaded from Brocade and loaded, before you can do anything with them. I'm also using Brocade 1020 CNAs (10GbE) and they're the same. Yesterday I've completed a full NexentaStor community edition v3.1.5 install and it did not recognised my 1020 CNA. I might give a try with OmniOS as well and try to load the Solaris driver (now OmniTI guys, let me know if this would be unsupported from your perspective). I just don't have a timeframe for this yet. Anyway, with regarding quality, you're safe enough with the Brocade cards. I hope this helps! Cheers, --- Fabio Rodrigues" Thanks for the info, Fabio! I'd be most interested in the compatibility with omnios, of coarse, since that is what we use as storage platform and as well as host platform. Which means we need both target and initiator support. I don't have much hope of a target implementation of the brocade driver, got to use good ol' qlogic instead, I suppose, but perhaps the initiator would work. Anyone else that has experience with this HBA? Rgrds Johan On 2 Oct 2013, at 18:45, Johan Kragsterman wrote: > Hi! > > Someone knows something about the Brocade Fc HBA 825? It's a dual port 8 Gbit HBA, and since I got hold of some of them, I wanted to test them. I thought they were either Emulex or Qlogic, or perhaps LSI, but they don't bind to any drivers, what I can see. > > Anyone got some experience of these? > > http://www.brocade.com/products/all/adapters/product-details/415-425-815-825-fibre-channel-hba/index.page > > > > Here I did some stuff to check things: > > > root at omni:~# mdb -k > Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp scsi_vhci zfs sata sd ip hook neti sockfs arp usba uhci stmf stmf_sbd md lofs mpt_sas random idm nfs crypto ptm cpc kvm smbsrv ufs logindmux nsmb ] > > Can't find any drivers loaded there... > > > And as well: > > root at omni:~# fcinfo hba-port > No Adapters Found. > > > No adapters.... > > > So I try: > > root at omni:~# prtconf -pv > > > And here, at least, I can see that they are discoverd as fibre channel devices: > > > > ?Node 0x000026 > ? ? ? ? ? ? ? ? assigned-addresses: ?83220010.00000000.dfdc0000.00000000.00020000.83220018.00000000.dfdb8000.00000000.00004000 > ? ? ? ? ? ? ? ? reg: ?00220000.00000000.00000000.00000000.00000000.03220010.00000000.00000000.00000000.00020000.03220018.00000000.00000000.00000000.00004000 > ? ? ? ? ? ? ? ? compatible: 'pciex1657,13.1657.14.1' + 'pciex1657,13.1657.14' + 'pciex1657,13.1' + 'pciex1657,13' + 'pciexclass,0c0400' + 'pciexclass,0c04' + 'pci1657,13.1657.14.1' + 'pci1657,13.1657.14' + 'pci1657,14' + 'pci1657,13.1' + 'pci1657,13' + 'pciclass,0c0400' + 'pciclass,0c04' > ? ? ? ? ? ? ? ? model: ?'Fibre Channel' > ? ? ? ? ? ? ? ? power-consumption: ?00000001.00000001 > ? ? ? ? ? ? ? ? devsel-speed: ?00000000 > ? ? ? ? ? ? ? ? interrupts: ?00000001 > ? ? ? ? ? ? ? ? subsystem-vendor-id: ?00001657 > ? ? ? ? ? ? ? ? subsystem-id: ?00000014 > ? ? ? ? ? ? ? ? unit-address: ?'0' > ? ? ? ? ? ? ? ? class-code: ?000c0400 > ? ? ? ? ? ? ? ? revision-id: ?00000001 > ? ? ? ? ? ? ? ? vendor-id: ?00001657 > ? ? ? ? ? ? ? ? device-id: ?00000013 > ? ? ? ? ? ? ? ? name: ?'pci1657,14' > > ? ? ? ? ? ? Node 0x000027 > ? ? ? ? ? ? ? ? assigned-addresses: ?83220110.00000000.dfde0000.00000000.00020000.83220118.00000000.dfdbc000.00000000.00004000 > ? ? ? ? ? ? ? ? reg: ?00220100.00000000.00000000.00000000.00000000.03220110.00000000.00000000.00000000.00020000.03220118.00000000.00000000.00000000.00004000 > ? ? ? ? ? ? ? ? compatible: 'pciex1657,13.1657.14.1' + 'pciex1657,13.1657.14' + 'pciex1657,13.1' + 'pciex1657,13' + 'pciexclass,0c0400' + 'pciexclass,0c04' + 'pci1657,13.1657.14.1' + 'pci1657,13.1657.14' + 'pci1657,14' + 'pci1657,13.1' + 'pci1657,13' + 'pciclass,0c0400' + 'pciclass,0c04' > ? ? ? ? ? ? ? ? model: ?'Fibre Channel' > ? ? ? ? ? ? ? ? power-consumption: ?00000001.00000001 > ? ? ? ? ? ? ? ? devsel-speed: ?00000000 > ? ? ? ? ? ? ? ? interrupts: ?00000002 > ? ? ? ? ? ? ? ? subsystem-vendor-id: ?00001657 > ? ? ? ? ? ? ? ? subsystem-id: ?00000014 > ? ? ? ? ? ? ? ? unit-address: ?'0,1' > ? ? ? ? ? ? ? ? class-code: ?000c0400 > ? ? ? ? ? ? ? ? revision-id: ?00000001 > ? ? ? ? ? ? ? ? vendor-id: ?00001657 > ? ? ? ? ? ? ? ? device-id: ?00000013 > ? ? ? ? ? ? ? ? name: ?'pci1657,14' > > > They seem to have a downloadable driver f?r Solaris 10 x86, haven't tried it yet, don't want to put in too much work, perhaps they're not worth it...? > > Any info would be nice... > > Rgrds Johan > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From tom.robinson at motec.com.au Mon Oct 7 04:26:34 2013 From: tom.robinson at motec.com.au (Tom Robinson) Date: Mon, 07 Oct 2013 15:26:34 +1100 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' Message-ID: <525237FA.7040609@motec.com.au> Hi, I'm running OmniOS r151006 on a SuperMicro X9 motherboard. when I do: reboot -- -r The system hangs on the 'rebooting...' message. I've disabled Suspend and C-states in the BIOS. I had one successful 'reboot' but now it's hanging again. Anyone have any clues on how to fix this? Kind regards, -- Tom Robinson IT Manager/System Administrator MoTeC Pty Ltd 121 Merrindale Drive Croydon South 3136 Victoria Australia T: +61 3 9761 5050 F: +61 3 9761 5051 E: tom.robinson at motec.com.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature URL: From tom.robinson at motec.com.au Mon Oct 7 04:37:36 2013 From: tom.robinson at motec.com.au (Tom Robinson) Date: Mon, 07 Oct 2013 15:37:36 +1100 Subject: [OmniOS-discuss] SAS tape driver Message-ID: <52523A90.1070700@motec.com.au> Hi, I'm running OmniOS r151006 on a SuperMicro X9 motherboard. I'm trying to configure an IBM TS3100 tape library with not much luck. I used to see the tape through the 'st' driver (at least I think it was the st driver). But after following the IBM documentation and installing the IBMtape driver a I can no longer see the tape. I'm also having issues with the 'reboot -- -r' command hanging on 'rebooting...' message and am wondering if that is compounding the issue (see separate thread). After no luck with the IBMtape driver, I am now trying to revert to the st driver and not having any luck with that either. The device links under /dev/rmt had to be removed as part of the IBMtape setup but they were similar to the following listing: lrwxrwxrwx 1 root root 88 Sep 20 03:18 0 -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0: I now have nothing listed under /dev/rmt and the st module appears not to load: # modinfo -cw | grep '\' 287 11 st UNLOADED/UNINSTALLED # modload -p drv/st can't load module: No such device or address # modload -p drv/amd64/st can't load module: No such device or address (not sure which of the above is the correct driver actually) Any help is much appreciated. Kind regards, Tom More info: # uname -m i86pc /kernel/drv/st.conf name="st" class="scsi" target=0 lun=0; name="st" class="scsi" target=1 lun=0; name="st" class="scsi" target=2 lun=0; name="st" class="scsi" target=3 lun=0; name="st" class="scsi" target=4 lun=0; name="st" class="scsi" target=5 lun=0; name="st" class="scsi" target=6 lun=0; /etc/driver_aliases ... st "scsiclass,01" ... -- Tom Robinson IT Manager/System Administrator MoTeC Pty Ltd 121 Merrindale Drive Croydon South 3136 Victoria Australia T: +61 3 9761 5050 F: +61 3 9761 5051 E: tom.robinson at motec.com.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature URL: From narayan.desai at gmail.com Mon Oct 7 11:34:37 2013 From: narayan.desai at gmail.com (Narayan Desai) Date: Mon, 7 Oct 2013 06:34:37 -0500 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <525237FA.7040609@motec.com.au> References: <525237FA.7040609@motec.com.au> Message-ID: This is caused by the system attempting to use fastboot on default reboot. We've disabled that and things seem to work properly; the following commands do the trick. (the first changes reboot not to use fastboot, the second causes the system to do a full reboot upon panic) -nld # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false # svcadm refresh svc:/system/boot-config:default # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false # svcadm refresh svc:/system/boot-config:default On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson wrote: > Hi, > > I'm running OmniOS r151006 on a SuperMicro X9 motherboard. > > when I do: > > reboot -- -r > > The system hangs on the 'rebooting...' message. > > I've disabled Suspend and C-states in the BIOS. I had one successful > 'reboot' but now it's hanging > again. > > Anyone have any clues on how to fix this? > > Kind regards, > > -- > > Tom Robinson > IT Manager/System Administrator > > MoTeC Pty Ltd > > 121 Merrindale Drive > Croydon South > 3136 Victoria > Australia > > T: +61 3 9761 5050 > F: +61 3 9761 5051 > E: tom.robinson at motec.com.au > > > > _______________________________________________ > 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: From alka at hfg-gmuend.de Mon Oct 7 12:47:19 2013 From: alka at hfg-gmuend.de (Guenther Alka) Date: Mon, 07 Oct 2013 14:47:19 +0200 Subject: [OmniOS-discuss] AMPO webserver stack (Apache, mySQL, PHPmyadmin, PHP, Owncloud) In-Reply-To: <52523A90.1070700@motec.com.au> References: <52523A90.1070700@motec.com.au> Message-ID: <5252AD57.9020403@hfg-gmuend.de> info: I try to support the ampo community add-on for OmniOS/ napp-it (free at home and commercially) it includes: * Apache 2.4.6, * MySQL 5.6.12, * PHPMyadmin, * PHP 5.4.19 * OwnCloud 5.0.10 You can install the whole ampo stack with one command (without napp-it you may get some messages about missing files but you can ignore). It uses the SmartOS repository as this is the best and most up to date source not only for SmartOS but for OmniOS and OpenIndiana as well: http://wiki.openindiana.org/oi/3.+Installing+software+and+package+management You can test the first version of the online installer (run as root at console) wget -O - www.napp-it.org/ampo | perl due to some dependencies, you need to run the installer twice. Any help with this package and the installer is welcome as well as help with other cloud add-ons like http://seafile.com/en/home/ more http://napp-it.org/extensions/ampo_en.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From garrett.damore at dey-sys.com Mon Oct 7 15:05:21 2013 From: garrett.damore at dey-sys.com (Garrett D'Amore) Date: Mon, 7 Oct 2013 08:05:21 -0700 Subject: [OmniOS-discuss] SAS tape driver In-Reply-To: <52523A90.1070700@motec.com.au> References: <52523A90.1070700@motec.com.au> Message-ID: <6519B345-5BC9-45A0-89BA-8E7009E33424@dey-sys.com> Need to see the IBM changes to /etc/driver_aliases. My guess is that this is the source of the problem. If you know the name of the kernel driver for the IBM tape module, you could rem_drv it. A reboot may be required for the change to take effect. - Garrett On Oct 6, 2013, at 9:37 PM, Tom Robinson wrote: > Hi, > > I'm running OmniOS r151006 on a SuperMicro X9 motherboard. > > I'm trying to configure an IBM TS3100 tape library with not much luck. > > I used to see the tape through the 'st' driver (at least I think it was the st driver). But after > following the IBM documentation and installing the IBMtape driver a I can no longer see the tape. > > I'm also having issues with the 'reboot -- -r' command hanging on 'rebooting...' message and am > wondering if that is compounding the issue (see separate thread). > > After no luck with the IBMtape driver, I am now trying to revert to the st driver and not having any > luck with that either. > > The device links under /dev/rmt had to be removed as part of the IBMtape setup but they were similar > to the following listing: > lrwxrwxrwx 1 root root 88 Sep 20 03:18 0 -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0: > > I now have nothing listed under /dev/rmt and the st module appears not to load: > # modinfo -cw | grep '\' > 287 11 st UNLOADED/UNINSTALLED > > # modload -p drv/st > can't load module: No such device or address > > # modload -p drv/amd64/st > can't load module: No such device or address > > (not sure which of the above is the correct driver actually) > > Any help is much appreciated. > > Kind regards, > Tom > > More info: > # uname -m > i86pc > > /kernel/drv/st.conf > name="st" class="scsi" target=0 lun=0; > name="st" class="scsi" target=1 lun=0; > name="st" class="scsi" target=2 lun=0; > name="st" class="scsi" target=3 lun=0; > name="st" class="scsi" target=4 lun=0; > name="st" class="scsi" target=5 lun=0; > name="st" class="scsi" target=6 lun=0; > > /etc/driver_aliases > ... > st "scsiclass,01" > ... > > > > > > > > -- > > Tom Robinson > IT Manager/System Administrator > > MoTeC Pty Ltd > > 121 Merrindale Drive > Croydon South > 3136 Victoria > Australia > > T: +61 3 9761 5050 > F: +61 3 9761 5051 > E: tom.robinson at motec.com.au > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From garrett.damore at dey-sys.com Mon Oct 7 15:06:25 2013 From: garrett.damore at dey-sys.com (Garrett D'Amore) Date: Mon, 7 Oct 2013 08:06:25 -0700 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: References: <525237FA.7040609@motec.com.au> Message-ID: <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> If you're seeing hangs like this, I would appreciate knowing the hardware configuration. Prtconf -vp might be helpful. Presumably this is the result of one or more devices not doing the right thing for quiesce(). - Garrett On Oct 7, 2013, at 4:34 AM, Narayan Desai wrote: > This is caused by the system attempting to use fastboot on default reboot. We've disabled that and things seem to work properly; the following commands do the trick. (the first changes reboot not to use fastboot, the second causes the system to do a full reboot upon panic) > -nld > > # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false > # svcadm refresh svc:/system/boot-config:default > # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false > # svcadm refresh svc:/system/boot-config:default > > > > On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson wrote: > Hi, > > I'm running OmniOS r151006 on a SuperMicro X9 motherboard. > > when I do: > > reboot -- -r > > The system hangs on the 'rebooting...' message. > > I've disabled Suspend and C-states in the BIOS. I had one successful 'reboot' but now it's hanging > again. > > Anyone have any clues on how to fix this? > > Kind regards, > > -- > > Tom Robinson > IT Manager/System Administrator > > MoTeC Pty Ltd > > 121 Merrindale Drive > Croydon South > 3136 Victoria > Australia > > T: +61 3 9761 5050 > F: +61 3 9761 5051 > E: tom.robinson at motec.com.au > > > > _______________________________________________ > 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: From fabio at fabiorabelo.wiki.br Mon Oct 7 17:43:37 2013 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Mon, 7 Oct 2013 14:43:37 -0300 Subject: [OmniOS-discuss] from LACP to LAG1 ?!? Message-ID: Hi to all I do not know if this is an off-topic, if it is, just inform me ... I will thank anyway .. I just received a follow-up from Netgear support in subject to a new 10GB switcher connecting to a Solaris box ( OmniOS naturaly, 151006 ) using LACP that is not working ( but works perfectly in another Cisco Switcher ) . They asked me to change from LACP to LAG1 , and I have no idea what they talking about ! Someone knows what is LAG1 ?!? And mostly, how to set it up ? Thanks in advance ... From seb.messier at gmail.com Mon Oct 7 18:04:50 2013 From: seb.messier at gmail.com (Sebastien Messier) Date: Mon, 7 Oct 2013 14:04:50 -0400 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> Message-ID: I had this problem too. It was a fastboot problem. I disabled the fastboot option and now my server is doing a full hard reboot on the command reboot. This suits my needs because I want to make sure that I can remotely reboot the server. On Mon, Oct 7, 2013 at 11:06 AM, Garrett D'Amore wrote: > If you're seeing hangs like this, I would appreciate knowing the hardware > configuration. Prtconf -vp might be helpful. Presumably this is the > result of one or more devices not doing the right thing for quiesce(). > > - Garrett > > On Oct 7, 2013, at 4:34 AM, Narayan Desai wrote: > > This is caused by the system attempting to use fastboot on default reboot. > We've disabled that and things seem to work properly; the following > commands do the trick. (the first changes reboot not to use fastboot, the > second causes the system to do a full reboot upon panic) > -nld > > # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false > # svcadm refresh svc:/system/boot-config:default > > # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false > # svcadm refresh svc:/system/boot-config:default > > > > > On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson wrote: > >> Hi, >> >> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >> >> when I do: >> >> reboot -- -r >> >> The system hangs on the 'rebooting...' message. >> >> I've disabled Suspend and C-states in the BIOS. I had one successful >> 'reboot' but now it's hanging >> again. >> >> Anyone have any clues on how to fix this? >> >> Kind regards, >> >> -- >> >> Tom Robinson >> IT Manager/System Administrator >> >> MoTeC Pty Ltd >> >> 121 Merrindale Drive >> Croydon South >> 3136 Victoria >> Australia >> >> T: +61 3 9761 5050 >> F: +61 3 9761 5051 >> E: tom.robinson at motec.com.au >> >> >> >> _______________________________________________ >> 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 > > -- *S?bastien Messier *?tudiant au baccalaur?at en g?nie m?canique ?cole de technologie Sup?rieure Directeur m?canique du club ?tudiant Walking Machine * **Walking Machine **| Robotique mobile autonome ** **P*:* *(514) 396-8800 x7408*| **| seb.messier at gmail.com* -------------- next part -------------- An HTML attachment was scrubbed... URL: From henson at acm.org Mon Oct 7 18:13:48 2013 From: henson at acm.org (Paul B. Henson) Date: Mon, 7 Oct 2013 11:13:48 -0700 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> Message-ID: <20131007181348.GF22464@bender.unx.csupomona.edu> On Mon, Oct 07, 2013 at 08:06:25AM -0700, Garrett D'Amore wrote: > If you're seeing hangs like this, I would appreciate knowing the hardware configuration. Prtconf -vp might be helpful. Presumably this is the result of one or more devices not doing the right thing for quiesce(). I had the same problem on a supermicro box: Case: 836BA-R920B Motherboard: X9SRI-F BIOS: 2.0a 04/19/2013 CPU: Intel Xeon E5-2620 Memory: 3 x Crucial CT2KIT102472BB160B (6 DIMMs, 48G) HBA: LSI 9201-16i prtconf attached. I disabled fastboot and don't care too much about fixing it; it gets rebooted very infrequently and probably 4 times out of 5 when I do reboot it I need to get into the bios or do something of that nature and ended up getting annoyed that I had to reboot it twice because I forgot about fastboot ;). -------------- next part -------------- System Configuration: Oracle Corporation i86pc Memory size: 49120 Megabytes System Peripherals (PROM Nodes): Node 0x000001 bios-boot-device: '80' stdout: 00000000 name: 'i86pc' Node 0x000002 existing: 00dd1000.00000000.0a46c401.00000000 name: 'ramdisk' Node 0x000003 acpi-namespace: '\_SB_.PCI0' compatible: 'pciex_root_complex' device_type: 'pciex' reg: 00000000.00000000.00000000 #size-cells: 00000002 #address-cells: 00000003 name: 'pci' Node 0x000004 reg: 00000000.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c00.15d9.62b.7' + 'pciex8086,3c00.15d9.62b' + 'pciex8086,3c00.7' + 'pciex8086,3c00' + 'pciexclass,060000' + 'pciexclass,0600' + 'pci8086,3c00.15d9.62b.7' + 'pci8086,3c00.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c00.7' + 'pci8086,3c00' + 'pciclass,060000' + 'pciclass,0600' model: 'Host bridge' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '0' class-code: 00060000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c00 name: 'pci15d9,62b' Node 0x000005 acpi-namespace: '\_SB_.PCI0.NPE1' reg: 00000800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c02.7' + 'pciex8086,3c02' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c02.7' + 'pci8086,3c02' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' bus-range: 00000001.00000001 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 000000ff devsel-speed: 00000000 interrupts: 00000001 unit-address: '1' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c02 name: 'pci8086,3c02' Node 0x000006 acpi-namespace: '\_SB_.PCI0.NPE3' slot-names: 00000001.746f6c53.00000034 reg: 00001000.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c04.7' + 'pciex8086,3c04' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c04.7' + 'pci8086,3c04' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' bus-range: 00000002.00000002 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000000 devsel-speed: 00000000 interrupts: 00000001 unit-address: '2' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c04 name: 'pci8086,3c04' Node 0x000007 acpi-namespace: '\_SB_.PCI0.NPE7' slot-names: 00000001.746f6c53.00000033 reg: 00001800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c08.7' + 'pciex8086,3c08' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c08.7' + 'pci8086,3c08' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 82000000.00000000.fbc00000.82000000.00000000.fbc00000.00000000.00100000 bus-range: 00000003.00000004 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000000 devsel-speed: 00000000 interrupts: 00000001 unit-address: '3' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c08 name: 'pci8086,3c08' Node 0x000020 assigned-addresses: 82030010.00000000.fbc20000.00000000.00020000.8203001c.00000000.fbcc4000.00000000.00004000 reg: 00030000.00000000.00000000.00000000.00000000.02030010.00000000.00000000.00000000.00020000.0203001c.00000000.00000000.00000000.00004000 compatible: 'pciex8086,1521.15d9.1521.1' + 'pciex8086,1521.15d9.1521' + 'pciex8086,1521.1' + 'pciex8086,1521' + 'pciexclass,020000' + 'pciexclass,0200' + 'pci8086,1521.15d9.1521.1' + 'pci8086,1521.15d9.1521' + 'pci15d9,1521' + 'pci8086,1521.1' + 'pci8086,1521' + 'pciclass,020000' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 00001521 unit-address: '0' class-code: 00020000 revision-id: 00000001 vendor-id: 00008086 device-id: 00001521 name: 'pci15d9,1521' Node 0x000021 assigned-addresses: 82030110.00000000.fbc00000.00000000.00020000.8203011c.00000000.fbcc0000.00000000.00004000 reg: 00030100.00000000.00000000.00000000.00000000.02030110.00000000.00000000.00000000.00020000.0203011c.00000000.00000000.00000000.00004000 compatible: 'pciex8086,1521.15d9.1521.1' + 'pciex8086,1521.15d9.1521' + 'pciex8086,1521.1' + 'pciex8086,1521' + 'pciexclass,020000' + 'pciexclass,0200' + 'pci8086,1521.15d9.1521.1' + 'pci8086,1521.15d9.1521' + 'pci15d9,1521' + 'pci8086,1521.1' + 'pci8086,1521' + 'pciclass,020000' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 000015d9 subsystem-id: 00001521 unit-address: '0,1' class-code: 00020000 revision-id: 00000001 vendor-id: 00008086 device-id: 00001521 name: 'pci15d9,1521' Node 0x000008 acpi-namespace: '\_SB_.PCI0.NPE9' slot-names: 00000001.746f6c53.00000036 reg: 00001a00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c0a.7' + 'pciex8086,3c0a' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c0a.7' + 'pci8086,3c0a' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 81000000.00000000.0000e000.81000000.00000000.0000e000.00000000.00001000.82000000.00000000.fb900000.82000000.00000000.fb900000.00000000.00300000 bus-range: 00000005.00000005 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000000 devsel-speed: 00000000 interrupts: 00000001 unit-address: '3,2' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c0a name: 'pci8086,3c0a' Node 0x000022 assigned-addresses: 81050010.00000000.0000e000.00000000.00000100.83050014.00000000.fbb9c000.00000000.00004000.8305001c.00000000.fbb40000.00000000.00040000 reg: 00050000.00000000.00000000.00000000.00000000.01050010.00000000.00000000.00000000.00000100.03050014.00000000.00000000.00000000.00004000.0305001c.00000000.00000000.00000000.00040000 compatible: 'pciex1000,64.1000.30c0.2' + 'pciex1000,64.1000.30c0' + 'pciex1000,64.2' + 'pciex1000,64' + 'pciexclass,010700' + 'pciexclass,0107' + 'pci1000,64.1000.30c0.2' + 'pci1000,64.1000.30c0' + 'pci1000,30c0' + 'pci1000,64.2' + 'pci1000,64' + 'pciclass,010700' + 'pciclass,0107' model: 'Serial Attached SCSI Controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 00001000 subsystem-id: 000030c0 unit-address: '0' class-code: 00010700 revision-id: 00000002 vendor-id: 00001000 device-id: 00000064 name: 'pci1000,30c0' Node 0x000009 assigned-addresses: 83002010.00000000.fbd1c000.00000000.00004000 reg: 00002000.00000000.00000000.00000000.00000000.03002010.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c20.15d9.62b.7' + 'pciex8086,3c20.15d9.62b' + 'pciex8086,3c20.7' + 'pciex8086,3c20' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c20.15d9.62b.7' + 'pci8086,3c20.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c20.7' + 'pci8086,3c20' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c20 name: 'pci15d9,62b' Node 0x00000a assigned-addresses: 83002110.00000000.fbd18000.00000000.00004000 reg: 00002100.00000000.00000000.00000000.00000000.03002110.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c21.15d9.62b.7' + 'pciex8086,3c21.15d9.62b' + 'pciex8086,3c21.7' + 'pciex8086,3c21' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c21.15d9.62b.7' + 'pci8086,3c21.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c21.7' + 'pci8086,3c21' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '4,1' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c21 name: 'pci15d9,62b' Node 0x00000b assigned-addresses: 83002210.00000000.fbd14000.00000000.00004000 reg: 00002200.00000000.00000000.00000000.00000000.03002210.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c22.15d9.62b.7' + 'pciex8086,3c22.15d9.62b' + 'pciex8086,3c22.7' + 'pciex8086,3c22' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c22.15d9.62b.7' + 'pci8086,3c22.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c22.7' + 'pci8086,3c22' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000003 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '4,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c22 name: 'pci15d9,62b' Node 0x00000c assigned-addresses: 83002310.00000000.fbd10000.00000000.00004000 reg: 00002300.00000000.00000000.00000000.00000000.03002310.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c23.15d9.62b.7' + 'pciex8086,3c23.15d9.62b' + 'pciex8086,3c23.7' + 'pciex8086,3c23' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c23.15d9.62b.7' + 'pci8086,3c23.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c23.7' + 'pci8086,3c23' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000004 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '4,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c23 name: 'pci15d9,62b' Node 0x00000d assigned-addresses: 83002410.00000000.fbd0c000.00000000.00004000 reg: 00002400.00000000.00000000.00000000.00000000.03002410.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c24.15d9.62b.7' + 'pciex8086,3c24.15d9.62b' + 'pciex8086,3c24.7' + 'pciex8086,3c24' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c24.15d9.62b.7' + 'pci8086,3c24.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c24.7' + 'pci8086,3c24' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '4,4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c24 name: 'pci15d9,62b' Node 0x00000e assigned-addresses: 83002510.00000000.fbd08000.00000000.00004000 reg: 00002500.00000000.00000000.00000000.00000000.03002510.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c25.15d9.62b.7' + 'pciex8086,3c25.15d9.62b' + 'pciex8086,3c25.7' + 'pciex8086,3c25' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c25.15d9.62b.7' + 'pci8086,3c25.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c25.7' + 'pci8086,3c25' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '4,5' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c25 name: 'pci15d9,62b' Node 0x00000f assigned-addresses: 83002610.00000000.fbd04000.00000000.00004000 reg: 00002600.00000000.00000000.00000000.00000000.03002610.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c26.15d9.62b.7' + 'pciex8086,3c26.15d9.62b' + 'pciex8086,3c26.7' + 'pciex8086,3c26' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c26.15d9.62b.7' + 'pci8086,3c26.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c26.7' + 'pci8086,3c26' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000003 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '4,6' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c26 name: 'pci15d9,62b' Node 0x000010 assigned-addresses: 83002710.00000000.fbd00000.00000000.00004000 reg: 00002700.00000000.00000000.00000000.00000000.03002710.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c27.15d9.62b.7' + 'pciex8086,3c27.15d9.62b' + 'pciex8086,3c27.7' + 'pciex8086,3c27' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c27.15d9.62b.7' + 'pci8086,3c27.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c27.7' + 'pci8086,3c27' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000004 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '4,7' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c27 name: 'pci15d9,62b' Node 0x000011 reg: 00002800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c28.15d9.62b.7' + 'pciex8086,3c28.15d9.62b' + 'pciex8086,3c28.7' + 'pciex8086,3c28' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c28.15d9.62b.7' + 'pci8086,3c28.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c28.7' + 'pci8086,3c28' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '5' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c28 name: 'pci15d9,62b' Node 0x000012 reg: 00002a00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c2a.15d9.62b.7' + 'pciex8086,3c2a.15d9.62b' + 'pciex8086,3c2a.7' + 'pciex8086,3c2a' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c2a.15d9.62b.7' + 'pci8086,3c2a.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c2a.7' + 'pci8086,3c2a' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '5,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c2a name: 'pci15d9,62b' Node 0x000013 assigned-addresses: 82002c10.00000000.fbd25000.00000000.00001000 reg: 00002c00.00000000.00000000.00000000.00000000.02002c10.00000000.00000000.00000000.00001000 compatible: 'pci8086,3c2c.15d9.62b.7' + 'pci8086,3c2c.15d9.62b' + 'pci15d9,62b' + 'pci8086,3c2c.7' + 'pci8086,3c2c' + 'pciclass,080020' + 'pciclass,0800' model: 'I/O(x) APIC' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '5,4' class-code: 00080020 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c2c name: 'pci15d9,62b' Node 0x000016 acpi-namespace: '\_SB_.PCI0.BR33' reg: 00008800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,1d3e.6' + 'pciex8086,1d3e' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,1d3e.6' + 'pci8086,1d3e' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' bus-range: 00000006.00000006 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 unit-address: '11' class-code: 00060400 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d3e name: 'pci8086,1d3e' Node 0x000017 acpi-namespace: '\_SB_.PCI0.HEC1' assigned-addresses: 8300b010.00000000.fed0e000.00000000.00000010 reg: 0000b000.00000000.00000000.00000000.00000000.0300b010.00000000.00000000.00000000.00000010 compatible: 'pci8086,1d3a.15d9.62b.5' + 'pci8086,1d3a.15d9.62b' + 'pci15d9,62b' + 'pci8086,1d3a.5' + 'pci8086,1d3a' + 'pciclass,078000' + 'pciclass,0780' model: 'Communication device' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '16' class-code: 00078000 revision-id: 00000005 vendor-id: 00008086 device-id: 00001d3a name: 'pci15d9,62b' Node 0x000018 acpi-namespace: '\_SB_.PCI0.HEC2' assigned-addresses: 8300b110.00000000.fed0f000.00000000.00000010 reg: 0000b100.00000000.00000000.00000000.00000000.0300b110.00000000.00000000.00000000.00000010 compatible: 'pci8086,1d3b.15d9.62b.5' + 'pci8086,1d3b.15d9.62b' + 'pci15d9,62b' + 'pci8086,1d3b.5' + 'pci8086,1d3b' + 'pciclass,078000' + 'pciclass,0780' model: 'Communication device' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '16,1' class-code: 00078000 revision-id: 00000005 vendor-id: 00008086 device-id: 00001d3b name: 'pci15d9,62b' Node 0x000019 acpi-namespace: '\_SB_.PCI0.USBE' assigned-addresses: 8200d010.00000000.fbd23000.00000000.00000400 reg: 0000d000.00000000.00000000.00000000.00000000.0200d010.00000000.00000000.00000000.00000400 compatible: 'pci8086,1d2d.15d9.62b.6' + 'pci8086,1d2d.15d9.62b' + 'pci15d9,62b' + 'pci8086,1d2d.6' + 'pci8086,1d2d' + 'pciclass,0c0320' + 'pciclass,0c03' model: 'Universal Serial Bus EHCI compliant' power-consumption: 00000001.00000001 fast-back-to-back: devsel-speed: 00000001 interrupts: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '1a' class-code: 000c0320 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d2d name: 'pci15d9,62b' Node 0x00001a acpi-namespace: '\_SB_.PCI0.EUSB' assigned-addresses: 8200e810.00000000.fbd22000.00000000.00000400 reg: 0000e800.00000000.00000000.00000000.00000000.0200e810.00000000.00000000.00000000.00000400 compatible: 'pci8086,1d26.15d9.62b.6' + 'pci8086,1d26.15d9.62b' + 'pci15d9,62b' + 'pci8086,1d26.6' + 'pci8086,1d26' + 'pciclass,0c0320' + 'pciclass,0c03' model: 'Universal Serial Bus EHCI compliant' power-consumption: 00000001.00000001 fast-back-to-back: devsel-speed: 00000001 interrupts: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '1d' class-code: 000c0320 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d26 name: 'pci15d9,62b' Node 0x00001b acpi-namespace: '\_SB_.PCI0.BR20' slot-names: 00000002.746f6c53.00003433 reg: 0000f000.00000000.00000000.00000000.00000000 compatible: 'pci8086,244e.a6' + 'pci8086,244e' + 'pciclass,060401' + 'pciclass,0604' model: 'Subtractive Decode PCI-PCI bridge' ranges: 81000000.00000000.000003b0.81000000.00000000.000003b0.00000000.0000000c.81000000.00000000.000003c0.81000000.00000000.000003c0.00000000.00000020.82000000.00000000.000a0000.82000000.00000000.000a0000.00000000.00020000.82000000.00000000.fb000000.82000000.00000000.fb000000.00000000.00900000.c2000000.00000000.fa000000.c2000000.00000000.fa000000.00000000.01000000 bus-range: 00000007.00000007 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pci' power-consumption: 00000001.00000001 devsel-speed: 00000000 unit-address: '1e' class-code: 00060401 revision-id: 000000a6 vendor-id: 00008086 device-id: 0000244e name: 'pci8086,244e' Node 0x000023 assigned-addresses: c2072010.00000000.fa000000.00000000.01000000.82072014.00000000.fb800000.00000000.00004000.82072018.00000000.fb000000.00000000.00800000.a1072000.00000000.000003b0.00000000.0000000c.a1072000.00000000.000003c0.00000000.00000020.a2072000.00000000.000a0000.00000000.00020000 reg: 00072000.00000000.00000000.00000000.00000000.42072010.00000000.00000000.00000000.01000000.02072014.00000000.00000000.00000000.00004000.02072018.00000000.00000000.00000000.00800000.a1072000.00000000.000003b0.00000000.0000000c.a1072000.00000000.000003c0.00000000.00000020.a2072000.00000000.000a0000.00000000.00020000 compatible: 'pci102b,532.15d9.62b.a' + 'pci102b,532.15d9.62b' + 'pci15d9,62b' + 'pci102b,532.a' + 'pci102b,532' + 'pciclass,030000' + 'pciclass,0300' model: 'VGA compatible controller' power-consumption: 00000001.00000001 fast-back-to-back: devsel-speed: 00000001 interrupts: 00000001 max-latency: 00000020 min-grant: 00000010 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b device_type: 'display' unit-address: '4' class-code: 00030000 revision-id: 0000000a vendor-id: 0000102b device-id: 00000532 name: 'display' Node 0x00001c ranges: 00000001.00000000.81000000.00000000.00000000.00000100.00000001.000002f8.81000000.00000000.000002f8.00000008.00000001.000003e8.81000000.00000000.000003e8.00000008.00000001.000003f8.81000000.00000000.000003f8.00000088.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000500.81000000.00000000.00000500.00000080.00000001.00000a30.81000000.00000000.00000a30.00000010.00000001.00000b00.81000000.00000000.00000b00.00000080.00000001.00000ca2.81000000.00000000.00000ca2.00000002.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00001180.81000000.00000000.00001180.00000020.00000000.00000000.82000000.00000000.00000000.000a0000.00000000.00000400.82000000.00000000.00000400.00000100.00000000.fbffc000.82000000.00000000.fbffc000.00002000.00000000.fc000000.82000000.00000000.fc000000.02d00400.00000000.fed1c000.82000000.00000000.fed1c000.00004000.00000000.ff000000.82000000.00000000.ff000000.01000000 acpi-namespace: '\_SB_.PCI0.SBRG' device_type: 'isa' reg: 0000f800.00000000.00000000.00000000.00000000 compatible: 'pci8086,1d41.15d9.62b.6' + 'pci8086,1d41.15d9.62b' + 'pci15d9,62b' + 'pci8086,1d41.6' + 'pci8086,1d41' + 'pciclass,060100' + 'pciclass,0601' model: 'ISA bridge' power-consumption: 00000001.00000001 devsel-speed: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '1f' class-code: 00060100 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d41 name: 'isa' Node 0x000034 compatible: 'pnpPNP,c01' reg: 00000000.fc000000.01000000.00000000.fd000000.01000000.00000000.fe000000.00b00000.00000000.feb00000.00100000 acpi-namespace: '\_SB_.PCI0.IOH_' model: 'Motherboard' name: 'motherboard' Node 0x000035 unit-address: '1,60' interrupts: 00000001.0000000c reg: 00000001.00000060.00000001.00000001.00000064.00000001 name: 'i8042' Node 0x000036 compatible: 'pnpPNP,f03' device-type: 'mouse' interrupts: 00000001.0000000c reg: 00000001 acpi-namespace: '\_SB_.PCI0.SBRG.PS2M' model: 'Microsoft PS/2-style Mouse' name: 'mouse' Node 0x000037 compatible: 'pnpPNP,501' interrupts: 00000004 reg: 00000001.000003f8.00000008 acpi-namespace: '\_SB_.PCI0.SBRG.UAR1' model: '16550A-compatible COM port' name: 'asy' Node 0x000038 compatible: 'pnpPNP,501' interrupts: 00000003 reg: 00000001.000002f8.00000008 acpi-namespace: '\_SB_.PCI0.SBRG.UAR2' model: '16550A-compatible COM port' name: 'asy' Node 0x000039 compatible: 'pnpPNP,501' interrupts: 0000000a reg: 00000001.000003e8.00000008 acpi-namespace: '\_SB_.PCI0.SBRG.UAR3' model: '16550A-compatible COM port' name: 'asy' Node 0x00003a compatible: 'pnpPNP,c01' reg: 00000001.00000400.00000054.00000001.00000458.00000028.00000001.00001180.00000020.00000001.00000500.00000080.00000000.fed1c000.00004000.00000000.fec00000.00100000.00000000.ff000000.01000000 acpi-namespace: '\_SB_.PCI0.PCH_' model: 'Motherboard' name: 'motherboard' Node 0x00003b compatible: 'pnpPNP,c01' reg: 00000000.00000000.000a0000 acpi-namespace: '\_SB_.RMEM' model: 'Motherboard' name: 'motherboard' Node 0x00001d acpi-namespace: '\_SB_.PCI0.SAT0' assigned-addresses: 8100fa10.00000000.0000f050.00000000.00000008.8100fa14.00000000.0000f040.00000000.00000004.8100fa18.00000000.0000f030.00000000.00000008.8100fa1c.00000000.0000f020.00000000.00000004.8100fa20.00000000.0000f000.00000000.00000020.8200fa24.00000000.fbd21000.00000000.00000800 reg: 0000fa00.00000000.00000000.00000000.00000000.0100fa10.00000000.00000000.00000000.00000008.0100fa14.00000000.00000000.00000000.00000004.0100fa18.00000000.00000000.00000000.00000008.0100fa1c.00000000.00000000.00000000.00000004.0100fa20.00000000.00000000.00000000.00000020.0200fa24.00000000.00000000.00000000.00000800 compatible: 'pci8086,1d02.15d9.62b.6' + 'pci8086,1d02.15d9.62b' + 'pci15d9,62b' + 'pci8086,1d02.6' + 'pci8086,1d02' + 'pciclass,010601' + 'pciclass,0106' model: 'SATA AHCI 1.0 Interface' power-consumption: 00000001.00000001 66mhz-capable: fast-back-to-back: devsel-speed: 00000001 interrupts: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '1f,2' class-code: 00010601 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d02 name: 'pci15d9,62b' Node 0x00001e assigned-addresses: 8300fb10.00000000.fbd20000.00000000.00000100.8100fb20.00000000.00001180.00000000.00000020 reg: 0000fb00.00000000.00000000.00000000.00000000.0300fb10.00000000.00000000.00000000.00000100.0100fb20.00000000.00000000.00000000.00000020 compatible: 'pci8086,1d22.15d9.62b.6' + 'pci8086,1d22.15d9.62b' + 'pci15d9,62b' + 'pci8086,1d22.6' + 'pci8086,1d22' + 'pciclass,0c0500' + 'pciclass,0c05' model: 'SMBus (System Management Bus)' power-consumption: 00000001.00000001 fast-back-to-back: devsel-speed: 00000001 interrupts: 00000003 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '1f,3' class-code: 000c0500 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d22 name: 'pci15d9,62b' Node 0x00001f assigned-addresses: 8300fe10.00000000.fed08000.00000000.00001000 reg: 0000fe00.00000000.00000000.00000000.00000000.0300fe10.00000000.00000000.00000000.00001000 compatible: 'pci8086,1d24.15d9.62b.6' + 'pci8086,1d24.15d9.62b' + 'pci15d9,62b' + 'pci8086,1d24.6' + 'pci8086,1d24' + 'pciclass,118000' + 'pciclass,1180' model: 'DSP/DAP controllers' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000003 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 0000062b unit-address: '1f,6' class-code: 00118000 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d24 name: 'pci15d9,62b' Node 0x000014 name: 'ioapics' Node 0x000015 reg: fbd25000.00000000 device_type: 'ioapic' device-id: 00003c2c vendor-id: 00008086 name: 'ioapic' Node 0x000024 device_type: 'acpirootnex' compatible: 'SOLA0001' + 'acpirootnex' + 'SOLA0002' + 'acpivirtnex' acpi-namespace: '\' name: 'fw' Node 0x000025 unit-address: '0' compatible: 'acpidevice' + 'SOLA0002' + 'acpivirtnex' acpi-namespace: '\_SB_' device_type: 'acpidevice' name: 'sb' Node 0x000026 unit-address: '0' acpi-uid: 'CPUSCK0' compatible: 'ACPI0004' + 'acpicontainer' + 'SOLA0002' + 'acpivirtnex' acpi-namespace: '\_SB_.SCK0' device_type: 'acpicontainer' name: 'socket' Node 0x000027 unit-address: '0' acpi-uid: 'PCI0-CP00' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000000 acpi-processor-id: 00000000 acpi-namespace: '\_SB_.SCK0.CP00' device_type: 'acpicpu' name: 'cpu' Node 0x000028 unit-address: '1' acpi-uid: 'PCI0-CP01' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000001 acpi-processor-id: 00000001 acpi-namespace: '\_SB_.SCK0.CP01' device_type: 'acpicpu' name: 'cpu' Node 0x000029 unit-address: '2' acpi-uid: 'PCI0-CP02' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000002 acpi-processor-id: 00000002 acpi-namespace: '\_SB_.SCK0.CP02' device_type: 'acpicpu' name: 'cpu' Node 0x00002a unit-address: '3' acpi-uid: 'PCI0-CP03' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000003 acpi-processor-id: 00000003 acpi-namespace: '\_SB_.SCK0.CP03' device_type: 'acpicpu' name: 'cpu' Node 0x00002b unit-address: '4' acpi-uid: 'PCI0-CP04' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000004 acpi-processor-id: 00000004 acpi-namespace: '\_SB_.SCK0.CP04' device_type: 'acpicpu' name: 'cpu' Node 0x00002c unit-address: '5' acpi-uid: 'PCI0-CP05' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000005 acpi-processor-id: 00000005 acpi-namespace: '\_SB_.SCK0.CP05' device_type: 'acpicpu' name: 'cpu' Node 0x00002d unit-address: '6' acpi-uid: 'PCI0-CP06' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000006 acpi-processor-id: 00000006 acpi-namespace: '\_SB_.SCK0.CP06' device_type: 'acpicpu' name: 'cpu' Node 0x00002e unit-address: '7' acpi-uid: 'PCI0-CP07' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000007 acpi-processor-id: 00000007 acpi-namespace: '\_SB_.SCK0.CP07' device_type: 'acpicpu' name: 'cpu' Node 0x00002f unit-address: '8' acpi-uid: 'PCI0-CP08' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000008 acpi-processor-id: 00000008 acpi-namespace: '\_SB_.SCK0.CP08' device_type: 'acpicpu' name: 'cpu' Node 0x000030 unit-address: '9' acpi-uid: 'PCI0-CP09' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000009 acpi-processor-id: 00000009 acpi-namespace: '\_SB_.SCK0.CP09' device_type: 'acpicpu' name: 'cpu' Node 0x000031 unit-address: '10' acpi-uid: 'PCI0-CP0A' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 0000000a acpi-processor-id: 0000000a acpi-namespace: '\_SB_.SCK0.CP0A' device_type: 'acpicpu' name: 'cpu' Node 0x000032 unit-address: '11' acpi-uid: 'PCI0-CP0B' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 0000000b acpi-processor-id: 0000000b acpi-namespace: '\_SB_.SCK0.CP0B' device_type: 'acpicpu' name: 'cpu' Node 0x000033 io-space: 00000000.00000010.00000010.00000010.00000020.00000002.00000022.0000001e.00000040.00000004.00000044.0000001c.00000060.00000001.00000061.00000001.00000062.00000002.00000064.00000001.00000065.0000000b.00000070.00000002.00000072.0000000e.00000080.00000001.00000081.00000003.00000084.00000003.00000087.00000001.00000088.00000001.00000089.00000003.0000008c.00000003.0000008f.00000001.00000090.00000010.000000a0.00000002.000000a2.0000001e.000000c0.00000020.000000e0.00000010.000000f0.00000010.000002f8.00000008.000003e8.00000008.000003f8.00000008.00000400.00000054.00000454.00000004.00000458.00000028.000004d0.00000002.00000500.00000080.00000a30.00000010.00000b00.00000080.00000ca2.00000001.00000ca3.00000001.00000cf8.00000008.00001180.00000020 device-memory: 00000000.000a0000.00000400.00000100.fbffc000.00002000.fc000000.01000000.fd000000.01000000.fe000000.00b00000.feb00000.00100000.fec00000.00100000.fed00000.00000400.fed1c000.00004000.ff000000.01000000 dma-channels: 00000004 interrupts: 00000000.00000001.00000002.00000003.00000004.00000008.0000000a.0000000c.0000000d name: 'used-resources' From daniel at dgnetwork.com.br Mon Oct 7 19:28:34 2013 From: daniel at dgnetwork.com.br (=?ISO-8859-1?Q?=22Daniel_D=2E_Gon=E7alves=22?=) Date: Mon, 07 Oct 2013 16:28:34 -0300 Subject: [OmniOS-discuss] from LACP to LAG1 ?!? In-Reply-To: References: Message-ID: <52530B62.3080208@dgnetwork.com.br> Hello Fabio, LAG is short for Link Aggregation, 1 is the interface number, LAG0, LAG1, LAG2 ... The term LAG, more specifically LAGG, is commonly used in FreeBSD to name the virtual aggregate multiple physical interfaces. In my understanding LAG = LACP (802.3ad), but there is the possibility of using the protocol CISCO (FEC - Cisco ? Fast EtherChannel ?), I've never seen anything related in OmniOS. Post more information about the dladm and check if the protocol is supported 802.3ad. Regards from countryman, Daniel Em 07/10/2013 14:43, F?bio Rabelo escreveu: > Hi to all > > I do not know if this is an off-topic, if it is, just inform me ... I > will thank anyway .. > > I just received a follow-up from Netgear support in subject to a new > 10GB switcher connecting to a Solaris box ( OmniOS naturaly, 151006 ) > using LACP that is not working ( but works perfectly in another Cisco > Switcher ) . > > They asked me to change from LACP to LAG1 , and I have no idea what > they talking about ! > > Someone knows what is LAG1 ?!? > > And mostly, how to set it up ? > > > Thanks in advance ... > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > From tom.robinson at motec.com.au Mon Oct 7 23:29:41 2013 From: tom.robinson at motec.com.au (Tom Robinson) Date: Tue, 08 Oct 2013 10:29:41 +1100 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> Message-ID: <525343E5.3040401@motec.com.au> Hi Garret, Thanks for your message. The host configuration is as follows: Supermicro X9DRi-F 256GB RAM (16x Hynix 16GB ECC Reg. DDR3 1600MHz) 2 x Intel Xeon E5-2620 2 x Intel SSD 320 80GB (rpool) 4 x STEC Enterprise S842 200GB (ARC) 1 x STEC ZeusRAM 8GB 3.5" SAS SSD (ZIL) 1 x LSI SAS 9207-8i (internal drives) 1 x Intel Ethernet Server Adapter X520-DA2, Dual Port 10Gbps SFP+ Direct Attach Copper, PCI-e 2.0 5GT/s 1 2 x Mellanox ConnectX?-2 VPI 2 x LSI SAS 9207-8e (JBODS) That is connected via external SAS to two JBODS containing 28 x 1TB disks each for mirrored zfs vdevs. The output from prtconf -vp is attached as it's very long (2042 lines). Kind regards, Tom On 08/10/13 02:06, Garrett D'Amore wrote: > If you're seeing hangs like this, I would appreciate knowing the hardware configuration. Prtconf > -vp might be helpful. Presumably this is the result of one or more devices not doing the right > thing for quiesce(). > > - Garrett > > On Oct 7, 2013, at 4:34 AM, Narayan Desai > wrote: > >> This is caused by the system attempting to use fastboot on default reboot. We've disabled that >> and things seem to work properly; the following commands do the trick. (the first changes reboot >> not to use fastboot, the second causes the system to do a full reboot upon panic) >> -nld >> >> # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false >> # svcadm refresh svc:/system/boot-config:default >> # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false >> # svcadm refresh svc:/system/boot-config:default >> >> >> >> On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson > > wrote: >> >> Hi, >> >> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >> >> when I do: >> >> reboot -- -r >> >> The system hangs on the 'rebooting...' message. >> >> I've disabled Suspend and C-states in the BIOS. I had one successful 'reboot' but now it's >> hanging >> again. >> >> Anyone have any clues on how to fix this? >> >> Kind regards, >> >> -- >> >> Tom Robinson >> IT Manager/System Administrator >> >> MoTeC Pty Ltd >> >> 121 Merrindale Drive >> Croydon South >> 3136 Victoria >> Australia >> >> T: +61 3 9761 5050 >> F: +61 3 9761 5051 >> E: tom.robinson at motec.com.au >> >> >> >> _______________________________________________ >> 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: -------------- next part -------------- System Configuration: Oracle Corporation i86pc Memory size: 262116 Megabytes System Peripherals (PROM Nodes): Node 0x000001 bios-boot-device: '80' stdout: 00000000 name: 'i86pc' Node 0x000002 existing: 00dd1000.00000000.0a536001.00000000 name: 'ramdisk' Node 0x000003 acpi-namespace: '\_SB_.PCI0' compatible: 'pciex_root_complex' device_type: 'pciex' reg: 00000000.00000000.00000000 #size-cells: 00000002 #address-cells: 00000003 name: 'pci' Node 0x000004 reg: 00000000.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c00.8086.3c00.7' + 'pciex8086,3c00.8086.3c00' + 'pciex8086,3c00.7' + 'pciex8086,3c00' + 'pciexclass,060000' + 'pciexclass,0600' + 'pci8086,3c00.8086.3c00.7' + 'pci8086,3c00.8086.3c00' + 'pci8086,3c00' + 'pci8086,3c00.7' + 'pci8086,3c00' + 'pciclass,060000' + 'pciclass,0600' model: 'Host bridge' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 00008086 subsystem-id: 00003c00 unit-address: '0' class-code: 00060000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c00 name: 'pci8086,3c00' Node 0x000005 acpi-namespace: '\_SB_.PCI0.NPE1' reg: 00000800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c02.7' + 'pciex8086,3c02' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c02.7' + 'pci8086,3c02' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' bus-range: 00000001.00000001 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000000 devsel-speed: 00000000 interrupts: 00000001 unit-address: '1' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c02 name: 'pci8086,3c02' Node 0x000006 acpi-namespace: '\_SB_.PCI0.NPE2' slot-names: 00000001.746f6c53.00000037 reg: 00000900.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c03.7' + 'pciex8086,3c03' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c03.7' + 'pci8086,3c03' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 81000000.00000000.00008000.81000000.00000000.00008000.00000000.00001000.82000000.00000000.dfd00000.82000000.00000000.dfd00000.00000000.00100000.c2000000.00000000.dee00000.c2000000.00000000.dee00000.00000000.00100000 bus-range: 00000002.00000003 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000002 devsel-speed: 00000000 interrupts: 00000001 unit-address: '1,1' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c03 name: 'pci8086,3c03' Node 0x000020 assigned-addresses: 82020010.00000000.dfd20000.00000000.00020000.81020018.00000000.00008020.00000000.00000020.8202001c.00000000.dfd44000.00000000.00004000 reg: 00020000.00000000.00000000.00000000.00000000.02020010.00000000.00000000.00000000.00020000.01020018.00000000.00000000.00000000.00000020.0202001c.00000000.00000000.00000000.00004000 compatible: 'pciex8086,1521.15d9.1521.1' + 'pciex8086,1521.15d9.1521' + 'pciex8086,1521.1' + 'pciex8086,1521' + 'pciexclass,020000' + 'pciexclass,0200' + 'pci8086,1521.15d9.1521.1' + 'pci8086,1521.15d9.1521' + 'pci15d9,1521' + 'pci8086,1521.1' + 'pci8086,1521' + 'pciclass,020000' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 00001521 unit-address: '0' class-code: 00020000 revision-id: 00000001 vendor-id: 00008086 device-id: 00001521 name: 'pci15d9,1521' Node 0x000021 assigned-addresses: 82020110.00000000.dfd00000.00000000.00020000.81020118.00000000.00008000.00000000.00000020.8202011c.00000000.dfd40000.00000000.00004000 reg: 00020100.00000000.00000000.00000000.00000000.02020110.00000000.00000000.00000000.00020000.01020118.00000000.00000000.00000000.00000020.0202011c.00000000.00000000.00000000.00004000 compatible: 'pciex8086,1521.15d9.1521.1' + 'pciex8086,1521.15d9.1521' + 'pciex8086,1521.1' + 'pciex8086,1521' + 'pciexclass,020000' + 'pciexclass,0200' + 'pci8086,1521.15d9.1521.1' + 'pci8086,1521.15d9.1521' + 'pci15d9,1521' + 'pci8086,1521.1' + 'pci8086,1521' + 'pciclass,020000' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 000015d9 subsystem-id: 00001521 unit-address: '0,1' class-code: 00020000 revision-id: 00000001 vendor-id: 00008086 device-id: 00001521 name: 'pci15d9,1521' Node 0x000007 acpi-namespace: '\_SB_.PCI0.NPE3' slot-names: 00000001.746f6c53.00000032 reg: 00001000.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c04.7' + 'pciex8086,3c04' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c04.7' + 'pci8086,3c04' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 82000000.00000000.dfc00000.82000000.00000000.dfc00000.00000000.00100000.c2000000.00000000.de000000.c2000000.00000000.de000000.00000000.00800000 bus-range: 00000004.00000004 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000004 devsel-speed: 00000000 interrupts: 00000001 unit-address: '2' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c04 name: 'pci8086,3c04' Node 0x000022 assigned-addresses: 83040010.00000000.dfc00000.00000000.00100000.c3040018.00000000.de000000.00000000.00800000 reg: 00040000.00000000.00000000.00000000.00000000.03040010.00000000.00000000.00000000.00100000.43040018.00000000.00000000.00000000.00800000 compatible: 'pciex15b3,673c.15b3.36.b0' + 'pciex15b3,673c.15b3.36' + 'pciex15b3,673c.b0' + 'pciex15b3,673c' + 'pciexclass,0c0600' + 'pciexclass,0c06' + 'pci15b3,673c.15b3.36.b0' + 'pci15b3,673c.15b3.36' + 'pci15b3,36' + 'pci15b3,673c.b0' + 'pci15b3,673c' + 'pciclass,0c0600' + 'pciclass,0c06' model: 'InfiniBand' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015b3 subsystem-id: 00000036 unit-address: '0' class-code: 000c0600 revision-id: 000000b0 vendor-id: 000015b3 device-id: 0000673c name: 'pci15b3,36' Node 0x000008 acpi-namespace: '\_SB_.PCI0.NPE7' slot-names: 00000001.746f6c53.00000031 reg: 00001800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c08.7' + 'pciex8086,3c08' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c08.7' + 'pci8086,3c08' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' bus-range: 00000005.00000005 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000003 devsel-speed: 00000000 interrupts: 00000001 unit-address: '3' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c08 name: 'pci8086,3c08' Node 0x000009 acpi-namespace: '\_SB_.PCI0.NPE9' slot-names: 00000001.746f6c53.00000033 reg: 00001a00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c0a.7' + 'pciex8086,3c0a' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c0a.7' + 'pci8086,3c0a' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 81000000.00000000.00007000.81000000.00000000.00007000.00000000.00001000.82000000.00000000.df900000.82000000.00000000.df900000.00000000.00200000 bus-range: 00000006.00000006 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000006 devsel-speed: 00000000 interrupts: 00000001 unit-address: '3,2' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c0a name: 'pci8086,3c0a' Node 0x000023 assigned-addresses: 81060010.00000000.00007000.00000000.00000100.83060014.00000000.dfa40000.00000000.00010000.8306001c.00000000.dfa00000.00000000.00040000 reg: 00060000.00000000.00000000.00000000.00000000.01060010.00000000.00000000.00000000.00000100.03060014.00000000.00000000.00000000.00010000.0306001c.00000000.00000000.00000000.00040000 compatible: 'pciex1000,87.1000.3020.5' + 'pciex1000,87.1000.3020' + 'pciex1000,87.5' + 'pciex1000,87' + 'pciexclass,010700' + 'pciexclass,0107' + 'pci1000,87.1000.3020.5' + 'pci1000,87.1000.3020' + 'pci1000,3020' + 'pci1000,87.5' + 'pci1000,87' + 'pciclass,010700' + 'pciclass,0107' model: 'Serial Attached SCSI Controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 00001000 subsystem-id: 00003020 unit-address: '0' class-code: 00010700 revision-id: 00000005 vendor-id: 00001000 device-id: 00000087 name: 'pci1000,3020' Node 0x00000a assigned-addresses: 83002010.00000000.dfe1c000.00000000.00004000 reg: 00002000.00000000.00000000.00000000.00000000.03002010.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c20.15d9.628.7' + 'pciex8086,3c20.15d9.628' + 'pciex8086,3c20.7' + 'pciex8086,3c20' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c20.15d9.628.7' + 'pci8086,3c20.15d9.628' + 'pci15d9,628' + 'pci8086,3c20.7' + 'pci8086,3c20' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c20 name: 'pci15d9,628' Node 0x00000b assigned-addresses: 83002110.00000000.dfe18000.00000000.00004000 reg: 00002100.00000000.00000000.00000000.00000000.03002110.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c21.15d9.628.7' + 'pciex8086,3c21.15d9.628' + 'pciex8086,3c21.7' + 'pciex8086,3c21' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c21.15d9.628.7' + 'pci8086,3c21.15d9.628' + 'pci15d9,628' + 'pci8086,3c21.7' + 'pci8086,3c21' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,1' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c21 name: 'pci15d9,628' Node 0x00000c assigned-addresses: 83002210.00000000.dfe14000.00000000.00004000 reg: 00002200.00000000.00000000.00000000.00000000.03002210.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c22.15d9.628.7' + 'pciex8086,3c22.15d9.628' + 'pciex8086,3c22.7' + 'pciex8086,3c22' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c22.15d9.628.7' + 'pci8086,3c22.15d9.628' + 'pci15d9,628' + 'pci8086,3c22.7' + 'pci8086,3c22' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000003 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c22 name: 'pci15d9,628' Node 0x00000d assigned-addresses: 83002310.00000000.dfe10000.00000000.00004000 reg: 00002300.00000000.00000000.00000000.00000000.03002310.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c23.15d9.628.7' + 'pciex8086,3c23.15d9.628' + 'pciex8086,3c23.7' + 'pciex8086,3c23' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c23.15d9.628.7' + 'pci8086,3c23.15d9.628' + 'pci15d9,628' + 'pci8086,3c23.7' + 'pci8086,3c23' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000004 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c23 name: 'pci15d9,628' Node 0x00000e assigned-addresses: 83002410.00000000.dfe0c000.00000000.00004000 reg: 00002400.00000000.00000000.00000000.00000000.03002410.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c24.15d9.628.7' + 'pciex8086,3c24.15d9.628' + 'pciex8086,3c24.7' + 'pciex8086,3c24' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c24.15d9.628.7' + 'pci8086,3c24.15d9.628' + 'pci15d9,628' + 'pci8086,3c24.7' + 'pci8086,3c24' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c24 name: 'pci15d9,628' Node 0x00000f assigned-addresses: 83002510.00000000.dfe08000.00000000.00004000 reg: 00002500.00000000.00000000.00000000.00000000.03002510.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c25.15d9.628.7' + 'pciex8086,3c25.15d9.628' + 'pciex8086,3c25.7' + 'pciex8086,3c25' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c25.15d9.628.7' + 'pci8086,3c25.15d9.628' + 'pci15d9,628' + 'pci8086,3c25.7' + 'pci8086,3c25' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,5' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c25 name: 'pci15d9,628' Node 0x000010 assigned-addresses: 83002610.00000000.dfe04000.00000000.00004000 reg: 00002600.00000000.00000000.00000000.00000000.03002610.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c26.15d9.628.7' + 'pciex8086,3c26.15d9.628' + 'pciex8086,3c26.7' + 'pciex8086,3c26' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c26.15d9.628.7' + 'pci8086,3c26.15d9.628' + 'pci15d9,628' + 'pci8086,3c26.7' + 'pci8086,3c26' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000003 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,6' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c26 name: 'pci15d9,628' Node 0x000011 assigned-addresses: 83002710.00000000.dfe00000.00000000.00004000 reg: 00002700.00000000.00000000.00000000.00000000.03002710.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c27.15d9.628.7' + 'pciex8086,3c27.15d9.628' + 'pciex8086,3c27.7' + 'pciex8086,3c27' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c27.15d9.628.7' + 'pci8086,3c27.15d9.628' + 'pci15d9,628' + 'pci8086,3c27.7' + 'pci8086,3c27' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000004 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,7' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c27 name: 'pci15d9,628' Node 0x000012 reg: 00002800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c28.15d9.628.7' + 'pciex8086,3c28.15d9.628' + 'pciex8086,3c28.7' + 'pciex8086,3c28' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c28.15d9.628.7' + 'pci8086,3c28.15d9.628' + 'pci15d9,628' + 'pci8086,3c28.7' + 'pci8086,3c28' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '5' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c28 name: 'pci15d9,628' Node 0x000013 reg: 00002a00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c2a.15d9.628.7' + 'pciex8086,3c2a.15d9.628' + 'pciex8086,3c2a.7' + 'pciex8086,3c2a' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c2a.15d9.628.7' + 'pci8086,3c2a.15d9.628' + 'pci15d9,628' + 'pci8086,3c2a.7' + 'pci8086,3c2a' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '5,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c2a name: 'pci15d9,628' Node 0x000014 assigned-addresses: 82002c10.00000000.dfe25000.00000000.00001000 reg: 00002c00.00000000.00000000.00000000.00000000.02002c10.00000000.00000000.00000000.00001000 compatible: 'pci8086,3c2c.8086.3c2c.7' + 'pci8086,3c2c.8086.3c2c' + 'pci8086,3c2c' + 'pci8086,3c2c.7' + 'pci8086,3c2c' + 'pciclass,080020' + 'pciclass,0800' model: 'I/O(x) APIC' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00003c2c unit-address: '5,4' class-code: 00080020 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c2c name: 'pci8086,3c2c' Node 0x000017 acpi-namespace: '\_SB_.PCI0.BR33' reg: 00008800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,1d3e.6' + 'pciex8086,1d3e' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,1d3e.6' + 'pci8086,1d3e' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 81000000.00000000.00006000.81000000.00000000.00006000.00000000.00001000.82000000.00000000.dfb00000.82000000.00000000.dfb00000.00000000.00100000.c2000000.00000000.de800000.c2000000.00000000.de800000.00000000.00500000 bus-range: 00000007.00000007 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 unit-address: '11' class-code: 00060400 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d3e name: 'pci8086,1d3e' Node 0x000024 assigned-addresses: c3070010.00000000.dec7c000.00000000.00004000.c3070018.00000000.de800000.00000000.00400000.81070020.00000000.00006000.00000000.00000100 reg: 00070000.00000000.00000000.00000000.00000000.43070010.00000000.00000000.00000000.00004000.43070018.00000000.00000000.00000000.00400000.01070020.00000000.00000000.00000000.00000100 compatible: 'pciex8086,1d6b.15d9.628.6' + 'pciex8086,1d6b.15d9.628' + 'pciex8086,1d6b.6' + 'pciex8086,1d6b' + 'pciexclass,010700' + 'pciexclass,0107' + 'pci8086,1d6b.15d9.628.6' + 'pci8086,1d6b.15d9.628' + 'pci15d9,628' + 'pci8086,1d6b.6' + 'pci8086,1d6b' + 'pciclass,010700' + 'pciclass,0107' model: 'Serial Attached SCSI Controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '0' class-code: 00010700 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d6b name: 'pci15d9,628' Node 0x000025 assigned-addresses: 82070310.00000000.dfb00000.00000000.00001000.81070320.00000000.00006100.00000000.00000020 reg: 00070300.00000000.00000000.00000000.00000000.02070310.00000000.00000000.00000000.00001000.01070320.00000000.00000000.00000000.00000020 compatible: 'pciex8086,1d70.15d9.628.6' + 'pciex8086,1d70.15d9.628' + 'pciex8086,1d70.6' + 'pciex8086,1d70' + 'pciexclass,0c0500' + 'pciexclass,0c05' + 'pci8086,1d70.15d9.628.6' + 'pci8086,1d70.15d9.628' + 'pci15d9,628' + 'pci8086,1d70.6' + 'pci8086,1d70' + 'pciclass,0c0500' + 'pciclass,0c05' model: 'SMBus (System Management Bus)' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000003 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '0,3' class-code: 000c0500 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d70 name: 'pci15d9,628' Node 0x000018 acpi-namespace: '\_SB_.PCI0.HEC1' assigned-addresses: 8300b010.00000000.fed0e000.00000000.00000010 reg: 0000b000.00000000.00000000.00000000.00000000.0300b010.00000000.00000000.00000000.00000010 compatible: 'pci8086,1d3a.15d9.628.5' + 'pci8086,1d3a.15d9.628' + 'pci15d9,628' + 'pci8086,1d3a.5' + 'pci8086,1d3a' + 'pciclass,078000' + 'pciclass,0780' model: 'Communication device' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '16' class-code: 00078000 revision-id: 00000005 vendor-id: 00008086 device-id: 00001d3a name: 'pci15d9,628' Node 0x000019 acpi-namespace: '\_SB_.PCI0.HEC2' assigned-addresses: 8300b110.00000000.fed0f000.00000000.00000010 reg: 0000b100.00000000.00000000.00000000.00000000.0300b110.00000000.00000000.00000000.00000010 compatible: 'pci8086,1d3b.15d9.628.5' + 'pci8086,1d3b.15d9.628' + 'pci15d9,628' + 'pci8086,1d3b.5' + 'pci8086,1d3b' + 'pciclass,078000' + 'pciclass,0780' model: 'Communication device' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '16,1' class-code: 00078000 revision-id: 00000005 vendor-id: 00008086 device-id: 00001d3b name: 'pci15d9,628' Node 0x00001a acpi-namespace: '\_SB_.PCI0.USBE' assigned-addresses: 8200d010.00000000.dfe23000.00000000.00000400 reg: 0000d000.00000000.00000000.00000000.00000000.0200d010.00000000.00000000.00000000.00000400 compatible: 'pci8086,1d2d.15d9.628.6' + 'pci8086,1d2d.15d9.628' + 'pci15d9,628' + 'pci8086,1d2d.6' + 'pci8086,1d2d' + 'pciclass,0c0320' + 'pciclass,0c03' model: 'Universal Serial Bus EHCI compliant' power-consumption: 00000001.00000001 fast-back-to-back: devsel-speed: 00000001 interrupts: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '1a' class-code: 000c0320 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d2d name: 'pci15d9,628' Node 0x00001b acpi-namespace: '\_SB_.PCI0.EUSB' assigned-addresses: 8200e810.00000000.dfe22000.00000000.00000400 reg: 0000e800.00000000.00000000.00000000.00000000.0200e810.00000000.00000000.00000000.00000400 compatible: 'pci8086,1d26.15d9.628.6' + 'pci8086,1d26.15d9.628' + 'pci15d9,628' + 'pci8086,1d26.6' + 'pci8086,1d26' + 'pciclass,0c0320' + 'pciclass,0c03' model: 'Universal Serial Bus EHCI compliant' power-consumption: 00000001.00000001 fast-back-to-back: devsel-speed: 00000001 interrupts: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '1d' class-code: 000c0320 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d26 name: 'pci15d9,628' Node 0x00001c acpi-namespace: '\_SB_.PCI0.BR20' slot-names: 00000002.746f6c53.00003433 reg: 0000f000.00000000.00000000.00000000.00000000 compatible: 'pci8086,244e.a6' + 'pci8086,244e' + 'pciclass,060401' + 'pciclass,0604' model: 'Subtractive Decode PCI-PCI bridge' ranges: 81000000.00000000.000003b0.81000000.00000000.000003b0.00000000.0000000c.81000000.00000000.000003c0.81000000.00000000.000003c0.00000000.00000020.82000000.00000000.000a0000.82000000.00000000.000a0000.00000000.00020000.82000000.00000000.df000000.82000000.00000000.df000000.00000000.00900000.c2000000.00000000.dd000000.c2000000.00000000.dd000000.00000000.01000000 bus-range: 00000008.00000008 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pci' power-consumption: 00000001.00000001 devsel-speed: 00000000 unit-address: '1e' class-code: 00060401 revision-id: 000000a6 vendor-id: 00008086 device-id: 0000244e name: 'pci8086,244e' Node 0x000026 assigned-addresses: c2081810.00000000.dd000000.00000000.01000000.82081814.00000000.df800000.00000000.00004000.82081818.00000000.df000000.00000000.00800000.a1081800.00000000.000003b0.00000000.0000000c.a1081800.00000000.000003c0.00000000.00000020.a2081800.00000000.000a0000.00000000.00020000 reg: 00081800.00000000.00000000.00000000.00000000.42081810.00000000.00000000.00000000.01000000.02081814.00000000.00000000.00000000.00004000.02081818.00000000.00000000.00000000.00800000.a1081800.00000000.000003b0.00000000.0000000c.a1081800.00000000.000003c0.00000000.00000020.a2081800.00000000.000a0000.00000000.00020000 compatible: 'pci102b,532.15d9.628.a' + 'pci102b,532.15d9.628' + 'pci15d9,628' + 'pci102b,532.a' + 'pci102b,532' + 'pciclass,030000' + 'pciclass,0300' model: 'VGA compatible controller' power-consumption: 00000001.00000001 fast-back-to-back: devsel-speed: 00000001 interrupts: 00000001 max-latency: 00000020 min-grant: 00000010 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 device_type: 'display' unit-address: '3' class-code: 00030000 revision-id: 0000000a vendor-id: 0000102b device-id: 00000532 name: 'display' Node 0x00001d ranges: 00000001.00000000.81000000.00000000.00000000.00000060.00000001.00000061.81000000.00000000.00000061.00000003.00000001.00000065.81000000.00000000.00000065.0000009b.00000001.000002f8.81000000.00000000.000002f8.00000008.00000001.000003f8.81000000.00000000.000003f8.00000088.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000500.81000000.00000000.00000500.00000080.00000001.00000a00.81000000.00000000.00000a00.00000080.00000001.00000ca2.81000000.00000000.00000ca2.00000002.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00001180.81000000.00000000.00001180.00000020.00000000.00000400.82000000.00000000.00000400.00000100.00000000.dfffc000.82000000.00000000.dfffc000.00002000.00000000.fbffe000.82000000.00000000.fbffe000.02d42000.00000000.fed08000.82000000.00000000.fed08000.00001000.00000000.fed1c000.82000000.00000000.fed1c000.00004000.00000000.fed45000.82000000.00000000.fed45000.000bb000.00000000.ff000000.82000000.00000000.ff000000.01000000 acpi-namespace: '\_SB_.PCI0.SBRG' device_type: 'isa' reg: 0000f800.00000000.00000000.00000000.00000000 compatible: 'pci8086,1d41.15d9.628.6' + 'pci8086,1d41.15d9.628' + 'pci15d9,628' + 'pci8086,1d41.6' + 'pci8086,1d41' + 'pciclass,060100' + 'pciclass,0601' model: 'ISA bridge' power-consumption: 00000001.00000001 devsel-speed: 00000001 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '1f' class-code: 00060100 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d41 name: 'isa' Node 0x000085 compatible: 'pnpPNP,c01' reg: 00000000.fc000000.01000000.00000000.fd000000.01000000.00000000.fe000000.00b00000.00000000.feb00000.00100000.00000000.fed00400.0003fc00.00000000.fed45000.000bb000 acpi-namespace: '\_SB_.PCI0.IOH_' model: 'Motherboard' name: 'motherboard' Node 0x000086 compatible: 'pnpPNP,501' interrupts: 00000004 reg: 00000001.000003f8.00000008 acpi-namespace: '\_SB_.PCI0.SBRG.UAR1' model: '16550A-compatible COM port' name: 'asy' Node 0x000087 compatible: 'pnpPNP,501' interrupts: 00000003 reg: 00000001.000002f8.00000008 acpi-namespace: '\_SB_.PCI0.SBRG.UAR2' model: '16550A-compatible COM port' name: 'asy' Node 0x000088 compatible: 'pnpPNP,c01' reg: 00000001.00000400.00000054.00000001.00000458.00000028.00000001.00001180.00000020.00000001.00000500.00000080.00000000.fed1c000.00004000.00000000.fec00000.00100000.00000000.fed08000.00001000.00000000.ff000000.01000000 acpi-namespace: '\_SB_.PCI0.PCH_' model: 'Motherboard' name: 'motherboard' Node 0x000089 compatible: 'pnpPNP,c01' acpi-namespace: '\_SB_.PCI1.IOH1' model: 'Motherboard' name: 'motherboard' Node 0x00008a compatible: 'pnpPNP,c01' acpi-namespace: '\_SB_.RMEM' model: 'Motherboard' name: 'motherboard' Node 0x00001e acpi-namespace: '\_SB_.PCI0.SAT0' assigned-addresses: 8100fa10.00000000.00009070.00000000.00000008.8100fa14.00000000.00009060.00000000.00000004.8100fa18.00000000.00009050.00000000.00000008.8100fa1c.00000000.00009040.00000000.00000004.8100fa20.00000000.00009020.00000000.00000020.8200fa24.00000000.dfe21000.00000000.00000800 reg: 0000fa00.00000000.00000000.00000000.00000000.0100fa10.00000000.00000000.00000000.00000008.0100fa14.00000000.00000000.00000000.00000004.0100fa18.00000000.00000000.00000000.00000008.0100fa1c.00000000.00000000.00000000.00000004.0100fa20.00000000.00000000.00000000.00000020.0200fa24.00000000.00000000.00000000.00000800 compatible: 'pci8086,1d02.15d9.628.6' + 'pci8086,1d02.15d9.628' + 'pci15d9,628' + 'pci8086,1d02.6' + 'pci8086,1d02' + 'pciclass,010601' + 'pciclass,0106' model: 'SATA AHCI 1.0 Interface' power-consumption: 00000001.00000001 66mhz-capable: fast-back-to-back: devsel-speed: 00000001 interrupts: 00000002 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '1f,2' class-code: 00010601 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d02 name: 'pci15d9,628' Node 0x00001f acpi-namespace: '\_SB_.PCI0.SMB_' assigned-addresses: 8300fb10.00000000.dfe20000.00000000.00000100.8100fb20.00000000.00009000.00000000.00000020 reg: 0000fb00.00000000.00000000.00000000.00000000.0300fb10.00000000.00000000.00000000.00000100.0100fb20.00000000.00000000.00000000.00000020 compatible: 'pci8086,1d22.15d9.628.6' + 'pci8086,1d22.15d9.628' + 'pci15d9,628' + 'pci8086,1d22.6' + 'pci8086,1d22' + 'pciclass,0c0500' + 'pciclass,0c05' model: 'SMBus (System Management Bus)' power-consumption: 00000001.00000001 fast-back-to-back: devsel-speed: 00000001 interrupts: 00000003 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '1f,3' class-code: 000c0500 revision-id: 00000006 vendor-id: 00008086 device-id: 00001d22 name: 'pci15d9,628' Node 0x000015 name: 'ioapics' Node 0x000016 reg: dfe25000.00000000 device_type: 'ioapic' device-id: 00003c2c vendor-id: 00008086 name: 'ioapic' Node 0x000063 reg: fbf20000.00000000 device_type: 'ioapic' device-id: 00003c2c vendor-id: 00008086 name: 'ioapic' Node 0x000027 acpi-namespace: '\_SB_.UNC0' compatible: 'pciex_root_complex' device_type: 'pciex' reg: 00000078.00000000.00000000 #size-cells: 00000002 #address-cells: 00000003 name: 'pci' Node 0x000028 reg: 007f4000.00000000.00000000.00000000.00000000 compatible: 'pci8086,3c80.8086.0.7' + 'pci8086,3c80.8086.0' + 'pci8086,0' + 'pci8086,3c80.7' + 'pci8086,3c80' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '8' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c80 name: 'pci8086,0' Node 0x000029 reg: 007f4300.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c83.8086.0.7' + 'pciex8086,3c83.8086.0' + 'pciex8086,3c83.7' + 'pciex8086,3c83' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c83.8086.0.7' + 'pci8086,3c83.8086.0' + 'pci8086,0' + 'pci8086,3c83.7' + 'pci8086,3c83' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '8,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c83 name: 'pci8086,0' Node 0x00002a reg: 007f4400.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c84.8086.0.7' + 'pciex8086,3c84.8086.0' + 'pciex8086,3c84.7' + 'pciex8086,3c84' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c84.8086.0.7' + 'pci8086,3c84.8086.0' + 'pci8086,0' + 'pci8086,3c84.7' + 'pci8086,3c84' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '8,4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c84 name: 'pci8086,0' Node 0x00002b reg: 007f4800.00000000.00000000.00000000.00000000 compatible: 'pci8086,3c90.8086.0.7' + 'pci8086,3c90.8086.0' + 'pci8086,0' + 'pci8086,3c90.7' + 'pci8086,3c90' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '9' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c90 name: 'pci8086,0' Node 0x00002c reg: 007f4b00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c93.8086.0.7' + 'pciex8086,3c93.8086.0' + 'pciex8086,3c93.7' + 'pciex8086,3c93' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c93.8086.0.7' + 'pci8086,3c93.8086.0' + 'pci8086,0' + 'pci8086,3c93.7' + 'pci8086,3c93' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '9,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c93 name: 'pci8086,0' Node 0x00002d reg: 007f4c00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c94.8086.0.7' + 'pciex8086,3c94.8086.0' + 'pciex8086,3c94.7' + 'pciex8086,3c94' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c94.8086.0.7' + 'pci8086,3c94.8086.0' + 'pci8086,0' + 'pci8086,3c94.7' + 'pci8086,3c94' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '9,4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c94 name: 'pci8086,0' Node 0x00002e reg: 007f5000.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cc0.8086.0.7' + 'pci8086,3cc0.8086.0' + 'pci8086,0' + 'pci8086,3cc0.7' + 'pci8086,3cc0' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'a' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cc0 name: 'pci8086,0' Node 0x00002f reg: 007f5100.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cc1.8086.0.7' + 'pci8086,3cc1.8086.0' + 'pci8086,0' + 'pci8086,3cc1.7' + 'pci8086,3cc1' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'a,1' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cc1 name: 'pci8086,0' Node 0x000030 reg: 007f5200.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cc2.8086.0.7' + 'pci8086,3cc2.8086.0' + 'pci8086,0' + 'pci8086,3cc2.7' + 'pci8086,3cc2' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'a,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cc2 name: 'pci8086,0' Node 0x000031 reg: 007f5300.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cd0.8086.0.7' + 'pci8086,3cd0.8086.0' + 'pci8086,0' + 'pci8086,3cd0.7' + 'pci8086,3cd0' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'a,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cd0 name: 'pci8086,0' Node 0x000032 reg: 007f5800.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce0.8086.0.7' + 'pci8086,3ce0.8086.0' + 'pci8086,0' + 'pci8086,3ce0.7' + 'pci8086,3ce0' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'b' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce0 name: 'pci8086,0' Node 0x000033 reg: 007f5b00.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce3.8086.0.7' + 'pci8086,3ce3.8086.0' + 'pci8086,0' + 'pci8086,3ce3.7' + 'pci8086,3ce3' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'b,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce3 name: 'pci8086,0' Node 0x000034 reg: 007f6000.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce8.8086.0.7' + 'pci8086,3ce8.8086.0' + 'pci8086,0' + 'pci8086,3ce8.7' + 'pci8086,3ce8' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'c' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce8 name: 'pci8086,0' Node 0x000035 reg: 007f6100.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce8.8086.0.7' + 'pci8086,3ce8.8086.0' + 'pci8086,0' + 'pci8086,3ce8.7' + 'pci8086,3ce8' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'c,1' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce8 name: 'pci8086,0' Node 0x000036 reg: 007f6200.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce8.8086.0.7' + 'pci8086,3ce8.8086.0' + 'pci8086,0' + 'pci8086,3ce8.7' + 'pci8086,3ce8' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'c,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce8 name: 'pci8086,0' Node 0x000037 reg: 007f6600.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cf4.8086.0.7' + 'pci8086,3cf4.8086.0' + 'pci8086,0' + 'pci8086,3cf4.7' + 'pci8086,3cf4' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'c,6' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cf4 name: 'pci8086,0' Node 0x000038 reg: 007f6700.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cf6.8086.0.7' + 'pci8086,3cf6.8086.0' + 'pci8086,0' + 'pci8086,3cf6.7' + 'pci8086,3cf6' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'c,7' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cf6 name: 'pci8086,0' Node 0x000039 reg: 007f6800.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce8.8086.0.7' + 'pci8086,3ce8.8086.0' + 'pci8086,0' + 'pci8086,3ce8.7' + 'pci8086,3ce8' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'd' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce8 name: 'pci8086,0' Node 0x00003a reg: 007f6900.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce8.8086.0.7' + 'pci8086,3ce8.8086.0' + 'pci8086,0' + 'pci8086,3ce8.7' + 'pci8086,3ce8' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'd,1' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce8 name: 'pci8086,0' Node 0x00003b reg: 007f6a00.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce8.8086.0.7' + 'pci8086,3ce8.8086.0' + 'pci8086,0' + 'pci8086,3ce8.7' + 'pci8086,3ce8' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'd,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce8 name: 'pci8086,0' Node 0x00003c reg: 007f6e00.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cf5.8086.0.7' + 'pci8086,3cf5.8086.0' + 'pci8086,0' + 'pci8086,3cf5.7' + 'pci8086,3cf5' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'd,6' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cf5 name: 'pci8086,0' Node 0x00003d reg: 007f7000.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ca0.7' + 'pci8086,3ca0' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 unit-address: 'e' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ca0 name: 'pci8086,3ca0' Node 0x00003e reg: 007f7100.00000000.00000000.00000000.00000000 compatible: 'pci8086,3c46.15d9.628.7' + 'pci8086,3c46.15d9.628' + 'pci15d9,628' + 'pci8086,3c46.7' + 'pci8086,3c46' + 'pciclass,110100' + 'pciclass,1101' model: 'Performance counters' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: 'e,1' class-code: 00110100 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c46 name: 'pci15d9,628' Node 0x00003f reg: 007f7800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3ca8.8086.0.7' + 'pciex8086,3ca8.8086.0' + 'pciex8086,3ca8.7' + 'pciex8086,3ca8' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3ca8.8086.0.7' + 'pci8086,3ca8.8086.0' + 'pci8086,0' + 'pci8086,3ca8.7' + 'pci8086,3ca8' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'f' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ca8 name: 'pci8086,0' Node 0x000040 reg: 007f7900.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c71.8086.0.7' + 'pciex8086,3c71.8086.0' + 'pciex8086,3c71.7' + 'pciex8086,3c71' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c71.8086.0.7' + 'pci8086,3c71.8086.0' + 'pci8086,0' + 'pci8086,3c71.7' + 'pci8086,3c71' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'f,1' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c71 name: 'pci8086,0' Node 0x000041 reg: 007f7a00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3caa.8086.0.7' + 'pciex8086,3caa.8086.0' + 'pciex8086,3caa.7' + 'pciex8086,3caa' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3caa.8086.0.7' + 'pci8086,3caa.8086.0' + 'pci8086,0' + 'pci8086,3caa.7' + 'pci8086,3caa' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'f,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003caa name: 'pci8086,0' Node 0x000042 reg: 007f7b00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cab.8086.0.7' + 'pciex8086,3cab.8086.0' + 'pciex8086,3cab.7' + 'pciex8086,3cab' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cab.8086.0.7' + 'pci8086,3cab.8086.0' + 'pci8086,0' + 'pci8086,3cab.7' + 'pci8086,3cab' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'f,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cab name: 'pci8086,0' Node 0x000043 reg: 007f7c00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cac.8086.0.7' + 'pciex8086,3cac.8086.0' + 'pciex8086,3cac.7' + 'pciex8086,3cac' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cac.8086.0.7' + 'pci8086,3cac.8086.0' + 'pci8086,0' + 'pci8086,3cac.7' + 'pci8086,3cac' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'f,4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cac name: 'pci8086,0' Node 0x000044 reg: 007f7d00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cad.8086.0.7' + 'pciex8086,3cad.8086.0' + 'pciex8086,3cad.7' + 'pciex8086,3cad' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cad.8086.0.7' + 'pci8086,3cad.8086.0' + 'pci8086,0' + 'pci8086,3cad.7' + 'pci8086,3cad' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'f,5' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cad name: 'pci8086,0' Node 0x000045 reg: 007f7e00.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cae.8086.0.7' + 'pci8086,3cae.8086.0' + 'pci8086,0' + 'pci8086,3cae.7' + 'pci8086,3cae' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: 'f,6' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cae name: 'pci8086,0' Node 0x000046 reg: 007f8000.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cb0.8086.0.7' + 'pciex8086,3cb0.8086.0' + 'pciex8086,3cb0.7' + 'pciex8086,3cb0' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cb0.8086.0.7' + 'pci8086,3cb0.8086.0' + 'pci8086,0' + 'pci8086,3cb0.7' + 'pci8086,3cb0' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '10' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb0 name: 'pci8086,0' Node 0x000047 reg: 007f8100.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cb1.8086.0.7' + 'pciex8086,3cb1.8086.0' + 'pciex8086,3cb1.7' + 'pciex8086,3cb1' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cb1.8086.0.7' + 'pci8086,3cb1.8086.0' + 'pci8086,0' + 'pci8086,3cb1.7' + 'pci8086,3cb1' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '10,1' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb1 name: 'pci8086,0' Node 0x000048 reg: 007f8200.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cb2.8086.0.7' + 'pciex8086,3cb2.8086.0' + 'pciex8086,3cb2.7' + 'pciex8086,3cb2' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cb2.8086.0.7' + 'pci8086,3cb2.8086.0' + 'pci8086,0' + 'pci8086,3cb2.7' + 'pci8086,3cb2' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '10,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb2 name: 'pci8086,0' Node 0x000049 reg: 007f8300.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cb3.8086.0.7' + 'pciex8086,3cb3.8086.0' + 'pciex8086,3cb3.7' + 'pciex8086,3cb3' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cb3.8086.0.7' + 'pci8086,3cb3.8086.0' + 'pci8086,0' + 'pci8086,3cb3.7' + 'pci8086,3cb3' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '10,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb3 name: 'pci8086,0' Node 0x00004a reg: 007f8400.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cb4.8086.0.7' + 'pciex8086,3cb4.8086.0' + 'pciex8086,3cb4.7' + 'pciex8086,3cb4' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cb4.8086.0.7' + 'pci8086,3cb4.8086.0' + 'pci8086,0' + 'pci8086,3cb4.7' + 'pci8086,3cb4' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '10,4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb4 name: 'pci8086,0' Node 0x00004b reg: 007f8500.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cb5.8086.0.7' + 'pciex8086,3cb5.8086.0' + 'pciex8086,3cb5.7' + 'pciex8086,3cb5' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cb5.8086.0.7' + 'pci8086,3cb5.8086.0' + 'pci8086,0' + 'pci8086,3cb5.7' + 'pci8086,3cb5' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '10,5' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb5 name: 'pci8086,0' Node 0x00004c reg: 007f8600.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cb6.8086.0.7' + 'pciex8086,3cb6.8086.0' + 'pciex8086,3cb6.7' + 'pciex8086,3cb6' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cb6.8086.0.7' + 'pci8086,3cb6.8086.0' + 'pci8086,0' + 'pci8086,3cb6.7' + 'pci8086,3cb6' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '10,6' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb6 name: 'pci8086,0' Node 0x00004d reg: 007f8700.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3cb7.8086.0.7' + 'pciex8086,3cb7.8086.0' + 'pciex8086,3cb7.7' + 'pciex8086,3cb7' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3cb7.8086.0.7' + 'pci8086,3cb7.8086.0' + 'pci8086,0' + 'pci8086,3cb7.7' + 'pci8086,3cb7' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '10,7' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb7 name: 'pci8086,0' Node 0x00004e reg: 007f8800.00000000.00000000.00000000.00000000 compatible: 'pci8086,3cb8.8086.0.7' + 'pci8086,3cb8.8086.0' + 'pci8086,0' + 'pci8086,3cb8.7' + 'pci8086,3cb8' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '11' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003cb8 name: 'pci8086,0' Node 0x00004f reg: 007f9800.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce4.8086.0.7' + 'pci8086,3ce4.8086.0' + 'pci8086,0' + 'pci8086,3ce4.7' + 'pci8086,3ce4' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '13' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce4 name: 'pci8086,0' Node 0x000050 reg: 007f9900.00000000.00000000.00000000.00000000 compatible: 'pci8086,3c43.15d9.628.7' + 'pci8086,3c43.15d9.628' + 'pci15d9,628' + 'pci8086,3c43.7' + 'pci8086,3c43' + 'pciclass,110100' + 'pciclass,1101' model: 'Performance counters' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '13,1' class-code: 00110100 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c43 name: 'pci15d9,628' Node 0x000051 reg: 007f9c00.00000000.00000000.00000000.00000000 compatible: 'pci8086,3ce6.15d9.628.7' + 'pci8086,3ce6.15d9.628' + 'pci15d9,628' + 'pci8086,3ce6.7' + 'pci8086,3ce6' + 'pciclass,110100' + 'pciclass,1101' model: 'Performance counters' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '13,4' class-code: 00110100 revision-id: 00000007 vendor-id: 00008086 device-id: 00003ce6 name: 'pci15d9,628' Node 0x000052 reg: 007f9d00.00000000.00000000.00000000.00000000 compatible: 'pci8086,3c44.15d9.628.7' + 'pci8086,3c44.15d9.628' + 'pci15d9,628' + 'pci8086,3c44.7' + 'pci8086,3c44' + 'pciclass,110100' + 'pciclass,1101' model: 'Performance counters' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '13,5' class-code: 00110100 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c44 name: 'pci15d9,628' Node 0x000053 reg: 007f9e00.00000000.00000000.00000000.00000000 compatible: 'pci8086,3c45.8086.0.7' + 'pci8086,3c45.8086.0' + 'pci8086,0' + 'pci8086,3c45.7' + 'pci8086,3c45' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00000000 unit-address: '13,6' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c45 name: 'pci8086,0' Node 0x000054 acpi-namespace: '\_SB_.PCI1' compatible: 'pciex_root_complex' device_type: 'pciex' reg: 00000079.00000000.00000000 #size-cells: 00000002 #address-cells: 00000003 name: 'pci' Node 0x000055 acpi-namespace: '\_SB_.PCI1.NPE1' slot-names: 00000001.746f6c53.00000035 reg: 00800800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c02.7' + 'pciex8086,3c02' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c02.7' + 'pci8086,3c02' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 81000000.00000000.0000f000.81000000.00000000.0000f000.00000000.00001000.82000000.00000000.fbd00000.82000000.00000000.fbd00000.00000000.00200000 bus-range: 00000081.00000081 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000000 devsel-speed: 00000000 interrupts: 00000001 unit-address: '1' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c02 name: 'pci8086,3c02' Node 0x000064 assigned-addresses: 81810010.00000000.0000f000.00000000.00000100.83810014.00000000.fbe40000.00000000.00010000.8381001c.00000000.fbe00000.00000000.00040000 reg: 00810000.00000000.00000000.00000000.00000000.01810010.00000000.00000000.00000000.00000100.03810014.00000000.00000000.00000000.00010000.0381001c.00000000.00000000.00000000.00040000 compatible: 'pciex1000,87.1000.3040.5' + 'pciex1000,87.1000.3040' + 'pciex1000,87.5' + 'pciex1000,87' + 'pciexclass,010700' + 'pciexclass,0107' + 'pci1000,87.1000.3040.5' + 'pci1000,87.1000.3040' + 'pci1000,3040' + 'pci1000,87.5' + 'pci1000,87' + 'pciclass,010700' + 'pciclass,0107' model: 'Serial Attached SCSI Controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 00001000 subsystem-id: 00003040 unit-address: '0' class-code: 00010700 revision-id: 00000005 vendor-id: 00001000 device-id: 00000087 name: 'pci1000,3040' Node 0x000056 acpi-namespace: '\_SB_.PCI1.NPE3' slot-names: 00000001.746f6c53.00000034 reg: 00801000.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c04.7' + 'pciex8086,3c04' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c04.7' + 'pci8086,3c04' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 81000000.00000000.0000e000.81000000.00000000.0000e000.00000000.00001000.82000000.00000000.fb700000.82000000.00000000.fb700000.00000000.00400000.c2000000.00000000.fb500000.c2000000.00000000.fb500000.00000000.00200000 bus-range: 00000082.00000083 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000000 devsel-speed: 00000000 interrupts: 00000001 unit-address: '2' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c04 name: 'pci8086,3c04' Node 0x000065 assigned-addresses: c3820010.00000000.fb580000.00000000.00080000.81820018.00000000.0000e020.00000000.00000020.c3820020.00000000.fb604000.00000000.00004000 reg: 00820000.00000000.00000000.00000000.00000000.43820010.00000000.00000000.00000000.00080000.01820018.00000000.00000000.00000000.00000020.43820020.00000000.00000000.00000000.00004000 compatible: 'pciex8086,10fb.8086.3.1' + 'pciex8086,10fb.8086.3' + 'pciex8086,10fb.1' + 'pciex8086,10fb' + 'pciexclass,020000' + 'pciexclass,0200' + 'pci8086,10fb.8086.3.1' + 'pci8086,10fb.8086.3' + 'pci8086,3' + 'pci8086,10fb.1' + 'pci8086,10fb' + 'pciclass,020000' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 00008086 subsystem-id: 00000003 unit-address: '0' class-code: 00020000 revision-id: 00000001 vendor-id: 00008086 device-id: 000010fb name: 'pci8086,3' Node 0x000066 assigned-addresses: c3820110.00000000.fb500000.00000000.00080000.81820118.00000000.0000e000.00000000.00000020.c3820120.00000000.fb600000.00000000.00004000 reg: 00820100.00000000.00000000.00000000.00000000.43820110.00000000.00000000.00000000.00080000.01820118.00000000.00000000.00000000.00000020.43820120.00000000.00000000.00000000.00004000 compatible: 'pciex8086,10fb.8086.3.1' + 'pciex8086,10fb.8086.3' + 'pciex8086,10fb.1' + 'pciex8086,10fb' + 'pciexclass,020000' + 'pciexclass,0200' + 'pci8086,10fb.8086.3.1' + 'pci8086,10fb.8086.3' + 'pci8086,3' + 'pci8086,10fb.1' + 'pci8086,10fb' + 'pciclass,020000' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 00008086 subsystem-id: 00000003 unit-address: '0,1' class-code: 00020000 revision-id: 00000001 vendor-id: 00008086 device-id: 000010fb name: 'pci8086,3' Node 0x000057 acpi-namespace: '\_SB_.PCI1.NPE7' slot-names: 00000001.746f6c53.00000036 reg: 00801800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c08.7' + 'pciex8086,3c08' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3c08.7' + 'pci8086,3c08' + 'pciclass,060400' + 'pciclass,0604' model: 'PCI-PCI bridge' ranges: 81000000.00000000.0000d000.81000000.00000000.0000d000.00000000.00001000.82000000.00000000.fbb00000.82000000.00000000.fbb00000.00000000.00200000 bus-range: 00000084.00000084 #size-cells: 00000002 #address-cells: 00000003 device_type: 'pciex' power-consumption: 00000001.00000001 physical-slot#: 00000000 devsel-speed: 00000000 interrupts: 00000001 unit-address: '3' class-code: 00060400 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c08 name: 'pci8086,3c08' Node 0x000067 assigned-addresses: 81840010.00000000.0000d000.00000000.00000100.83840014.00000000.fbc40000.00000000.00010000.8384001c.00000000.fbc00000.00000000.00040000 reg: 00840000.00000000.00000000.00000000.00000000.01840010.00000000.00000000.00000000.00000100.03840014.00000000.00000000.00000000.00010000.0384001c.00000000.00000000.00000000.00040000 compatible: 'pciex1000,87.1000.3040.5' + 'pciex1000,87.1000.3040' + 'pciex1000,87.5' + 'pciex1000,87' + 'pciexclass,010700' + 'pciexclass,0107' + 'pci1000,87.1000.3040.5' + 'pci1000,87.1000.3040' + 'pci1000,3040' + 'pci1000,87.5' + 'pci1000,87' + 'pciclass,010700' + 'pciclass,0107' model: 'Serial Attached SCSI Controller' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 00001000 subsystem-id: 00003040 unit-address: '0' class-code: 00010700 revision-id: 00000005 vendor-id: 00001000 device-id: 00000087 name: 'pci1000,3040' Node 0x000058 assigned-addresses: 83802010.00000000.fbf1c000.00000000.00004000 reg: 00802000.00000000.00000000.00000000.00000000.03802010.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c20.15d9.628.7' + 'pciex8086,3c20.15d9.628' + 'pciex8086,3c20.7' + 'pciex8086,3c20' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c20.15d9.628.7' + 'pci8086,3c20.15d9.628' + 'pci15d9,628' + 'pci8086,3c20.7' + 'pci8086,3c20' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c20 name: 'pci15d9,628' Node 0x000059 assigned-addresses: 83802110.00000000.fbf18000.00000000.00004000 reg: 00802100.00000000.00000000.00000000.00000000.03802110.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c21.15d9.628.7' + 'pciex8086,3c21.15d9.628' + 'pciex8086,3c21.7' + 'pciex8086,3c21' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c21.15d9.628.7' + 'pci8086,3c21.15d9.628' + 'pci15d9,628' + 'pci8086,3c21.7' + 'pci8086,3c21' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,1' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c21 name: 'pci15d9,628' Node 0x00005a assigned-addresses: 83802210.00000000.fbf14000.00000000.00004000 reg: 00802200.00000000.00000000.00000000.00000000.03802210.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c22.15d9.628.7' + 'pciex8086,3c22.15d9.628' + 'pciex8086,3c22.7' + 'pciex8086,3c22' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c22.15d9.628.7' + 'pci8086,3c22.15d9.628' + 'pci15d9,628' + 'pci8086,3c22.7' + 'pci8086,3c22' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000003 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c22 name: 'pci15d9,628' Node 0x00005b assigned-addresses: 83802310.00000000.fbf10000.00000000.00004000 reg: 00802300.00000000.00000000.00000000.00000000.03802310.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c23.15d9.628.7' + 'pciex8086,3c23.15d9.628' + 'pciex8086,3c23.7' + 'pciex8086,3c23' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c23.15d9.628.7' + 'pci8086,3c23.15d9.628' + 'pci15d9,628' + 'pci8086,3c23.7' + 'pci8086,3c23' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000004 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,3' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c23 name: 'pci15d9,628' Node 0x00005c assigned-addresses: 83802410.00000000.fbf0c000.00000000.00004000 reg: 00802400.00000000.00000000.00000000.00000000.03802410.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c24.15d9.628.7' + 'pciex8086,3c24.15d9.628' + 'pciex8086,3c24.7' + 'pciex8086,3c24' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c24.15d9.628.7' + 'pci8086,3c24.15d9.628' + 'pci15d9,628' + 'pci8086,3c24.7' + 'pci8086,3c24' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000001 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,4' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c24 name: 'pci15d9,628' Node 0x00005d assigned-addresses: 83802510.00000000.fbf08000.00000000.00004000 reg: 00802500.00000000.00000000.00000000.00000000.03802510.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c25.15d9.628.7' + 'pciex8086,3c25.15d9.628' + 'pciex8086,3c25.7' + 'pciex8086,3c25' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c25.15d9.628.7' + 'pci8086,3c25.15d9.628' + 'pci15d9,628' + 'pci8086,3c25.7' + 'pci8086,3c25' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000002 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,5' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c25 name: 'pci15d9,628' Node 0x00005e assigned-addresses: 83802610.00000000.fbf04000.00000000.00004000 reg: 00802600.00000000.00000000.00000000.00000000.03802610.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c26.15d9.628.7' + 'pciex8086,3c26.15d9.628' + 'pciex8086,3c26.7' + 'pciex8086,3c26' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c26.15d9.628.7' + 'pci8086,3c26.15d9.628' + 'pci15d9,628' + 'pci8086,3c26.7' + 'pci8086,3c26' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000003 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,6' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c26 name: 'pci15d9,628' Node 0x00005f assigned-addresses: 83802710.00000000.fbf00000.00000000.00004000 reg: 00802700.00000000.00000000.00000000.00000000.03802710.00000000.00000000.00000000.00004000 compatible: 'pciex8086,3c27.15d9.628.7' + 'pciex8086,3c27.15d9.628' + 'pciex8086,3c27.7' + 'pciex8086,3c27' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c27.15d9.628.7' + 'pci8086,3c27.15d9.628' + 'pci15d9,628' + 'pci8086,3c27.7' + 'pci8086,3c27' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 interrupts: 00000004 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '4,7' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c27 name: 'pci15d9,628' Node 0x000060 reg: 00802800.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c28.15d9.628.7' + 'pciex8086,3c28.15d9.628' + 'pciex8086,3c28.7' + 'pciex8086,3c28' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c28.15d9.628.7' + 'pci8086,3c28.15d9.628' + 'pci15d9,628' + 'pci8086,3c28.7' + 'pci8086,3c28' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '5' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c28 name: 'pci15d9,628' Node 0x000061 reg: 00802a00.00000000.00000000.00000000.00000000 compatible: 'pciex8086,3c2a.15d9.628.7' + 'pciex8086,3c2a.15d9.628' + 'pciex8086,3c2a.7' + 'pciex8086,3c2a' + 'pciexclass,088000' + 'pciexclass,0880' + 'pci8086,3c2a.15d9.628.7' + 'pci8086,3c2a.15d9.628' + 'pci15d9,628' + 'pci8086,3c2a.7' + 'pci8086,3c2a' + 'pciclass,088000' + 'pciclass,0880' model: 'System peripheral' power-consumption: 00000001.00000001 devsel-speed: 00000000 subsystem-vendor-id: 000015d9 subsystem-id: 00000628 unit-address: '5,2' class-code: 00088000 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c2a name: 'pci15d9,628' Node 0x000062 assigned-addresses: 82802c10.00000000.fbf20000.00000000.00001000 reg: 00802c00.00000000.00000000.00000000.00000000.02802c10.00000000.00000000.00000000.00001000 compatible: 'pci8086,3c2c.8086.3c2c.7' + 'pci8086,3c2c.8086.3c2c' + 'pci8086,3c2c' + 'pci8086,3c2c.7' + 'pci8086,3c2c' + 'pciclass,080020' + 'pciclass,0800' model: 'I/O(x) APIC' power-consumption: 00000001.00000001 devsel-speed: 00000000 max-latency: 00000000 min-grant: 00000000 subsystem-vendor-id: 00008086 subsystem-id: 00003c2c unit-address: '5,4' class-code: 00080020 revision-id: 00000007 vendor-id: 00008086 device-id: 00003c2c name: 'pci8086,3c2c' Node 0x000068 device_type: 'acpirootnex' compatible: 'SOLA0001' + 'acpirootnex' + 'SOLA0002' + 'acpivirtnex' acpi-namespace: '\' name: 'fw' Node 0x000069 unit-address: '0' compatible: 'acpidevice' + 'SOLA0002' + 'acpivirtnex' acpi-namespace: '\_SB_' device_type: 'acpidevice' name: 'sb' Node 0x00006a unit-address: '0' acpi-uid: 'CPUSCK0' compatible: 'ACPI0004' + 'acpicontainer' + 'SOLA0002' + 'acpivirtnex' acpi-namespace: '\_SB_.SCK0' device_type: 'acpicontainer' name: 'socket' Node 0x00006b unit-address: '0' acpi-uid: 'PCI0-CP00' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000000 acpi-processor-id: 00000000 acpi-namespace: '\_SB_.SCK0.CP00' device_type: 'acpicpu' name: 'cpu' Node 0x00006c unit-address: '1' acpi-uid: 'PCI0-CP01' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000001 acpi-processor-id: 00000001 acpi-namespace: '\_SB_.SCK0.CP01' device_type: 'acpicpu' name: 'cpu' Node 0x00006d unit-address: '2' acpi-uid: 'PCI0-CP02' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000002 acpi-processor-id: 00000002 acpi-namespace: '\_SB_.SCK0.CP02' device_type: 'acpicpu' name: 'cpu' Node 0x00006e unit-address: '3' acpi-uid: 'PCI0-CP03' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000003 acpi-processor-id: 00000003 acpi-namespace: '\_SB_.SCK0.CP03' device_type: 'acpicpu' name: 'cpu' Node 0x00006f unit-address: '4' acpi-uid: 'PCI0-CP04' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000004 acpi-processor-id: 00000004 acpi-namespace: '\_SB_.SCK0.CP04' device_type: 'acpicpu' name: 'cpu' Node 0x000070 unit-address: '5' acpi-uid: 'PCI0-CP05' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000005 acpi-processor-id: 00000005 acpi-namespace: '\_SB_.SCK0.CP05' device_type: 'acpicpu' name: 'cpu' Node 0x000071 unit-address: '6' acpi-uid: 'PCI0-CP06' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000006 acpi-processor-id: 00000006 acpi-namespace: '\_SB_.SCK0.CP06' device_type: 'acpicpu' name: 'cpu' Node 0x000072 unit-address: '7' acpi-uid: 'PCI0-CP07' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000007 acpi-processor-id: 00000007 acpi-namespace: '\_SB_.SCK0.CP07' device_type: 'acpicpu' name: 'cpu' Node 0x000073 unit-address: '8' acpi-uid: 'PCI0-CP08' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000008 acpi-processor-id: 00000008 acpi-namespace: '\_SB_.SCK0.CP08' device_type: 'acpicpu' name: 'cpu' Node 0x000074 unit-address: '9' acpi-uid: 'PCI0-CP09' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 00000009 acpi-processor-id: 00000009 acpi-namespace: '\_SB_.SCK0.CP09' device_type: 'acpicpu' name: 'cpu' Node 0x000075 unit-address: '10' acpi-uid: 'PCI0-CP0A' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 0000000a acpi-processor-id: 0000000a acpi-namespace: '\_SB_.SCK0.CP0A' device_type: 'acpicpu' name: 'cpu' Node 0x000076 unit-address: '11' acpi-uid: 'PCI0-CP0B' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000000 apic-id: 0000000b acpi-processor-id: 0000000b acpi-namespace: '\_SB_.SCK0.CP0B' device_type: 'acpicpu' name: 'cpu' Node 0x000077 unit-address: '1' acpi-uid: 'CPUSCK1' compatible: 'ACPI0004' + 'acpicontainer' + 'SOLA0002' + 'acpivirtnex' acpi-namespace: '\_SB_.SCK1' device_type: 'acpicontainer' name: 'socket' Node 0x000078 unit-address: '12' acpi-uid: 'PCI1-CP10' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000020 acpi-processor-id: 0000000c acpi-namespace: '\_SB_.SCK1.CP10' device_type: 'acpicpu' name: 'cpu' Node 0x000079 unit-address: '13' acpi-uid: 'PCI1-CP11' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000021 acpi-processor-id: 0000000d acpi-namespace: '\_SB_.SCK1.CP11' device_type: 'acpicpu' name: 'cpu' Node 0x00007a unit-address: '14' acpi-uid: 'PCI1-CP12' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000022 acpi-processor-id: 0000000e acpi-namespace: '\_SB_.SCK1.CP12' device_type: 'acpicpu' name: 'cpu' Node 0x00007b unit-address: '15' acpi-uid: 'PCI1-CP13' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000023 acpi-processor-id: 0000000f acpi-namespace: '\_SB_.SCK1.CP13' device_type: 'acpicpu' name: 'cpu' Node 0x00007c unit-address: '16' acpi-uid: 'PCI1-CP14' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000024 acpi-processor-id: 00000010 acpi-namespace: '\_SB_.SCK1.CP14' device_type: 'acpicpu' name: 'cpu' Node 0x00007d unit-address: '17' acpi-uid: 'PCI1-CP15' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000025 acpi-processor-id: 00000011 acpi-namespace: '\_SB_.SCK1.CP15' device_type: 'acpicpu' name: 'cpu' Node 0x00007e unit-address: '18' acpi-uid: 'PCI1-CP16' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000026 acpi-processor-id: 00000012 acpi-namespace: '\_SB_.SCK1.CP16' device_type: 'acpicpu' name: 'cpu' Node 0x00007f unit-address: '19' acpi-uid: 'PCI1-CP17' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000027 acpi-processor-id: 00000013 acpi-namespace: '\_SB_.SCK1.CP17' device_type: 'acpicpu' name: 'cpu' Node 0x000080 unit-address: '20' acpi-uid: 'PCI1-CP18' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000028 acpi-processor-id: 00000014 acpi-namespace: '\_SB_.SCK1.CP18' device_type: 'acpicpu' name: 'cpu' Node 0x000081 unit-address: '21' acpi-uid: 'PCI1-CP19' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 00000029 acpi-processor-id: 00000015 acpi-namespace: '\_SB_.SCK1.CP19' device_type: 'acpicpu' name: 'cpu' Node 0x000082 unit-address: '22' acpi-uid: 'PCI1-CP1A' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 0000002a acpi-processor-id: 00000016 acpi-namespace: '\_SB_.SCK1.CP1A' device_type: 'acpicpu' name: 'cpu' Node 0x000083 unit-address: '23' acpi-uid: 'PCI1-CP1B' compatible: 'ACPI0007' + 'SOLA0004' + 'acpicpu' + 'cpu' proximity-id: 00000001 apic-id: 0000002b acpi-processor-id: 00000017 acpi-namespace: '\_SB_.SCK1.CP1B' device_type: 'acpicpu' name: 'cpu' Node 0x000084 io-space: 00000000.00000010.00000010.00000010.00000020.00000002.00000022.0000001e.00000040.00000004.00000044.0000001c.00000061.00000001.00000062.00000002.00000065.0000000b.00000070.00000002.00000072.0000000e.00000080.00000001.00000081.00000003.00000084.00000003.00000087.00000001.00000088.00000001.00000089.00000003.0000008c.00000003.0000008f.00000001.00000090.00000010.000000a0.00000002.000000a2.0000001e.000000c0.00000020.000000e0.00000010.000000f0.00000010.000002f8.00000008.000003f8.00000008.00000400.00000054.00000454.00000004.00000458.00000028.000004d0.00000002.00000500.00000080.00000a00.00000080.00000ca2.00000001.00000ca3.00000001.00000cf8.00000008.00001180.00000020 device-memory: 00000400.00000100.dfffc000.00002000.fbffe000.00002000.fc000000.01000000.fd000000.01000000.fe000000.00b00000.feb00000.00100000.fec00000.00100000.fed00000.00000400.fed00400.0003fc00.fed08000.00001000.fed1c000.00004000.fed45000.000bb000.ff000000.01000000 dma-channels: 00000004 interrupts: 00000000.00000002.00000003.00000004.00000008.0000000d name: 'used-resources' -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature URL: From skiselkov.ml at gmail.com Mon Oct 7 23:37:27 2013 From: skiselkov.ml at gmail.com (Saso Kiselkov) Date: Tue, 08 Oct 2013 00:37:27 +0100 Subject: [OmniOS-discuss] from LACP to LAG1 ?!? In-Reply-To: <52530B62.3080208@dgnetwork.com.br> References: <52530B62.3080208@dgnetwork.com.br> Message-ID: <525345B7.7080307@gmail.com> On 10/7/13 8:28 PM, "Daniel D. Gon?alves" wrote: > Hello Fabio, > > LAG is short for Link Aggregation, 1 is the interface number, LAG0, > LAG1, LAG2 ... > The term LAG, more specifically LAGG, is commonly used in FreeBSD to > name the virtual aggregate multiple physical interfaces. > In my understanding LAG = LACP (802.3ad), but there is the possibility > of using the protocol CISCO (FEC - Cisco ? Fast EtherChannel ?), I've > never seen anything related in OmniOS. > > Post more information about the dladm and check if the protocol is > supported 802.3ad. Daniel, just as a quick note, OmniOS (and Illumos for that matter) only supports 802.3ad LACP. There's no support for EtherChannel that I'm aware of. See http://illumos.org/man/1M/dladm and the section on the "dladm create-aggr" subcommand: dladm create-aggr [-t] [-R root-dir] [-P policy] [-L mode] [-T time] [-u address] -l ether-link1 [-l ether-link2...] aggr-link Combine a set of links into a single IEEE 802.3ad link aggregation named aggr-link. The use of an integer key to generate a link name for the aggregation is also sup- ported for backward compatibility. Many of the *-aggr subcommands below also support the use of a key to refer to a given aggregation, but use of the aggregation link name is preferred. See the NOTES section for more infor- mation on keys. Cheers, -- Saso From henson at acm.org Tue Oct 8 00:22:00 2013 From: henson at acm.org (Paul B. Henson) Date: Mon, 7 Oct 2013 17:22:00 -0700 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <084B749B-F6C1-4BB3-9A32-5542AD4C96BC@dey-sys.com> References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <20131007181348.GF22464@bender.unx.csupomona.edu> <084B749B-F6C1-4BB3-9A32-5542AD4C96BC@dey-sys.com> Message-ID: <20131008002200.GG22464@bender.unx.csupomona.edu> On Mon, Oct 07, 2013 at 05:11:10PM -0700, Garrett D'Amore wrote: > Can you also send /etc/path_to_inst? Attached. -------------- next part -------------- # # Caution! This file contains critical kernel state # "/iscsi" 0 "iscsi" "/agpgart" 0 "agpgart" "/options" 0 "options" "/pseudo" 0 "pseudo" "/scsi_vhci" 0 "scsi_vhci" "/scsi_vhci/disk at g50014ee6ade8c850" 4 "sd" "/scsi_vhci/disk at g50014ee6033e39d8" 5 "sd" "/scsi_vhci/disk at g50014ee6ade88be8" 6 "sd" "/scsi_vhci/disk at g50014ee6ade8b955" 7 "sd" "/scsi_vhci/disk at g50014ee0ae34ff74" 8 "sd" "/scsi_vhci/disk at g50014ee2080825c2" 9 "sd" "/scsi_vhci/disk at g50014ee603347e67" 10 "sd" "/scsi_vhci/disk at g50014ee25d5d754a" 11 "sd" "/scsi_vhci/disk at g50014ee25d5d799b" 12 "sd" "/scsi_vhci/disk at g50014ee2af0bec2f" 13 "sd" "/scsi_vhci/disk at g50015178f35c3aa9" 14 "sd" "/scsi_vhci/disk at g50014ee058df2f3e" 15 "sd" "/scsi_vhci/disk at g50014ee058dfa569" 16 "sd" "/scsi_vhci/disk at g50014ee658938c98" 17 "sd" "/scsi_vhci/disk at g50014ee058df988c" 18 "sd" "/pci at 0,0" 0 "npe" "/pci at 0,0/isa at 1f" 0 "isa" "/pci at 0,0/isa at 1f/pit_beep" 0 "pit_beep" "/pci at 0,0/isa at 1f/i8042 at 1,60" 0 "i8042" "/pci at 0,0/isa at 1f/i8042 at 1,60/mouse at 1" 0 "mouse8042" "/pci at 0,0/isa at 1f/asy at 1,3f8" 0 "asy" "/pci at 0,0/isa at 1f/asy at 1,2f8" 1 "asy" "/pci at 0,0/isa at 1f/asy at 1,3e8" 2 "asy" "/pci at 0,0/pci15d9,62b at 1a" 0 "ehci" "/pci at 0,0/pci15d9,62b at 1a/hub at 1" 1 "hubd" "/pci at 0,0/pci15d9,62b at 1a/hub at 1/device at 5" 0 "usb_mid" "/pci at 0,0/pci15d9,62b at 1a/hub at 1/device at 5/storage at 0" 0 "scsa2usb" "/pci at 0,0/pci15d9,62b at 1a/hub at 1/device at 5/storage at 0/disk at 0,0" 2 "sd" "/pci at 0,0/pci15d9,62b at 1a/hub at 1/device at 5/storage at 1" 1 "scsa2usb" "/pci at 0,0/pci15d9,62b at 1a/hub at 1/device at 5/storage at 1/disk at 0,0" 3 "sd" "/pci at 0,0/pci15d9,62b at 1a/hub at 1/device at 6" 1 "usb_mid" "/pci at 0,0/pci15d9,62b at 1a/hub at 1/device at 6/mouse at 0" 0 "hid" "/pci at 0,0/pci15d9,62b at 1a/hub at 1/device at 6/keyboard at 1" 1 "hid" "/pci at 0,0/pci15d9,62b at 1d" 1 "ehci" "/pci at 0,0/pci15d9,62b at 1d/hub at 1" 0 "hubd" "/pci at 0,0/pci15d9,62b at 1f,2" 0 "ahci" "/pci at 0,0/pci15d9,62b at 1f,2/disk at 0,0" 0 "sd" "/pci at 0,0/pci15d9,62b at 1f,2/disk at 1,0" 1 "sd" "/pci at 0,0/pci8086,3c08 at 3" 2 "pcieb" "/pci at 0,0/pci8086,3c08 at 3/pci15d9,1521 at 0" 0 "igb" "/pci at 0,0/pci8086,3c08 at 3/pci15d9,1521 at 0,1" 1 "igb" "/pci at 0,0/pci8086,3c0a at 3,2" 3 "pcieb" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0" 0 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 1000" 1 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 80" 2 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 10" 3 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 40" 4 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 8" 5 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 2" 6 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 1" 7 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 4" 8 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 100" 9 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 2000" 10 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 8000" 11 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 200" 12 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 400" 13 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 20" 14 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at 800" 15 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,30c0 at 0/iport at v0" 16 "mpt_sas" "/pci at 0,0/pci8086,244e at 1e" 0 "pci_pci" "/pci at 0,0/pci8086,244e at 1e/display at 4" 0 "vgatext" "/fw" 0 "acpinex" "/fw/sb at 0" 1 "acpinex" "/fw/sb at 0/socket at 0" 2 "acpinex" "/fw/sb at 0/socket at 0/cpu at 0" 0 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 2" 2 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 4" 4 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 6" 6 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 8" 8 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 10" 10 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 1" 1 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 3" 3 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 5" 5 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 7" 7 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 9" 9 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 11" 11 "cpudrv" From tom.robinson at motec.com.au Tue Oct 8 00:37:45 2013 From: tom.robinson at motec.com.au (Tom Robinson) Date: Tue, 08 Oct 2013 11:37:45 +1100 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <525343E5.3040401@motec.com.au> Message-ID: <525353D9.90600@motec.com.au> Hi Garret, Thanks again. On 08/10/13 11:10, Garrett D'Amore wrote: > > On Oct 7, 2013, at 4:29 PM, Tom Robinson > wrote: > >> Hi Garret, >> >> Thanks for your message. >> >> The host configuration is as follows: >> >> Supermicro X9DRi-F >> 256GB RAM (16x Hynix 16GB ECC Reg. DDR3 1600MHz) >> 2 x Intel Xeon E5-2620 >> 2 x Intel SSD 320 80GB (rpool) >> 4 x STEC Enterprise S842 200GB (ARC) >> 1 x STEC ZeusRAM 8GB 3.5" SAS SSD (ZIL) >> 1 x LSI SAS 9207-8i (internal drives) >> 1 x Intel Ethernet Server Adapter X520-DA2, Dual Port 10Gbps SFP+ Direct Attach Copper, PCI-e 2.0 >> 5GT/s 1 >> 2 x Mellanox ConnectX?-2 VPI >> 2 x LSI SAS 9207-8e (JBODS) > > I'd be suspicious of the Mellanox cards. Are these the hermon driver? It looks like there is an > attempt to do the right thing for those drivers, but? I don't know if I believe it all works > properly. The other cards should be fine. > > - Garrett It is indeed the hermon driver: /etc/driver_aliases hermon "pciex15b3,6340" hermon "pciex15b3,634a" hermon "pciex15b3,6732" hermon "pciex15b3,673c" hermon "pciex15b3,6746" > >> >> That is connected via external SAS to two JBODS containing 28 x 1TB disks each for mirrored zfs >> vdevs. >> >> The output from prtconf -vp is attached as it's very long (2042 lines). >> >> Kind regards, >> Tom >> >> On 08/10/13 02:06, Garrett D'Amore wrote: >>> If you're seeing hangs like this, I would appreciate knowing the hardware configuration. >>> Prtconf -vp might be helpful. Presumably this is the result of one or more devices not doing >>> the right thing for quiesce(). >>> >>> - Garrett >>> >>> On Oct 7, 2013, at 4:34 AM, Narayan Desai >> > wrote: >>> >>>> This is caused by the system attempting to use fastboot on default reboot. We've disabled that >>>> and things seem to work properly; the following commands do the trick. (the first changes >>>> reboot not to use fastboot, the second causes the system to do a full reboot upon panic) >>>> -nld >>>> >>>> # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false >>>> # svcadm refresh svc:/system/boot-config:default >>>> # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false >>>> # svcadm refresh svc:/system/boot-config:default >>>> I did have fastreboot set to true (installed default setting): # svcs -vl system/boot-config | grep fastreboot config/fastreboot_default (boolean) = true config/fastreboot_onpanic (boolean) = true fastreboot_blacklist (application) fastreboot_blacklist/platforms (astring) = VirtualBox "VMware Virtual Platform"MCP55 "Precision WorkStation 650 ""PowerEdge 1600SC " fastreboot_blacklist/stability (astring) = Unstable I'm not sure what the fastboot_blacklist settings are or why they are there. Should I remove that? Looks like some sort of remnant I don't need. I have set config/fastreboot_default=false and config/fastreboot_onpanic=false. I now get: "bootadm: failed to find boot signature. Reboot with arguments failed." but the system does reboot every time now. What is the significance of the above message? Does that indicate that the "-r" option will be ignored on reboot? Regards, Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature URL: From narayan.desai at gmail.com Tue Oct 8 01:08:43 2013 From: narayan.desai at gmail.com (Narayan Desai) Date: Mon, 7 Oct 2013 20:08:43 -0500 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <525343E5.3040401@motec.com.au> Message-ID: So, specifically wrt the mellanox cards, we have four identical systems with mellanox cards running with the hermon driver. One is running OI 151a3, and reboots properly. The ones running a recent omnios don't with fastboot. Just one data point. -nld On Mon, Oct 7, 2013 at 7:10 PM, Garrett D'Amore wrote: > > On Oct 7, 2013, at 4:29 PM, Tom Robinson > wrote: > > Hi Garret, > > Thanks for your message. > > The host configuration is as follows: > > Supermicro X9DRi-F > 256GB RAM (16x Hynix 16GB ECC Reg. DDR3 1600MHz) > 2 x Intel Xeon E5-2620 > 2 x Intel SSD 320 80GB (rpool) > 4 x STEC Enterprise S842 200GB (ARC) > 1 x STEC ZeusRAM 8GB 3.5" SAS SSD (ZIL) > 1 x LSI SAS 9207-8i (internal drives) > 1 x Intel Ethernet Server Adapter X520-DA2, Dual Port 10Gbps SFP+ Direct > Attach Copper, PCI-e 2.0 5GT/s 1 > 2 x Mellanox ConnectX?-2 VPI > 2 x LSI SAS 9207-8e (JBODS) > > > I'd be suspicious of the Mellanox cards. Are these the hermon driver? It > looks like there is an attempt to do the right thing for those drivers, > but? I don't know if I believe it all works properly. The other cards > should be fine. > > - Garrett > > > That is connected via external SAS to two JBODS containing 28 x 1TB disks > each for mirrored zfs vdevs. > > The output from prtconf -vp is attached as it's very long (2042 lines). > > Kind regards, > Tom > > On 08/10/13 02:06, Garrett D'Amore wrote: > > If you're seeing hangs like this, I would appreciate knowing the hardware > configuration. Prtconf -vp might be helpful. Presumably this is the > result of one or more devices not doing the right thing for quiesce(). > > - Garrett > > On Oct 7, 2013, at 4:34 AM, Narayan Desai > wrote: > > This is caused by the system attempting to use fastboot on default > reboot. We've disabled that and things seem to work properly; the following > commands do the trick. (the first changes reboot not to use fastboot, the > second causes the system to do a full reboot upon panic) > -nld > > # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false > # svcadm refresh svc:/system/boot-config:default > > # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false > # svcadm refresh svc:/system/boot-config:default > > > > > On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson wrote: > >> Hi, >> >> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >> >> when I do: >> >> reboot -- -r >> >> The system hangs on the 'rebooting...' message. >> >> I've disabled Suspend and C-states in the BIOS. I had one successful >> 'reboot' but now it's hanging >> again. >> >> Anyone have any clues on how to fix this? >> >> Kind regards, >> >> -- >> >> Tom Robinson >> IT Manager/System Administrator >> >> MoTeC Pty Ltd >> >> 121 Merrindale Drive >> Croydon South >> 3136 Victoria >> Australia >> >> T: +61 3 9761 5050 >> F: +61 3 9761 5051 >> E: tom.robinson at motec.com.au >> >> >> >> _______________________________________________ >> 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: From narayan.desai at gmail.com Tue Oct 8 02:24:23 2013 From: narayan.desai at gmail.com (Narayan Desai) Date: Mon, 7 Oct 2013 21:24:23 -0500 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <0692F2D3-87BC-497C-BF1E-5A7A9E466D28@dey-sys.com> References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <525343E5.3040401@motec.com.au> <0692F2D3-87BC-497C-BF1E-5A7A9E466D28@dey-sys.com> Message-ID: I actually hadn't posted a full description of our systems. Here is prtconf output. The system is a: System Configuration: Supermicro X8DAH BIOS Configuration: American Megatrends Inc. 2.1 12/30/2011 a pile of LSI 92xx controllers (mix of internal and external) Mellanox ConnectX 2 nic Intel gigabit (igb) Someone suggested that this might be some sort of ACPI problem at one point. Does that seem reasonable? -nld On Mon, Oct 7, 2013 at 9:13 PM, Garrett D'Amore wrote: > > On Oct 7, 2013, at 6:08 PM, Narayan Desai wrote: > > So, specifically wrt the mellanox cards, we have four identical systems > with mellanox cards running with the hermon driver. One is running OI > 151a3, and reboots properly. The ones running a recent omnios don't with > fastboot. Just one data point. > > > > Oh, that's interesting. Would be interesting to see what's different. I > doubt its the hermon driver. More suspicious of the Intel ethernet now. > > - Garrett > > -nld > > > On Mon, Oct 7, 2013 at 7:10 PM, Garrett D'Amore < > garrett.damore at dey-sys.com> wrote: > >> >> On Oct 7, 2013, at 4:29 PM, Tom Robinson >> wrote: >> >> Hi Garret, >> >> Thanks for your message. >> >> The host configuration is as follows: >> >> Supermicro X9DRi-F >> 256GB RAM (16x Hynix 16GB ECC Reg. DDR3 1600MHz) >> 2 x Intel Xeon E5-2620 >> 2 x Intel SSD 320 80GB (rpool) >> 4 x STEC Enterprise S842 200GB (ARC) >> 1 x STEC ZeusRAM 8GB 3.5" SAS SSD (ZIL) >> 1 x LSI SAS 9207-8i (internal drives) >> 1 x Intel Ethernet Server Adapter X520-DA2, Dual Port 10Gbps SFP+ Direct >> Attach Copper, PCI-e 2.0 5GT/s 1 >> 2 x Mellanox ConnectX?-2 VPI >> 2 x LSI SAS 9207-8e (JBODS) >> >> >> I'd be suspicious of the Mellanox cards. Are these the hermon driver? >> It looks like there is an attempt to do the right thing for those drivers, >> but? I don't know if I believe it all works properly. The other cards >> should be fine. >> >> - Garrett >> >> >> That is connected via external SAS to two JBODS containing 28 x 1TB disks >> each for mirrored zfs vdevs. >> >> The output from prtconf -vp is attached as it's very long (2042 lines). >> >> Kind regards, >> Tom >> >> On 08/10/13 02:06, Garrett D'Amore wrote: >> >> If you're seeing hangs like this, I would appreciate knowing the hardware >> configuration. Prtconf -vp might be helpful. Presumably this is the >> result of one or more devices not doing the right thing for quiesce(). >> >> - Garrett >> >> On Oct 7, 2013, at 4:34 AM, Narayan Desai >> wrote: >> >> This is caused by the system attempting to use fastboot on default >> reboot. We've disabled that and things seem to work properly; the following >> commands do the trick. (the first changes reboot not to use fastboot, the >> second causes the system to do a full reboot upon panic) >> -nld >> >> # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false >> # svcadm refresh svc:/system/boot-config:default >> >> # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false >> # svcadm refresh svc:/system/boot-config:default >> >> >> >> >> On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson wrote: >> >>> Hi, >>> >>> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >>> >>> when I do: >>> >>> reboot -- -r >>> >>> The system hangs on the 'rebooting...' message. >>> >>> I've disabled Suspend and C-states in the BIOS. I had one successful >>> 'reboot' but now it's hanging >>> again. >>> >>> Anyone have any clues on how to fix this? >>> >>> Kind regards, >>> >>> -- >>> >>> Tom Robinson >>> IT Manager/System Administrator >>> >>> MoTeC Pty Ltd >>> >>> 121 Merrindale Drive >>> Croydon South >>> 3136 Victoria >>> Australia >>> >>> T: +61 3 9761 5050 >>> F: +61 3 9761 5051 >>> E: tom.robinson at motec.com.au >>> >>> >>> >>> _______________________________________________ >>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: prtconf.log.gz Type: application/x-gzip Size: 5986 bytes Desc: not available URL: From tom.robinson at motec.com.au Tue Oct 8 03:11:14 2013 From: tom.robinson at motec.com.au (Tom Robinson) Date: Tue, 08 Oct 2013 14:11:14 +1100 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <525343E5.3040401@motec.com.au> <0692F2D3-87BC-497C-BF1E-5A7A9E466D28@dey-sys.com> Message-ID: <525377D2.6080901@motec.com.au> On 08/10/13 13:24, Narayan Desai wrote: > I actually hadn't posted a full description of our systems. Here is prtconf output. > > The system is a: > System Configuration: Supermicro X8DAH > BIOS Configuration: American Megatrends Inc. 2.1 12/30/2011 > a pile of LSI 92xx controllers (mix of internal and external) > Mellanox ConnectX 2 nic > Intel gigabit (igb) > > Someone suggested that this might be some sort of ACPI problem at one point. Does that seem > reasonable? > -nld > I had some 'luck' when I disabled the following in the BIOS: Advanced->ACPI Settings->ACPI Sleep State = Suspend Disabled By 'luck' I mean it rebooted without hanging once. Subsequent reboots kept hanging on 'rebooting...'. I then made the following BIOS config changes: Advanced->CPU Power Management Configuration-> C1E Support = Disabled CPU C3 Report = Disabled CPU C6 Report = Disabled CPU C7 Report = Disabled But that didn't stop the reboot hang. Would it have anything to do with NUMA? t. > > > On Mon, Oct 7, 2013 at 9:13 PM, Garrett D'Amore > wrote: > > > On Oct 7, 2013, at 6:08 PM, Narayan Desai > wrote: > >> So, specifically wrt the mellanox cards, we have four identical systems with mellanox cards >> running with the hermon driver. One is running OI 151a3, and reboots properly. The ones >> running a recent omnios don't with fastboot. Just one data point. > > > Oh, that's interesting. Would be interesting to see what's different. I doubt its the hermon > driver. More suspicious of the Intel ethernet now. > > - Garrett > >> -nld >> >> >> On Mon, Oct 7, 2013 at 7:10 PM, Garrett D'Amore > > wrote: >> >> >> On Oct 7, 2013, at 4:29 PM, Tom Robinson > > wrote: >> >>> Hi Garret, >>> >>> Thanks for your message. >>> >>> The host configuration is as follows: >>> >>> Supermicro X9DRi-F >>> 256GB RAM (16x Hynix 16GB ECC Reg. DDR3 1600MHz) >>> 2 x Intel Xeon E5-2620 >>> 2 x Intel SSD 320 80GB (rpool) >>> 4 x STEC Enterprise S842 200GB (ARC) >>> 1 x STEC ZeusRAM 8GB 3.5" SAS SSD (ZIL) >>> 1 x LSI SAS 9207-8i (internal drives) >>> 1 x Intel Ethernet Server Adapter X520-DA2, Dual Port 10Gbps SFP+ Direct Attach Copper, >>> PCI-e 2.0 5GT/s 1 >>> 2 x Mellanox ConnectX?-2 VPI >>> 2 x LSI SAS 9207-8e (JBODS) >> >> I'd be suspicious of the Mellanox cards. Are these the hermon driver? It looks like >> there is an attempt to do the right thing for those drivers, but? I don't know if I >> believe it all works properly. The other cards should be fine. >> >> - Garrett >> >>> >>> That is connected via external SAS to two JBODS containing 28 x 1TB disks each for >>> mirrored zfs vdevs. >>> >>> The output from prtconf -vp is attached as it's very long (2042 lines). >>> >>> Kind regards, >>> Tom >>> >>> On 08/10/13 02:06, Garrett D'Amore wrote: >>>> If you're seeing hangs like this, I would appreciate knowing the hardware >>>> configuration. Prtconf -vp might be helpful. Presumably this is the result of one or >>>> more devices not doing the right thing for quiesce(). >>>> >>>> - Garrett >>>> >>>> On Oct 7, 2013, at 4:34 AM, Narayan Desai >>> > wrote: >>>> >>>>> This is caused by the system attempting to use fastboot on default reboot. We've >>>>> disabled that and things seem to work properly; the following commands do the trick. >>>>> (the first changes reboot not to use fastboot, the second causes the system to do a >>>>> full reboot upon panic) >>>>> -nld >>>>> >>>>> # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false >>>>> # svcadm refresh svc:/system/boot-config:default >>>>> # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false >>>>> # svcadm refresh svc:/system/boot-config:default >>>>> >>>>> >>>>> >>>>> On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson >>>> > wrote: >>>>> >>>>> Hi, >>>>> >>>>> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >>>>> >>>>> when I do: >>>>> >>>>> reboot -- -r >>>>> >>>>> The system hangs on the 'rebooting...' message. >>>>> >>>>> I've disabled Suspend and C-states in the BIOS. I had one successful 'reboot' but >>>>> now it's hanging >>>>> again. >>>>> >>>>> Anyone have any clues on how to fix this? >>>>> >>>>> Kind regards, >>>>> >>>>> -- >>>>> >>>>> Tom Robinson >>>>> IT Manager/System Administrator >>>>> >>>>> MoTeC Pty Ltd >>>>> >>>>> 121 Merrindale Drive >>>>> Croydon South >>>>> 3136 Victoria >>>>> Australia >>>>> >>>>> T: +61 3 9761 5050 >>>>> F: +61 3 9761 5051 >>>>> E: tom.robinson at motec.com.au >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature URL: From tom.robinson at motec.com.au Tue Oct 8 06:12:44 2013 From: tom.robinson at motec.com.au (Tom Robinson) Date: Tue, 08 Oct 2013 17:12:44 +1100 Subject: [OmniOS-discuss] SAS tape driver In-Reply-To: <6519B345-5BC9-45A0-89BA-8E7009E33424@dey-sys.com> References: <52523A90.1070700@motec.com.au> <6519B345-5BC9-45A0-89BA-8E7009E33424@dey-sys.com> Message-ID: <5253A25C.2020306@motec.com.au> Hi Garret, Thanks for your help on this. At the moment I'm actually trying to get to grips with the device management by trying to restore the installed settings I had before I attempted the IBMtape driver installation. My thinking was that if I can restore those settings I will understand the whole set up a bit better. So I have re-established the 'st' driver by doing the following: # rem_drv st Driver (st) not installed. # add_drv st devfsadm: driver failed to attach: st # modinfo -cw | grep '\' 288 1 st LOADED/INSTALLED # update_drv -av -i '"scsiclass,01"' st exit status = 0 devfsadm[957]: verbose: symlink /dev/rmt/0 -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0: devfsadm[957]: verbose: symlink /dev/rmt/0n -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:n devfsadm[957]: verbose: symlink /dev/rmt/0b -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:b devfsadm[957]: verbose: symlink /dev/rmt/0bn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:bn devfsadm[957]: verbose: symlink /dev/rmt/0l -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:l devfsadm[957]: verbose: symlink /dev/rmt/0m -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:m devfsadm[957]: verbose: symlink /dev/rmt/0h -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:h devfsadm[957]: verbose: symlink /dev/rmt/0c -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:c devfsadm[957]: verbose: symlink /dev/rmt/0u -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:u devfsadm[957]: verbose: symlink /dev/rmt/0ln -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:ln devfsadm[957]: verbose: symlink /dev/rmt/0mn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:mn devfsadm[957]: verbose: symlink /dev/rmt/0hn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:hn devfsadm[957]: verbose: symlink /dev/rmt/0cn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:cn devfsadm[957]: verbose: symlink /dev/rmt/0un -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:un devfsadm[957]: verbose: symlink /dev/rmt/0lb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:lb devfsadm[957]: verbose: symlink /dev/rmt/0mb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:mb devfsadm[957]: verbose: symlink /dev/rmt/0hb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:hb devfsadm[957]: verbose: symlink /dev/rmt/0cb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:cb devfsadm[957]: verbose: symlink /dev/rmt/0ub -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:ub devfsadm[957]: verbose: symlink /dev/rmt/0lbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:lbn devfsadm[957]: verbose: symlink /dev/rmt/0mbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:mbn devfsadm[957]: verbose: symlink /dev/rmt/0hbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:hbn devfsadm[957]: verbose: symlink /dev/rmt/0cbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:cbn devfsadm[957]: verbose: symlink /dev/rmt/0ubn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:ubn devfsadm[957]: verbose: symlink /dev/rmt/1 -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0: devfsadm[957]: verbose: symlink /dev/rmt/1n -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:n devfsadm[957]: verbose: symlink /dev/rmt/1b -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:b devfsadm[957]: verbose: symlink /dev/rmt/1bn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:bn devfsadm[957]: verbose: symlink /dev/rmt/1l -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:l devfsadm[957]: verbose: symlink /dev/rmt/1m -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:m devfsadm[957]: verbose: symlink /dev/rmt/1h -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:h devfsadm[957]: verbose: symlink /dev/rmt/1c -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:c devfsadm[957]: verbose: symlink /dev/rmt/1u -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:u devfsadm[957]: verbose: symlink /dev/rmt/1ln -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:ln devfsadm[957]: verbose: symlink /dev/rmt/1mn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:mn devfsadm[957]: verbose: symlink /dev/rmt/1hn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:hn devfsadm[957]: verbose: symlink /dev/rmt/1cn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:cn devfsadm[957]: verbose: symlink /dev/rmt/1un -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:un devfsadm[957]: verbose: symlink /dev/rmt/1lb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:lb devfsadm[957]: verbose: symlink /dev/rmt/1mb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:mb devfsadm[957]: verbose: symlink /dev/rmt/1hb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:hb devfsadm[957]: verbose: symlink /dev/rmt/1cb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:cb devfsadm[957]: verbose: symlink /dev/rmt/1ub -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:ub devfsadm[957]: verbose: symlink /dev/rmt/1lbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:lbn devfsadm[957]: verbose: symlink /dev/rmt/1mbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:mbn devfsadm[957]: verbose: symlink /dev/rmt/1hbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:hbn devfsadm[957]: verbose: symlink /dev/rmt/1cbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:cbn devfsadm[957]: verbose: symlink /dev/rmt/1ubn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:ubn Now I need to try again with the IBMtape driver. Regards, Tom On 08/10/13 02:05, Garrett D'Amore wrote: > Need to see the IBM changes to /etc/driver_aliases. My guess is that this is the source of the problem. If you know the name of the kernel driver for the IBM tape module, you could rem_drv it. A reboot may be required for the change to take effect. > > - Garrett > > On Oct 6, 2013, at 9:37 PM, Tom Robinson wrote: > >> Hi, >> >> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >> >> I'm trying to configure an IBM TS3100 tape library with not much luck. >> >> I used to see the tape through the 'st' driver (at least I think it was the st driver). But after >> following the IBM documentation and installing the IBMtape driver a I can no longer see the tape. >> >> I'm also having issues with the 'reboot -- -r' command hanging on 'rebooting...' message and am >> wondering if that is compounding the issue (see separate thread). >> >> After no luck with the IBMtape driver, I am now trying to revert to the st driver and not having any >> luck with that either. >> >> The device links under /dev/rmt had to be removed as part of the IBMtape setup but they were similar >> to the following listing: >> lrwxrwxrwx 1 root root 88 Sep 20 03:18 0 -> >> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0: >> >> I now have nothing listed under /dev/rmt and the st module appears not to load: >> # modinfo -cw | grep '\' >> 287 11 st UNLOADED/UNINSTALLED >> >> # modload -p drv/st >> can't load module: No such device or address >> >> # modload -p drv/amd64/st >> can't load module: No such device or address >> >> (not sure which of the above is the correct driver actually) >> >> Any help is much appreciated. >> >> Kind regards, >> Tom >> >> More info: >> # uname -m >> i86pc >> >> /kernel/drv/st.conf >> name="st" class="scsi" target=0 lun=0; >> name="st" class="scsi" target=1 lun=0; >> name="st" class="scsi" target=2 lun=0; >> name="st" class="scsi" target=3 lun=0; >> name="st" class="scsi" target=4 lun=0; >> name="st" class="scsi" target=5 lun=0; >> name="st" class="scsi" target=6 lun=0; >> >> /etc/driver_aliases >> ... >> st "scsiclass,01" >> ... >> >> >> >> >> >> >> >> -- >> >> Tom Robinson >> IT Manager/System Administrator >> >> MoTeC Pty Ltd >> >> 121 Merrindale Drive >> Croydon South >> 3136 Victoria >> Australia >> >> T: +61 3 9761 5050 >> F: +61 3 9761 5051 >> E: tom.robinson at motec.com.au >> >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature URL: From garrett.damore at dey-sys.com Tue Oct 8 00:10:05 2013 From: garrett.damore at dey-sys.com (Garrett D'Amore) Date: Mon, 7 Oct 2013 17:10:05 -0700 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <525343E5.3040401@motec.com.au> References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <525343E5.3040401@motec.com.au> Message-ID: On Oct 7, 2013, at 4:29 PM, Tom Robinson wrote: > Hi Garret, > > Thanks for your message. > > The host configuration is as follows: > > Supermicro X9DRi-F > 256GB RAM (16x Hynix 16GB ECC Reg. DDR3 1600MHz) > 2 x Intel Xeon E5-2620 > 2 x Intel SSD 320 80GB (rpool) > 4 x STEC Enterprise S842 200GB (ARC) > 1 x STEC ZeusRAM 8GB 3.5" SAS SSD (ZIL) > 1 x LSI SAS 9207-8i (internal drives) > 1 x Intel Ethernet Server Adapter X520-DA2, Dual Port 10Gbps SFP+ Direct Attach Copper, PCI-e 2.0 5GT/s 1 > 2 x Mellanox ConnectX?-2 VPI > 2 x LSI SAS 9207-8e (JBODS) I'd be suspicious of the Mellanox cards. Are these the hermon driver? It looks like there is an attempt to do the right thing for those drivers, but? I don't know if I believe it all works properly. The other cards should be fine. - Garrett > > That is connected via external SAS to two JBODS containing 28 x 1TB disks each for mirrored zfs vdevs. > > The output from prtconf -vp is attached as it's very long (2042 lines). > > Kind regards, > Tom > > On 08/10/13 02:06, Garrett D'Amore wrote: >> If you're seeing hangs like this, I would appreciate knowing the hardware configuration. Prtconf -vp might be helpful. Presumably this is the result of one or more devices not doing the right thing for quiesce(). >> >> - Garrett >> >> On Oct 7, 2013, at 4:34 AM, Narayan Desai wrote: >> >>> This is caused by the system attempting to use fastboot on default reboot. We've disabled that and things seem to work properly; the following commands do the trick. (the first changes reboot not to use fastboot, the second causes the system to do a full reboot upon panic) >>> -nld >>> >>> # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false >>> # svcadm refresh svc:/system/boot-config:default >>> # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false >>> # svcadm refresh svc:/system/boot-config:default >>> >>> >>> >>> On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson wrote: >>> Hi, >>> >>> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >>> >>> when I do: >>> >>> reboot -- -r >>> >>> The system hangs on the 'rebooting...' message. >>> >>> I've disabled Suspend and C-states in the BIOS. I had one successful 'reboot' but now it's hanging >>> again. >>> >>> Anyone have any clues on how to fix this? >>> >>> Kind regards, >>> >>> -- >>> >>> Tom Robinson >>> IT Manager/System Administrator >>> >>> MoTeC Pty Ltd >>> >>> 121 Merrindale Drive >>> Croydon South >>> 3136 Victoria >>> Australia >>> >>> T: +61 3 9761 5050 >>> F: +61 3 9761 5051 >>> E: tom.robinson at motec.com.au >>> >>> >>> >>> _______________________________________________ >>> 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: From garrett.damore at dey-sys.com Tue Oct 8 00:11:10 2013 From: garrett.damore at dey-sys.com (Garrett D'Amore) Date: Mon, 7 Oct 2013 17:11:10 -0700 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <20131007181348.GF22464@bender.unx.csupomona.edu> References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <20131007181348.GF22464@bender.unx.csupomona.edu> Message-ID: <084B749B-F6C1-4BB3-9A32-5542AD4C96BC@dey-sys.com> I don't see anything immediately obvious here. Can you also send /etc/path_to_inst? - Garrett On Oct 7, 2013, at 11:13 AM, Paul B. Henson wrote: > On Mon, Oct 07, 2013 at 08:06:25AM -0700, Garrett D'Amore wrote: >> If you're seeing hangs like this, I would appreciate knowing the hardware configuration. Prtconf -vp might be helpful. Presumably this is the result of one or more devices not doing the right thing for quiesce(). > > I had the same problem on a supermicro box: > > Case: 836BA-R920B > Motherboard: X9SRI-F > BIOS: 2.0a 04/19/2013 > CPU: Intel Xeon E5-2620 > Memory: 3 x Crucial CT2KIT102472BB160B (6 DIMMs, 48G) > HBA: LSI 9201-16i > > prtconf attached. I disabled fastboot and don't care too much about > fixing it; it gets rebooted very infrequently and probably 4 times out > of 5 when I do reboot it I need to get into the bios or do something of > that nature and ended up getting annoyed that I had to reboot it twice > because I forgot about fastboot ;). > > From garrett.damore at dey-sys.com Tue Oct 8 02:13:12 2013 From: garrett.damore at dey-sys.com (Garrett D'Amore) Date: Mon, 7 Oct 2013 19:13:12 -0700 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <525343E5.3040401@motec.com.au> Message-ID: <0692F2D3-87BC-497C-BF1E-5A7A9E466D28@dey-sys.com> On Oct 7, 2013, at 6:08 PM, Narayan Desai wrote: > So, specifically wrt the mellanox cards, we have four identical systems with mellanox cards running with the hermon driver. One is running OI 151a3, and reboots properly. The ones running a recent omnios don't with fastboot. Just one data point. Oh, that's interesting. Would be interesting to see what's different. I doubt its the hermon driver. More suspicious of the Intel ethernet now. - Garrett > -nld > > > On Mon, Oct 7, 2013 at 7:10 PM, Garrett D'Amore wrote: > > On Oct 7, 2013, at 4:29 PM, Tom Robinson wrote: > >> Hi Garret, >> >> Thanks for your message. >> >> The host configuration is as follows: >> >> Supermicro X9DRi-F >> 256GB RAM (16x Hynix 16GB ECC Reg. DDR3 1600MHz) >> 2 x Intel Xeon E5-2620 >> 2 x Intel SSD 320 80GB (rpool) >> 4 x STEC Enterprise S842 200GB (ARC) >> 1 x STEC ZeusRAM 8GB 3.5" SAS SSD (ZIL) >> 1 x LSI SAS 9207-8i (internal drives) >> 1 x Intel Ethernet Server Adapter X520-DA2, Dual Port 10Gbps SFP+ Direct Attach Copper, PCI-e 2.0 5GT/s 1 >> 2 x Mellanox ConnectX?-2 VPI >> 2 x LSI SAS 9207-8e (JBODS) > > I'd be suspicious of the Mellanox cards. Are these the hermon driver? It looks like there is an attempt to do the right thing for those drivers, but? I don't know if I believe it all works properly. The other cards should be fine. > > - Garrett > >> >> That is connected via external SAS to two JBODS containing 28 x 1TB disks each for mirrored zfs vdevs. >> >> The output from prtconf -vp is attached as it's very long (2042 lines). >> >> Kind regards, >> Tom >> >> On 08/10/13 02:06, Garrett D'Amore wrote: >>> If you're seeing hangs like this, I would appreciate knowing the hardware configuration. Prtconf -vp might be helpful. Presumably this is the result of one or more devices not doing the right thing for quiesce(). >>> >>> - Garrett >>> >>> On Oct 7, 2013, at 4:34 AM, Narayan Desai wrote: >>> >>>> This is caused by the system attempting to use fastboot on default reboot. We've disabled that and things seem to work properly; the following commands do the trick. (the first changes reboot not to use fastboot, the second causes the system to do a full reboot upon panic) >>>> -nld >>>> >>>> # svccfg -s "system/boot-config:default" setprop config/fastreboot_default=false >>>> # svcadm refresh svc:/system/boot-config:default >>>> # svccfg -s "system/boot-config:default" setprop config/fastreboot_onpanic=false >>>> # svcadm refresh svc:/system/boot-config:default >>>> >>>> >>>> >>>> On Sun, Oct 6, 2013 at 11:26 PM, Tom Robinson wrote: >>>> Hi, >>>> >>>> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >>>> >>>> when I do: >>>> >>>> reboot -- -r >>>> >>>> The system hangs on the 'rebooting...' message. >>>> >>>> I've disabled Suspend and C-states in the BIOS. I had one successful 'reboot' but now it's hanging >>>> again. >>>> >>>> Anyone have any clues on how to fix this? >>>> >>>> Kind regards, >>>> >>>> -- >>>> >>>> Tom Robinson >>>> IT Manager/System Administrator >>>> >>>> MoTeC Pty Ltd >>>> >>>> 121 Merrindale Drive >>>> Croydon South >>>> 3136 Victoria >>>> Australia >>>> >>>> T: +61 3 9761 5050 >>>> F: +61 3 9761 5051 >>>> E: tom.robinson at motec.com.au >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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: From ci4 at outlook.com Thu Oct 10 10:30:43 2013 From: ci4 at outlook.com (Chavdar Ivanov) Date: Thu, 10 Oct 2013 11:30:43 +0100 Subject: [OmniOS-discuss] AMPO webserver stack (Apache, mySQL, PHPmyadmin, PHP, Owncloud) In-Reply-To: <5252AD57.9020403@hfg-gmuend.de> References: <52523A90.1070700@motec.com.au> <5252AD57.9020403@hfg-gmuend.de> Message-ID: From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On Behalf Of Guenther Alka Sent: 07 October 2013 13:47 To: omnios-discuss at lists.omniti.com Subject: [OmniOS-discuss] AMPO webserver stack (Apache, mySQL, PHPmyadmin, PHP, Owncloud) info: I try to support the ampo community add-on for OmniOS/ napp-it (free at home and commercially) it includes: * Apache 2.4.6, * MySQL 5.6.12, * PHPMyadmin, * PHP 5.4.19 * OwnCloud 5.0.10 You can install the whole ampo stack with one command (without napp-it you may get some messages about missing files but you can ignore). It uses the SmartOS repository as this is the best and most up to date source not only for SmartOS but for OmniOS and OpenIndiana as well: http://wiki.openindiana.org/oi/3.+Installing+software+and+package+management You can test the first version of the online installer (run as root at console) wget -O - www.napp-it.org/ampo | perl due to some dependencies, you need to run the installer twice. Any help with this package and the installer is welcome as well as help with other cloud add-ons like http://seafile.com/en/home/ more http://napp-it.org/extensions/ampo_en.html Just to let you know it worked flawlessly on my OmniOS internal host; there was already napp-it installed. Next I will test the first Alpha of owncloud 6. Chavdar -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel at dgnetwork.com.br Thu Oct 10 14:31:46 2013 From: daniel at dgnetwork.com.br (=?ISO-8859-1?Q?=22Daniel_D=2E_Gon=E7alves=22?=) Date: Thu, 10 Oct 2013 11:31:46 -0300 Subject: [OmniOS-discuss] ZFS, BUG ?? Message-ID: <5256BA52.1090304@dgnetwork.com.br> I have a difficult problem to solve that has already dragged on for months, it all started when I was trying to replace a HD in "mirror-1", there were several problems with the HDD swapped, creating multiple records in ZFS POOL: 2172725334577304178 UNAVAIL 0 0 0 was /dev/dsk/c17t22d1s0 844126543414690630 UNAVAIL 0 0 0 was /dev/dsk/c17t12d1s0 13311585097705723147 UNAVAIL 0 0 0 was /dev/dsk/c17t21d1s0 14208018708240497353 UNAVAIL 0 0 0 was /dev/dsk/c17t13d1s0 By the current state of POOL, everything is ok, I have two hard drives inside the MIRROR-1 synchronized, but the records of HDs are UNAVAIL and the health of my pool is only DEGRADED. I've tried to import/export POOL, zpool clear and nothing. Can anyone help me? zpool status: pool: STORAGE01 state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: resilvered 1.31T in 17h52m with 14 errors on Thu Oct 10 06:17:44 2013 config: NAME STATE READ WRITE CKSUM STORAGE01 DEGRADED 28 0 0 mirror-0 ONLINE 0 0 0 c17t15d1 ONLINE 0 0 0 c17t19d1 ONLINE 0 0 0 mirror-1 DEGRADED 56 0 0 c17t24d1 ONLINE 0 0 56 replacing-1 DEGRADED 56 0 0 2172725334577304178 UNAVAIL 0 0 0 was /dev/dsk/c17t22d1s0 844126543414690630 UNAVAIL 0 0 0 was /dev/dsk/c17t12d1s0 13311585097705723147 UNAVAIL 0 0 0 was /dev/dsk/c17t21d1s0 c14t0d0 ONLINE 0 0 56 14208018708240497353 UNAVAIL 0 0 0 was /dev/dsk/c17t13d1s0 mirror-2 ONLINE 0 0 0 c17t18d1 ONLINE 0 0 0 c17t17d1 ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 c17t20d1 ONLINE 0 0 0 c14t2d0 ONLINE 0 0 0 mirror-5 ONLINE 0 0 0 c17t25d1 ONLINE 0 0 0 c17t27d1 ONLINE 0 0 0 mirror-6 ONLINE 0 0 0 c17t26d1 ONLINE 0 0 0 c17t28d1 ONLINE 0 0 0 mirror-7 ONLINE 0 0 0 c17t29d1 ONLINE 0 0 0 c17t31d1 ONLINE 0 0 0 mirror-8 ONLINE 0 0 0 c17t32d1 ONLINE 0 0 0 c17t30d1 ONLINE 0 0 0 mirror-9 ONLINE 0 0 0 c17t23d1 ONLINE 0 0 0 c17t14d1 ONLINE 0 0 0 logs mirror-4 ONLINE 0 0 0 c14t1d0 ONLINE 0 0 0 c14t3d0 ONLINE 0 0 0 cache c14t4d0 ONLINE 0 0 0 Thanks, Daniel From tom.robinson at motec.com.au Fri Oct 11 03:37:18 2013 From: tom.robinson at motec.com.au (Tom Robinson) Date: Fri, 11 Oct 2013 14:37:18 +1100 Subject: [OmniOS-discuss] reboot hangs on 'rebooting...' In-Reply-To: <084B749B-F6C1-4BB3-9A32-5542AD4C96BC@dey-sys.com> References: <525237FA.7040609@motec.com.au> <60E1FD35-1059-4D6F-9DE8-415591598581@dey-sys.com> <20131007181348.GF22464@bender.unx.csupomona.edu> <084B749B-F6C1-4BB3-9A32-5542AD4C96BC@dey-sys.com> Message-ID: <5257726E.4090303@motec.com.au> On 08/10/13 11:11, Garrett D'Amore wrote: > I don't see anything immediately obvious here. > > Can you also send /etc/path_to_inst? > Hi Garrett, Don't know why I didn't see this request before. Here's my path_to_inst # # Caution! This file contains critical kernel state # "/iscsi" 0 "iscsi" "/agpgart" 0 "agpgart" "/ib" 0 "ib" "/ib/rpcib at 0" 0 "rpcib" "/ib/eibnx at 0" 0 "eibnx" "/ib/rdsib at 0" 0 "rdsib" "/ib/daplt at 0" 0 "daplt" "/ib/rdsv3 at 0" 0 "rdsv3" "/ib/sol_uverbs at 0" 0 "sol_uverbs" "/ib/sol_umad at 0" 0 "sol_umad" "/ib/sdpib at 0" 0 "sdpib" "/ib/iser at 0" 0 "iser" "/ib/srpt at 0" 0 "srpt" "/options" 0 "options" "/pseudo" 0 "pseudo" "/scsi_vhci" 0 "scsi_vhci" "/scsi_vhci/disk at g5000c500564c3973" 12 "sd" "/scsi_vhci/disk at g5000c500564d9473" 13 "sd" "/scsi_vhci/disk at g5000c500564daa33" 14 "sd" "/scsi_vhci/disk at g5000c500564d93b3" 15 "sd" "/scsi_vhci/disk at g5000c500564d93c3" 16 "sd" "/scsi_vhci/disk at g5000c500564dbaa3" 17 "sd" "/scsi_vhci/disk at g5000c500564d879b" 18 "sd" "/scsi_vhci/disk at g5000c500564da5a3" 19 "sd" "/scsi_vhci/disk at g5000c500564db613" 20 "sd" "/scsi_vhci/disk at g5000c500564d8853" 21 "sd" "/scsi_vhci/disk at g5000c500564df953" 22 "sd" "/scsi_vhci/disk at g5000c500564d8a63" 23 "sd" "/scsi_vhci/disk at g5000c500564d9407" 24 "sd" "/scsi_vhci/disk at g5000c500564dca27" 25 "sd" "/scsi_vhci/disk at g5000c500564da3e7" 26 "sd" "/scsi_vhci/disk at g5000c500564daab7" 27 "sd" "/scsi_vhci/disk at g5000c500564da3cb" 28 "sd" "/scsi_vhci/disk at g5000c500564dba5b" 29 "sd" "/scsi_vhci/disk at g5000c500564d98db" 30 "sd" "/scsi_vhci/disk at g5000c500564da01b" 31 "sd" "/scsi_vhci/disk at g5000c500564d935f" 32 "sd" "/scsi_vhci/disk at g5000c500564da8cf" 33 "sd" "/scsi_vhci/disk at g5000c500563a5a6f" 34 "sd" "/scsi_vhci/disk at g5000c500564dcadf" 35 "sd" "/scsi_vhci/disk at g5000c500564d962f" 36 "sd" "/scsi_vhci/disk at g5000c500564da01f" 37 "sd" "/scsi_vhci/disk at g5000c500564d931f" 38 "sd" "/scsi_vhci/disk at g5000c500564dfa0f" 39 "sd" "/scsi_vhci/disk at g5000c500564d972b" 40 "sd" "/scsi_vhci/disk at g5000c500564e25f3" 41 "sd" "/scsi_vhci/disk at g5000c500564c23d3" 42 "sd" "/scsi_vhci/disk at g5000c500564d9f7b" 43 "sd" "/scsi_vhci/disk at g5000c500564d967b" 44 "sd" "/scsi_vhci/disk at g5000c500564daadb" 45 "sd" "/scsi_vhci/disk at g5000c500564bf7c3" 46 "sd" "/scsi_vhci/disk at g5000c500564d898b" 47 "sd" "/scsi_vhci/disk at g5000c500564e2673" 48 "sd" "/scsi_vhci/disk at g5000c500564e25df" 49 "sd" "/scsi_vhci/disk at g5000c500564da313" 50 "sd" "/scsi_vhci/disk at g5000c500564da787" 51 "sd" "/scsi_vhci/disk at g5000c500564de6e3" 52 "sd" "/scsi_vhci/disk at g5000c500564df58f" 53 "sd" "/scsi_vhci/disk at g5000c500564da3b3" 54 "sd" "/scsi_vhci/disk at g5000c500564d94df" 55 "sd" "/scsi_vhci/disk at g5000c500564dd063" 56 "sd" "/scsi_vhci/disk at g5000c500564da2ef" 57 "sd" "/scsi_vhci/disk at g5000c500564da593" 58 "sd" "/scsi_vhci/disk at g5000c500564d94c7" 59 "sd" "/scsi_vhci/disk at g5000c500564da9df" 60 "sd" "/scsi_vhci/disk at g5000c500564d94a7" 61 "sd" "/scsi_vhci/disk at g5000c500564dc53f" 62 "sd" "/scsi_vhci/disk at g5000c500564d959f" 63 "sd" "/scsi_vhci/disk at g5000c500564d8873" 64 "sd" "/scsi_vhci/disk at g5000c500564db697" 65 "sd" "/scsi_vhci/disk at g5000c500564df15b" 66 "sd" "/scsi_vhci/disk at g5000c500564df557" 67 "sd" "/pci at 0,0" 0 "npe" "/pci at 0,0/isa at 1f" 0 "isa" "/pci at 0,0/isa at 1f/pit_beep" 0 "pit_beep" "/pci at 0,0/isa at 1f/asy at 1,3f8" 0 "asy" "/pci at 0,0/isa at 1f/asy at 1,2f8" 1 "asy" "/pci at 0,0/pci15d9,628 at 1a" 0 "ehci" "/pci at 0,0/pci15d9,628 at 1a/hub at 1" 0 "hubd" "/pci at 0,0/pci15d9,628 at 1a/hub at 1/device at 6" 0 "usb_mid" "/pci at 0,0/pci15d9,628 at 1a/hub at 1/device at 6/mouse at 0" 0 "hid" "/pci at 0,0/pci15d9,628 at 1a/hub at 1/device at 6/keyboard at 1" 1 "hid" "/pci at 0,0/pci15d9,628 at 1d" 1 "ehci" "/pci at 0,0/pci15d9,628 at 1d/hub at 1" 1 "hubd" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 3" 2 "hubd" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 3/device at 1" 1 "usb_mid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 3/device at 1/keyboard at 0" 2 "hid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 3/device at 1/input at 1" 3 "hid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 3/device at 1/mouse at 2" 4 "hid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 3/device at 1/mouse at 3" 5 "hid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 1" 3 "hubd" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 1/device at 1" 2 "usb_mid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 1/device at 1/keyboard at 0" 6 "hid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 1/device at 1/input at 1" 7 "hid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 1/device at 1/mouse at 2" 8 "hid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 1/device at 1/mouse at 3" 9 "hid" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 1/storage at 3" 0 "scsa2usb" "/pci at 0,0/pci15d9,628 at 1d/hub at 1/hub at 1/storage at 3/disk at 0,0" 68 "sd" "/pci at 0,0/pci15d9,628 at 1f,2" 0 "ahci" "/pci at 0,0/pci15d9,628 at 1f,2/disk at 2,0" 0 "sd" "/pci at 0,0/pci15d9,628 at 1f,2/disk at 3,0" 1 "sd" "/pci at 0,0/pci8086,3c03 at 1,1" 1 "pcieb" "/pci at 0,0/pci8086,3c03 at 1,1/pci15d9,1521 at 0" 0 "igb" "/pci at 0,0/pci8086,3c03 at 1,1/pci15d9,1521 at 0,1" 1 "igb" "/pci at 0,0/pci8086,3c04 at 2" 2 "pcieb" "/pci at 0,0/pci8086,3c04 at 2/pci15b3,36 at 0" 0 "hermon" "/pci at 0,0/pci8086,3c04 at 2/pci15b3,36 at 0/ibport at 1,0,ipib" 0 "ibp" "/pci at 0,0/pci8086,3c04 at 2/pci15b3,36 at 0/ibport at 2,0,ipib" 1 "ibp" "/pci at 0,0/pci8086,3c0a at 3,2" 4 "pcieb" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0" 0 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0" 3 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/smp at w50030480005f72bf" 0 "smp" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/disk at w5000a72b300893f1,0" 2 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/disk at w5000a72b300893e9,0" 3 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/disk at w5000a72b300893eb,0" 4 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/enclosure at w50030480005f72bd,0" 0 "ses" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/disk at w5000a72b300893ed,0" 5 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/disk at w5000a72b30086bbd,0" 6 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0" 2 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/medium-changer at w5000e11156304003,1" 3 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/medium-changer at w5000e11156304003,1" 1 "sgen" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0" 4 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/medium-changer at w5000e11156304002,1" 3 "sgen" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f" 4 "mpt_sas" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/smp at w50030480005f723f" 1 "smp" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/disk at w5000a72a300893f1,0" 7 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/disk at w5000a72a300893e9,0" 8 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/disk at w5000a72a300893eb,0" 9 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/enclosure at w50030480005f723d,0" 1 "ses" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/disk at w5000a72a300893ed,0" 10 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/disk at w5000a72a30086bbd,0" 11 "sd" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0" 0 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/medium-changer at w5000e11156304002,1" 1 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/medium-changer at w5000e11156304002,1" 0 "sgen" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0" 5 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/medium-changer at w5000e11156304003,1" 2 "sgen" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at v0" 5 "mpt_sas" "/pci at 0,0/pci8086,1d3e at 11" 5 "pcieb" "/pci at 0,0/pci8086,244e at 1e" 0 "pci_pci" "/pci at 0,0/pci8086,244e at 1e/display at 3" 0 "vgatext" "/fw" 0 "acpinex" "/fw/sb at 0" 1 "acpinex" "/fw/sb at 0/socket at 0" 2 "acpinex" "/fw/sb at 0/socket at 0/cpu at 0" 0 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 2" 2 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 4" 4 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 6" 6 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 8" 8 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 10" 10 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 1" 1 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 3" 3 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 5" 5 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 7" 7 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 9" 9 "cpudrv" "/fw/sb at 0/socket at 0/cpu at 11" 11 "cpudrv" "/fw/sb at 0/socket at 1" 3 "acpinex" "/fw/sb at 0/socket at 1/cpu at 12" 12 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 14" 14 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 16" 16 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 18" 18 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 20" 20 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 22" 22 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 13" 13 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 15" 15 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 17" 17 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 19" 19 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 21" 21 "cpudrv" "/fw/sb at 0/socket at 1/cpu at 23" 23 "cpudrv" "/pci at 78,0" 1 "npe" "/pci at 79,0" 2 "npe" "/pci at 79,0/pci8086,3c02 at 1" 6 "pcieb" "/pci at 79,0/pci8086,3c02 at 1/pci1000,3040 at 0" 1 "mpt_sas" "/pci at 79,0/pci8086,3c02 at 1/pci1000,3040 at 0/iport at v0" 6 "mpt_sas" "/pci at 79,0/pci8086,3c02 at 1/pci1000,3040 at 0/iport at f0" 8 "mpt_sas" "/pci at 79,0/pci8086,3c02 at 1/pci1000,3040 at 0/iport at f0/smp at w5003048001195e7f" 2 "smp" "/pci at 79,0/pci8086,3c02 at 1/pci1000,3040 at 0/iport at f0/enclosure at w5003048001195e7d,0" 3 "ses" "/pci at 79,0/pci8086,3c02 at 1/pci1000,3040 at 0/iport at f" 10 "mpt_sas" "/pci at 79,0/pci8086,3c02 at 1/pci1000,3040 at 0/iport at f/smp at w500304800119617f" 4 "smp" "/pci at 79,0/pci8086,3c02 at 1/pci1000,3040 at 0/iport at f/enclosure at w500304800119617d,0" 4 "ses" "/pci at 79,0/pci8086,3c04 at 2" 7 "pcieb" "/pci at 79,0/pci8086,3c04 at 2/pci8086,3 at 0" 0 "ixgbe" "/pci at 79,0/pci8086,3c04 at 2/pci8086,3 at 0,1" 1 "ixgbe" "/pci at 79,0/pci8086,3c08 at 3" 8 "pcieb" "/pci at 79,0/pci8086,3c08 at 3/pci1000,3040 at 0" 2 "mpt_sas" "/pci at 79,0/pci8086,3c08 at 3/pci1000,3040 at 0/iport at v0" 7 "mpt_sas" "/pci at 79,0/pci8086,3c08 at 3/pci1000,3040 at 0/iport at f0" 9 "mpt_sas" "/pci at 79,0/pci8086,3c08 at 3/pci1000,3040 at 0/iport at f0/smp at w5003048001195eff" 3 "smp" "/pci at 79,0/pci8086,3c08 at 3/pci1000,3040 at 0/iport at f0/enclosure at w5003048001195efd,0" 2 "ses" "/pci at 79,0/pci8086,3c08 at 3/pci1000,3040 at 0/iport at f" 11 "mpt_sas" "/pci at 79,0/pci8086,3c08 at 3/pci1000,3040 at 0/iport at f/smp at w50030480011961ff" 5 "smp" "/pci at 79,0/pci8086,3c08 at 3/pci1000,3040 at 0/iport at f/enclosure at w50030480011961fd,0" 5 "ses" "/fcoe" 0 "fcoe" > - Garrett > > On Oct 7, 2013, at 11:13 AM, Paul B. Henson wrote: > >> On Mon, Oct 07, 2013 at 08:06:25AM -0700, Garrett D'Amore wrote: >>> If you're seeing hangs like this, I would appreciate knowing the hardware configuration. Prtconf -vp might be helpful. Presumably this is the result of one or more devices not doing the right thing for quiesce(). >> I had the same problem on a supermicro box: >> >> Case: 836BA-R920B >> Motherboard: X9SRI-F >> BIOS: 2.0a 04/19/2013 >> CPU: Intel Xeon E5-2620 >> Memory: 3 x Crucial CT2KIT102472BB160B (6 DIMMs, 48G) >> HBA: LSI 9201-16i >> >> prtconf attached. I disabled fastboot and don't care too much about >> fixing it; it gets rebooted very infrequently and probably 4 times out >> of 5 when I do reboot it I need to get into the bios or do something of >> that nature and ended up getting annoyed that I had to reboot it twice >> because I forgot about fastboot ;). >> >> > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature URL: From tom.robinson at motec.com.au Fri Oct 11 04:04:19 2013 From: tom.robinson at motec.com.au (Tom Robinson) Date: Fri, 11 Oct 2013 15:04:19 +1100 Subject: [OmniOS-discuss] SAS tape driver In-Reply-To: <5253A25C.2020306@motec.com.au> References: <52523A90.1070700@motec.com.au> <6519B345-5BC9-45A0-89BA-8E7009E33424@dey-sys.com> <5253A25C.2020306@motec.com.au> Message-ID: <525778C3.9040204@motec.com.au> Hi, I've been banging on the IBMtape driver configuration but I can't get it to work. I found that I actually won't need it as I can use a combination of st and sgen drivers. st does the tape and sgen does the library robot via the mtx utility (installed from openCSW). I hope this helps someone else sometime so here's my configuration: I actually commented out the example entries in /kernel/drv/st.conf and /kernel/drv/sgen.conf so these files are effectively empty. The SAS addressing is different to the examples and the drivers seem to dynamically pick up the target addresses and LUNs anyway. # add_drv st # add_drv sgen For each target address, the tape driver is on LUN 0 and the library on LUN 1. Check the /etc/path_to_inst. # grep -e '\' -e '\' /etc/path_to_inst "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0" 2 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/medium-changer at w5000e11156304003,1" 3 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/medium-changer at w5000e11156304003,1" 1 "sgen" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0" 4 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/medium-changer at w5000e11156304002,1" 3 "sgen" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0" 0 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/medium-changer at w5000e11156304002,1" 1 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/medium-changer at w5000e11156304002,1" 0 "sgen" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0" 5 "st" "/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/medium-changer at w5000e11156304003,1" 2 "sgen" The st driver wants to sit on the same address/LUN as sgen for the library. I tried removing it but it kept re-appearing so I left in there. # update_drv -av -i '"scsiclass,01"' st # update_drv -av -i '"scsiclass,08"' sgen (not sure about ownership or permissions?) The devices are created! # ls -l /dev/scsi/changer/ total 1 lrwxrwxrwx 1 root root 107 Oct 11 14:23 c1t5000E11156304003d1 -> ../../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/medium-changer at w5000e11156304003,1:changer lrwxrwxrwx 1 root root 108 Oct 11 14:23 c2t5000E11156304002d1 -> ../../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/medium-changer at w5000e11156304002,1:changer # ls -l /dev/rmt total 24 lrwxrwxrwx 1 root root 87 Oct 11 14:22 0 -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0: lrwxrwxrwx 1 root root 88 Oct 11 14:22 0b -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:b lrwxrwxrwx 1 root root 89 Oct 11 14:22 0bn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:bn lrwxrwxrwx 1 root root 88 Oct 11 14:22 0c -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:c lrwxrwxrwx 1 root root 89 Oct 11 14:22 0cb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:cb lrwxrwxrwx 1 root root 90 Oct 11 14:22 0cbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:cbn lrwxrwxrwx 1 root root 89 Oct 11 14:22 0cn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:cn lrwxrwxrwx 1 root root 88 Oct 11 14:22 0h -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:h lrwxrwxrwx 1 root root 89 Oct 11 14:22 0hb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:hb lrwxrwxrwx 1 root root 90 Oct 11 14:22 0hbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:hbn lrwxrwxrwx 1 root root 89 Oct 11 14:22 0hn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:hn lrwxrwxrwx 1 root root 88 Oct 11 14:22 0l -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:l lrwxrwxrwx 1 root root 89 Oct 11 14:22 0lb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:lb lrwxrwxrwx 1 root root 90 Oct 11 14:22 0lbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:lbn lrwxrwxrwx 1 root root 89 Oct 11 14:22 0ln -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:ln lrwxrwxrwx 1 root root 88 Oct 11 14:22 0m -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:m lrwxrwxrwx 1 root root 89 Oct 11 14:22 0mb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:mb lrwxrwxrwx 1 root root 90 Oct 11 14:22 0mbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:mbn lrwxrwxrwx 1 root root 89 Oct 11 14:22 0mn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:mn lrwxrwxrwx 1 root root 88 Oct 11 14:22 0n -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:n lrwxrwxrwx 1 root root 88 Oct 11 14:22 0u -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:u lrwxrwxrwx 1 root root 89 Oct 11 14:22 0ub -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:ub lrwxrwxrwx 1 root root 90 Oct 11 14:22 0ubn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:ubn lrwxrwxrwx 1 root root 89 Oct 11 14:22 0un -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304003,0:un lrwxrwxrwx 1 root root 88 Oct 11 14:22 1 -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0: lrwxrwxrwx 1 root root 89 Oct 11 14:22 1b -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:b lrwxrwxrwx 1 root root 90 Oct 11 14:22 1bn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:bn lrwxrwxrwx 1 root root 89 Oct 11 14:22 1c -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:c lrwxrwxrwx 1 root root 90 Oct 11 14:22 1cb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:cb lrwxrwxrwx 1 root root 91 Oct 11 14:22 1cbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:cbn lrwxrwxrwx 1 root root 90 Oct 11 14:22 1cn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:cn lrwxrwxrwx 1 root root 89 Oct 11 14:22 1h -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:h lrwxrwxrwx 1 root root 90 Oct 11 14:22 1hb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:hb lrwxrwxrwx 1 root root 91 Oct 11 14:22 1hbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:hbn lrwxrwxrwx 1 root root 90 Oct 11 14:22 1hn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:hn lrwxrwxrwx 1 root root 89 Oct 11 14:22 1l -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:l lrwxrwxrwx 1 root root 90 Oct 11 14:22 1lb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:lb lrwxrwxrwx 1 root root 91 Oct 11 14:22 1lbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:lbn lrwxrwxrwx 1 root root 90 Oct 11 14:22 1ln -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:ln lrwxrwxrwx 1 root root 89 Oct 11 14:22 1m -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:m lrwxrwxrwx 1 root root 90 Oct 11 14:22 1mb -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:mb lrwxrwxrwx 1 root root 91 Oct 11 14:22 1mbn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:mbn lrwxrwxrwx 1 root root 90 Oct 11 14:22 1mn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:mn lrwxrwxrwx 1 root root 89 Oct 11 14:22 1n -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:n lrwxrwxrwx 1 root root 89 Oct 11 14:22 1u -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:u lrwxrwxrwx 1 root root 90 Oct 11 14:22 1ub -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:ub lrwxrwxrwx 1 root root 91 Oct 11 14:22 1ubn -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:ubn lrwxrwxrwx 1 root root 90 Oct 11 14:22 1un -> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304002,0:un Ok, still reading? Here's cfgadm output: # cfgadm -av ...8<... c1::rmt/0 connected configured unknown IBM ULT3580-TD5 unavailable tape n /devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f:scsi::rmt/0 c1::scsi/changer/c1t5000E1115 connected configured unknown IBM 3573-TL unavailable med-changer n /devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f:scsi::scsi/changer/c1t5000E11156304003d1 ...8<... Make sure you reboot -- -r to confirm the configuration. Here's mt and mtx output: # mt -f /dev/rmt/0 config "IBM ULT3580-TD5", "IBM ULT3580-TD5 ", "CFGIBMULT3580TD5"; CFGIBMULT3580TD5 = 2,0x3B,0,0x1018619,4,0x46,0x46,0x58,0x58,3,60,1500,600,16920,780,780,16380; # mt -f /dev/rmt/0 status IBM ULT3580-TD5 tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 # mtx -f /dev/scsi/changer/c1t5000E11156304003d1 inquiry Product Type: Medium Changer Vendor ID: 'IBM ' Product ID: '3573-TL ' Revision: 'B.90' Attached Changer API: No # mtx -f /dev/scsi/changer/c1t5000E11156304003d1 status Storage Changer /dev/scsi/changer/c1t5000E11156304003d1:1 Drives, 24 Slots ( 1 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag = 050CHOL5 Storage Element 1:Empty Storage Element 2:Full :VolumeTag=051CHOL5 Storage Element 3:Full :VolumeTag=052CHOL5 Storage Element 4:Full :VolumeTag=053CHOL5 Storage Element 5:Full :VolumeTag=054CHOL5 Storage Element 6:Empty Storage Element 7:Empty Storage Element 8:Empty Storage Element 9:Empty Storage Element 10:Empty Storage Element 11:Empty Storage Element 12:Empty Storage Element 13:Empty Storage Element 14:Empty Storage Element 15:Empty Storage Element 16:Empty Storage Element 17:Empty Storage Element 18:Empty Storage Element 19:Empty Storage Element 20:Empty Storage Element 21:Empty Storage Element 22:Empty Storage Element 23:Empty Storage Element 24 IMPORT/EXPORT:Empty Regards, Tom On 08/10/13 17:12, Tom Robinson wrote: > Hi Garret, > > Thanks for your help on this. > > At the moment I'm actually trying to get to grips with the device management by trying to restore > the installed settings I had before I attempted the IBMtape driver installation. My thinking was > that if I can restore those settings I will understand the whole set up a bit better. > > So I have re-established the 'st' driver by doing the following: > > # rem_drv st > Driver (st) not installed. > > # add_drv st > devfsadm: driver failed to attach: st > > # modinfo -cw | grep '\' > 288 1 st LOADED/INSTALLED > > # update_drv -av -i '"scsiclass,01"' st > exit status = 0 > devfsadm[957]: verbose: symlink /dev/rmt/0 -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0: > devfsadm[957]: verbose: symlink /dev/rmt/0n -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:n > devfsadm[957]: verbose: symlink /dev/rmt/0b -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:b > devfsadm[957]: verbose: symlink /dev/rmt/0bn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:bn > devfsadm[957]: verbose: symlink /dev/rmt/0l -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:l > devfsadm[957]: verbose: symlink /dev/rmt/0m -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:m > devfsadm[957]: verbose: symlink /dev/rmt/0h -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:h > devfsadm[957]: verbose: symlink /dev/rmt/0c -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:c > devfsadm[957]: verbose: symlink /dev/rmt/0u -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:u > devfsadm[957]: verbose: symlink /dev/rmt/0ln -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:ln > devfsadm[957]: verbose: symlink /dev/rmt/0mn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:mn > devfsadm[957]: verbose: symlink /dev/rmt/0hn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:hn > devfsadm[957]: verbose: symlink /dev/rmt/0cn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:cn > devfsadm[957]: verbose: symlink /dev/rmt/0un -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:un > devfsadm[957]: verbose: symlink /dev/rmt/0lb -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:lb > devfsadm[957]: verbose: symlink /dev/rmt/0mb -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:mb > devfsadm[957]: verbose: symlink /dev/rmt/0hb -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:hb > devfsadm[957]: verbose: symlink /dev/rmt/0cb -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:cb > devfsadm[957]: verbose: symlink /dev/rmt/0ub -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:ub > devfsadm[957]: verbose: symlink /dev/rmt/0lbn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:lbn > devfsadm[957]: verbose: symlink /dev/rmt/0mbn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:mbn > devfsadm[957]: verbose: symlink /dev/rmt/0hbn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:hbn > devfsadm[957]: verbose: symlink /dev/rmt/0cbn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:cbn > devfsadm[957]: verbose: symlink /dev/rmt/0ubn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0:ubn > devfsadm[957]: verbose: symlink /dev/rmt/1 -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0: > devfsadm[957]: verbose: symlink /dev/rmt/1n -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:n > devfsadm[957]: verbose: symlink /dev/rmt/1b -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:b > devfsadm[957]: verbose: symlink /dev/rmt/1bn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:bn > devfsadm[957]: verbose: symlink /dev/rmt/1l -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:l > devfsadm[957]: verbose: symlink /dev/rmt/1m -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:m > devfsadm[957]: verbose: symlink /dev/rmt/1h -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:h > devfsadm[957]: verbose: symlink /dev/rmt/1c -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:c > devfsadm[957]: verbose: symlink /dev/rmt/1u -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:u > devfsadm[957]: verbose: symlink /dev/rmt/1ln -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:ln > devfsadm[957]: verbose: symlink /dev/rmt/1mn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:mn > devfsadm[957]: verbose: symlink /dev/rmt/1hn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:hn > devfsadm[957]: verbose: symlink /dev/rmt/1cn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:cn > devfsadm[957]: verbose: symlink /dev/rmt/1un -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:un > devfsadm[957]: verbose: symlink /dev/rmt/1lb -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:lb > devfsadm[957]: verbose: symlink /dev/rmt/1mb -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:mb > devfsadm[957]: verbose: symlink /dev/rmt/1hb -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:hb > devfsadm[957]: verbose: symlink /dev/rmt/1cb -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:cb > devfsadm[957]: verbose: symlink /dev/rmt/1ub -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:ub > devfsadm[957]: verbose: symlink /dev/rmt/1lbn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:lbn > devfsadm[957]: verbose: symlink /dev/rmt/1mbn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:mbn > devfsadm[957]: verbose: symlink /dev/rmt/1hbn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:hbn > devfsadm[957]: verbose: symlink /dev/rmt/1cbn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:cbn > devfsadm[957]: verbose: symlink /dev/rmt/1ubn -> > ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f/tape at w5000e11156304002,0:ubn > > Now I need to try again with the IBMtape driver. > > Regards, > Tom > > > On 08/10/13 02:05, Garrett D'Amore wrote: >> Need to see the IBM changes to /etc/driver_aliases. My guess is that this is the source of the problem. If you know the name of the kernel driver for the IBM tape module, you could rem_drv it. A reboot may be required for the change to take effect. >> >> - Garrett >> >> On Oct 6, 2013, at 9:37 PM, Tom Robinson wrote: >> >>> Hi, >>> >>> I'm running OmniOS r151006 on a SuperMicro X9 motherboard. >>> >>> I'm trying to configure an IBM TS3100 tape library with not much luck. >>> >>> I used to see the tape through the 'st' driver (at least I think it was the st driver). But after >>> following the IBM documentation and installing the IBMtape driver a I can no longer see the tape. >>> >>> I'm also having issues with the 'reboot -- -r' command hanging on 'rebooting...' message and am >>> wondering if that is compounding the issue (see separate thread). >>> >>> After no luck with the IBMtape driver, I am now trying to revert to the st driver and not having any >>> luck with that either. >>> >>> The device links under /dev/rmt had to be removed as part of the IBMtape setup but they were similar >>> to the following listing: >>> lrwxrwxrwx 1 root root 88 Sep 20 03:18 0 -> >>> ../../devices/pci at 0,0/pci8086,3c0a at 3,2/pci1000,3020 at 0/iport at f0/tape at w5000e11156304003,0: >>> >>> I now have nothing listed under /dev/rmt and the st module appears not to load: >>> # modinfo -cw | grep '\' >>> 287 11 st UNLOADED/UNINSTALLED >>> >>> # modload -p drv/st >>> can't load module: No such device or address >>> >>> # modload -p drv/amd64/st >>> can't load module: No such device or address >>> >>> (not sure which of the above is the correct driver actually) >>> >>> Any help is much appreciated. >>> >>> Kind regards, >>> Tom >>> >>> More info: >>> # uname -m >>> i86pc >>> >>> /kernel/drv/st.conf >>> name="st" class="scsi" target=0 lun=0; >>> name="st" class="scsi" target=1 lun=0; >>> name="st" class="scsi" target=2 lun=0; >>> name="st" class="scsi" target=3 lun=0; >>> name="st" class="scsi" target=4 lun=0; >>> name="st" class="scsi" target=5 lun=0; >>> name="st" class="scsi" target=6 lun=0; >>> >>> /etc/driver_aliases >>> ... >>> st "scsiclass,01" >>> ... >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Tom Robinson >>> IT Manager/System Administrator >>> >>> MoTeC Pty Ltd >>> >>> 121 Merrindale Drive >>> Croydon South >>> 3136 Victoria >>> Australia >>> >>> T: +61 3 9761 5050 >>> F: +61 3 9761 5051 >>> E: tom.robinson at motec.com.au >>> >>> >>> _______________________________________________ >>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 254 bytes Desc: OpenPGP digital signature URL: From mmabis at vmware.com Fri Oct 11 15:26:59 2013 From: mmabis at vmware.com (Matthew Mabis) Date: Fri, 11 Oct 2013 08:26:59 -0700 (PDT) Subject: [OmniOS-discuss] vSphere 5.5 and OmniOS nic issues In-Reply-To: <1794418794.81618257.1381505135174.JavaMail.root@vmware.com> Message-ID: <1617113765.81619358.1381505218997.JavaMail.root@vmware.com> Hey All, Was wondering where your stance is with vSphere 5.5 and Deploying OmniOS with the issues i have seen so far i am having issues with the E1000 Nic where i believe disabling TOE on the VM resolves the issue but i have heard of some vmxnet3 issues with high CPU consumption as well.. Is there a guideline to utilize OmniOS with vSphere 5.5? -------------- next part -------------- An HTML attachment was scrubbed... URL: From esproul at omniti.com Fri Oct 11 15:35:57 2013 From: esproul at omniti.com (Eric Sproul) Date: Fri, 11 Oct 2013 11:35:57 -0400 Subject: [OmniOS-discuss] Shared library error In-Reply-To: References: Message-ID: Michael, I can't reproduce this on the latest published bits (omnios-f62543a 2013.09.30). Can you share the output of `modinfo` from your system? Also, you're using the packages from our repo, and not building your own copy, correct? Eric On Wed, Oct 2, 2013 at 2:38 PM, outlook wrote: > It's been like that for quite sometime now. I pkg update my omnios bloody box weekly only to revert back. Hope 151008, which should be out midmonth, will be sorted. Bloody is expected to have that sort of problems from time to time. > > Chavdar > > > --- Original Message --- > > From: "Michael Rasmussen" > Sent: 2 October 2013 19:18 > To: "omnios-discuss" > Subject: [OmniOS-discuss] Shared library error > > Hi List, > > cat /etc/release > OmniOS v11 r151007 > Copyright 2013 OmniTI Computer Consulting, Inc. All rights reserved. > Use is subject to license terms. > > mdb -k > ld.so.1: mdb: fatal: relocation error: file /usr/bin/amd64/mdb: symbol > kvm_namelist: referenced symbol not found > Killed > > -- > Hilsen/Regards > Michael Rasmussen > > Get my public GnuPG keys: > michael rasmussen cc > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E > mir datanom net > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C > mir miras org > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 > -------------------------------------------------------------- > When a fly lands on the ceiling, does it do a half roll or a half loop? > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > From fabio at fabiorabelo.wiki.br Fri Oct 11 15:47:02 2013 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Fri, 11 Oct 2013 12:47:02 -0300 Subject: [OmniOS-discuss] LACP how-to Message-ID: Hi to all I am trying to get a dual port 10GB network card to work with a newly released 10GB switcher from Netgear, and been found lots of different how-to guides, some really really different from each other . Someone please can point me to the more up to date one ? I am running stable ( r151006 ) Thanks in advance ... F?bio Rabelo From mir at miras.org Fri Oct 11 17:45:52 2013 From: mir at miras.org (Michael Rasmussen) Date: Fri, 11 Oct 2013 19:45:52 +0200 Subject: [OmniOS-discuss] Shared library error In-Reply-To: References: Message-ID: <20131011194552.09e7adf7@sleipner.datanom.net> Hi Eric, On Fri, 11 Oct 2013 11:35:57 -0400 Eric Sproul wrote: > I can't reproduce this on the latest published bits (omnios-f62543a > 2013.09.30). Can you share the output of `modinfo` from your system? > Also, you're using the packages from our repo, and not building your > own copy, correct? > Every package is installed from official omniti repo except the ones which is installed as part of napp-it. Output from modinfo is attached as file. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- Sorry. I just realized this sentance makes no sense :) -- Ian Main -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: modinfo.txt URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From mayuresh at kathe.in Sat Oct 12 17:36:08 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Sat, 12 Oct 2013 13:36:08 -0400 Subject: [OmniOS-discuss] gcc : include path settings? Message-ID: <20131012173607.GA27593@wolfman.devio.us> hello, new here, just started off today. i've installed gcc47 from the pkg repository. how do i set the include path for gcc47? simple programs like the one below fail to compile. -- helloworld.c -- #include int main(void) { printf("Hello, World!\n"); return 0; } -- helloworld.c -- overall, the omnios environment feels good, just a bit strange for someone migrating from bsd. :) best, ~mayuresh From cnehren+omnios-discuss at omniti.com Sat Oct 12 17:49:09 2013 From: cnehren+omnios-discuss at omniti.com (Chris Nehren) Date: Sat, 12 Oct 2013 13:49:09 -0400 Subject: [OmniOS-discuss] gcc : include path settings? In-Reply-To: <20131012173607.GA27593@wolfman.devio.us> References: <20131012173607.GA27593@wolfman.devio.us> Message-ID: <20131012174909.GK5066@eschaton.local> On Sat, Oct 12, 2013 at 13:36:08 -0400, Mayuresh Kathe wrote: > hello, new here, just started off today. > i've installed gcc47 from the pkg repository. > how do i set the include path for gcc47? > simple programs like the one below fail to compile. > > -- helloworld.c -- > #include > int main(void) { > printf("Hello, World!\n"); > return 0; > } > -- helloworld.c -- Please show the commandline you're using to build this application, and all output until the next shell prompt. > overall, the omnios environment feels good, just > a bit strange for someone migrating from bsd. :) It's a bit strange at first but, coming from BSD, I think you'll grow to appreciate the minimalism and lack of nonsense that you find in the Linux world. -- Chris Nehren From ben at fluffy.co.uk Sat Oct 12 19:39:38 2013 From: ben at fluffy.co.uk (Ben Summers) Date: Sat, 12 Oct 2013 20:39:38 +0100 Subject: [OmniOS-discuss] ZBEs when moving zones Message-ID: Hello, I'm writing a script to move zones between OmniOS servers, using snapshots zfs send | recv, so I can transfer it while it's running, then do a final snapshot when it's finally down. The problem comes when I come to import it. I get the problem described here: http://everycity.co.uk/alasdair/2010/09/moving-zones-between-servers-on-opensolaris/ However, I have multiple zbes, and so I have to mount the right one on the destination server. Something like: zonecfg -z app0 -f /zones/app0/zone-config zfs set zoned=off rpool/zones/app0/ROOT mount -F zfs rpool/zones/app0/ROOT/zbe-2 /zones/app0/root zoneadm -z app0 attach zoneadm -z app0 boot And this works. Rebooting gets the right BE. But I have no idea why. The org.opensolaris.libbe:active property is 'on' for every one of those zbe datasets. If it's moving between different revisions of OmniOS, it will patch when it's attached. To get all the updates, I do pkg -R /zones/app0/root update This doesn't create a new zbe. I'm mildly concerned something won't be quite right in the future, as I can't see why it appears to be doing the right thing. Thanks for any advice on how to do this properly! Ben From jesus at omniti.com Sat Oct 12 19:47:12 2013 From: jesus at omniti.com (Theo Schlossnagle) Date: Sat, 12 Oct 2013 15:47:12 -0400 Subject: [OmniOS-discuss] gcc : include path settings? In-Reply-To: <20131012173607.GA27593@wolfman.devio.us> References: <20131012173607.GA27593@wolfman.devio.us> Message-ID: You likely don't have any system headers installed. Those come in the system/header package. On Sat, Oct 12, 2013 at 1:36 PM, Mayuresh Kathe wrote: > hello, new here, just started off today. > i've installed gcc47 from the pkg repository. > how do i set the include path for gcc47? > simple programs like the one below fail to compile. > > -- helloworld.c -- > #include > int main(void) { > printf("Hello, World!\n"); > return 0; > } > -- helloworld.c -- > > overall, the omnios environment feels good, just > a bit strange for someone migrating from bsd. :) > > best, > > ~mayuresh > > _______________________________________________ > 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: From mayuresh at kathe.in Sun Oct 13 03:18:54 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Sat, 12 Oct 2013 23:18:54 -0400 Subject: [OmniOS-discuss] scheme9 fails to compile Message-ID: <20131013031854.GA11882@wolfman.devio.us> hello, tried compiling scheme9, available at; http://www.t3x.org/ (main site), http://devio.us/~mayuresh/s9fes.tgz (directly). the compilation output errors are below; Undefined first referenced symbol in file pp_curs_endwin s9.o ld: fatal: symbol referencing errors. No output written to s9 collect2: error: ld returned 1 exit status make: Fatal error: Command failed for target `s9' compiles cleanly under openbsd 5.3 and ubuntu server 13.04. best. ~mayuresh From eugen at leitl.org Sun Oct 13 08:03:16 2013 From: eugen at leitl.org (Eugen Leitl) Date: Sun, 13 Oct 2013 10:03:16 +0200 Subject: [OmniOS-discuss] napp-it OmniOS appliance boots very slow, used to work on OpenIndiana Message-ID: <20131013080316.GE10405@leitl.org> Not sure what is going on, can anyone spot a smoking gun in this dmesg? System doesn't reboot/init 5 doesn't shutdown either. October 13, 2013 10:00:22 AM CEST Oct 13 09:56:56 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:56:56 oozfs mpt0 Firmware version v2.0.50.0 (?) Oct 13 09:56:56 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:56:56 oozfs mpt0: IOC Operational. Oct 13 09:56:56 oozfs scsi: [ID 243001 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:56:56 oozfs mpt0: Initiator WWNs: 0x500605b0017c1b20-0x500605b0017c1b27 Oct 13 09:56:56 oozfs pcieb: [ID 586369 kern.info] PCIE-device: pci1000,3050 at 0, mpt_sas0 Oct 13 09:56:56 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1000,3050 at 0, mpt_sas0 Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] mpt_sas0 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 Oct 13 09:56:56 oozfs scsi: [ID 583861 kern.info] mpt_sas5 at mpt_sas0: scsi-iport 8 Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] mpt_sas5 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 8 Oct 13 09:56:56 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 8 (mpt_sas5) online Oct 13 09:56:56 oozfs scsi: [ID 583861 kern.info] sd6 at scsi_vhci0: unit-address g5000c5000fd2e794: f_sym Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] sd6 is /scsi_vhci/disk at g5000c5000fd2e794 Oct 13 09:56:56 oozfs genunix: [ID 408114 kern.info] /scsi_vhci/disk at g5000c5000fd2e794 (sd6) online Oct 13 09:56:56 oozfs genunix: [ID 483743 kern.info] /scsi_vhci/disk at g5000c5000fd2e794 (sd6) multipath status: degraded: path 1 mpt_sas5/disk at w5000c5000fd2e794,0 is online Oct 13 09:56:56 oozfs scsi: [ID 583861 kern.info] mpt_sas8 at mpt_sas0: scsi-iport 40 Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] mpt_sas8 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 40 Oct 13 09:56:56 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 40 (mpt_sas8) online Oct 13 09:56:56 oozfs scsi: [ID 583861 kern.info] sd9 at scsi_vhci0: unit-address g5000c5000fd39d53: f_sym Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] sd9 is /scsi_vhci/disk at g5000c5000fd39d53 Oct 13 09:56:56 oozfs genunix: [ID 408114 kern.info] /scsi_vhci/disk at g5000c5000fd39d53 (sd9) online Oct 13 09:56:56 oozfs genunix: [ID 483743 kern.info] /scsi_vhci/disk at g5000c5000fd39d53 (sd9) multipath status: degraded: path 2 mpt_sas8/disk at w5000c5000fd39d53,0 is online Oct 13 09:56:56 oozfs scsi: [ID 583861 kern.info] mpt_sas3 at mpt_sas0: scsi-iport 2 Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] mpt_sas3 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 2 Oct 13 09:56:56 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 2 (mpt_sas3) online Oct 13 09:56:56 oozfs scsi: [ID 583861 kern.info] sd4 at scsi_vhci0: unit-address g5000c500098be9dd: f_sym Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] sd4 is /scsi_vhci/disk at g5000c500098be9dd Oct 13 09:56:56 oozfs genunix: [ID 408114 kern.info] /scsi_vhci/disk at g5000c500098be9dd (sd4) online Oct 13 09:56:56 oozfs genunix: [ID 483743 kern.info] /scsi_vhci/disk at g5000c500098be9dd (sd4) multipath status: degraded: path 3 mpt_sas3/disk at w5000c500098be9dd,0 is online Oct 13 09:56:56 oozfs scsi: [ID 583861 kern.info] mpt_sas6 at mpt_sas0: scsi-iport 10 Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] mpt_sas6 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 10 Oct 13 09:56:56 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 10 (mpt_sas6) online Oct 13 09:56:56 oozfs scsi: [ID 583861 kern.info] sd7 at scsi_vhci0: unit-address g5000c5000fd37075: f_sym Oct 13 09:56:56 oozfs genunix: [ID 936769 kern.info] sd7 is /scsi_vhci/disk at g5000c5000fd37075 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /scsi_vhci/disk at g5000c5000fd37075 (sd7) online Oct 13 09:56:57 oozfs genunix: [ID 483743 kern.info] /scsi_vhci/disk at g5000c5000fd37075 (sd7) multipath status: degraded: path 4 mpt_sas6/disk at w5000c5000fd37075,0 is online Oct 13 09:56:57 oozfs scsi: [ID 583861 kern.info] mpt_sas9 at mpt_sas0: scsi-iport 80 Oct 13 09:56:57 oozfs genunix: [ID 936769 kern.info] mpt_sas9 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 80 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 80 (mpt_sas9) online Oct 13 09:56:57 oozfs scsi: [ID 583861 kern.info] sd10 at scsi_vhci0: unit-address g5000c50009c73968: f_sym Oct 13 09:56:57 oozfs genunix: [ID 936769 kern.info] sd10 is /scsi_vhci/disk at g5000c50009c73968 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /scsi_vhci/disk at g5000c50009c73968 (sd10) online Oct 13 09:56:57 oozfs genunix: [ID 483743 kern.info] /scsi_vhci/disk at g5000c50009c73968 (sd10) multipath status: degraded: path 5 mpt_sas9/disk at w5000c50009c73968,0 is online Oct 13 09:56:57 oozfs scsi: [ID 583861 kern.info] mpt_sas7 at mpt_sas0: scsi-iport 20 Oct 13 09:56:57 oozfs genunix: [ID 936769 kern.info] mpt_sas7 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 20 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 20 (mpt_sas7) online Oct 13 09:56:57 oozfs scsi: [ID 583861 kern.info] sd8 at scsi_vhci0: unit-address g5000c5000fd3bc10: f_sym Oct 13 09:56:57 oozfs genunix: [ID 936769 kern.info] sd8 is /scsi_vhci/disk at g5000c5000fd3bc10 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /scsi_vhci/disk at g5000c5000fd3bc10 (sd8) online Oct 13 09:56:57 oozfs genunix: [ID 483743 kern.info] /scsi_vhci/disk at g5000c5000fd3bc10 (sd8) multipath status: degraded: path 6 mpt_sas7/disk at w5000c5000fd3bc10,0 is online Oct 13 09:56:57 oozfs scsi: [ID 583861 kern.info] mpt_sas2 at mpt_sas0: scsi-iport 1 Oct 13 09:56:57 oozfs genunix: [ID 936769 kern.info] mpt_sas2 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 1 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 1 (mpt_sas2) online Oct 13 09:56:57 oozfs scsi: [ID 583861 kern.info] sd3 at scsi_vhci0: unit-address g5000c50009c72c48: f_sym Oct 13 09:56:57 oozfs genunix: [ID 936769 kern.info] sd3 is /scsi_vhci/disk at g5000c50009c72c48 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /scsi_vhci/disk at g5000c50009c72c48 (sd3) online Oct 13 09:56:57 oozfs genunix: [ID 483743 kern.info] /scsi_vhci/disk at g5000c50009c72c48 (sd3) multipath status: degraded: path 7 mpt_sas2/disk at w5000c50009c72c48,0 is online Oct 13 09:56:57 oozfs scsi: [ID 583861 kern.info] mpt_sas4 at mpt_sas0: scsi-iport 4 Oct 13 09:56:57 oozfs genunix: [ID 936769 kern.info] mpt_sas4 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 4 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 4 (mpt_sas4) online Oct 13 09:56:57 oozfs scsi: [ID 583861 kern.info] sd5 at scsi_vhci0: unit-address g5000c5000fd3e8a7: f_sym Oct 13 09:56:57 oozfs genunix: [ID 936769 kern.info] sd5 is /scsi_vhci/disk at g5000c5000fd3e8a7 Oct 13 09:56:57 oozfs genunix: [ID 408114 kern.info] /scsi_vhci/disk at g5000c5000fd3e8a7 (sd5) online Oct 13 09:56:57 oozfs genunix: [ID 483743 kern.info] /scsi_vhci/disk at g5000c5000fd3e8a7 (sd5) multipath status: degraded: path 8 mpt_sas4/disk at w5000c5000fd3e8a7,0 is online Oct 13 09:56:57 oozfs mac: [ID 435574 kern.info] NOTICE: e1000g0 link up, 1000 Mbps, full duplex Oct 13 09:57:04 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:04 oozfs Log info 0x31080000 received for target 15. Oct 13 09:57:04 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0x0 Oct 13 09:57:08 oozfs scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:08 oozfs mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31110630 Oct 13 09:57:08 oozfs scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:08 oozfs mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x31110630 Oct 13 09:57:08 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:08 oozfs Log info 0x31110630 received for target 15. Oct 13 09:57:08 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 13 09:57:08 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:08 oozfs Log info 0x31110630 received for target 15. Oct 13 09:57:08 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 13 09:57:13 oozfs scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1 Oct 13 09:57:31 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:31 oozfs Log info 0x31080000 received for target 15. Oct 13 09:57:31 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0x0 Oct 13 09:57:31 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:31 oozfs Log info 0x31080000 received for target 15. Oct 13 09:57:31 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0x0 Oct 13 09:57:35 oozfs scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:35 oozfs mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31110630 Oct 13 09:57:35 oozfs scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:35 oozfs mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x31110630 Oct 13 09:57:35 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:35 oozfs Log info 0x31110630 received for target 15. Oct 13 09:57:35 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 13 09:57:35 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:35 oozfs Log info 0x31110630 received for target 15. Oct 13 09:57:35 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 13 09:57:40 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:40 oozfs Log info 0x31080000 received for target 15. Oct 13 09:57:40 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0x0 Oct 13 09:57:40 oozfs scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1 Oct 13 09:57:43 oozfs scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:43 oozfs mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31110e00 Oct 13 09:57:43 oozfs scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:43 oozfs mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x31110e00 Oct 13 09:57:43 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:43 oozfs Log info 0x31110e00 received for target 15. Oct 13 09:57:43 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 13 09:57:43 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 13 09:57:43 oozfs Log info 0x31110e00 received for target 15. Oct 13 09:57:43 oozfs scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 13 09:57:56 oozfs svc.startd[10]: [ID 122153 daemon.warning] svc:/system/boot-archive:default: Method or service exit timed out. Killing contract 16. Oct 13 09:57:56 oozfs svc.startd[10]: [ID 636263 daemon.warning] svc:/system/boot-archive:default: Method "/lib/svc/method/boot-archive" failed due to signal KILL. Oct 13 09:57:56 oozfs genunix: [ID 227219 kern.info] This Solaris instance has UUID 740e0123-a62e-44a9-8972-be024f8297d1 Oct 13 09:57:57 oozfs genunix: [ID 454863 kern.info] dump on /dev/zvol/dsk/rpool/dump size 3895 MB Oct 13 09:57:57 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1002,4384 at 14,4, pci_pci0 Oct 13 09:57:57 oozfs genunix: [ID 936769 kern.info] pci_pci0 is /pci at 0,0/pci1002,4384 at 14,4 Oct 13 09:57:57 oozfs pseudo: [ID 129642 kern.info] pseudo-device: pm0 Oct 13 09:57:57 oozfs genunix: [ID 936769 kern.info] pm0 is /pseudo/pm at 0 Oct 13 09:57:57 oozfs pseudo: [ID 129642 kern.info] pseudo-device: power0 Oct 13 09:57:57 oozfs genunix: [ID 936769 kern.info] power0 is /pseudo/power at 0 Oct 13 09:57:57 oozfs pseudo: [ID 129642 kern.info] pseudo-device: srn0 Oct 13 09:57:57 oozfs genunix: [ID 936769 kern.info] srn0 is /pseudo/srn at 0 Oct 13 09:57:57 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: pci10ec,8168 (rge) instance 0 irq 0x1a vector 0x61 ioapic 0xff intin 0xff is bound to cpu 1 Oct 13 09:57:57 oozfs rge: [ID 801725 kern.info] NOTICE: rge0: Using MSI interrupt type Oct 13 09:57:58 oozfs mac: [ID 469746 kern.info] NOTICE: rge0 registered Oct 13 09:58:00 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: lp (ecpp) instance 0 irq 0x5 vector 0x44 ioapic 0x3 intin 0x5 is bound to cpu 0 Oct 13 09:58:00 oozfs isa: [ID 202937 kern.info] ISA-device: ecpp0 Oct 13 09:58:00 oozfs genunix: [ID 936769 kern.info] ecpp0 is /pci at 0,0/isa at 14,3/lp at 1,378 Oct 13 09:58:01 oozfs rootnex: [ID 349649 kern.info] iscsi0 at root Oct 13 09:58:01 oozfs genunix: [ID 936769 kern.info] iscsi0 is /iscsi Oct 13 09:58:01 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: asy (asy) instance 0 irq 0x4 vector 0xb0 ioapic 0x3 intin 0x4 is bound to cpu 1 Oct 13 09:58:01 oozfs isa: [ID 202937 kern.info] ISA-device: asy0 Oct 13 09:58:01 oozfs genunix: [ID 936769 kern.info] asy0 is /pci at 0,0/isa at 14,3/asy at 1,3f8 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: dtrace0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: ucode0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode at 0 Oct 13 09:58:04 oozfs scsi: [ID 583861 kern.info] mpt_sas1 at mpt_sas0: scsi-iport v0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] mpt_sas1 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at v0 Oct 13 09:58:04 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at v0 (mpt_sas1) online Oct 13 09:58:04 oozfs acpinex: [ID 328922 kern.info] acpinex: sb at 0, acpinex1 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] acpinex1 is /fw/sb at 0 Oct 13 09:58:04 oozfs isa: [ID 202937 kern.info] ISA-device: pit_beep0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] pit_beep0 is /pci at 0,0/isa at 14,3/pit_beep Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: pseudo1 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex at 1 Oct 13 09:58:04 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 0 irq 0xe vector 0x45 ioapic 0x3 intin 0xe is bound to cpu 0 Oct 13 09:58:04 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 1 irq 0xf vector 0x45 ioapic 0x3 intin 0xf is bound to cpu 1 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fct0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] fct0 is /pseudo/fct at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: stmf0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] stmf0 is /pseudo/stmf at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: dcpc0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] dcpc0 is /pseudo/dcpc at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fbt0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: lockstat0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: profile0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] profile0 is /pseudo/profile at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: sdt0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: systrace0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace at 0 Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fcsm0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm at 0 Oct 13 09:58:04 oozfs kvm: [ID 721306 kern.warning] WARNING: kvm: no hardware support Oct 13 09:58:04 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fcp0 Oct 13 09:58:04 oozfs genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp at 0 Oct 13 09:58:05 oozfs pseudo: [ID 129642 kern.info] pseudo-device: llc10 Oct 13 09:58:05 oozfs genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1 at 0 Oct 13 09:58:05 oozfs pseudo: [ID 129642 kern.info] pseudo-device: lofi0 Oct 13 09:58:05 oozfs genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi at 0 Oct 13 09:58:05 oozfs pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024 Oct 13 09:58:05 oozfs genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk at 1024 Oct 13 09:58:05 oozfs pseudo: [ID 129642 kern.info] pseudo-device: pool0 Oct 13 09:58:05 oozfs genunix: [ID 936769 kern.info] pool0 is /pseudo/pool at 0 Oct 13 09:58:05 oozfs ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running. Oct 13 09:58:05 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fssnap0 Oct 13 09:58:05 oozfs genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap at 0 Oct 13 09:58:05 oozfs pseudo: [ID 129642 kern.info] pseudo-device: nsmb0 Oct 13 09:58:05 oozfs genunix: [ID 936769 kern.info] nsmb0 is /pseudo/nsmb at 0 Oct 13 09:58:05 oozfs pseudo: [ID 129642 kern.info] pseudo-device: bpf0 Oct 13 09:58:05 oozfs genunix: [ID 936769 kern.info] bpf0 is /pseudo/bpf at 0 Oct 13 09:58:05 oozfs smbd[578]: [ID 413393 daemon.error] dyndns: failed to get domainname Oct 13 09:58:08 oozfs napp-it-mhttpd[636]: [ID 732965 daemon.warning] started as root without requesting chroot(), warning only Oct 13 09:58:08 oozfs napp-it-mhttpd[636]: [ID 692443 daemon.notice] mini_httpd/1.19 19dec2003 starting on oozfs, port 81 Oct 13 09:58:09 oozfs smbsrv: [ID 138215 kern.notice] NOTICE: smbd[OOZFS\guest]: raidz3 access denied: guest disabled Oct 13 09:58:12 oozfs last message repeated 5 times Oct 13 09:58:13 oozfs mac: [ID 736570 kern.info] NOTICE: rge0 unregistered Oct 13 09:58:14 oozfs smbsrv: [ID 138215 kern.notice] NOTICE: smbd[OOZFS\guest]: raidz3 access denied: guest disabled Oct 13 09:59:33 oozfs last message repeated 64 times Oct 13 09:59:34 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: pci10ec,8168 (rge) instance 0 irq 0x1a vector 0x61 ioapic 0xff intin 0xff is bound to cpu 0 Oct 13 09:59:34 oozfs rge: [ID 801725 kern.info] NOTICE: rge0: Using MSI interrupt type Oct 13 09:59:34 oozfs mac: [ID 469746 kern.info] NOTICE: rge0 registered Oct 13 09:59:34 oozfs pseudo: [ID 129642 kern.info] pseudo-device: devinfo0 Oct 13 09:59:34 oozfs genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo at 0 Oct 13 09:59:38 oozfs smbsrv: [ID 138215 kern.notice] NOTICE: smbd[OOZFS\guest]: raidz3 access denied: guest disabled From ben at fluffy.co.uk Sun Oct 13 08:45:16 2013 From: ben at fluffy.co.uk (Ben Summers) Date: Sun, 13 Oct 2013 09:45:16 +0100 Subject: [OmniOS-discuss] ZBEs when moving zones In-Reply-To: References: Message-ID: <11F1329A-53EF-4818-8A9C-F6BDE6A6A8EE@fluffy.co.uk> To answer my own question: When zoneadm attach is run for ipkg zones, /usr/lib/brand/ipkg/attach : * Determines which ZBE is the root by seeing which fs is mounted at the right point: # Since we're using a pre-existing dataset, the dataset currently # mounted on the {zonepath}/root becomes the active dataset. We # can't depend on the usual dataset attributes to detect this since # the dataset could be a detached zone or one that the user set up by # hand and lacking the proper attributes. However, since the zone is # not attached yet, the 'install_media == -' means the dataset must be # mounted at this point. * Finds the global zone's BE UUID using beadm * Sets the org.opensolaris.libbe:parentbe property on the mounted zone root fs to the BE UUID. This then means that when the server boots, the right fs is mounted. The other ZBEs will never be used, because the UUIDs won't match the BE's UUID, but then, the previous BEs didn't have that zone. If I then create a new global BE with beadm, a new ZBE is also created with the expected properties, cloned from the active BE. So I'm pretty sure this is all correct. Ben On 12 Oct 2013, at 20:39, Ben Summers wrote: > > Hello, > > I'm writing a script to move zones between OmniOS servers, using snapshots zfs send | recv, so I can transfer it while it's running, then do a final snapshot when it's finally down. > > The problem comes when I come to import it. I get the problem described here: > > http://everycity.co.uk/alasdair/2010/09/moving-zones-between-servers-on-opensolaris/ > > However, I have multiple zbes, and so I have to mount the right one on the destination server. Something like: > > zonecfg -z app0 -f /zones/app0/zone-config > zfs set zoned=off rpool/zones/app0/ROOT > mount -F zfs rpool/zones/app0/ROOT/zbe-2 /zones/app0/root > zoneadm -z app0 attach > zoneadm -z app0 boot > > And this works. Rebooting gets the right BE. But I have no idea why. The org.opensolaris.libbe:active property is 'on' for every one of those zbe datasets. > > If it's moving between different revisions of OmniOS, it will patch when it's attached. To get all the updates, I do > > pkg -R /zones/app0/root update > > This doesn't create a new zbe. I'm mildly concerned something won't be quite right in the future, as I can't see why it appears to be doing the right thing. > > Thanks for any advice on how to do this properly! > > Ben > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- http://bens.me.uk From alka at hfg-gmuend.de Sun Oct 13 14:17:50 2013 From: alka at hfg-gmuend.de (=?ISO-8859-1?Q?G=FCnther_Alka?=) Date: Sun, 13 Oct 2013 16:17:50 +0200 Subject: [OmniOS-discuss] napp-it OmniOS appliance boots very slow, used to work on OpenIndiana In-Reply-To: <20131013080316.GE10405@leitl.org> References: <20131013080316.GE10405@leitl.org> Message-ID: <525AAB8E.7000408@hfg-gmuend.de> One problem I am aware if you are using the ESXi appliance resulting in very slow bootup, extreme high CPU load and even data corruption: If you are on ESXi 5.5, you must use the vmxnet3 vnic or disable TCP segmentation offload in e1000.conf; add the following and reboot tx_hcksum_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; lso_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; Maybe similar to this problem: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2058692 (in the current appliance v. 13b, this is disabled per default) Gea On 13.10.2013 10:03, Eugen Leitl wrote: > Not sure what is going on, can anyone spot a smoking gun > in this dmesg? System doesn't reboot/init 5 doesn't > shutdown either. > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- From Rob at Logan.com Sun Oct 13 15:05:50 2013 From: Rob at Logan.com (Rob Logan) Date: Sun, 13 Oct 2013 11:05:50 -0400 Subject: [OmniOS-discuss] napp-it OmniOS appliance boots very slow, used to work on OpenIndiana In-Reply-To: <525AAB8E.7000408@hfg-gmuend.de> References: <20131013080316.GE10405@leitl.org> <525AAB8E.7000408@hfg-gmuend.de> Message-ID: > If you are on ESXi 5.5, you must use the vmxnet3 vmic certainly gives omnios more options than hardware emulation of an intel 82545EM (e1000) or 82574 (e1000e) > or disable TCP segmentation offload in e1000.conf; that does make it as easy as possible on esxi for hardware emulation. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805 > appliance boots very slow Oct 13 09:58:13 oozfs mac: [ID 736570 kern.info] NOTICE: rge0 unregistered Oct 13 09:59:34 oozfs mac: [ID 469746 kern.info] NOTICE: rge0 registered why emulate a Realtek ethernet? perhaps e1000e or as Gea points out, a vmxnet3 Rob ps: public thanks to Gea for his napp-it work. From alka at hfg-gmuend.de Sun Oct 13 18:48:45 2013 From: alka at hfg-gmuend.de (alka) Date: Sun, 13 Oct 2013 20:48:45 +0200 Subject: [OmniOS-discuss] napp-it OmniOS appliance boots very slow, used to work on OpenIndiana In-Reply-To: <20131013153814.GQ10405@leitl.org> References: <20131013080316.GE10405@leitl.org> <525AAB8E.7000408@hfg-gmuend.de> <20131013153814.GQ10405@leitl.org> Message-ID: hi Eugen beside the ESXi appliance, napp-it does not modify any system setting (you can even disable napp-it without problems) so this must be a "maybe simulanious" but different problem. In your logs are controller and multipath errors so I would check iostat, zpool status and format behaviours. You may try to disable multipath in your controller.conf settings. if you can - compare an Intel Nic - compare an LSI HBA as your hardware is not "best use". (My backup systen is also an older AMD + Realtek but works well) Gea Am 13.10.2013 um 17:38 schrieb Eugen Leitl: > On Sun, Oct 13, 2013 at 04:17:50PM +0200, G?nther Alka wrote: >> One problem I am aware if you are using the ESXi appliance > > Hi Guenther -- no, I'm not using the ESXi appliance, > this is physical hardware (MSI E350DM-E33, AMD Dual-Core E-350). > > The problems started after I updated napp-it to latest > as of yesterday, after that I nuked OpenIndiana and > installed OmniOS and latest napp-it again. > > The system *is* working, but I'm looking for hints how to > diagnose the residual problems. > > P.S. Thanks for napp-it > >> resulting in very slow bootup, extreme high CPU load and even data >> corruption: >> >> If you are on ESXi 5.5, you must use the vmxnet3 vnic >> or disable TCP segmentation offload in e1000.conf; add the following >> and reboot >> >> tx_hcksum_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; >> lso_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; >> >> Maybe similar to this problem: >> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2058692 >> >> (in the current appliance v. 13b, this is disabled per default) -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobi at oetiker.ch Mon Oct 14 06:29:57 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 14 Oct 2013 08:29:57 +0200 (CEST) Subject: [OmniOS-discuss] nfs problems linux (client) illumos (server) Message-ID: Folks, I have this nfs client (ubunty 3.5 kernel) which seems to have issues talking to our omnios server. In the example below the client does not seem to get an answer to his ACCESS3 call from 08:19:48.43 and starts retransmitting. It does not seem as if packets got lost ... Does this pattern ring a bell? (as seen from the omnios server) 8:19:42.11355 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=1F8F (read,lookup,modify,extend,delete) 8:19:42.11358 10.10.10.1 -> 10.10.10.2 NFS R ACCESS3 OK (read,lookup,modify,extend,delete) 8:19:42.11372 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B8A (read,lookup,modify,extend,delete) 8:19:42.11387 10.10.10.1 -> 10.10.10.2 NFS R ACCESS3 OK (read,lookup,modify,extend,delete) 8:19:42.15340 10.10.10.2 -> 10.10.10.1 TCP D=2049 S=822 Ack=3569055649 Seq=330388801 Len=0 Win=20638 Options= 8:19:42.65429 10.10.10.2 -> 10.10.10.1 NFS C GETATTR3 FH=1391 8:19:42.65493 10.10.10.1 -> 10.10.10.2 NFS R GETATTR3 OK 8:19:42.65507 10.10.10.2 -> 10.10.10.1 TCP D=2049 S=822 Ack=3569055765 Seq=330388917 Len=0 Win=20638 Options= 8:19:48.43236 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B45 (read,lookup,modify,extend,delete) 8:19:48.49820 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389029 Seq=3569055765 Len=0 Win=32806 Options= 8:19:49.12947 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B45 (read,lookup,modify,extend,delete) (retransmit) 8:19:49.19819 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389141 Seq=3569055765 Len=0 Win=32806 Options= 8:19:50.53345 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B45 (read,lookup,modify,extend,delete) (retransmit) 8:19:50.59817 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389253 Seq=3569055765 Len=0 Win=32806 Options= 8:19:52.64147 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B45 (read,lookup,modify,extend,delete) (retransmit) 8:19:52.70810 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389365 Seq=3569055765 Len=0 Win=32806 Options= 8:19:53.50200 10.10.10.2 -> 10.10.10.1 NFS C GETATTR3 FH=08CA 8:19:53.56808 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389477 Seq=3569055765 Len=0 Win=32806 Options= (as seeen from the ubuntu linux 3.5 client) 08:19:42.113444 10.10.10.2 -> 10.10.10.1 NFS 186 V3 ACCESS Call, FH:0xbff47443, [Check: RD LU MD XT DL] 08:19:42.113512 10.10.10.1 -> 10.10.10.2 NFS 190 V3 ACCESS Reply (Call In 86), [Allowed: RD LU MD XT DL] 08:19:42.113620 10.10.10.2 -> 10.10.10.1 NFS 186 V3 ACCESS Call, FH:0x312c9eb9, [Check: RD LU MD XT DL] 08:19:42.113804 10.10.10.1 -> 10.10.10.2 NFS 190 V3 ACCESS Reply (Call In 88), [Allowed: RD LU MD XT DL] 08:19:42.153301 10.10.10.2 -> 10.10.10.1 TCP 66 822 > nfs [ACK] Seq=7121 Ack=4485 Win=20638 Len=0 TSval=3449855200 TSecr=396193080 08:19:42.654182 10.10.10.2 -> 10.10.10.1 NFS 182 V3 GETATTR Call, FH:0x7b7d2a4e 08:19:42.654932 10.10.10.1 -> 10.10.10.2 NFS 182 V3 GETATTR Reply (Call In 91) Regular File mode:0644 uid:0 gid:0 08:19:42.654979 10.10.10.2 -> 10.10.10.1 TCP 66 822 > nfs [ACK] Seq=7237 Ack=4601 Win=20638 Len=0 TSval=3449855325 TSecr=396193134 08:19:48.432250 10.10.10.2 -> 10.10.10.1 NFS 178 V3 ACCESS Call, FH:0x505b4bee, [Check: RD LU MD XT DL] 08:19:48.498217 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7349 Win=32806 Len=0 TSval=396193719 TSecr=3449856769 08:19:49.129364 10.10.10.2 -> 10.10.10.1 NFS 178 [RPC retransmission of #94]V3 ACCESS Call, FH:0x505b4bee, [Check: RD LU MD XT DL] 08:19:49.198215 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7461 Win=32806 Len=0 TSval=396193789 TSecr=3449856944 08:19:50.533336 10.10.10.2 -> 10.10.10.1 NFS 178 [RPC retransmission of #94]V3 ACCESS Call, FH:0x505b4bee, [Check: RD LU MD XT DL] 08:19:50.598191 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7573 Win=32806 Len=0 TSval=396193929 TSecr=3449857295 08:19:52.641348 10.10.10.2 -> 10.10.10.1 NFS 178 [RPC retransmission of #94]V3 ACCESS Call, FH:0x505b4bee, [Check: RD LU MD XT DL] 08:19:52.708091 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7685 Win=32806 Len=0 TSval=396194140 TSecr=3449857822 08:19:53.501892 10.10.10.2 -> 10.10.10.1 NFS 178 V3 GETATTR Call, FH:0x8a584406 08:19:53.568104 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7797 Win=32806 Len=0 TSval=396194226 TSecr=3449858037 cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From mayuresh at kathe.in Mon Oct 14 07:47:04 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Mon, 14 Oct 2013 03:47:04 -0400 Subject: [OmniOS-discuss] console login : backspace not working Message-ID: <20131014074704.GA15799@wolfman.devio.us> hello, getting to know omnios better. liking it more everyday. :) the backspace key doesn't work at the console login prompt. any way to make it work? (have faced the same issue while i worked on smartos). thanks. From eugen at leitl.org Mon Oct 14 08:53:23 2013 From: eugen at leitl.org (Eugen Leitl) Date: Mon, 14 Oct 2013 10:53:23 +0200 Subject: [OmniOS-discuss] napp-it OmniOS appliance boots very slow, used to work on OpenIndiana In-Reply-To: References: <20131013080316.GE10405@leitl.org> <525AAB8E.7000408@hfg-gmuend.de> <20131013153814.GQ10405@leitl.org> Message-ID: <20131014085323.GN10405@leitl.org> On Sun, Oct 13, 2013 at 08:48:45PM +0200, alka wrote: > hi Eugen > > beside the ESXi appliance, napp-it does not modify > any system setting (you can even disable napp-it without problems) > so this must be a "maybe simulanious" but different problem. > > In your logs are controller and multipath errors so I would check > iostat, zpool status and format behaviours. > > You may try to disable multipath in your controller.conf settings. > if you can > - compare an Intel Nic > - compare an LSI HBA I have both in my system. The LSI is driving the 8-drive pool. Only rpool and log device, all SSD, are on onboard SATA ports. I'm not using the onboard Realtek, only the Intel NIC is used. Is information in http://docs.oracle.com/cd/E19957-01/819-0139/ch_4_config_multi_SW.html /kernel/drv/fp.conf mpxio-disable="yes"; applicable for OmniOS? Do I need to touch /reconfigure to make it stick? > as your hardware is not "best use". > (My backup systen is also an older AMD + Realtek but works well) > > > Gea > > > Am 13.10.2013 um 17:38 schrieb Eugen Leitl: > > > On Sun, Oct 13, 2013 at 04:17:50PM +0200, G?nther Alka wrote: > >> One problem I am aware if you are using the ESXi appliance > > > > Hi Guenther -- no, I'm not using the ESXi appliance, > > this is physical hardware (MSI E350DM-E33, AMD Dual-Core E-350). > > > > The problems started after I updated napp-it to latest > > as of yesterday, after that I nuked OpenIndiana and > > installed OmniOS and latest napp-it again. > > > > The system *is* working, but I'm looking for hints how to > > diagnose the residual problems. > > > > P.S. Thanks for napp-it > > > >> resulting in very slow bootup, extreme high CPU load and even data > >> corruption: > >> > >> If you are on ESXi 5.5, you must use the vmxnet3 vnic > >> or disable TCP segmentation offload in e1000.conf; add the following > >> and reboot > >> > >> tx_hcksum_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; > >> lso_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; > >> > >> Maybe similar to this problem: > >> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2058692 > >> > >> (in the current appliance v. 13b, this is disabled per default) > > -- > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Eugen* Leitl leitl http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://ativel.com http://postbiota.org AC894EC5: 38A5 5F46 A4FF 59B8 336B 47EE F46E 3489 AC89 4EC5 From jimklimov at cos.ru Mon Oct 14 08:59:08 2013 From: jimklimov at cos.ru (Jim Klimov) Date: Mon, 14 Oct 2013 10:59:08 +0200 Subject: [OmniOS-discuss] console login : backspace not working In-Reply-To: <20131014074704.GA15799@wolfman.devio.us> References: <20131014074704.GA15799@wolfman.devio.us> Message-ID: <525BB25C.6050307@cos.ru> On 2013-10-14 09:47, Mayuresh Kathe wrote: > hello, getting to know omnios better. > liking it more everyday. :) > > the backspace key doesn't work at the > console login prompt. > any way to make it work? > (have faced the same issue while i > worked on smartos). Check to see if DEL or CTRL+H do the backspace action in the password/login prompt? Overall, I think this plagued Solaris like forever and apparently either nobody cared enough, or not much can be done (perhaps no terminal-type context is available before login?) BTW, IIRC, terminal type might be settable via "eeprom" command. I'd be interested to see proper solutions. :) From alka at hfg-gmuend.de Mon Oct 14 09:24:34 2013 From: alka at hfg-gmuend.de (Guenther Alka) Date: Mon, 14 Oct 2013 11:24:34 +0200 Subject: [OmniOS-discuss] napp-it OmniOS appliance boots very slow, used to work on OpenIndiana In-Reply-To: <20131014085323.GN10405@leitl.org> References: <20131013080316.GE10405@leitl.org> <525AAB8E.7000408@hfg-gmuend.de> <20131013153814.GQ10405@leitl.org> <20131014085323.GN10405@leitl.org> Message-ID: <525BB852.8090105@hfg-gmuend.de> hi Eugen First, check napp-it menu Disks Details prtconf diskinfos (for driver info of affected disks, probably mpt_sas/ sd) then goto Disks Details edit mpt sas conf disable MPIO: # To globally enable MPxIO on all LSI MPT SAS 2.0 controllers set: mpxio-disable="yes"; I would reboot then > On Sun, Oct 13, 2013 at 08:48:45PM +0200, alka wrote: >> hi Eugen >> >> beside the ESXi appliance, napp-it does not modify >> any system setting (you can even disable napp-it without problems) >> so this must be a "maybe simulanious" but different problem. >> >> In your logs are controller and multipath errors so I would check >> iostat, zpool status and format behaviours. >> >> You may try to disable multipath in your controller.conf settings. >> if you can >> - compare an Intel Nic >> - compare an LSI HBA > I have both in my system. The LSI is driving the 8-drive pool. > Only rpool and log device, all SSD, are on onboard SATA ports. > > I'm not using the onboard Realtek, only the Intel NIC is used. > > Is information in http://docs.oracle.com/cd/E19957-01/819-0139/ch_4_config_multi_SW.html > /kernel/drv/fp.conf > mpxio-disable="yes"; > applicable for OmniOS? Do I need to touch /reconfigure to > make it stick? > >> as your hardware is not "best use". >> (My backup systen is also an older AMD + Realtek but works well) >> >> >> Gea >> >> >> Am 13.10.2013 um 17:38 schrieb Eugen Leitl: >> >>> On Sun, Oct 13, 2013 at 04:17:50PM +0200, G?nther Alka wrote: >>>> One problem I am aware if you are using the ESXi appliance >>> Hi Guenther -- no, I'm not using the ESXi appliance, >>> this is physical hardware (MSI E350DM-E33, AMD Dual-Core E-350). >>> >>> The problems started after I updated napp-it to latest >>> as of yesterday, after that I nuked OpenIndiana and >>> installed OmniOS and latest napp-it again. >>> >>> The system *is* working, but I'm looking for hints how to >>> diagnose the residual problems. >>> >>> P.S. Thanks for napp-it >>> >>>> resulting in very slow bootup, extreme high CPU load and even data >>>> corruption: >>>> >>>> If you are on ESXi 5.5, you must use the vmxnet3 vnic >>>> or disable TCP segmentation offload in e1000.conf; add the following >>>> and reboot >>>> >>>> tx_hcksum_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; >>>> lso_enable=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; >>>> >>>> Maybe similar to this problem: >>>> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2058692 >>>> >>>> (in the current appliance v. 13b, this is disabled per default) >> -- >> >> >> _______________________________________________ >> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: gt.png Type: image/png Size: 203 bytes Desc: not available URL: From ben at fluffy.co.uk Mon Oct 14 09:52:40 2013 From: ben at fluffy.co.uk (Ben Summers) Date: Mon, 14 Oct 2013 10:52:40 +0100 Subject: [OmniOS-discuss] WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision Message-ID: <53DDBD0E-9874-46B5-B55B-D7A77660DD2F@fluffy.co.uk> Hello, After updating to OmniOS r151006p on an X4150 without enough hardware support for KVM, I see this on the console after booting: Hostname: REDACTED Configuring devices. WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision WARNING: kstat_create('unix', 0, 'kvm_rmap_desc'): namespace collision WARNING: kstat_create('unix', 0, 'kvm_mmu_page_header'): namespace collision WARNING: kvm: insufficient hardware support (lacking EPT) I'm assuming it's not an issue as I'm not using KVM, but warnings on boot are always amusing. Ben -- http://bens.me.uk From vab at bb-c.de Mon Oct 14 17:19:39 2013 From: vab at bb-c.de (Volker A. Brandt) Date: Mon, 14 Oct 2013 19:19:39 +0200 Subject: [OmniOS-discuss] console login : backspace not working In-Reply-To: <525BB25C.6050307@cos.ru> References: <20131014074704.GA15799@wolfman.devio.us> <525BB25C.6050307@cos.ru> Message-ID: <21084.10155.187128.794721@glaurung.bb-c.de> > On 2013-10-14 09:47, Mayuresh Kathe wrote: > > the backspace key doesn't work at the > > console login prompt. > > any way to make it work? >[...] > > Check to see if DEL or CTRL+H do the backspace action in the > password/login prompt? Overall, I think this plagued Solaris > like forever and apparently either nobody cared enough, or > not much can be done (perhaps no terminal-type context is > available before login?) Try "stty erase < /dev/console > /dev/console" in some rc script... maybe wrap it with a check using the tty command, and only exec stty if tty does not return "not a tty". Anyway, no big deal, nobody was ever bothered by that... :-) Cheers -- Volker -- ------------------------------------------------------------------------ Volker A. Brandt Consulting and Support for Oracle Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim, GERMANY Email: vab at bb-c.de Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgr??e: 46 Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt "When logic and proportion have fallen sloppy dead" From nsmith at careyweb.com Mon Oct 14 18:01:50 2013 From: nsmith at careyweb.com (Nate Smith) Date: Mon, 14 Oct 2013 14:01:50 -0400 Subject: [OmniOS-discuss] RAID/SAS Controller Recommendations Message-ID: I'm looking to install a new Omnios server on a Dell T710 server with an HP MDS 600 RAID Cabinet. I currently run a similar setup with OpenIndiana and an MDS600. On this machine, I use LSI-9285-8e controllers, which are the LSISAS2208 Chipset. All targets are set to JBOD pass/thru mode. This was a finicky setup when I got it going on OI, and it took the Solaris drivers for the card to get it work. I could never get the setup to work with an LSI 9201-16e. It would not play nice with the SAS expanders (yes, all my disks are SAS). The nice upshot with the 9285 was that I could use the Megaraid Utility for monitoring, and the hardware drivers handled the dual attached SAS perfectly. But... I have had the occasional hardware lockup when using Napp-it. Forward to 18 months later, and I want to switch to Omnios, or at least test, and I've purchased another MDS600 cabinet off ebay to do it. I'm looking at controllers, and I've noticed that the OmniOS compatibility list is pretty extensive. I'm thinking about getting 9286-8e again, which is still based on the LSISAS2208 Chipset, but is PCIE 3.0 instead of 2.0 (which really is a negligible difference). Can anyone recommend any other controllers to look at? I was perusing the LSI SAS2308 based chipsets, but I'm not sure how mature the drivers are. So if anyone knows any controllers which they've worked with an HP MDS600, dual attached, etc, that would be great. Otherwise, any words of wisdom would be appreciated. Thanks. -Nate From alka at hfg-gmuend.de Mon Oct 14 18:27:37 2013 From: alka at hfg-gmuend.de (alka) Date: Mon, 14 Oct 2013 20:27:37 +0200 Subject: [OmniOS-discuss] RAID/SAS Controller Recommendations In-Reply-To: References: Message-ID: LSI 2308 is fine with OmniOS I use the LSI 9207 alike controller on a SuperMicro Board without problem. The LSI 9207-8e is what you may want in general (Have not had a MD S600 to test against). Am 14.10.2013 um 20:01 schrieb Nate Smith: > I'm looking to install a new Omnios server on a Dell T710 server with an HP MDS 600 RAID Cabinet. > > I currently run a similar setup with OpenIndiana and an MDS600. On this machine, I use LSI-9285-8e controllers, which are the LSISAS2208 Chipset. All targets are set to JBOD pass/thru mode. This was a finicky setup when I got it going on OI, and it took the Solaris drivers for the card to get it work. I could never get the setup to work with an LSI 9201-16e. It would not play nice with the SAS expanders (yes, all my disks are SAS). The nice upshot with the 9285 was that I could use the Megaraid Utility for monitoring, and the hardware drivers handled the dual attached SAS perfectly. But... I have had the occasional hardware lockup when using Napp-it. > > Forward to 18 months later, and I want to switch to Omnios, or at least test, and I've purchased another MDS600 cabinet off ebay to do it. I'm looking at controllers, and I've noticed that the OmniOS compatibility list is pretty extensive. I'm thinking about getting 9286-8e again, which is still based on the LSISAS2208 Chipset, but is PCIE 3.0 instead of 2.0 (which really is a negligible difference). Can anyone recommend any other controllers to look at? I was perusing the LSI SAS2308 based chipsets, but I'm not sure how mature the drivers are. > > So if anyone knows any controllers which they've worked with an HP MDS600, dual attached, etc, that would be great. Otherwise, any words of wisdom would be appreciated. Thanks. > > -Nate > > _______________________________________________ > 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: From eugen at leitl.org Mon Oct 14 18:28:55 2013 From: eugen at leitl.org (Eugen Leitl) Date: Mon, 14 Oct 2013 20:28:55 +0200 Subject: [OmniOS-discuss] napp-it OmniOS appliance boots very slow, used to work on OpenIndiana In-Reply-To: <525BB852.8090105@hfg-gmuend.de> References: <20131013080316.GE10405@leitl.org> <525AAB8E.7000408@hfg-gmuend.de> <20131013153814.GQ10405@leitl.org> <20131014085323.GN10405@leitl.org> <525BB852.8090105@hfg-gmuend.de> Message-ID: <20131014182855.GZ10405@leitl.org> On Mon, Oct 14, 2013 at 11:24:34AM +0200, Guenther Alka wrote: > hi Eugen > > First, check napp-it menu > > Disks > Details > prtconf diskinfos > > (for driver info of affected disks, probably mpt_sas/ sd) > > then goto > Disks > Details > edit mpt sas conf > > disable MPIO: > # To globally enable MPxIO on all LSI MPT SAS 2.0 controllers set: > mpxio-disable="yes"; > > I would reboot then I picked the wrong mpxio-disable before obviously. This did the trick, thanks! Notice this is crappy IBM ServeRAID (probably M1015, I forget), with possibly botched LSI firmware reflash. New dmesg: October 14, 2013 08:26:40 PM CEST Oct 14 20:22:45 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1462,7720 at 12, ohci0 Oct 14 20:22:45 oozfs genunix: [ID 936769 kern.info] ohci0 is /pci at 0,0/pci1462,7720 at 12 Oct 14 20:22:45 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1462,7720 at 13, ohci1 Oct 14 20:22:45 oozfs genunix: [ID 936769 kern.info] ohci1 is /pci at 0,0/pci1462,7720 at 13 Oct 14 20:22:45 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1462,7720 at 14,5, ohci2 Oct 14 20:22:45 oozfs genunix: [ID 936769 kern.info] ohci2 is /pci at 0,0/pci1462,7720 at 14,5 Oct 14 20:22:45 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1462,7720 at 16, ohci3 Oct 14 20:22:45 oozfs genunix: [ID 936769 kern.info] ohci3 is /pci at 0,0/pci1462,7720 at 16 Oct 14 20:22:45 oozfs i8042: [ID 526150 kern.info] 8042 device: keyboard at 0, kb8042 # 0 Oct 14 20:22:45 oozfs genunix: [ID 936769 kern.info] kb80420 is /pci at 0,0/isa at 14,3/i8042 at 1,60/keyboard at 0 Oct 14 20:22:45 oozfs i8042: [ID 526150 kern.info] 8042 device: mouse at 1, mouse8042 # 0 Oct 14 20:22:45 oozfs genunix: [ID 936769 kern.info] mouse80420 is /pci at 0,0/isa at 14,3/i8042 at 1,60/mouse at 1 Oct 14 20:22:48 oozfs unix: [ID 950921 kern.info] cpu0: x86 (chipid 0x0 AuthenticAMD 500F10 family 20 model 1 step 0 clock 1600 MHz) Oct 14 20:22:48 oozfs unix: [ID 950921 kern.info] cpu0: AMD E-350 Processor Oct 14 20:22:48 oozfs acpinex: [ID 328922 kern.info] acpinex: cpu at 2, cpudrv1 Oct 14 20:22:48 oozfs genunix: [ID 408114 kern.info] /fw/cpu at 2 (cpudrv1) online Oct 14 20:22:48 oozfs unix: [ID 950921 kern.info] cpu1: x86 (chipid 0x0 AuthenticAMD 500F10 family 20 model 1 step 0 clock 1600 MHz) Oct 14 20:22:48 oozfs unix: [ID 950921 kern.info] cpu1: AMD E-350 Processor Oct 14 20:22:48 oozfs unix: [ID 557947 kern.info] cpu1 initialization complete - online Oct 14 20:22:48 oozfs pseudo: [ID 129642 kern.info] pseudo-device: stmf_sbd0 Oct 14 20:22:48 oozfs genunix: [ID 936769 kern.info] stmf_sbd0 is /pseudo/stmf_sbd at 0 Oct 14 20:22:49 oozfs pseudo: [ID 129642 kern.info] pseudo-device: audio0 Oct 14 20:22:49 oozfs genunix: [ID 936769 kern.info] audio0 is /pseudo/audio at 0 Oct 14 20:22:49 oozfs usba: [ID 912658 kern.info] USB 1.10 device (usb4b4,101) operating at low speed (USB 1.x) on USB 1.10 root hub: device at 5, usb_mid0 at bus address 2 Oct 14 20:22:49 oozfs usba: [ID 349649 kern.info] DATACOMP SteelS Oct 14 20:22:49 oozfs genunix: [ID 936769 kern.info] usb_mid0 is /pci at 0,0/pci1462,7720 at 12/device at 5 Oct 14 20:22:49 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1462,7720 at 12/device at 5 (usb_mid0) online Oct 14 20:22:49 oozfs usba: [ID 912658 kern.info] USB 1.10 interface (usbif4b4,101.config1.0) operating at low speed (USB 1.x) on USB 1.10 root hub: keyboard at 0, hid1 at bus address 2 Oct 14 20:22:49 oozfs usba: [ID 349649 kern.info] DATACOMP SteelS Oct 14 20:22:49 oozfs genunix: [ID 936769 kern.info] hid1 is /pci at 0,0/pci1462,7720 at 12/device at 5/keyboard at 0 Oct 14 20:22:49 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1462,7720 at 12/device at 5/keyboard at 0 (hid1) online Oct 14 20:22:49 oozfs usba: [ID 912658 kern.info] USB 1.10 interface (usbif4b4,101.config1.1) operating at low speed (USB 1.x) on USB 1.10 root hub: mouse at 1, hid2 at bus address 2 Oct 14 20:22:49 oozfs usba: [ID 349649 kern.info] DATACOMP SteelS Oct 14 20:22:49 oozfs genunix: [ID 936769 kern.info] hid2 is /pci at 0,0/pci1462,7720 at 12/device at 5/mouse at 1 Oct 14 20:22:49 oozfs consconfig_dacf: [ID 215896 kern.warning] WARNING: consconfig_prepare_dev: can't push streams module "usbms", error 22 Oct 14 20:22:49 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1462,7720 at 12/device at 5/mouse at 1 (hid2) online Oct 14 20:22:49 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1022,1512 at 4, pcieb0 Oct 14 20:22:49 oozfs genunix: [ID 936769 kern.info] pcieb0 is /pci at 0,0/pci1022,1512 at 4 Oct 14 20:22:49 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1002,43a1 at 15,1, pcieb2 Oct 14 20:22:49 oozfs genunix: [ID 936769 kern.info] pcieb2 is /pci at 0,0/pci1002,43a1 at 15,1 Oct 14 20:22:49 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1002,43a2 at 15,2, pcieb3 Oct 14 20:22:49 oozfs genunix: [ID 936769 kern.info] pcieb3 is /pci at 0,0/pci1002,43a2 at 15,2 Oct 14 20:22:50 oozfs usba: [ID 912658 kern.info] USB 1.10 device (usb51d,2) operating at low speed (USB 1.x) on USB 1.10 root hub: input at 1, hid0 at bus address 2 Oct 14 20:22:50 oozfs usba: [ID 349649 kern.info] American Power Conversion Back-UPS CS 650 FW:817.v2.I USB FW:v2 QB0444136087 Oct 14 20:22:50 oozfs genunix: [ID 936769 kern.info] hid0 is /pci at 0,0/pci1462,7720 at 13/input at 1 Oct 14 20:22:50 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1462,7720 at 13/input at 1 (hid0) online Oct 14 20:22:53 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: pciex8086,10b9 (e1000g) instance 0 irq 0x18 vector 0x60 ioapic 0xff intin 0xff is bound to cpu 1 Oct 14 20:22:53 oozfs mac: [ID 469746 kern.info] NOTICE: e1000g0 registered Oct 14 20:22:54 oozfs pseudo: [ID 129642 kern.info] pseudo-device: devinfo0 Oct 14 20:22:54 oozfs genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo at 0 Oct 14 20:22:54 oozfs pseudo: [ID 129642 kern.info] pseudo-device: zfs0 Oct 14 20:22:54 oozfs genunix: [ID 936769 kern.info] zfs0 is /pseudo/zfs at 0 Oct 14 20:22:55 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 14 20:22:55 oozfs mptsas0 supports power management. Oct 14 20:22:55 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: pciex1000,72 (mpt_sas) instance 0 irq 0x19 vector 0x43 ioapic 0xff intin 0xff is bound to cpu 0 Oct 14 20:22:55 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 14 20:22:55 oozfs mptsas0 supports power management. Oct 14 20:22:55 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 14 20:22:55 oozfs mpt0 Firmware version v2.0.50.0 (?) Oct 14 20:22:55 oozfs scsi: [ID 365881 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 14 20:22:55 oozfs mpt0: IOC Operational. Oct 14 20:22:55 oozfs scsi: [ID 243001 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 (mpt_sas0): Oct 14 20:22:55 oozfs mpt0: Initiator WWNs: 0x500605b0017c1b20-0x500605b0017c1b27 Oct 14 20:22:55 oozfs pcieb: [ID 586369 kern.info] PCIE-device: pci1000,3050 at 0, mpt_sas0 Oct 14 20:22:55 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1000,3050 at 0, mpt_sas0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas0 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0 Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas4 at mpt_sas0: scsi-iport 4 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas4 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 4 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 4 (mpt_sas4) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] sd11 at mpt_sas4: unit-address w5000c5000fd3e8a7,0: w5000c5000fd3e8a7,0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] sd11 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 4/disk at w5000c5000fd3e8a7,0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 4/disk at w5000c5000fd3e8a7,0 (sd11) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas7 at mpt_sas0: scsi-iport 20 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas7 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 20 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 20 (mpt_sas7) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] sd12 at mpt_sas7: unit-address w5000c5000fd3bc10,0: w5000c5000fd3bc10,0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] sd12 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 20/disk at w5000c5000fd3bc10,0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 20/disk at w5000c5000fd3bc10,0 (sd12) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas2 at mpt_sas0: scsi-iport 1 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas2 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 1 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 1 (mpt_sas2) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] sd13 at mpt_sas2: unit-address w5000c50009c72c48,0: w5000c50009c72c48,0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] sd13 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 1/disk at w5000c50009c72c48,0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 1/disk at w5000c50009c72c48,0 (sd13) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas3 at mpt_sas0: scsi-iport 2 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas3 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 2 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 2 (mpt_sas3) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] sd14 at mpt_sas3: unit-address w5000c500098be9dd,0: w5000c500098be9dd,0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] sd14 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 2/disk at w5000c500098be9dd,0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 2/disk at w5000c500098be9dd,0 (sd14) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas5 at mpt_sas0: scsi-iport 8 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas5 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 8 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 8 (mpt_sas5) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] sd15 at mpt_sas5: unit-address w5000c5000fd2e794,0: w5000c5000fd2e794,0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] sd15 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 8/disk at w5000c5000fd2e794,0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 8/disk at w5000c5000fd2e794,0 (sd15) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas6 at mpt_sas0: scsi-iport 10 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas6 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 10 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 10 (mpt_sas6) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] sd16 at mpt_sas6: unit-address w5000c5000fd37075,0: w5000c5000fd37075,0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] sd16 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 10/disk at w5000c5000fd37075,0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 10/disk at w5000c5000fd37075,0 (sd16) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas8 at mpt_sas0: scsi-iport 40 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas8 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 40 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 40 (mpt_sas8) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] sd17 at mpt_sas8: unit-address w5000c5000fd39d53,0: w5000c5000fd39d53,0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] sd17 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 40/disk at w5000c5000fd39d53,0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 40/disk at w5000c5000fd39d53,0 (sd17) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas9 at mpt_sas0: scsi-iport 80 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas9 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 80 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 80 (mpt_sas9) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] sd18 at mpt_sas9: unit-address w5000c50009c73968,0: w5000c50009c73968,0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] sd18 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 80/disk at w5000c50009c73968,0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at 80/disk at w5000c50009c73968,0 (sd18) online Oct 14 20:22:55 oozfs scsi: [ID 583861 kern.info] mpt_sas1 at mpt_sas0: scsi-iport v0 Oct 14 20:22:55 oozfs genunix: [ID 936769 kern.info] mpt_sas1 is /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at v0 Oct 14 20:22:55 oozfs genunix: [ID 408114 kern.info] /pci at 0,0/pci1022,1512 at 4/pci1000,3050 at 0/iport at v0 (mpt_sas1) online Oct 14 20:22:56 oozfs rootnex: [ID 349649 kern.info] iscsi0 at root Oct 14 20:22:56 oozfs genunix: [ID 936769 kern.info] iscsi0 is /iscsi Oct 14 20:22:56 oozfs mac: [ID 435574 kern.info] NOTICE: e1000g0 link up, 1000 Mbps, full duplex Oct 14 20:23:12 oozfs genunix: [ID 227219 kern.info] This Solaris instance has UUID e5d6ac3b-9aa6-4d85-8023-9613698f624d Oct 14 20:23:12 oozfs genunix: [ID 454863 kern.info] dump on /dev/zvol/dsk/rpool/dump size 3895 MB Oct 14 20:23:12 oozfs npe: [ID 236367 kern.info] PCI Express-device: pci1002,4384 at 14,4, pci_pci0 Oct 14 20:23:12 oozfs genunix: [ID 936769 kern.info] pci_pci0 is /pci at 0,0/pci1002,4384 at 14,4 Oct 14 20:23:13 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: pci10ec,8168 (rge) instance 0 irq 0x1a vector 0x61 ioapic 0xff intin 0xff is bound to cpu 1 Oct 14 20:23:13 oozfs rge: [ID 801725 kern.info] NOTICE: rge0: Using MSI interrupt type Oct 14 20:23:13 oozfs mac: [ID 469746 kern.info] NOTICE: rge0 registered Oct 14 20:23:13 oozfs pseudo: [ID 129642 kern.info] pseudo-device: pm0 Oct 14 20:23:13 oozfs genunix: [ID 936769 kern.info] pm0 is /pseudo/pm at 0 Oct 14 20:23:13 oozfs pseudo: [ID 129642 kern.info] pseudo-device: power0 Oct 14 20:23:13 oozfs genunix: [ID 936769 kern.info] power0 is /pseudo/power at 0 Oct 14 20:23:13 oozfs pseudo: [ID 129642 kern.info] pseudo-device: srn0 Oct 14 20:23:13 oozfs genunix: [ID 936769 kern.info] srn0 is /pseudo/srn at 0 Oct 14 20:23:14 oozfs acpinex: [ID 328922 kern.info] acpinex: sb at 0, acpinex1 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] acpinex1 is /fw/sb at 0 Oct 14 20:23:14 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: lp (ecpp) instance 0 irq 0x5 vector 0x44 ioapic 0x3 intin 0x5 is bound to cpu 0 Oct 14 20:23:14 oozfs isa: [ID 202937 kern.info] ISA-device: ecpp0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] ecpp0 is /pci at 0,0/isa at 14,3/lp at 1,378 Oct 14 20:23:14 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: asy (asy) instance 0 irq 0x4 vector 0xb0 ioapic 0x3 intin 0x4 is bound to cpu 1 Oct 14 20:23:14 oozfs isa: [ID 202937 kern.info] ISA-device: asy0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] asy0 is /pci at 0,0/isa at 14,3/asy at 1,3f8 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: pseudo1 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex at 1 Oct 14 20:23:14 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 0 irq 0xe vector 0x45 ioapic 0x3 intin 0xe is bound to cpu 0 Oct 14 20:23:14 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 1 irq 0xf vector 0x45 ioapic 0x3 intin 0xf is bound to cpu 1 Oct 14 20:23:14 oozfs isa: [ID 202937 kern.info] ISA-device: pit_beep0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] pit_beep0 is /pci at 0,0/isa at 14,3/pit_beep Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fct0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] fct0 is /pseudo/fct at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: stmf0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] stmf0 is /pseudo/stmf at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: dcpc0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] dcpc0 is /pseudo/dcpc at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: dtrace0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fbt0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: lockstat0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: profile0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] profile0 is /pseudo/profile at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: sdt0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: systrace0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fcsm0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm at 0 Oct 14 20:23:14 oozfs kvm: [ID 721306 kern.warning] WARNING: kvm: no hardware support Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fcp0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: llc10 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1 at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: lofi0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk at 1024 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: ucode0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: pool0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] pool0 is /pseudo/pool at 0 Oct 14 20:23:14 oozfs ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running. Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: fssnap0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: nsmb0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] nsmb0 is /pseudo/nsmb at 0 Oct 14 20:23:14 oozfs pseudo: [ID 129642 kern.info] pseudo-device: bpf0 Oct 14 20:23:14 oozfs genunix: [ID 936769 kern.info] bpf0 is /pseudo/bpf at 0 Oct 14 20:23:17 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 0 irq 0xe vector 0x45 ioapic 0x3 intin 0xe is bound to cpu 0 Oct 14 20:23:17 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 1 irq 0xf vector 0x45 ioapic 0x3 intin 0xf is bound to cpu 1 Oct 14 20:23:20 oozfs smbd[554]: [ID 413393 daemon.error] dyndns: failed to get domainname Oct 14 20:23:24 oozfs napp-it-mhttpd[628]: [ID 732965 daemon.warning] started as root without requesting chroot(), warning only Oct 14 20:23:24 oozfs napp-it-mhttpd[628]: [ID 692443 daemon.notice] mini_httpd/1.19 19dec2003 starting on oozfs, port 81 Oct 14 20:23:29 oozfs mac: [ID 736570 kern.info] NOTICE: rge0 unregistered Oct 14 20:24:02 oozfs pcplusmp: [ID 805372 kern.info] pcplusmp: pci10ec,8168 (rge) instance 0 irq 0x1a vector 0x61 ioapic 0xff intin 0xff is bound to cpu 0 Oct 14 20:24:02 oozfs rge: [ID 801725 kern.info] NOTICE: rge0: Using MSI interrupt type Oct 14 20:24:02 oozfs mac: [ID 469746 kern.info] NOTICE: rge0 registered Oct 14 20:24:02 oozfs pseudo: [ID 129642 kern.info] pseudo-device: devinfo0 Oct 14 20:24:02 oozfs genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo at 0 From mmabis at vmware.com Mon Oct 14 22:07:09 2013 From: mmabis at vmware.com (Matthew Mabis) Date: Mon, 14 Oct 2013 15:07:09 -0700 (PDT) Subject: [OmniOS-discuss] RAID/SAS Controller Recommendations In-Reply-To: References: Message-ID: <1640729554.1991057.1381788429081.JavaMail.root@vmware.com> I have been using a LSI 1068E card for a very long time (Multiple years) with solaris foundations Pre-Omni... SOLID as a ROCK! downside is that you cant have >2TB Drives with the LSI 1068E you would have to get a LSI 2008 or better Matt Mabis Sr. Consultant PSO (End User Computing) mmabis at vmware.com 3401 Hillview Avenue, Palo Alto, CA 94304 530.481.5405 Mobile ----- Original Message ----- From: "alka" To: "omnios-discuss" Sent: Monday, October 14, 2013 12:27:37 PM Subject: Re: [OmniOS-discuss] RAID/SAS Controller Recommendations LSI 2308 is fine with OmniOS I use the LSI 9207 alike controller on a SuperMicro Board without problem. The LSI 9207-8e is what you may want in general (Have not had a MD S600 to test against). Am 14.10.2013 um 20:01 schrieb Nate Smith: I'm looking to install a new Omnios server on a Dell T710 server with an HP MDS 600 RAID Cabinet. I currently run a similar setup with OpenIndiana and an MDS600. On this machine, I use LSI-9285-8e controllers, which are the LSISAS2208 Chipset. All targets are set to JBOD pass/thru mode. This was a finicky setup when I got it going on OI, and it took the Solaris drivers for the card to get it work. I could never get the setup to work with an LSI 9201-16e. It would not play nice with the SAS expanders (yes, all my disks are SAS). The nice upshot with the 9285 was that I could use the Megaraid Utility for monitoring, and the hardware drivers handled the dual attached SAS perfectly. But... I have had the occasional hardware lockup when using Napp-it. Forward to 18 months later, and I want to switch to Omnios, or at least test, and I've purchased another MDS600 cabinet off ebay to do it. I'm looking at controllers, and I've noticed that the OmniOS compatibility list is pretty extensive. I'm thinking about getting 9286-8e again, which is still based on the LSISAS2208 Chipset, but is PCIE 3.0 instead of 2.0 (which really is a negligible difference). Can anyone recommend any other controllers to look at? I was perusing the LSI SAS2308 based chipsets, but I'm not sure how mature the drivers are. So if anyone knows any controllers which they've worked with an HP MDS600, dual attached, etc, that would be great. Otherwise, any words of wisdom would be appreciated. Thanks. -Nate _______________________________________________ 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: From narayan.desai at gmail.com Tue Oct 15 05:09:25 2013 From: narayan.desai at gmail.com (Narayan Desai) Date: Tue, 15 Oct 2013 00:09:25 -0500 Subject: [OmniOS-discuss] RAID/SAS Controller Recommendations In-Reply-To: <1640729554.1991057.1381788429081.JavaMail.root@vmware.com> References: <1640729554.1991057.1381788429081.JavaMail.root@vmware.com> Message-ID: On a related note, is there a driver in the pipeline for the new LSI 12gb HBAs? -nld On Mon, Oct 14, 2013 at 5:07 PM, Matthew Mabis wrote: > I have been using a LSI 1068E card for a very long time (Multiple years) > with solaris foundations Pre-Omni... SOLID as a ROCK! > > downside is that you cant have >2TB Drives with the LSI 1068E you would > have to get a LSI 2008 or better > > *Matt Mabis* > *Sr. Consultant PSO (End User Computing)* > mmabis at vmware.com > 3401 Hillview Avenue, Palo Alto, CA 94304 > 530.481.5405 Mobile > > [image: VMware] > > > > ------------------------------ > *From: *"alka" > *To: *"omnios-discuss" > *Sent: *Monday, October 14, 2013 12:27:37 PM > *Subject: *Re: [OmniOS-discuss] RAID/SAS Controller Recommendations > > > LSI 2308 is fine with OmniOS > I use the LSI 9207 alike controller on a SuperMicro Board without problem. > > The LSI 9207-8e is what you may want in general (Have not had a MD S600 to > test against). > > > > Am 14.10.2013 um 20:01 schrieb Nate Smith: > > I'm looking to install a new Omnios server on a Dell T710 server with an > HP MDS 600 RAID Cabinet. > > I currently run a similar setup with OpenIndiana and an MDS600. On this > machine, I use LSI-9285-8e controllers, which are the LSISAS2208 Chipset. > All targets are set to JBOD pass/thru mode. This was a finicky setup when > I got it going on OI, and it took the Solaris drivers for the card to get > it work. I could never get the setup to work with an LSI 9201-16e. It > would not play nice with the SAS expanders (yes, all my disks are SAS). > The nice upshot with the 9285 was that I could use the Megaraid Utility > for monitoring, and the hardware drivers handled the dual attached SAS > perfectly. But... I have had the occasional hardware lockup when using > Napp-it. > > Forward to 18 months later, and I want to switch to Omnios, or at least > test, and I've purchased another MDS600 cabinet off ebay to do it. I'm > looking at controllers, and I've noticed that the OmniOS compatibility list > is pretty extensive. I'm thinking about getting 9286-8e again, which is > still based on the LSISAS2208 Chipset, but is PCIE 3.0 instead of 2.0 > (which really is a negligible difference). Can anyone recommend any other > controllers to look at? I was perusing the LSI SAS2308 based chipsets, but > I'm not sure how mature the drivers are. > > So if anyone knows any controllers which they've worked with an HP MDS600, > dual attached, etc, that would be great. Otherwise, any words of wisdom > would be appreciated. Thanks. > > -Nate > > _______________________________________________ > 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: From mayuresh at kathe.in Tue Oct 15 06:49:30 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Tue, 15 Oct 2013 02:49:30 -0400 Subject: [OmniOS-discuss] a text-mode web browser! Message-ID: <20131015064929.GA31444@wolfman.devio.us> hi, are there any chances of including a text-mode web browser in the package repository for the upcoming release? how about atleast "lynx"? From lionelcons1972 at gmail.com Tue Oct 15 12:51:32 2013 From: lionelcons1972 at gmail.com (Lionel Cons) Date: Tue, 15 Oct 2013 14:51:32 +0200 Subject: [OmniOS-discuss] nfs problems linux (client) illumos (server) In-Reply-To: References: Message-ID: On 14 October 2013 08:29, Tobias Oetiker wrote: > Folks, > > I have this nfs client (ubunty 3.5 kernel) which seems to have > issues talking to our omnios server. In the example below the > client does not seem to get an answer to his ACCESS3 call from > 08:19:48.43 and starts retransmitting. It does not seem as if > packets got lost ... Does this pattern ring a bell? > > (as seen from the omnios server) > > 8:19:42.11355 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=1F8F (read,lookup,modify,extend,delete) > 8:19:42.11358 10.10.10.1 -> 10.10.10.2 NFS R ACCESS3 OK (read,lookup,modify,extend,delete) > 8:19:42.11372 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B8A (read,lookup,modify,extend,delete) > 8:19:42.11387 10.10.10.1 -> 10.10.10.2 NFS R ACCESS3 OK (read,lookup,modify,extend,delete) > 8:19:42.15340 10.10.10.2 -> 10.10.10.1 TCP D=2049 S=822 Ack=3569055649 Seq=330388801 Len=0 Win=20638 Options= > 8:19:42.65429 10.10.10.2 -> 10.10.10.1 NFS C GETATTR3 FH=1391 > 8:19:42.65493 10.10.10.1 -> 10.10.10.2 NFS R GETATTR3 OK > 8:19:42.65507 10.10.10.2 -> 10.10.10.1 TCP D=2049 S=822 Ack=3569055765 Seq=330388917 Len=0 Win=20638 Options= > 8:19:48.43236 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B45 (read,lookup,modify,extend,delete) > 8:19:48.49820 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389029 Seq=3569055765 Len=0 Win=32806 Options= > 8:19:49.12947 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B45 (read,lookup,modify,extend,delete) (retransmit) > 8:19:49.19819 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389141 Seq=3569055765 Len=0 Win=32806 Options= > 8:19:50.53345 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B45 (read,lookup,modify,extend,delete) (retransmit) > 8:19:50.59817 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389253 Seq=3569055765 Len=0 Win=32806 Options= > 8:19:52.64147 10.10.10.2 -> 10.10.10.1 NFS C ACCESS3 FH=8B45 (read,lookup,modify,extend,delete) (retransmit) > 8:19:52.70810 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389365 Seq=3569055765 Len=0 Win=32806 Options= > 8:19:53.50200 10.10.10.2 -> 10.10.10.1 NFS C GETATTR3 FH=08CA > 8:19:53.56808 10.10.10.1 -> 10.10.10.2 TCP D=822 S=2049 Ack=330389477 Seq=3569055765 Len=0 Win=32806 Options= > > (as seeen from the ubuntu linux 3.5 client) > > 08:19:42.113444 10.10.10.2 -> 10.10.10.1 NFS 186 V3 ACCESS Call, FH:0xbff47443, [Check: RD LU MD XT DL] > 08:19:42.113512 10.10.10.1 -> 10.10.10.2 NFS 190 V3 ACCESS Reply (Call In 86), [Allowed: RD LU MD XT DL] > 08:19:42.113620 10.10.10.2 -> 10.10.10.1 NFS 186 V3 ACCESS Call, FH:0x312c9eb9, [Check: RD LU MD XT DL] > 08:19:42.113804 10.10.10.1 -> 10.10.10.2 NFS 190 V3 ACCESS Reply (Call In 88), [Allowed: RD LU MD XT DL] > 08:19:42.153301 10.10.10.2 -> 10.10.10.1 TCP 66 822 > nfs [ACK] Seq=7121 Ack=4485 Win=20638 Len=0 TSval=3449855200 TSecr=396193080 > 08:19:42.654182 10.10.10.2 -> 10.10.10.1 NFS 182 V3 GETATTR Call, FH:0x7b7d2a4e > 08:19:42.654932 10.10.10.1 -> 10.10.10.2 NFS 182 V3 GETATTR Reply (Call In 91) Regular File mode:0644 uid:0 gid:0 > 08:19:42.654979 10.10.10.2 -> 10.10.10.1 TCP 66 822 > nfs [ACK] Seq=7237 Ack=4601 Win=20638 Len=0 TSval=3449855325 TSecr=396193134 > 08:19:48.432250 10.10.10.2 -> 10.10.10.1 NFS 178 V3 ACCESS Call, FH:0x505b4bee, [Check: RD LU MD XT DL] > 08:19:48.498217 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7349 Win=32806 Len=0 TSval=396193719 TSecr=3449856769 > 08:19:49.129364 10.10.10.2 -> 10.10.10.1 NFS 178 [RPC retransmission of #94]V3 ACCESS Call, FH:0x505b4bee, [Check: RD LU MD XT DL] > 08:19:49.198215 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7461 Win=32806 Len=0 TSval=396193789 TSecr=3449856944 > 08:19:50.533336 10.10.10.2 -> 10.10.10.1 NFS 178 [RPC retransmission of #94]V3 ACCESS Call, FH:0x505b4bee, [Check: RD LU MD XT DL] > 08:19:50.598191 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7573 Win=32806 Len=0 TSval=396193929 TSecr=3449857295 > 08:19:52.641348 10.10.10.2 -> 10.10.10.1 NFS 178 [RPC retransmission of #94]V3 ACCESS Call, FH:0x505b4bee, [Check: RD LU MD XT DL] > 08:19:52.708091 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7685 Win=32806 Len=0 TSval=396194140 TSecr=3449857822 > 08:19:53.501892 10.10.10.2 -> 10.10.10.1 NFS 178 V3 GETATTR Call, FH:0x8a584406 > 08:19:53.568104 10.10.10.1 -> 10.10.10.2 TCP 66 nfs > 822 [ACK] Seq=4601 Ack=7797 Win=32806 Len=0 TSval=396194226 TSecr=3449858037 Tobias, please send all NFS issues to the Illumos developer (Illumos's equivalent of the Linux kernel.org lists) list because the NFS developers are concentrated there. Lionel From esproul at omniti.com Tue Oct 15 16:05:18 2013 From: esproul at omniti.com (Eric Sproul) Date: Tue, 15 Oct 2013 12:05:18 -0400 Subject: [OmniOS-discuss] RAID/SAS Controller Recommendations In-Reply-To: References: <1640729554.1991057.1381788429081.JavaMail.root@vmware.com> Message-ID: On Tue, Oct 15, 2013 at 1:09 AM, Narayan Desai wrote: > On a related note, is there a driver in the pipeline for the new LSI 12gb > HBAs? > There was a brief discussion on #illumos about a month ago: http://echelog.com/logs/browse/illumos/1379282400 ([22:23:38] wesolows: Have you played with the LSI 9300 board, with its 3008 chip and "MPT Fusion 2.5"?) The short answer is that developers need hardware and access to programming information for that hardware. If you can help make that happen, it'd be much appreciated. Dan McDonald at Nexenta has done a lot of work on mpt_sas/mr_sas in the past, and Keith Wesolowski at Joyent would also be a good recipient of test gear. Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From mayuresh at kathe.in Tue Oct 15 16:15:01 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Tue, 15 Oct 2013 12:15:01 -0400 Subject: [OmniOS-discuss] omnios : documentation : another approach Message-ID: <20131015161500.GA25324@wolfman.devio.us> hi, while new here, facing a lot of problems while accessing documentation at the console. literally had to boot off ubuntu-live, copy the general administration contents off the wiki, paste them into libre-office writer and get a printout. the document was totally worth the effort. :) but, it's quite a pain to not have access to it while at the console. an alternative would be to build the documentation as a set of html pages (http://devio.us/~mayuresh/omnios/) and have some text-mode browser in the package repository. also, essential would be a firstboot/afterboot manpage which shows how to access such hyperlinked documentation after network setup. please take a look at the above mentioned page, it's multi-device viewable and is quite accessible even via lynx at the console. :) being honest, i'd started off with the same for smartos, but, now that i've completely migrated to omnios, i believe i should invest my time and energy out here, i know it will be worth it. :) best. From olaf.lists at gmail.com Tue Oct 15 21:48:39 2013 From: olaf.lists at gmail.com (Olaf Marzocchi) Date: Tue, 15 Oct 2013 23:48:39 +0200 Subject: [OmniOS-discuss] libgcrypt apparently not updated on 151006 Message-ID: <96C21979-DBCF-4E04-A8FB-33918DA242F8@gmail.com> Hello everyone, I was checking my install (151006 stable) looking for old packages and I saw pkg:/system/library/security/libgcrypt at 1.5.0-0.151004 installed. At the same time, I see pkg:/omniti/security/libgcrypt at 1.5.3-0.151006 available on the secondary repo. Why hasn't it been pushed to mainline? it's a security fix. If you just forgot it, then this is a reminder :) Regards, Olaf Marzocchi From jesus at omniti.com Tue Oct 15 21:57:00 2013 From: jesus at omniti.com (Theo Schlossnagle) Date: Tue, 15 Oct 2013 17:57:00 -0400 Subject: [OmniOS-discuss] libgcrypt apparently not updated on 151006 In-Reply-To: <96C21979-DBCF-4E04-A8FB-33918DA242F8@gmail.com> References: <96C21979-DBCF-4E04-A8FB-33918DA242F8@gmail.com> Message-ID: There is no libgcrypt in 151006. It's not needed for anything in core. Just uninstall it. On Tue, Oct 15, 2013 at 5:48 PM, Olaf Marzocchi wrote: > Hello everyone, > I was checking my install (151006 stable) looking for old packages and I > saw > > pkg:/system/library/security/libgcrypt at 1.5.0-0.151004 > > installed. At the same time, I see > > pkg:/omniti/security/libgcrypt at 1.5.3-0.151006 > > available on the secondary repo. > Why hasn't it been pushed to mainline? it's a security fix. If you just > forgot it, then this is a reminder :) > > Regards, > Olaf Marzocchi > > _______________________________________________ > 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: From mayuresh at kathe.in Wed Oct 16 04:32:35 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Wed, 16 Oct 2013 00:32:35 -0400 Subject: [OmniOS-discuss] next release : lesser gnu! Message-ID: <20131016043235.GA2661@wolfman.devio.us> hi, been fiddling around with the system for less than a week, and found that there's an over-abundance of 'gnu' stuff in the base install (which is minimalistic). any particular reason why there's so much reliance on /usr/gnu/bin when there is already /usr/bin. just curious. :) From mayuresh at kathe.in Wed Oct 16 14:24:18 2013 From: mayuresh at kathe.in (mayuresh at kathe.in) Date: Wed, 16 Oct 2013 19:54:18 +0530 Subject: [OmniOS-discuss] documentation : faq style... Message-ID: hello, do take a look at, and keep an eye on; http://kathe.in/omnios/faq.html need to know if i would need permission from omniti to pull information out of the omnios wiki(s). feedback, suggestions and content welcome. :) ~mayuresh From mir at miras.org Wed Oct 16 14:52:14 2013 From: mir at miras.org (Michael Rasmussen) Date: Wed, 16 Oct 2013 16:52:14 +0200 Subject: [OmniOS-discuss] Latest 15007 fails to run zilstat Message-ID: <20131016165214.228380c5@sleipner.datanom.net> Hi list, I am not able to run Richard Ellings script zilstat anymore since upgrading omnios bloody to latest "release". Running the script gives the following error: dtrace: invalid probe specifier : "/usr/lib/dtrace/nfssrv.d", line 34: operator . cannot be applied to type "phy_if_t (*)()"; must be applied to a struct or union -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- Breeding rabbits is a hare raising experience. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From fabio at fabiorabelo.wiki.br Wed Oct 16 15:41:39 2013 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Wed, 16 Oct 2013 12:41:39 -0300 Subject: [OmniOS-discuss] Netgear 10GB switch LACP SOLVED Message-ID: Hi to all last week I ask here what was the most up-to-date how-to about LACP and OmniOS . Nobody answered, so I keep trying, and now I get it ! In the netgear 10 GB switch ( very good by the way !!! ) create the LACP with all defaults . In OmniOS I did this : dladm add-aggr -d ixgbe0 -d ixgbe1 1 ipadm create-addr -T static -a 192.168.1.20/24 aggr1/v4 dladm modify-aggr -L active -T short 1 My netwotk card are Intel, and the IP for this OmniOS box are 192.168.1.10 And now, finaly it is up and running ... I am posting it here to save time, if someone get this switcher, this are the way ... F?bio Rabelo From skiselkov.ml at gmail.com Wed Oct 16 15:47:22 2013 From: skiselkov.ml at gmail.com (Saso Kiselkov) Date: Wed, 16 Oct 2013 16:47:22 +0100 Subject: [OmniOS-discuss] Netgear 10GB switch LACP SOLVED In-Reply-To: References: Message-ID: <525EB50A.9090209@gmail.com> On 10/16/13 4:41 PM, F?bio Rabelo wrote: > Hi to all > > last week I ask here what was the most up-to-date how-to about LACP and OmniOS . > > Nobody answered, so I keep trying, and now I get it ! > > In the netgear 10 GB switch ( very good by the way !!! ) create the > LACP with all defaults . > > In OmniOS I did this : > > > dladm add-aggr -d ixgbe0 -d ixgbe1 1 > > ipadm create-addr -T static -a 192.168.1.20/24 aggr1/v4 > > dladm modify-aggr -L active -T short 1 > > > My netwotk card are Intel, and the IP for this OmniOS box are 192.168.1.10 > > And now, finaly it is up and running ... > > I am posting it here to save time, if someone get this switcher, this > are the way ... Thanks for following up on this, Fabio, too few people do that and then we get unresolved threads lingering in mailing list archives. You did the right thing! Cheers, -- Saso From mir at miras.org Wed Oct 16 16:17:00 2013 From: mir at miras.org (Michael Rasmussen) Date: Wed, 16 Oct 2013 18:17:00 +0200 Subject: [OmniOS-discuss] Netgear 10GB switch LACP SOLVED In-Reply-To: References: Message-ID: <20131016181700.60864d80@sleipner.datanom.net> On Wed, 16 Oct 2013 12:41:39 -0300 F?bio Rabelo wrote: > Hi to all > > last week I ask here what was the most up-to-date how-to about LACP and OmniOS . > > Nobody answered, so I keep trying, and now I get it ! > > In the netgear 10 GB switch ( very good by the way !!! ) create the > LACP with all defaults . > > In OmniOS I did this : > > > dladm add-aggr -d ixgbe0 -d ixgbe1 1 > According to the man page for dladm -d should be -l ???? dladm add-aggr [-t] [-R root-dir] -l ether-link1 [-l ether-link2...] aggr-link -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- Make sure all variables are initialised before use. - The Elements of Programming Style (Kernighan & Plaugher) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From fabio at fabiorabelo.wiki.br Wed Oct 16 16:27:13 2013 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Wed, 16 Oct 2013 13:27:13 -0300 Subject: [OmniOS-discuss] Netgear 10GB switch LACP SOLVED In-Reply-To: <20131016181700.60864d80@sleipner.datanom.net> References: <20131016181700.60864d80@sleipner.datanom.net> Message-ID: 2013/10/16 Michael Rasmussen : > On Wed, 16 Oct 2013 12:41:39 -0300 > F?bio Rabelo wrote: > >> Hi to all >> >> last week I ask here what was the most up-to-date how-to about LACP and OmniOS . >> >> Nobody answered, so I keep trying, and now I get it ! >> >> In the netgear 10 GB switch ( very good by the way !!! ) create the >> LACP with all defaults . >> >> In OmniOS I did this : >> >> >> dladm add-aggr -d ixgbe0 -d ixgbe1 1 >> > According to the man page for dladm -d should be -l ???? > > dladm add-aggr [-t] [-R root-dir] -l ether-link1 [-l ether-link2...] > aggr-link That's the kind of problem I faced with this issue ... All how-tos over the web, ans most of man pages are out-dated ... I had to take one peace of info from here, another peace from there, and it took over a week to get all I need . F?bio Rabelo From richard.elling at richardelling.com Wed Oct 16 16:30:36 2013 From: richard.elling at richardelling.com (Richard Elling) Date: Wed, 16 Oct 2013 09:30:36 -0700 Subject: [OmniOS-discuss] Latest 15007 fails to run zilstat In-Reply-To: <20131016165214.228380c5@sleipner.datanom.net> References: <20131016165214.228380c5@sleipner.datanom.net> Message-ID: On Oct 16, 2013, at 7:52 AM, Michael Rasmussen wrote: > Hi list, > > I am not able to run Richard Ellings script zilstat anymore since > upgrading omnios bloody to latest "release". > > Running the script gives the following error: > dtrace: invalid probe specifier > : "/usr/lib/dtrace/nfssrv.d", line 34: operator . cannot be applied to > type "phy_if_t (*)()"; must be applied to a struct or union That is strange. This should not have changed recently. Can you compare the *.d files to those on http://src.illumos.org/source/xref/illumos-gate/usr/src/lib/libdtrace/common/ -- richard > > -- > Hilsen/Regards > Michael Rasmussen > > Get my public GnuPG keys: > michael rasmussen cc > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E > mir datanom net > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C > mir miras org > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 > -------------------------------------------------------------- > Breeding rabbits is a hare raising experience. > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Richard.Elling at RichardElling.com +1-760-896-4422 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mir at miras.org Wed Oct 16 17:56:08 2013 From: mir at miras.org (Michael Rasmussen) Date: Wed, 16 Oct 2013 19:56:08 +0200 Subject: [OmniOS-discuss] Latest 15007 fails to run zilstat In-Reply-To: References: <20131016165214.228380c5@sleipner.datanom.net> Message-ID: <20131016195608.19721a45@sleipner.datanom.net> On Wed, 16 Oct 2013 09:30:36 -0700 Richard Elling wrote: > > That is strange. This should not have changed recently. Can you compare > the *.d files to those on http://src.illumos.org/source/xref/illumos-gate/usr/src/lib/libdtrace/common/ Here goes: -rw-r--r-- 1 root root 4967 Oct 16 19:52 fc.d -rw-r--r-- 1 root root 17162 Oct 16 19:52 iscsit.d -rw-r--r-- 1 root root 4335 Oct 16 19:52 nfs.d -rw-r--r-- 1 root root 1632 Oct 16 19:52 nfssrv.d -rw-r--r-- 1 root root 2699 Oct 16 19:52 sched.d -rw-r--r-- 1 root root 3035 Oct 16 19:52 scsi.d -rw-r--r-- 1 root root 5405 Oct 16 19:52 srp.d -rw-r--r-- 1 root root 1962 Oct 16 19:52 unistd.d root at nas:/tmp/dtrace# diff -u fc.d /usr/lib/dtrace/fc.d root at nas:/tmp/dtrace# diff -u iscsit.d /usr/lib/dtrace/iscsit.d root at nas:/tmp/dtrace# diff -u nfs.d /usr/lib/dtrace/nfs.d root at nas:/tmp/dtrace# diff -u nfssrv.d /usr/lib/dtrace/nfssrv.d root at nas:/tmp/dtrace# diff -u sched.d /usr/lib/dtrace/sched.d root at nas:/tmp/dtrace# diff -u scsi.d /usr/lib/dtrace/scsi.d root at nas:/tmp/dtrace# diff -u srp.d /usr/lib/dtrace/srp.d root at nas:/tmp/dtrace# diff -u unistd.d /usr/lib/dtrace/unistd.d No difference what so ever! -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- Weinberg's First Law: Progress is only made on alternate Fridays. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From richard.elling at richardelling.com Wed Oct 16 20:43:23 2013 From: richard.elling at richardelling.com (Richard Elling) Date: Wed, 16 Oct 2013 13:43:23 -0700 Subject: [OmniOS-discuss] Latest 15007 fails to run zilstat In-Reply-To: <20131016195608.19721a45@sleipner.datanom.net> References: <20131016165214.228380c5@sleipner.datanom.net> <20131016195608.19721a45@sleipner.datanom.net> Message-ID: <63B746E7-D23C-4AEB-9037-CB6999E0AAC4@richardelling.com> On Oct 16, 2013, at 10:56 AM, Michael Rasmussen wrote: > On Wed, 16 Oct 2013 09:30:36 -0700 > Richard Elling wrote: > >> >> That is strange. This should not have changed recently. Can you compare >> the *.d files to those on http://src.illumos.org/source/xref/illumos-gate/usr/src/lib/libdtrace/common/ > > Here goes: > -rw-r--r-- 1 root root 4967 Oct 16 19:52 fc.d > -rw-r--r-- 1 root root 17162 Oct 16 19:52 iscsit.d > -rw-r--r-- 1 root root 4335 Oct 16 19:52 nfs.d > -rw-r--r-- 1 root root 1632 Oct 16 19:52 nfssrv.d > -rw-r--r-- 1 root root 2699 Oct 16 19:52 sched.d > -rw-r--r-- 1 root root 3035 Oct 16 19:52 scsi.d > -rw-r--r-- 1 root root 5405 Oct 16 19:52 srp.d > -rw-r--r-- 1 root root 1962 Oct 16 19:52 unistd.d > root at nas:/tmp/dtrace# diff -u fc.d /usr/lib/dtrace/fc.d > root at nas:/tmp/dtrace# diff -u iscsit.d /usr/lib/dtrace/iscsit.d > root at nas:/tmp/dtrace# diff -u nfs.d /usr/lib/dtrace/nfs.d > root at nas:/tmp/dtrace# diff -u nfssrv.d /usr/lib/dtrace/nfssrv.d > root at nas:/tmp/dtrace# diff -u sched.d /usr/lib/dtrace/sched.d > root at nas:/tmp/dtrace# diff -u scsi.d /usr/lib/dtrace/scsi.d > root at nas:/tmp/dtrace# diff -u srp.d /usr/lib/dtrace/srp.d > root at nas:/tmp/dtrace# diff -u unistd.d /usr/lib/dtrace/unistd.d > > No difference what so ever! ok, next question for OmniTI: is this release compiled with gcc? There are/were some CTF issues when using gcc. I thought that they were fixed upstream. -- richard > > -- > Hilsen/Regards > Michael Rasmussen > > Get my public GnuPG keys: > michael rasmussen cc > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E > mir datanom net > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C > mir miras org > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 > -------------------------------------------------------------- > Weinberg's First Law: > Progress is only made on alternate Fridays. -- Richard.Elling at RichardElling.com +1-760-896-4422 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesus at omniti.com Wed Oct 16 20:49:29 2013 From: jesus at omniti.com (Theo Schlossnagle) Date: Wed, 16 Oct 2013 16:49:29 -0400 Subject: [OmniOS-discuss] Latest 15007 fails to run zilstat In-Reply-To: <63B746E7-D23C-4AEB-9037-CB6999E0AAC4@richardelling.com> References: <20131016165214.228380c5@sleipner.datanom.net> <20131016195608.19721a45@sleipner.datanom.net> <63B746E7-D23C-4AEB-9037-CB6999E0AAC4@richardelling.com> Message-ID: On Wed, Oct 16, 2013 at 4:43 PM, Richard Elling < richard.elling at richardelling.com> wrote: > On Oct 16, 2013, at 10:56 AM, Michael Rasmussen wrote: > > On Wed, 16 Oct 2013 09:30:36 -0700 > Richard Elling wrote: > > > That is strange. This should not have changed recently. Can you compare > the *.d files to those on > http://src.illumos.org/source/xref/illumos-gate/usr/src/lib/libdtrace/common/ > > > Here goes: > -rw-r--r-- 1 root root 4967 Oct 16 19:52 fc.d > -rw-r--r-- 1 root root 17162 Oct 16 19:52 iscsit.d > -rw-r--r-- 1 root root 4335 Oct 16 19:52 nfs.d > -rw-r--r-- 1 root root 1632 Oct 16 19:52 nfssrv.d > -rw-r--r-- 1 root root 2699 Oct 16 19:52 sched.d > -rw-r--r-- 1 root root 3035 Oct 16 19:52 scsi.d > -rw-r--r-- 1 root root 5405 Oct 16 19:52 srp.d > -rw-r--r-- 1 root root 1962 Oct 16 19:52 unistd.d > root at nas:/tmp/dtrace# diff -u fc.d /usr/lib/dtrace/fc.d > root at nas:/tmp/dtrace# diff -u iscsit.d /usr/lib/dtrace/iscsit.d > root at nas:/tmp/dtrace# diff -u nfs.d /usr/lib/dtrace/nfs.d > root at nas:/tmp/dtrace# diff -u nfssrv.d /usr/lib/dtrace/nfssrv.d > root at nas:/tmp/dtrace# diff -u sched.d /usr/lib/dtrace/sched.d > root at nas:/tmp/dtrace# diff -u scsi.d /usr/lib/dtrace/scsi.d > root at nas:/tmp/dtrace# diff -u srp.d /usr/lib/dtrace/srp.d > root at nas:/tmp/dtrace# diff -u unistd.d /usr/lib/dtrace/unistd.d > > No difference what so ever! > > > ok, next question for OmniTI: is this release compiled with gcc? > There are/were some CTF issues when using gcc. I thought that they > were fixed upstream. > -- richard > > Gate is built with gcc 4.4 (upstream) and the userland is built with gcc 4.8 -- Theo Schlossnagle http://omniti.com/is/theo-schlossnagle -------------- next part -------------- An HTML attachment was scrubbed... URL: From mir at miras.org Wed Oct 16 21:25:32 2013 From: mir at miras.org (Michael Rasmussen) Date: Wed, 16 Oct 2013 23:25:32 +0200 Subject: [OmniOS-discuss] Latest 15007 fails to run zilstat In-Reply-To: References: <20131016165214.228380c5@sleipner.datanom.net> <20131016195608.19721a45@sleipner.datanom.net> <63B746E7-D23C-4AEB-9037-CB6999E0AAC4@richardelling.com> Message-ID: <20131016232532.717f6030@sleipner.datanom.net> On Wed, 16 Oct 2013 16:49:29 -0400 Theo Schlossnagle wrote: > Gate is built with gcc 4.4 (upstream) and the userland is built with gcc 4.8 > If I recall correct type casting in gcc 4.4 was more forgiven than is the case with gcc 4.8. It seems the following cause problems: (/usr/lib/dtrace/nfssrv.d line 34) #pragma D binding "1.5" translator translator conninfo_t < rfs4_client_t *P > { ci_protocol = (P->rc_addr.ss_family == AF_INET) ? "ipv4" : "ipv6"; More precisely: P->rc_addr.ss_family This should have been explicitly type casted before referencing the struct like: ( (* TYPE) P )->rc_addr.ss_family -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- Why bother building any more nuclear warheads until we use the ones we have? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From mayuresh at kathe.in Thu Oct 17 03:58:05 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Wed, 16 Oct 2013 23:58:05 -0400 Subject: [OmniOS-discuss] hostid missing or corrupt Message-ID: <20131017035805.GA5050@wolfman.devio.us> hello, noticed the following messages just before the login prompt after bootup; WARNING: hostid missing or corrupt on line 3 of /etc/hostid WARNING: Unable to set hostid upon opening /etc/hostid, found a line stating; # DO NOT EDIT how do i rectify the problem (if any)? thanks, ~mayuresh From obencandemir at gmail.com Thu Oct 17 06:47:34 2013 From: obencandemir at gmail.com (Gmail Account) Date: Thu, 17 Oct 2013 16:47:34 +1000 Subject: [OmniOS-discuss] Microserver G8 : NIC not working. Message-ID: I have recently purchased a HP Microserver G8 and upgraded it with a Xeon 1265 Vt-d capable CPU and 16GB of ECC RAM. Problem is that the NIC doesn't seem to work in any of the Solaris based OSes. SmartOS fails; and sadly OmniOS does too. It seems to find the interfaces and I can run through the instructions for network setup but the machine is unable to ping any WAN or LAN machines. The confusing thing is that when I configure as 'dhcp' type, the machine is able to obtain an address - but again it is unable to ping any local machines or indeed any other WAN machines. The card is a HP 332i which is a Broadcom 5720 - which the Illumos HCL says isn't supported. Is this card supported fully in OmniOS? Are there any other configuration tips that might get things going on the G8 Microserver? Thanks in advance, Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: From mayuresh at kathe.in Thu Oct 17 07:23:48 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 17 Oct 2013 03:23:48 -0400 Subject: [OmniOS-discuss] hostid missing or corrupt In-Reply-To: <20131017035805.GA5050@wolfman.devio.us> References: <20131017035805.GA5050@wolfman.devio.us> Message-ID: <20131017072346.GA1829@wolfman.devio.us> hi, digging up showed the following to be a solution. rm /etc/hostid /lib/svc/method/svc-hostid and yeah, it just works. :) On Wed, Oct 16, 2013 at 11:58:05PM -0400, Mayuresh Kathe wrote: > hello, > > noticed the following messages just before the login prompt > after bootup; > WARNING: hostid missing or corrupt on line 3 of /etc/hostid > WARNING: Unable to set hostid > > upon opening /etc/hostid, found a line stating; > # DO NOT EDIT > > how do i rectify the problem (if any)? > > thanks, > > ~mayuresh > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From mayuresh at kathe.in Thu Oct 17 07:43:42 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 17 Oct 2013 03:43:42 -0400 Subject: [OmniOS-discuss] login error : solaris_audit Message-ID: <20131017074339.GA13258@wolfman.devio.us> hi, my system is now throwing up errors after logging in. Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 Solaris_audit mapping to : Error 9 any pointers on how to resolve this would be welcome. (my google skills aren't as well develped as i would've liked them to be). ~mayuresh From mayuresh at kathe.in Thu Oct 17 07:47:05 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 17 Oct 2013 03:47:05 -0400 Subject: [OmniOS-discuss] login error : solaris_audit Message-ID: <20131017074701.GA14110@wolfman.devio.us> previous message showed the wrong error number, so here goes again. ---- hi, my system is now throwing up errors after logging in. Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 Solaris_audit mapping to : Error 0 any pointers on how to resolve this would be welcome. (my google skills aren't as well develped as i would've liked them to be). thanks, ~mayuresh From eugen at leitl.org Thu Oct 17 07:54:22 2013 From: eugen at leitl.org (Eugen Leitl) Date: Thu, 17 Oct 2013 09:54:22 +0200 Subject: [OmniOS-discuss] Microserver G8 : NIC not working. In-Reply-To: References: Message-ID: <20131017075422.GA10405@leitl.org> On Thu, Oct 17, 2013 at 04:47:34PM +1000, Gmail Account wrote: > Is this card supported fully in OmniOS? Are there any other configuration > tips that might get things going on the G8 Microserver? I always put Intel NICs in all my Microservers, whether the onboard NIC is supported, or not. Put in a dual-port one, if you don't mind paying 3-4 times the price of single-port. From borising at gmail.com Thu Oct 17 07:55:24 2013 From: borising at gmail.com (Bo Agerskov Rising) Date: Thu, 17 Oct 2013 09:55:24 +0200 Subject: [OmniOS-discuss] login error : solaris_audit In-Reply-To: <20131017074339.GA13258@wolfman.devio.us> References: <20131017074339.GA13258@wolfman.devio.us> Message-ID: <78F04535-23BA-48FA-8228-907B1898DCDE@gmail.com> Hi Mayuresh, My guess is that the system can't lookup it's hostname in the DNS server. Regards, Bo Agerskov Rising borising at gmail.com On 17/10/2013, at 09.43, Mayuresh Kathe wrote: > hi, my system is now throwing up errors after logging in. > > Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 > Solaris_audit mapping to : Error 9 > > any pointers on how to resolve this would be welcome. > (my google skills aren't as well develped as i would've liked them to be). > > ~mayuresh > > _______________________________________________ > 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: From mayuresh at kathe.in Thu Oct 17 08:00:58 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 17 Oct 2013 04:00:58 -0400 Subject: [OmniOS-discuss] login error : solaris_audit In-Reply-To: <78F04535-23BA-48FA-8228-907B1898DCDE@gmail.com> References: <20131017074339.GA13258@wolfman.devio.us> <78F04535-23BA-48FA-8228-907B1898DCDE@gmail.com> Message-ID: <20131017080054.GA548@wolfman.devio.us> hi bo, thanks for the note. but, how do i solve the problem? the system is at home, connected to the internet via 'adsl' and without a public static ip address. thanks, ~mayuresh On Thu, Oct 17, 2013 at 09:55:24AM +0200, Bo Agerskov Rising wrote: > Hi Mayuresh, > > My guess is that the system can't lookup it's hostname in the DNS server. > > Regards, > Bo Agerskov Rising > borising at gmail.com > > On 17/10/2013, at 09.43, Mayuresh Kathe wrote: > > > hi, my system is now throwing up errors after logging in. > > > > Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 > > Solaris_audit mapping to : Error 9 > > > > any pointers on how to resolve this would be welcome. > > (my google skills aren't as well develped as i would've liked them to be). > > > > ~mayuresh > > > > _______________________________________________ > > OmniOS-discuss mailing list > > OmniOS-discuss at lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > From borising at gmail.com Thu Oct 17 08:09:16 2013 From: borising at gmail.com (Bo Agerskov Rising) Date: Thu, 17 Oct 2013 10:09:16 +0200 Subject: [OmniOS-discuss] login error : solaris_audit In-Reply-To: <20131017080054.GA548@wolfman.devio.us> References: <20131017074339.GA13258@wolfman.devio.us> <78F04535-23BA-48FA-8228-907B1898DCDE@gmail.com> <20131017080054.GA548@wolfman.devio.us> Message-ID: Hi Mayuresh, I have my own DNS server in my home lab, so I have just added the DNS correctly. Have you configured the /etc/hosts file with the hostname of the server and IP address? Regards, Bo Agerskov Rising borising at gmail.com On 17/10/2013, at 10.00, Mayuresh Kathe wrote: > hi bo, thanks for the note. > but, how do i solve the problem? > the system is at home, connected to the internet via 'adsl' and > without a public static ip address. > > thanks, > > ~mayuresh > > On Thu, Oct 17, 2013 at 09:55:24AM +0200, Bo Agerskov Rising wrote: >> Hi Mayuresh, >> >> My guess is that the system can't lookup it's hostname in the DNS server. >> >> Regards, >> Bo Agerskov Rising >> borising at gmail.com >> >> On 17/10/2013, at 09.43, Mayuresh Kathe wrote: >> >>> hi, my system is now throwing up errors after logging in. >>> >>> Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 >>> Solaris_audit mapping to : Error 9 >>> >>> any pointers on how to resolve this would be welcome. >>> (my google skills aren't as well develped as i would've liked them to be). >>> >>> ~mayuresh >>> >>> _______________________________________________ >>> 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: From borising at gmail.com Thu Oct 17 08:54:07 2013 From: borising at gmail.com (Bo Agerskov Rising) Date: Thu, 17 Oct 2013 10:54:07 +0200 Subject: [OmniOS-discuss] login error : solaris_audit In-Reply-To: <20131017082016.GA25192@wolfman.devio.us> References: <20131017074339.GA13258@wolfman.devio.us> <78F04535-23BA-48FA-8228-907B1898DCDE@gmail.com> <20131017080054.GA548@wolfman.devio.us> <20131017082016.GA25192@wolfman.devio.us> Message-ID: Hi Mayuresh, NP glad that it helped you out :) CC to the list. Regards, Bo Agerskov Rising borising at gmail.com On 17/10/2013, at 10.20, Mayuresh Kathe wrote: > hi bo, thanks again. > and yes, i just did as you'd suggested, and it works. :) > > ~mayuresh > > On Thu, Oct 17, 2013 at 10:09:16AM +0200, Bo Agerskov Rising wrote: >> Hi Mayuresh, >> >> I have my own DNS server in my home lab, so I have just added the DNS correctly. >> >> Have you configured the /etc/hosts file with the hostname of the server and IP address? >> >> Regards, >> Bo Agerskov Rising >> borising at gmail.com >> >> >> >> >> On 17/10/2013, at 10.00, Mayuresh Kathe wrote: >> >>> hi bo, thanks for the note. >>> but, how do i solve the problem? >>> the system is at home, connected to the internet via 'adsl' and >>> without a public static ip address. >>> >>> thanks, >>> >>> ~mayuresh >>> >>> On Thu, Oct 17, 2013 at 09:55:24AM +0200, Bo Agerskov Rising wrote: >>>> Hi Mayuresh, >>>> >>>> My guess is that the system can't lookup it's hostname in the DNS server. >>>> >>>> Regards, >>>> Bo Agerskov Rising >>>> borising at gmail.com >>>> >>>> On 17/10/2013, at 09.43, Mayuresh Kathe wrote: >>>> >>>>> hi, my system is now throwing up errors after logging in. >>>>> >>>>> Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 >>>>> Solaris_audit mapping to : Error 9 >>>>> >>>>> any pointers on how to resolve this would be welcome. >>>>> (my google skills aren't as well develped as i would've liked them to be). >>>>> >>>>> ~mayuresh >>>>> >>>>> _______________________________________________ >>>>> 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: From obencandemir at gmail.com Thu Oct 17 13:19:28 2013 From: obencandemir at gmail.com (Gmail Account) Date: Thu, 17 Oct 2013 23:19:28 +1000 Subject: [OmniOS-discuss] Microserver G8 : NIC not working. In-Reply-To: <20131017122029.GJ10405@leitl.org> References: <20131017075422.GA10405@leitl.org> <20131017122029.GJ10405@leitl.org> Message-ID: On Thu, Oct 17, 2013 at 10:20 PM, Eugen Leitl wrote: > > > Thanks Eugen, > > > > I have indeed put an Intel in my N40L, but the G8 has an inbuilt dual NIC > > Broadcom and only one PCI slot. > > Are you happy with the G8 so far? Is the onboard IPMI useful > and stable? > The G8 is a fine small form server but still has some annoying issues. The primary problem is the fan control in the BIOS has a bug which leads to >30% fan speed at idle when you use AHCI mode on the disk controller. HP is apparently aware of the issue and hopefully will release a fix soon. The iLO 4 is very useful. It has a third dedicated NIC for this purpose and it works very well. Remote console appears to work for non Windows OS variably, but really requires an "Advanced" license to activate full functions. I don't really need it for remote console as I use ssh, VNC and X forwarding from my KVM virtual machines. > I wanted to use the PCI for a HP P420 RAID controller and use passthrough > > if it wasn't supported in OmniOS directly. > > I'm not sure the Microserver G8 does support hardware > pass-through (VT-d). Have you put a Xeon into it? > > http://b3n.org/installed-xeon-e3-1230v2-in-gen8-hp-microserver/ > > Yes I have installed a Xeon 1265 in mine as well as 16GB ECC RAM. In time it will make a fine machine, but I'm still getting it up to production state through experimentation with various options. OmniOS would be a very desirable one. > > Putting in the Intel NIC would squash this plan. > > > > It is a shame because I am a Solaris person at heart and watching Theo's > > presentation on OmniOS is very compelling. > > > > Maybe I'll have to wait out a few releases but life is short! I'm running > > an el6 platform now with KVM. Anyhow; I'll see how things go and continue > > to watch OmniOS. > > I'm not really comfortable with Solaris, but I can blunder myself > through with web and ML support. OmniOS has been working at least as well > as OpenIndiana > so far. > ... > ______________________________________________________________ > ICBM: 48.07100, 11.36820 http://ativel.com http://postbiota.org > AC894EC5: 38A5 5F46 A4FF 59B8 336B 47EE F46E 3489 AC89 4EC5 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From esproul at omniti.com Thu Oct 17 13:44:14 2013 From: esproul at omniti.com (Eric Sproul) Date: Thu, 17 Oct 2013 09:44:14 -0400 Subject: [OmniOS-discuss] next release : lesser gnu! In-Reply-To: <20131016043235.GA2661@wolfman.devio.us> References: <20131016043235.GA2661@wolfman.devio.us> Message-ID: On Wed, Oct 16, 2013 at 12:32 AM, Mayuresh Kathe wrote: > hi, been fiddling around with the system for less than > a week, and found that there's an over-abundance of > 'gnu' stuff in the base install (which is minimalistic). > any particular reason why there's so much reliance on > /usr/gnu/bin when there is already /usr/bin. In short, we want people to have choices and to be able to use the tools with which they are comfortable. Solaris has long had multiple sets of userland tools that conform to different standards (POSIX, XPG4, XPG6, etc.) which is why there are places like /usr/xpg4, /usr/xpg6, /usr/ucb and /usr/gnu. illumos carries this onward. Eric From esproul at omniti.com Thu Oct 17 13:45:38 2013 From: esproul at omniti.com (Eric Sproul) Date: Thu, 17 Oct 2013 09:45:38 -0400 Subject: [OmniOS-discuss] WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision In-Reply-To: <53DDBD0E-9874-46B5-B55B-D7A77660DD2F@fluffy.co.uk> References: <53DDBD0E-9874-46B5-B55B-D7A77660DD2F@fluffy.co.uk> Message-ID: On Mon, Oct 14, 2013 at 5:52 AM, Ben Summers wrote: > > Hello, > > After updating to OmniOS r151006p on an X4150 without enough hardware support for KVM, I see this on the console after booting: > > Hostname: REDACTED > Configuring devices. > WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision > WARNING: kstat_create('unix', 0, 'kvm_rmap_desc'): namespace collision > WARNING: kstat_create('unix', 0, 'kvm_mmu_page_header'): namespace collision > WARNING: kvm: insufficient hardware support (lacking EPT) > > I'm assuming it's not an issue as I'm not using KVM, but warnings on boot are always amusing. Huh, that's pretty ugly. Does `rem_drv kvm` get rid of those messages? From esproul at omniti.com Thu Oct 17 14:11:10 2013 From: esproul at omniti.com (Eric Sproul) Date: Thu, 17 Oct 2013 10:11:10 -0400 Subject: [OmniOS-discuss] WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision In-Reply-To: <78A2F3B2-2C0B-4C4B-B1F8-21FECA19593F@fluffy.co.uk> References: <53DDBD0E-9874-46B5-B55B-D7A77660DD2F@fluffy.co.uk> <78A2F3B2-2C0B-4C4B-B1F8-21FECA19593F@fluffy.co.uk> Message-ID: On Thu, Oct 17, 2013 at 9:55 AM, Ben Summers wrote: > > On 17 Oct 2013, at 14:45, Eric Sproul wrote: > >> On Mon, Oct 14, 2013 at 5:52 AM, Ben Summers wrote: >>> >>> Hello, >>> >>> After updating to OmniOS r151006p on an X4150 without enough hardware support for KVM, I see this on the console after booting: >>> >>> Hostname: REDACTED >>> Configuring devices. >>> WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision >>> WARNING: kstat_create('unix', 0, 'kvm_rmap_desc'): namespace collision >>> WARNING: kstat_create('unix', 0, 'kvm_mmu_page_header'): namespace collision >>> WARNING: kvm: insufficient hardware support (lacking EPT) >>> >>> I'm assuming it's not an issue as I'm not using KVM, but warnings on boot are always amusing. >> >> Huh, that's pretty ugly. Does `rem_drv kvm` get rid of those messages? > > It only seems to do it on first boot after the update. Weird, maybe it's a bug, maybe not. I'll file a ticket and find out. :) Eric From esproul at omniti.com Thu Oct 17 14:20:53 2013 From: esproul at omniti.com (Eric Sproul) Date: Thu, 17 Oct 2013 10:20:53 -0400 Subject: [OmniOS-discuss] WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision In-Reply-To: References: <53DDBD0E-9874-46B5-B55B-D7A77660DD2F@fluffy.co.uk> <78A2F3B2-2C0B-4C4B-B1F8-21FECA19593F@fluffy.co.uk> Message-ID: Ben, What package updates had been applied when you encountered these warnings? In other words, was it just the delta from 006n -> 006p or was there more? Eric From ben at fluffy.co.uk Thu Oct 17 14:24:55 2013 From: ben at fluffy.co.uk (Ben Summers) Date: Thu, 17 Oct 2013 15:24:55 +0100 Subject: [OmniOS-discuss] WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision In-Reply-To: References: <53DDBD0E-9874-46B5-B55B-D7A77660DD2F@fluffy.co.uk> <78A2F3B2-2C0B-4C4B-B1F8-21FECA19593F@fluffy.co.uk> Message-ID: <108B32A7-8DE6-4AFC-AD7F-BB20C1676BC8@fluffy.co.uk> On 17 Oct 2013, at 15:20, Eric Sproul wrote: > Ben, > What package updates had been applied when you encountered these > warnings? In other words, was it just the delta from 006n -> 006p or > was there more? It was 006c -> 006p, as I installed from the c media and updated (on an X4150 without the processor support for KVM). Thanks! Ben -- http://bens.me.uk From esproul at omniti.com Thu Oct 17 14:42:51 2013 From: esproul at omniti.com (Eric Sproul) Date: Thu, 17 Oct 2013 10:42:51 -0400 Subject: [OmniOS-discuss] WARNING: kstat_create('unix', 0, 'kvm_pte_chain'): namespace collision In-Reply-To: <108B32A7-8DE6-4AFC-AD7F-BB20C1676BC8@fluffy.co.uk> References: <53DDBD0E-9874-46B5-B55B-D7A77660DD2F@fluffy.co.uk> <78A2F3B2-2C0B-4C4B-B1F8-21FECA19593F@fluffy.co.uk> <108B32A7-8DE6-4AFC-AD7F-BB20C1676BC8@fluffy.co.uk> Message-ID: On Thu, Oct 17, 2013 at 10:24 AM, Ben Summers wrote: > > On 17 Oct 2013, at 15:20, Eric Sproul wrote: > >> Ben, >> What package updates had been applied when you encountered these >> warnings? In other words, was it just the delta from 006n -> 006p or >> was there more? > > It was 006c -> 006p, as I installed from the c media and updated (on an X4150 without the processor support for KVM). Thanks. I opened https://github.com/joyent/illumos-kvm/issues/19 Eric From mayuresh at kathe.in Thu Oct 17 18:42:35 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 17 Oct 2013 14:42:35 -0400 Subject: [OmniOS-discuss] perl : only for pkg tools? Message-ID: <20131017184235.GA27551@wolfman.devio.us> hi, is perl included in the base distribution only for supporting pkg tools? From tim at multitalents.net Thu Oct 17 18:52:00 2013 From: tim at multitalents.net (Tim Rice) Date: Thu, 17 Oct 2013 11:52:00 -0700 (PDT) Subject: [OmniOS-discuss] login error : solaris_audit In-Reply-To: <20131017074701.GA14110@wolfman.devio.us> References: <20131017074701.GA14110@wolfman.devio.us> Message-ID: On Thu, 17 Oct 2013, Mayuresh Kathe wrote: > previous message showed the wrong error number, so here goes again. > ---- > hi, my system is now throwing up errors after logging in. > > Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 > Solaris_audit mapping to : Error 0 > > any pointers on how to resolve this would be welcome. > (my google skills aren't as well develped as i would've liked them to be). Is your network connection static or dynamic? Now track down some info and report back. # /sbin/ifconfig -a # cat /etc/inet/hosts # cat /etc/resolv.conf # egrep '^hosts:|^ipnodes:' /etc/nsswitch.conf > > thanks, > > ~mayuresh -- Tim Rice Multitalents tim at multitalents.net From esproul at omniti.com Thu Oct 17 18:52:00 2013 From: esproul at omniti.com (Eric Sproul) Date: Thu, 17 Oct 2013 14:52:00 -0400 Subject: [OmniOS-discuss] perl : only for pkg tools? In-Reply-To: <20131017184235.GA27551@wolfman.devio.us> References: <20131017184235.GA27551@wolfman.devio.us> Message-ID: On Thu, Oct 17, 2013 at 2:42 PM, Mayuresh Kathe wrote: > hi, is perl included in the base distribution only > for supporting pkg tools? Most of the pkg toolkit is in Python, but: pkg search -r 'depend::runtime/perl' shows that quite a few things in upstream illumos do require perl. From mayuresh at kathe.in Thu Oct 17 18:56:29 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 17 Oct 2013 14:56:29 -0400 Subject: [OmniOS-discuss] perl : only for pkg tools? In-Reply-To: References: <20131017184235.GA27551@wolfman.devio.us> Message-ID: <20131017185629.GA15454@wolfman.devio.us> On Thu, Oct 17, 2013 at 02:52:00PM -0400, Eric Sproul wrote: > On Thu, Oct 17, 2013 at 2:42 PM, Mayuresh Kathe wrote: > > hi, is perl included in the base distribution only > > for supporting pkg tools? > > Most of the pkg toolkit is in Python, but: > > pkg search -r 'depend::runtime/perl' > > shows that quite a few things in upstream illumos do require perl. great, that means, perl is here to stay... :) From jesus at omniti.com Thu Oct 17 21:39:07 2013 From: jesus at omniti.com (Theo Schlossnagle) Date: Thu, 17 Oct 2013 17:39:07 -0400 Subject: [OmniOS-discuss] perl : only for pkg tools? In-Reply-To: <20131017185629.GA15454@wolfman.devio.us> References: <20131017184235.GA27551@wolfman.devio.us> <20131017185629.GA15454@wolfman.devio.us> Message-ID: perl is likely to stay, but the perl shipped in core is for use by core. We can change configuration and the version at any time. If you really want perl to power your app, you should consider building your own perl. See: http://pkg.omniti.com/omniti-ms/ http://pkg.omniti.com/omniti-perl/ For how we do it at OmniTI. On Thu, Oct 17, 2013 at 2:56 PM, Mayuresh Kathe wrote: > On Thu, Oct 17, 2013 at 02:52:00PM -0400, Eric Sproul wrote: > > On Thu, Oct 17, 2013 at 2:42 PM, Mayuresh Kathe > wrote: > > > hi, is perl included in the base distribution only > > > for supporting pkg tools? > > > > Most of the pkg toolkit is in Python, but: > > > > pkg search -r 'depend::runtime/perl' > > > > shows that quite a few things in upstream illumos do require perl. > > great, that means, perl is here to stay... :) > > _______________________________________________ > 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: From mayuresh at kathe.in Fri Oct 18 02:37:51 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 17 Oct 2013 22:37:51 -0400 Subject: [OmniOS-discuss] perl : only for pkg tools? In-Reply-To: References: <20131017184235.GA27551@wolfman.devio.us> <20131017185629.GA15454@wolfman.devio.us> Message-ID: <20131018023700.GA20844@wolfman.devio.us> theo, thanks for those links, much appreciated. :) On Thu, Oct 17, 2013 at 05:39:07PM -0400, Theo Schlossnagle wrote: > perl is likely to stay, but the perl shipped in core is for use by core. > We can change configuration and the version at any time. > > If you really want perl to power your app, you should consider building > your own perl. > > See: > http://pkg.omniti.com/omniti-ms/ > http://pkg.omniti.com/omniti-perl/ > > For how we do it at OmniTI. > > > On Thu, Oct 17, 2013 at 2:56 PM, Mayuresh Kathe wrote: > > > On Thu, Oct 17, 2013 at 02:52:00PM -0400, Eric Sproul wrote: > > > On Thu, Oct 17, 2013 at 2:42 PM, Mayuresh Kathe > > wrote: > > > > hi, is perl included in the base distribution only > > > > for supporting pkg tools? > > > > > > Most of the pkg toolkit is in Python, but: > > > > > > pkg search -r 'depend::runtime/perl' > > > > > > shows that quite a few things in upstream illumos do require perl. > > > > great, that means, perl is here to stay... :) > > > > _______________________________________________ > > 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 From mayuresh at kathe.in Fri Oct 18 02:43:36 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 17 Oct 2013 22:43:36 -0400 Subject: [OmniOS-discuss] login error : solaris_audit In-Reply-To: References: <20131017074701.GA14110@wolfman.devio.us> Message-ID: <20131018024336.GB20844@wolfman.devio.us> On Thu, Oct 17, 2013 at 11:52:00AM -0700, Tim Rice wrote: > On Thu, 17 Oct 2013, Mayuresh Kathe wrote: > > > previous message showed the wrong error number, so here goes again. > > ---- > > hi, my system is now throwing up errors after logging in. > > > > Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 > > Solaris_audit mapping to : Error 0 > > > > any pointers on how to resolve this would be welcome. > > (my google skills aren't as well develped as i would've liked them to be). > > Is your network connection static or dynamic? > > Now track down some info and report back. > # /sbin/ifconfig -a > # cat /etc/inet/hosts > # cat /etc/resolv.conf > # egrep '^hosts:|^ipnodes:' /etc/nsswitch.conf thanks tim, my external network connection is dynamic, internal is static. bo had pointed out the error in my /etc/hosts file. i hadn't entered the hostname and ip address in there. did it, and the problem got resolved. :) best, ~mayuresh From mayuresh at kathe.in Fri Oct 18 15:22:58 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Fri, 18 Oct 2013 11:22:58 -0400 Subject: [OmniOS-discuss] the wonders of java under omnios Message-ID: <20131018152257.GA31784@wolfman.devio.us> hello, just a note expressing my amazement. the jdk installable pkg is only around 35MB under omnios. compare that with over 90MB under ubuntu server 13.10. what theo and his team are doing is *very* impressive. From lionelcons1972 at gmail.com Fri Oct 18 22:03:35 2013 From: lionelcons1972 at gmail.com (Lionel Cons) Date: Sat, 19 Oct 2013 00:03:35 +0200 Subject: [OmniOS-discuss] the wonders of java under omnios In-Reply-To: <20131018152257.GA31784@wolfman.devio.us> References: <20131018152257.GA31784@wolfman.devio.us> Message-ID: On 18 October 2013 17:22, Mayuresh Kathe wrote: > hello, just a note expressing my amazement. > the jdk installable pkg is only around 35MB under omnios. > compare that with over 90MB under ubuntu server 13.10. > what theo and his team are doing is *very* impressive. Does anyone know why there is such a huge difference? Is this Ubuntu being so bad, or are features missing? Or are the binaries shipped as stripped binaries? Lionel From mir at miras.org Fri Oct 18 22:13:39 2013 From: mir at miras.org (Michael Rasmussen) Date: Sat, 19 Oct 2013 00:13:39 +0200 Subject: [OmniOS-discuss] the wonders of java under omnios In-Reply-To: References: <20131018152257.GA31784@wolfman.devio.us> Message-ID: <20131019001339.1a5e0286@sleipner.datanom.net> On Sat, 19 Oct 2013 00:03:35 +0200 Lionel Cons wrote: > > Does anyone know why there is such a huge difference? Is this Ubuntu > being so bad, or are features missing? Or are the binaries shipped as > stripped binaries? > I guess the answer to the question is that somebody compares apples with pears;-) A Java size 90MB seems to be a JDK while a Java size 35MB seems to be a JRE. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- Beer -- it's not just for breakfast anymore. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From mayuresh at kathe.in Sat Oct 19 04:05:41 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Sat, 19 Oct 2013 00:05:41 -0400 Subject: [OmniOS-discuss] the wonders of java under omnios In-Reply-To: <20131019001339.1a5e0286@sleipner.datanom.net> References: <20131018152257.GA31784@wolfman.devio.us> <20131019001339.1a5e0286@sleipner.datanom.net> Message-ID: <20131019040541.GA5999@wolfman.devio.us> On Sat, Oct 19, 2013 at 12:13:39AM +0200, Michael Rasmussen wrote: > On Sat, 19 Oct 2013 00:03:35 +0200 > Lionel Cons wrote: > > > > > Does anyone know why there is such a huge difference? Is this Ubuntu > > being so bad, or are features missing? Or are the binaries shipped as > > stripped binaries? > > > I guess the answer to the question is that somebody compares apples > with pears;-) > > A Java size 90MB seems to be a JDK while a Java size 35MB seems to be a > JRE. not really, i am comparing apples with apples. :) developer/java/jdk is 35.x MB under omnios stable (currently). and the 90.x MB under ubuntu server 13.10 is openjdk. both at 1.6.x. :) i believe the huge size under ubuntu is from being linked with various x-win related stuff, inspite of being jre-headless. From olaf.lists at gmail.com Sat Oct 19 22:24:13 2013 From: olaf.lists at gmail.com (Olaf Marzocchi) Date: Sun, 20 Oct 2013 00:24:13 +0200 Subject: [OmniOS-discuss] login error : solaris_audit In-Reply-To: References: Message-ID: Hello, in my case I have two NICs with two static IPs. My local network also has a dynamic external IP and a 3rd level domain name associated with it (I use Dyn.com). Is this the correct way to setup the /etc/hosts file? ::1 localhost 192.168.2.5 OmniOS.3rd-level.domain.ext #192.168.2.5 OmniOS 192.168.2.6 OmniOS.3rd-level.domain.ext #192.168.2.6 OmniOS 127.0.0.1 localhost Thank you Olaf Il giorno 17/ott/2013, alle ore 10:54, omnios-discuss-request at lists.omniti.com ha scritto: > Hi Mayuresh, > > NP glad that it helped you out :) > > CC to the list. > > Regards, > Bo Agerskov Rising > borising at gmail.com > > > > > On 17/10/2013, at 10.20, Mayuresh Kathe wrote: > >> hi bo, thanks again. >> and yes, i just did as you'd suggested, and it works. :) >> >> ~mayuresh >> >> On Thu, Oct 17, 2013 at 10:09:16AM +0200, Bo Agerskov Rising wrote: >>> Hi Mayuresh, >>> >>> I have my own DNS server in my home lab, so I have just added the DNS correctly. >>> >>> Have you configured the /etc/hosts file with the hostname of the server and IP address? >>> >>> Regards, >>> Bo Agerskov Rising >>> borising at gmail.com >>> >>> >>> >>> >>> On 17/10/2013, at 10.00, Mayuresh Kathe wrote: >>> >>>> hi bo, thanks for the note. >>>> but, how do i solve the problem? >>>> the system is at home, connected to the internet via 'adsl' and >>>> without a public static ip address. >>>> >>>> thanks, >>>> >>>> ~mayuresh >>>> >>>> On Thu, Oct 17, 2013 at 09:55:24AM +0200, Bo Agerskov Rising wrote: >>>>> Hi Mayuresh, >>>>> >>>>> My guess is that the system can't lookup it's hostname in the DNS server. >>>>> >>>>> Regards, >>>>> Bo Agerskov Rising >>>>> borising at gmail.com >>>>> >>>>> On 17/10/2013, at 09.43, Mayuresh Kathe wrote: >>>>> >>>>>> hi, my system is now throwing up errors after logging in. >>>>>> >>>>>> Solaris_audit getaddrinfo() failed[node name or service name not known] : Error 0 >>>>>> Solaris_audit mapping to : Error 9 >>>>>> >>>>>> any pointers on how to resolve this would be welcome. >>>>>> (my google skills aren't as well develped as i would've liked them to be). >>>>>> >>>>>> ~mayuresh >>>>>> >>>>>> _______________________________________________ >>>>>> OmniOS-discuss mailing list >>>>>> OmniOS-discuss at lists.omniti.com >>>>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >>>>> >>> > From fabio at fabiorabelo.wiki.br Mon Oct 21 10:58:11 2013 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Mon, 21 Oct 2013 08:58:11 -0200 Subject: [OmniOS-discuss] next stable release Message-ID: Hi to all Please, there are no pressure here, just planning my next implementation ... When will be released the next stable branch ?? F?bio Rabelo From ben at fluffy.co.uk Mon Oct 21 11:05:19 2013 From: ben at fluffy.co.uk (Ben Summers) Date: Mon, 21 Oct 2013 12:05:19 +0100 Subject: [OmniOS-discuss] next stable release In-Reply-To: References: Message-ID: On 21 Oct 2013, at 11:58, F?bio Rabelo wrote: > Hi to all > > Please, there are no pressure here, just planning my next implementation ... > > When will be released the next stable branch ?? http://omnios.omniti.com/wiki.php/ReleaseCycle Ben -- http://bens.me.uk From jperkin at joyent.com Mon Oct 21 12:51:15 2013 From: jperkin at joyent.com (Jonathan Perkin) Date: Mon, 21 Oct 2013 13:51:15 +0100 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available Message-ID: <20131021125115.GA452@joyent.com> I'm pleased to announce that the pkgsrc-2013Q3 release for illumos platforms is now available. This is an alternative repository of over 11,000 binary packages built for illumos systems. A quick-start tutorial is available here: http://www.perkin.org.uk/pages/pkgsrc-binary-packages-for-illumos.html In the 2013Q3 release we added around 1,000 additional binary packages to the repositories, as well as updating many hundreds of packages to newer versions. Please report any bugs or feature requests to our GitHub issues page: https://github.com/joyent/pkgsrc/issues Thanks, -- Jonathan Perkin - Joyent, Inc. - www.joyent.com From daniel at dgnetwork.com.br Tue Oct 22 13:31:12 2013 From: daniel at dgnetwork.com.br (=?ISO-8859-1?Q?=22Daniel_D=2E_Gon=E7alves=22?=) Date: Tue, 22 Oct 2013 11:31:12 -0200 Subject: [OmniOS-discuss] Fwd: ZFS, BUG ?? In-Reply-To: <5256BA52.1090304@dgnetwork.com.br> References: <5256BA52.1090304@dgnetwork.com.br> Message-ID: <52667E20.3070207@dgnetwork.com.br> An HTML attachment was scrubbed... URL: From skiselkov.ml at gmail.com Tue Oct 22 14:01:34 2013 From: skiselkov.ml at gmail.com (Saso Kiselkov) Date: Tue, 22 Oct 2013 23:01:34 +0900 Subject: [OmniOS-discuss] Fwd: ZFS, BUG ?? In-Reply-To: <52667E20.3070207@dgnetwork.com.br> References: <5256BA52.1090304@dgnetwork.com.br> <52667E20.3070207@dgnetwork.com.br> Message-ID: <5266853E.1010306@gmail.com> On 10/22/13 10:31 PM, "Daniel D. Gon?alves" wrote: > I need to solve this problem, had no return of the mail list, could > someone tell me another mail list where I can get help? Hey Daniel, you may want to try the openzfs or Illumos ZFS lists. Cheers -- Saso From travis.laduke at techmdinc.com Tue Oct 22 19:17:31 2013 From: travis.laduke at techmdinc.com (Travis LaDuke) Date: Tue, 22 Oct 2013 12:17:31 -0700 Subject: [OmniOS-discuss] How can I best get Duplicity onto my system? Message-ID: I'm trying to get this rsync frontend[1] running. I can't find it in any repos, so I'm installing from (python) source, but I can't find a librsync package either. [1] http://duplicity.nongnu.org/ :~/duplicity-0.6.22# python setup.py install running install running build running build_py running build_ext building 'duplicity._librsync' extension gcc -m64 -fno-strict-aliasing -std=c99 -m64 -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.6 -c duplicity/_librsyncmodule.c -o build/temp.solaris-2.11-i86pc-2.6/duplicity/_librsyncmodule.o duplicity/_librsyncmodule.c:26:22: fatal error: librsync.h: No such file or directory compilation terminated. error: command 'gcc' failed with exit status 1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From travis.laduke at techmdinc.com Tue Oct 22 23:13:57 2013 From: travis.laduke at techmdinc.com (Travis LaDuke) Date: Tue, 22 Oct 2013 16:13:57 -0700 Subject: [OmniOS-discuss] How can I best get Duplicity onto my system? In-Reply-To: References: Message-ID: Or, can someone smarter than me get librsync to build then duplicity to install and run? It only takes a second. :) http://sourceforge.net/projects/librsync/files/librsync/0.9.7/ http://duplicity.nongnu.org/ I can get both to build/install, but then depending on how I do it, I get different errors when I try to actually run duplicity. Is it some python32/64 thing? I either get ImportError: ld.so.1: python2.6: fatal: relocation error: file /usr/lib/python2.6/site-packages/duplicity/64/_librsync.so: symbol rs_file_copy_cb: referenced symbol not found or ImportError: No module named _librsync Or, is there another good, encrypted rsync script you solaris types like to use? --travis On Tue, Oct 22, 2013 at 12:17 PM, Travis LaDuke wrote: > I'm trying to get this rsync frontend[1] running. > I can't find it in any repos, so I'm installing from (python) source, but > I can't find a librsync package either. > > [1] http://duplicity.nongnu.org/ > > :~/duplicity-0.6.22# python setup.py install > running install > running build > running build_py > running build_ext > building 'duplicity._librsync' extension > gcc -m64 -fno-strict-aliasing -std=c99 -m64 -DNDEBUG -g -O3 -Wall > -Wstrict-prototypes -fPIC -I/usr/include/python2.6 -c > duplicity/_librsyncmodule.c -o > build/temp.solaris-2.11-i86pc-2.6/duplicity/_librsyncmodule.o > duplicity/_librsyncmodule.c:26:22: fatal error: librsync.h: No such file > or directory > compilation terminated. > error: command 'gcc' failed with exit status 1 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mayuresh at kathe.in Wed Oct 23 03:02:33 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Wed, 23 Oct 2013 08:32:33 +0530 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available In-Reply-To: <20131021125115.GA452@joyent.com> References: <20131021125115.GA452@joyent.com> Message-ID: <20131023030232.GA1117@dingbat.kathe.in> does this actually work under omnios? tried the 64-bit as well as multi-arch options, none of the stuff works. no error messages, nothing. if it has worked for everybody else, there's got to be something wrong with my system, time for a fresh install. :) On Mon, Oct 21, 2013 at 01:51:15PM +0100, Jonathan Perkin wrote: > I'm pleased to announce that the pkgsrc-2013Q3 release for illumos > platforms is now available. This is an alternative repository of over > 11,000 binary packages built for illumos systems. > > A quick-start tutorial is available here: > > http://www.perkin.org.uk/pages/pkgsrc-binary-packages-for-illumos.html > > In the 2013Q3 release we added around 1,000 additional binary packages > to the repositories, as well as updating many hundreds of packages to > newer versions. > > Please report any bugs or feature requests to our GitHub issues page: > > https://github.com/joyent/pkgsrc/issues > > Thanks, > > -- > Jonathan Perkin - Joyent, Inc. - www.joyent.com > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From jperkin at joyent.com Wed Oct 23 08:27:26 2013 From: jperkin at joyent.com (Jonathan Perkin) Date: Wed, 23 Oct 2013 09:27:26 +0100 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available In-Reply-To: <20131023030232.GA1117@dingbat.kathe.in> References: <20131021125115.GA452@joyent.com> <20131023030232.GA1117@dingbat.kathe.in> Message-ID: <20131023082726.GE452@joyent.com> * On 2013-10-23 at 04:02 BST, Mayuresh Kathe wrote: > does this actually work under omnios? > tried the 64-bit as well as multi-arch options, none of the stuff works. > no error messages, nothing. Could you clarify on exactly what you are seeing? At which point in the instructions do things stop working? If you don't see error messages, do you at least see some output? What is the return code of the commands which appear to do nothing? A full gist/pastebin of your entire session would be helpful, as well as any *.log files under the /var/db/pkgin directory. Clear out /opt/local and /var/db/pkgin before retrying to avoid any conflicts with an existing installation. The quick start tutorial works as expected for me on omnios-dda4bb3. Thanks, -- Jonathan Perkin - Joyent, Inc. - www.joyent.com From mayuresh at kathe.in Wed Oct 23 08:40:32 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Wed, 23 Oct 2013 14:10:32 +0530 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available In-Reply-To: <20131023082726.GE452@joyent.com> References: <20131021125115.GA452@joyent.com> <20131023030232.GA1117@dingbat.kathe.in> <20131023082726.GE452@joyent.com> Message-ID: <20131023084007.GA1918@dingbat.kathe.in> On Wed, Oct 23, 2013 at 09:27:26AM +0100, Jonathan Perkin wrote: > * On 2013-10-23 at 04:02 BST, Mayuresh Kathe wrote: > > > does this actually work under omnios? > > tried the 64-bit as well as multi-arch options, none of the stuff works. > > no error messages, nothing. > > Could you clarify on exactly what you are seeing? At which point in > the instructions do things stop working? If you don't see error > messages, do you at least see some output? What is the return code of > the commands which appear to do nothing? A full gist/pastebin of your > entire session would be helpful, as well as any *.log files under the > /var/db/pkgin directory. Clear out /opt/local and /var/db/pkgin > before retrying to avoid any conflicts with an existing installation. > > The quick start tutorial works as expected for me on omnios-dda4bb3. Yes, i did mess up my system with all the fiddling and installs. did a fresh install, and the quick start tutorial instructions worked like a charm. BTW, any reason why "sun-jdk6-6.0.26nbl" is over a 100MB? It's similar in size to what's available with Ubuntu Server 13.10. Compare those with "developer/java/jdk" @ 1.6.x being only 35.5MB under OmniOS stable (currently). Best, ~Mayuresh From jperkin at joyent.com Wed Oct 23 08:55:30 2013 From: jperkin at joyent.com (Jonathan Perkin) Date: Wed, 23 Oct 2013 09:55:30 +0100 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available In-Reply-To: <20131023084007.GA1918@dingbat.kathe.in> References: <20131021125115.GA452@joyent.com> <20131023030232.GA1117@dingbat.kathe.in> <20131023082726.GE452@joyent.com> <20131023084007.GA1918@dingbat.kathe.in> Message-ID: <20131023085530.GF452@joyent.com> * On 2013-10-23 at 09:40 BST, Mayuresh Kathe wrote: > On Wed, Oct 23, 2013 at 09:27:26AM +0100, Jonathan Perkin wrote: > > * On 2013-10-23 at 04:02 BST, Mayuresh Kathe wrote: > > > > > does this actually work under omnios? > > > tried the 64-bit as well as multi-arch options, none of the stuff works. > > > no error messages, nothing. > > > > Could you clarify on exactly what you are seeing? At which point in > > the instructions do things stop working? If you don't see error > > messages, do you at least see some output? What is the return code of > > the commands which appear to do nothing? A full gist/pastebin of your > > entire session would be helpful, as well as any *.log files under the > > /var/db/pkgin directory. Clear out /opt/local and /var/db/pkgin > > before retrying to avoid any conflicts with an existing installation. > > > > The quick start tutorial works as expected for me on omnios-dda4bb3. > > Yes, i did mess up my system with all the fiddling and installs. > did a fresh install, and the quick start tutorial instructions worked > like a charm. Ok, great. > BTW, any reason why "sun-jdk6-6.0.26nbl" is over a 100MB? > It's similar in size to what's available with Ubuntu Server 13.10. > Compare those with "developer/java/jdk" @ 1.6.x being only 35.5MB under > OmniOS stable (currently). There are probably a couple things at play here: - The jdk package depends on the jre package, so the size given by pkgin will be the total for both. - In pkgsrc we do not split packages into separate runtime and developer components, which I believe IPS does. Either way, I'd strongly recommend using the openjdk7 package instead, the sun-jdk6 package is out of date and insecure due to Oracle's change of licensing, and we only provide it for historical reasons. Cheers, -- Jonathan Perkin - Joyent, Inc. - www.joyent.com From cnehren+omnios-discuss at omniti.com Wed Oct 23 14:05:47 2013 From: cnehren+omnios-discuss at omniti.com (Chris Nehren) Date: Wed, 23 Oct 2013 10:05:47 -0400 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available In-Reply-To: <20131023085530.GF452@joyent.com> References: <20131021125115.GA452@joyent.com> <20131023030232.GA1117@dingbat.kathe.in> <20131023082726.GE452@joyent.com> <20131023084007.GA1918@dingbat.kathe.in> <20131023085530.GF452@joyent.com> Message-ID: <20131023140547.GA18552@eschaton.local> On Wed, Oct 23, 2013 at 09:55:30 +0100, Jonathan Perkin wrote: > - In pkgsrc we do not split packages into separate runtime and > developer components, which I believe IPS does. IPS doesn't do this either, at least not with the packages I've worked with. I know the Joyent folks don't like IPS, but please don't compare us to Linux that way. ;) -- Chris Nehren From esproul at omniti.com Wed Oct 23 14:16:37 2013 From: esproul at omniti.com (Eric Sproul) Date: Wed, 23 Oct 2013 10:16:37 -0400 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available In-Reply-To: <20131023140547.GA18552@eschaton.local> References: <20131021125115.GA452@joyent.com> <20131023030232.GA1117@dingbat.kathe.in> <20131023082726.GE452@joyent.com> <20131023084007.GA1918@dingbat.kathe.in> <20131023085530.GF452@joyent.com> <20131023140547.GA18552@eschaton.local> Message-ID: On Wed, Oct 23, 2013 at 10:05 AM, Chris Nehren wrote: > On Wed, Oct 23, 2013 at 09:55:30 +0100, Jonathan Perkin wrote: >> - In pkgsrc we do not split packages into separate runtime and >> developer components, which I believe IPS does. > > IPS doesn't do this either, at least not with the packages I've > worked with. I know the Joyent folks don't like IPS, but please > don't compare us to Linux that way. ;) Let's be clear. IPS itself doesn't care what's in a package. That is a policy decision by the package author. At OmniTI, our custom packages tend to be monolithic, including headers and runtime bits. It's simpler, and disk space is cheap. The package set from illumos-gate has numerous examples of separate header packages (system/header being the most obvious). Eric From jperkin at joyent.com Wed Oct 23 14:55:46 2013 From: jperkin at joyent.com (Jonathan Perkin) Date: Wed, 23 Oct 2013 15:55:46 +0100 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available In-Reply-To: <20131023140547.GA18552@eschaton.local> References: <20131021125115.GA452@joyent.com> <20131023030232.GA1117@dingbat.kathe.in> <20131023082726.GE452@joyent.com> <20131023084007.GA1918@dingbat.kathe.in> <20131023085530.GF452@joyent.com> <20131023140547.GA18552@eschaton.local> Message-ID: <20131023145546.GH452@joyent.com> * On 2013-10-23 at 15:05 BST, Chris Nehren wrote: > On Wed, Oct 23, 2013 at 09:55:30 +0100, Jonathan Perkin wrote: > > - In pkgsrc we do not split packages into separate runtime and > > developer components, which I believe IPS does. > > IPS doesn't do this either, at least not with the packages I've > worked with. I know the Joyent folks don't like IPS, but please > don't compare us to Linux that way. ;) That wasn't my intention. Unlike a number of my colleagues I've not personally used IPS enough to form an opinion on it, and I was simply going on my naive understanding of the 'pkg search jdk' output, which suggested that the separate developer/runtime packages listed were a possible explanation for the size discrepancy. Regards, -- Jonathan Perkin - Joyent, Inc. - www.joyent.com From mayuresh at kathe.in Wed Oct 23 16:16:01 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Wed, 23 Oct 2013 21:46:01 +0530 Subject: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available In-Reply-To: <20131023145546.GH452@joyent.com> References: <20131021125115.GA452@joyent.com> <20131023030232.GA1117@dingbat.kathe.in> <20131023082726.GE452@joyent.com> <20131023084007.GA1918@dingbat.kathe.in> <20131023085530.GF452@joyent.com> <20131023140547.GA18552@eschaton.local> <20131023145546.GH452@joyent.com> Message-ID: <20131023161601.GB1068@dingbat> On Wed, Oct 23, 2013 at 03:55:46PM +0100, Jonathan Perkin wrote: > * On 2013-10-23 at 15:05 BST, Chris Nehren wrote: > > > On Wed, Oct 23, 2013 at 09:55:30 +0100, Jonathan Perkin wrote: > > > - In pkgsrc we do not split packages into separate runtime and > > > developer components, which I believe IPS does. > > > > IPS doesn't do this either, at least not with the packages I've > > worked with. I know the Joyent folks don't like IPS, but please > > don't compare us to Linux that way. ;) > > That wasn't my intention. Unlike a number of my colleagues I've not > personally used IPS enough to form an opinion on it, and I was simply > going on my naive understanding of the 'pkg search jdk' output, which > suggested that the separate developer/runtime packages listed were a > possible explanation for the size discrepancy. Umnn, the last few times I installed my workstation with OmniOS for Java development scenario, all I had to do was issue; pkg install developer/java/jdk and it downloaded a 35.5 MB package and installed it. There were no references to anything like a separate JRE install. This is the smoothest and fastest Java development system setup I've experienced under any of the Unix-like systems I've worked on till date. ~Mayuresh PS: Yeah, I've fiddled around with my workstation running OmniOS a few times to have caused enough damage to warrant a re-install. :) From geoffn at gnaa.net Wed Oct 23 21:13:01 2013 From: geoffn at gnaa.net (Geoff Nordli) Date: Wed, 23 Oct 2013 14:13:01 -0700 Subject: [OmniOS-discuss] i210 support in bloody Message-ID: <52683BDD.3040303@gnaa.net> I am looking at the timeline for OmniOS. I can't find this commit: https://github.com/illumos/illumos-gate/commit/6ed0a5cff079e25f4aa15cef67c6dd48ee60b018 Is it in bloody? thanks, Geoff From esproul at omniti.com Wed Oct 23 21:25:58 2013 From: esproul at omniti.com (Eric Sproul) Date: Wed, 23 Oct 2013 17:25:58 -0400 Subject: [OmniOS-discuss] i210 support in bloody In-Reply-To: <52683BDD.3040303@gnaa.net> References: <52683BDD.3040303@gnaa.net> Message-ID: On Wed, Oct 23, 2013 at 5:13 PM, Geoff Nordli wrote: > I am looking at the timeline for OmniOS. > > I can't find this commit: > > https://github.com/illumos/illumos-gate/commit/6ed0a5cff079e25f4aa15cef67c6dd48ee60b018 > > Is it in bloody? It's there. On the master branch of git at github.com:omniti-labs/illumos-omnios.git : $ git log -1 6ed0a5cff079e25f4aa15cef67c6dd48ee60b018 commit 6ed0a5cff079e25f4aa15cef67c6dd48ee60b018 Author: Tycho Nightingale Date: Sun Jun 30 18:25:02 2013 +0000 4090 igb I210/I211 support Reviewed by: Robert Mustacchi Reviewed by: Dan McDonald Approved by: Richard Lowe From geoffn at gnaa.net Wed Oct 23 21:49:40 2013 From: geoffn at gnaa.net (Geoff Nordli) Date: Wed, 23 Oct 2013 14:49:40 -0700 Subject: [OmniOS-discuss] i210 support in bloody In-Reply-To: References: <52683BDD.3040303@gnaa.net> Message-ID: <52684474.2070604@gnaa.net> Thank you Eric. I see it now. On 13-10-23 02:25 PM, Eric Sproul wrote: > On Wed, Oct 23, 2013 at 5:13 PM, Geoff Nordli wrote: >> I am looking at the timeline for OmniOS. >> >> I can't find this commit: >> >> https://github.com/illumos/illumos-gate/commit/6ed0a5cff079e25f4aa15cef67c6dd48ee60b018 >> >> Is it in bloody? > It's there. On the master branch of > git at github.com:omniti-labs/illumos-omnios.git : > > $ git log -1 6ed0a5cff079e25f4aa15cef67c6dd48ee60b018 > commit 6ed0a5cff079e25f4aa15cef67c6dd48ee60b018 > Author: Tycho Nightingale > Date: Sun Jun 30 18:25:02 2013 +0000 > > 4090 igb I210/I211 support > Reviewed by: Robert Mustacchi > Reviewed by: Dan McDonald > Approved by: Richard Lowe From mayuresh at kathe.in Thu Oct 24 10:57:58 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 24 Oct 2013 16:27:58 +0530 Subject: [OmniOS-discuss] =?utf-8?q?network_utils_=3A_any_repositories=3F?= Message-ID: hi, do any of the omnios users/developers have third-party repositories for network utils required for regular work? like lynx, mutt, gopher. ~mayuresh From ben at fluffy.co.uk Thu Oct 24 11:06:46 2013 From: ben at fluffy.co.uk (Ben Summers) Date: Thu, 24 Oct 2013 12:06:46 +0100 Subject: [OmniOS-discuss] network utils : any repositories? In-Reply-To: References: Message-ID: <4CEDC6B4-CA26-49F9-990C-81D2BA6860DA@fluffy.co.uk> On 24 Oct 2013, at 11:57, Mayuresh Kathe wrote: > hi, do any of the omnios users/developers have third-party repositories > for network utils required for regular work? like lynx, mutt, gopher. Do a search in the non-OmniTI repos listed here: http://omnios.omniti.com/wiki.php/Packaging For example, I found lynx and mutt in the niksula.hut.fi repo. Ben -- http://bens.me.uk From mayuresh at kathe.in Thu Oct 24 11:13:52 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 24 Oct 2013 16:43:52 +0530 Subject: [OmniOS-discuss] =?utf-8?q?network_utils_=3A_any_repositories=3F?= In-Reply-To: <4CEDC6B4-CA26-49F9-990C-81D2BA6860DA@fluffy.co.uk> References: <4CEDC6B4-CA26-49F9-990C-81D2BA6860DA@fluffy.co.uk> Message-ID: <143405ce3cd42d1724762e132dca4042@kathe.in> On 2013-10-24 16:36, Ben Summers wrote: > On 24 Oct 2013, at 11:57, Mayuresh Kathe wrote: > >> hi, do any of the omnios users/developers have third-party >> repositories >> for network utils required for regular work? like lynx, mutt, >> gopher. > > Do a search in the non-OmniTI repos listed here: > > http://omnios.omniti.com/wiki.php/Packaging > > For example, I found lynx and mutt in the niksula.hut.fi repo. cool. ben, thanks a million for that 'url'. :) ~mayuresh From mayuresh at kathe.in Thu Oct 24 12:59:23 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 24 Oct 2013 08:59:23 -0400 Subject: [OmniOS-discuss] network utils : any repositories? In-Reply-To: <4CEDC6B4-CA26-49F9-990C-81D2BA6860DA@fluffy.co.uk> References: <4CEDC6B4-CA26-49F9-990C-81D2BA6860DA@fluffy.co.uk> Message-ID: <20131024125922.GA6711@wolfman.devio.us> On Thu, Oct 24, 2013 at 12:06:46PM +0100, Ben Summers wrote: > > On 24 Oct 2013, at 11:57, Mayuresh Kathe wrote: > > > hi, do any of the omnios users/developers have third-party repositories > > for network utils required for regular work? like lynx, mutt, gopher. > > Do a search in the non-OmniTI repos listed here: > > http://omnios.omniti.com/wiki.php/Packaging > > For example, I found lynx and mutt in the niksula.hut.fi repo. somehow, that 'url' is unusable via lynx. ~mayuresh From emunch at utmi.in Fri Oct 25 06:02:14 2013 From: emunch at utmi.in (Sam M) Date: Fri, 25 Oct 2013 11:32:14 +0530 Subject: [OmniOS-discuss] pkgsrc for OmniOS Message-ID: Hello all. Anyone using packages from http://www.perkin.org.uk/pages/pkgsrc-binary-packages-for-illumos.html on OmniOS? Can pkg and pkgin co-exist on the same system? TIA. Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: From mayuresh at kathe.in Fri Oct 25 07:46:09 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Fri, 25 Oct 2013 13:16:09 +0530 Subject: [OmniOS-discuss] cde Message-ID: <62657e7a4a79d8bd51b6ff2757ea6495@kathe.in> hi, if someone is indeed working on creating a package for the x windowing system under omnios, please consider using the common desktop environment. more about 'cde' at; http://sourceforge.net/projects/cdesktopenv/ it would be a pleasure to have a solaris-like environment, through and through. :) best, ~mayuresh From jesus at omniti.com Fri Oct 25 11:49:52 2013 From: jesus at omniti.com (Theo Schlossnagle) Date: Fri, 25 Oct 2013 07:49:52 -0400 Subject: [OmniOS-discuss] pkgsrc for OmniOS In-Reply-To: References: Message-ID: People are indeed using pkgsrc on OmniOS machines: http://www.perkin.org.uk/posts/whats-new-in-pkgsrc-2013Q2.html On Fri, Oct 25, 2013 at 2:02 AM, Sam M wrote: > Hello all. > > Anyone using packages from > http://www.perkin.org.uk/pages/pkgsrc-binary-packages-for-illumos.html on > OmniOS? Can pkg and pkgin co-exist on the same system? > > TIA. > > Sam > > > _______________________________________________ > 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: From emunch at utmi.in Sun Oct 27 12:04:29 2013 From: emunch at utmi.in (Sam M) Date: Sun, 27 Oct 2013 17:34:29 +0530 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash Message-ID: Hello all. After installing napp-it, OmniOS got hosed. Not sure what caused it, probably not napp-it, because I couldn't boot up my system with any of the boot images, including the original. Now, on a brand new installation, I'm getting the following error - *# pkg update web/ca-bundle pkg* *Creating Plan - * *pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release Signing Certificate/emailAddress=omnios-support at omniti.com could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority* *The package involved is:pkg://omnios/library/python-2/pybonjour at 1.1.1 ,5.11-0.151007:20130516T114553Z* * * *# uname -a* *SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris* There were no errors earlier after the installation when updating packages. How can I fix this? Where can I find OmniTI's CA certificate? TIA. Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: From emunch at utmi.in Sun Oct 27 12:16:40 2013 From: emunch at utmi.in (Sam M) Date: Sun, 27 Oct 2013 17:46:40 +0530 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] Message-ID: Hello all. After installing napp-it, OmniOS got hosed. Not sure what caused it, probably not napp-it, because I couldn't boot up my system with any of the boot images, including the original. Now, on a brand new installation, I'm getting the following error - *# pkg update web/ca-bundle pkg* *Creating Plan - * *pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release Signing Certificate/emailAddress=omnios-support at omniti.com could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority* *The package involved is:pkg://omnios/library/python-2/pybonjour at 1.1.1 ,5.11-0.151007:20130516T114553Z* * * *# uname -a* *SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris* There were no errors earlier after the installation when updating packages. How can I fix this? Where can I find OmniTI's CA certificate? TIA. Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: From cnehren+omnios-discuss at omniti.com Sun Oct 27 16:32:58 2013 From: cnehren+omnios-discuss at omniti.com (Chris Nehren) Date: Sun, 27 Oct 2013 12:32:58 -0400 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: References: Message-ID: <20131027163258.GC18552@eschaton.local> Are you on bloody? We're in the middle of getting signed packages ready. Hold off on updating for now. On Sun, Oct 27, 2013 at 17:46:40 +0530, Sam M wrote: > Hello all. > > After installing napp-it, OmniOS got hosed. Not sure what caused it, > probably not napp-it, because I couldn't boot up my system with any of the > boot images, including the original. > > Now, on a brand new installation, I'm getting the following error - > > *# pkg update web/ca-bundle pkg* > *Creating Plan - * > *pkg update: The certificate which issued this > certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release > Signing Certificate/emailAddress=omnios-support at omniti.com could not be > found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI > Certificate Authority* > *The package involved is:pkg://omnios/library/python-2/pybonjour at 1.1.1 > ,5.11-0.151007:20130516T114553Z* > * > * > *# uname -a* > *SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris* > > There were no errors earlier after the installation when updating packages. > > How can I fix this? Where can I find OmniTI's CA certificate? > > TIA. > > Sam > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Chris Nehren Site Reliability Engineer, OmniTI From emunch at utmi.in Sun Oct 27 17:04:54 2013 From: emunch at utmi.in (Sam M) Date: Sun, 27 Oct 2013 22:34:54 +0530 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: <20131027163258.GC18552@eschaton.local> References: <20131027163258.GC18552@eschaton.local> Message-ID: Yes, on Bloody. OK. Thanks. On 27 October 2013 22:02, Chris Nehren wrote: > Are you on bloody? We're in the middle of getting signed packages > ready. Hold off on updating for now. > > On Sun, Oct 27, 2013 at 17:46:40 +0530, Sam M wrote: > > Hello all. > > > > After installing napp-it, OmniOS got hosed. Not sure what caused it, > > probably not napp-it, because I couldn't boot up my system with any of > the > > boot images, including the original. > > > > Now, on a brand new installation, I'm getting the following error - > > > > *# pkg update web/ca-bundle pkg* > > *Creating Plan - * > > *pkg update: The certificate which issued this > > certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 > Release > > Signing Certificate/emailAddress=omnios-support at omniti.com could not be > > found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI > > Certificate Authority* > > *The package involved is:pkg://omnios/library/python-2/pybonjour at 1.1.1 > > ,5.11-0.151007:20130516T114553Z* > > * > > * > > *# uname -a* > > *SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris* > > > > There were no errors earlier after the installation when updating > packages. > > > > How can I fix this? Where can I find OmniTI's CA certificate? > > > > TIA. > > > > Sam > > > _______________________________________________ > > OmniOS-discuss mailing list > > OmniOS-discuss at lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > -- > Chris Nehren > Site Reliability Engineer, OmniTI > _______________________________________________ > 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: From emunch at utmi.in Tue Oct 29 08:00:49 2013 From: emunch at utmi.in (Sam M) Date: Tue, 29 Oct 2013 13:30:49 +0530 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: <20131027163258.GC18552@eschaton.local> References: <20131027163258.GC18552@eschaton.local> Message-ID: Hello Chris. Any update on this? Kindly let us know when the process is completed and I can update. Thanks. Sam. On 27 October 2013 22:02, Chris Nehren wrote: > Are you on bloody? We're in the middle of getting signed packages > ready. Hold off on updating for now. > > On Sun, Oct 27, 2013 at 17:46:40 +0530, Sam M wrote: > > Hello all. > > > > After installing napp-it, OmniOS got hosed. Not sure what caused it, > > probably not napp-it, because I couldn't boot up my system with any of > the > > boot images, including the original. > > > > Now, on a brand new installation, I'm getting the following error - > > > > *# pkg update web/ca-bundle pkg* > > *Creating Plan - * > > *pkg update: The certificate which issued this > > certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 > Release > > Signing Certificate/emailAddress=omnios-support at omniti.com could not be > > found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI > > Certificate Authority* > > *The package involved is:pkg://omnios/library/python-2/pybonjour at 1.1.1 > > ,5.11-0.151007:20130516T114553Z* > > * > > * > > *# uname -a* > > *SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris* > > > > There were no errors earlier after the installation when updating > packages. > > > > How can I fix this? Where can I find OmniTI's CA certificate? > > > > TIA. > > > > Sam > > > _______________________________________________ > > OmniOS-discuss mailing list > > OmniOS-discuss at lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > -- > Chris Nehren > Site Reliability Engineer, OmniTI > _______________________________________________ > 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: From tobi at oetiker.ch Tue Oct 29 10:21:12 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 29 Oct 2013 11:21:12 +0100 (CET) Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network Message-ID: Folks, I am runnning omnios OmniOS 5.11 omnios-8d266aa 2013.05.04 on a box where we server zfs storage space and also run a few kvm hosts. Over the last few days, omnios has intermittently become 'mute' on its network interface. Not answering to tcp or icmp requests. Connecting via the console shows that the host is otherwhise fine, it just can not talk over the network anymore. Normally the condition cleared after a few minutes. The kernel does not write anything into the log file (running with *.debug /var/log/debug.log) Whats more, the virtual machines running on the machine, talking over the same physical network interface continue their work unperturbed. With network connectivity and all ... but they also can not talk to the omnios server via the network. I have the following network setup oot at fugu:~# dladm show-link LINK CLASS MTU STATE BRIDGE OVER igb0 phys 1500 up -- -- igb1 phys 1500 up -- -- igb2 phys 1500 unknown -- -- igb3 phys 1500 unknown -- -- akami0 vnic 1500 up -- igb0 nigiri0 vnic 1500 up -- igb0 fugu0 vnic 1500 up -- igb0 fugu1 vnic 1500 up -- igb1 the interfaces akami0 and nigiri0 are assigned to two kvm hosts fugu0 is used by the omnios host and fugu1 is a direct link to a second omnios host for zfs send receive backups. anyone seem such a behaviour ? any debugging ideas ? cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From esproul at omniti.com Tue Oct 29 13:49:24 2013 From: esproul at omniti.com (Eric Sproul) Date: Tue, 29 Oct 2013 09:49:24 -0400 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: References: <20131027163258.GC18552@eschaton.local> Message-ID: On Tue, Oct 29, 2013 at 4:00 AM, Sam M wrote: > Hello Chris. > > Any update on this? Kindly let us know when the process is completed and I > can update. The unstable (aka bloody) repo is frequently, well, unstable. If this is inconvenient for you, then the stable release (currently r151006, soon to be r151008) would be a better choice. Eric From esproul at omniti.com Tue Oct 29 13:55:40 2013 From: esproul at omniti.com (Eric Sproul) Date: Tue, 29 Oct 2013 09:55:40 -0400 Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network In-Reply-To: References: Message-ID: On Tue, Oct 29, 2013 at 6:21 AM, Tobias Oetiker wrote: > oot at fugu:~# dladm show-link > LINK CLASS MTU STATE BRIDGE OVER > igb0 phys 1500 up -- -- > igb1 phys 1500 up -- -- > igb2 phys 1500 unknown -- -- > igb3 phys 1500 unknown -- -- > akami0 vnic 1500 up -- igb0 > nigiri0 vnic 1500 up -- igb0 > fugu0 vnic 1500 up -- igb0 > fugu1 vnic 1500 up -- igb1 > > the interfaces akami0 and nigiri0 are assigned to two kvm hosts > fugu0 is used by the omnios host and fugu1 is a direct link to a > second omnios host for zfs send receive backups. Could we see the output of `ipadm show-addr` in the global zone? If not, are fugu0 and fugu1 in the same subnet? Does the drop-out coincide with any other usage patterns, such as an active backup over fugu1? For good measure, let's also look at `prtconf -d` to see what this igb hardware is. Eric From tobi at oetiker.ch Tue Oct 29 14:06:00 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 29 Oct 2013 15:06:00 +0100 (CET) Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network In-Reply-To: References: Message-ID: Today Eric Sproul wrote: > On Tue, Oct 29, 2013 at 6:21 AM, Tobias Oetiker wrote: > > oot at fugu:~# dladm show-link > > LINK CLASS MTU STATE BRIDGE OVER > > igb0 phys 1500 up -- -- > > igb1 phys 1500 up -- -- > > igb2 phys 1500 unknown -- -- > > igb3 phys 1500 unknown -- -- > > akami0 vnic 1500 up -- igb0 > > nigiri0 vnic 1500 up -- igb0 > > fugu0 vnic 1500 up -- igb0 > > fugu1 vnic 1500 up -- igb1 > > > > the interfaces akami0 and nigiri0 are assigned to two kvm hosts > > fugu0 is used by the omnios host and fugu1 is a direct link to a > > second omnios host for zfs send receive backups. > > Could we see the output of `ipadm show-addr` in the global zone? If > not, are fugu0 and fugu1 in the same subnet? Does the drop-out > coincide with any other usage patterns, such as an active backup over > fugu1? ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 fugu0/v4static static ok zzz.yy.8.5/23 fugu1/v4static static ok 10.10.10.1/30 lo0/v6 static ok ::1/128 the dropout does not coincide with a big backup job ... I am running collectd on the omnios host, and it has been faithfully recoding what happend on the interface while it was offline. The trafic stats show that packets have been coming into fugu0 but only very few got sent out ... (if it happens again I will do a snoop in the interface) > For good measure, let's also look at `prtconf -d` to see what this igb > hardware is. pci8086,1d10 (pciex8086,1d10) [Intel Corporation C600/X79 series chipset PCI Express Root Port 1], instance #6 pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #0 pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #1 pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #2 pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #3 note that the kvm hosts were able to talk via igb0 while fugu (zone0) was not. cheers tobi > > Eric > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From esproul at omniti.com Tue Oct 29 17:48:51 2013 From: esproul at omniti.com (Eric Sproul) Date: Tue, 29 Oct 2013 13:48:51 -0400 Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network In-Reply-To: References: Message-ID: On Tue, Oct 29, 2013 at 10:06 AM, Tobias Oetiker wrote: > ADDROBJ TYPE STATE ADDR > lo0/v4 static ok 127.0.0.1/8 > fugu0/v4static static ok zzz.yy.8.5/23 > fugu1/v4static static ok 10.10.10.1/30 > lo0/v6 static ok ::1/128 > > the dropout does not coincide with a big backup job ... I am > running collectd on the omnios host, and it has been faithfully > recoding what happend on the interface while it was offline. > > The trafic stats show that packets have been coming into fugu0 but > only very few got sent out ... (if it happens again I will do a > snoop in the interface) A snoop would be my first tactic too. Are these VNICs using VLAN tags or is everything untagged? > >> For good measure, let's also look at `prtconf -d` to see what this igb >> hardware is. > > pci8086,1d10 (pciex8086,1d10) [Intel Corporation C600/X79 series chipset PCI Express Root Port 1], instance #6 > pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #0 > pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #1 > pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #2 > pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #3 > > note that the kvm hosts were able to talk via igb0 while fugu (zone0) was not. OK, so this is I350, for which support should be pretty stable (it's been in upstream illumos for over a year and I know Joyent deploys I350 heavily in their public cloud). I don't see any open issues on igb or I350 that would be relevant here. Eric From tobi at oetiker.ch Tue Oct 29 19:10:59 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 29 Oct 2013 20:10:59 +0100 (CET) Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network In-Reply-To: References: Message-ID: Hi Eric, Today Eric Sproul wrote: > On Tue, Oct 29, 2013 at 10:06 AM, Tobias Oetiker wrote: > > ADDROBJ TYPE STATE ADDR > > lo0/v4 static ok 127.0.0.1/8 > > fugu0/v4static static ok zzz.yy.8.5/23 > > fugu1/v4static static ok 10.10.10.1/30 > > lo0/v6 static ok ::1/128 > > > > the dropout does not coincide with a big backup job ... I am > > running collectd on the omnios host, and it has been faithfully > > recoding what happend on the interface while it was offline. > > > > The trafic stats show that packets have been coming into fugu0 but > > only very few got sent out ... (if it happens again I will do a > > snoop in the interface) > > A snoop would be my first tactic too. Are these VNICs using VLAN tags > or is everything untagged? will do when I get access next ... > >> For good measure, let's also look at `prtconf -d` to see what this igb > >> hardware is. > > > > pci8086,1d10 (pciex8086,1d10) [Intel Corporation C600/X79 series chipset PCI Express Root Port 1], instance #6 > > pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #0 > > pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #1 > > pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #2 > > pci8086,3584 (pciex8086,1521) [Intel Corporation I350 Gigabit Network Connection], instance #3 > > > > note that the kvm hosts were able to talk via igb0 while fugu (zone0) was not. > > OK, so this is I350, for which support should be pretty stable (it's > been in upstream illumos for over a year and I know Joyent deploys > I350 heavily in their public cloud). I don't see any open issues on > igb or I350 that would be relevant here. the troubling bit is that during the outage, the kvm hosts on akami0 and nigiri0 were able to talk to the physical network just fine, but they were not able to talk to fugu0 ... and this is all happening inside the crossbow switch within illumos if I understand the concept correctly ... cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From esproul at omniti.com Tue Oct 29 19:23:58 2013 From: esproul at omniti.com (Eric Sproul) Date: Tue, 29 Oct 2013 15:23:58 -0400 Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network In-Reply-To: References: Message-ID: On Tue, Oct 29, 2013 at 3:10 PM, Tobias Oetiker wrote: > the troubling bit is that during the outage, the kvm hosts on > akami0 and nigiri0 were able to talk to the physical network just > fine, but they were not able to talk to fugu0 ... and this is all > happening inside the crossbow switch within illumos if I > understand the concept correctly ... I'm not an expert on the Crossbow stack, but essentially I think this is correct, so perhaps we're looking at a VNIC issue with fugu0 and not anything to do with hardware. Since you're not using aggregate links, it should be possible to let the global zone use igb0 directly without disturbing the KVM vnics. I do this on a number of dev systems. It might be worth a try to move the address fugu0/v4static to igb0/v4static, though you'll of course need out-of-band or console access to do that. Eric From tobi at oetiker.ch Tue Oct 29 19:55:31 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 29 Oct 2013 20:55:31 +0100 (CET) Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network In-Reply-To: References: Message-ID: Today Eric Sproul wrote: > On Tue, Oct 29, 2013 at 3:10 PM, Tobias Oetiker wrote: > > the troubling bit is that during the outage, the kvm hosts on > > akami0 and nigiri0 were able to talk to the physical network just > > fine, but they were not able to talk to fugu0 ... and this is all > > happening inside the crossbow switch within illumos if I > > understand the concept correctly ... > > I'm not an expert on the Crossbow stack, but essentially I think this > is correct, so perhaps we're looking at a VNIC issue with fugu0 and > not anything to do with hardware. > > Since you're not using aggregate links, it should be possible to let > the global zone use igb0 directly without disturbing the KVM vnics. I > do this on a number of dev systems. It might be worth a try to move > the address fugu0/v4static to igb0/v4static, though you'll of course > need out-of-band or console access to do that. this how we had it setup originally :-) we thought that it might be better to hook zone0 into the virtual switch ... for performance since the kvms are using nfs resources from zone0 ... but you are right, it might make sense to switch back ... cheers tobi > > Eric > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From esproul at omniti.com Tue Oct 29 20:12:49 2013 From: esproul at omniti.com (Eric Sproul) Date: Tue, 29 Oct 2013 16:12:49 -0400 Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network In-Reply-To: References: Message-ID: On Tue, Oct 29, 2013 at 3:55 PM, Tobias Oetiker wrote: > this how we had it setup originally :-) we thought that it might be > better to hook zone0 into the virtual switch ... for performance > since the kvms are using nfs resources from zone0 ... > > but you are right, it might make sense to switch back ... AFAIK, unless you are actually using etherstubs, there is no "virtual switch" in the strict sense-- there's just a pathway out of one virtualized TCP/IP stack in the kernel (the one for the KVM vnic) and into another (fugu0). I'm not sure it's any different if the destination address is over a hardware interface as opposed to a vnic, but it seems simpler to my eyes. I am not a kernel engineer though. :) Eric From tobi at oetiker.ch Tue Oct 29 20:17:26 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 29 Oct 2013 21:17:26 +0100 (CET) Subject: [OmniOS-discuss] omnios host goes suddenly silent on the network In-Reply-To: References: Message-ID: Hi Eric, Today Eric Sproul wrote: > On Tue, Oct 29, 2013 at 3:10 PM, Tobias Oetiker wrote: > > the troubling bit is that during the outage, the kvm hosts on > > akami0 and nigiri0 were able to talk to the physical network just > > fine, but they were not able to talk to fugu0 ... and this is all > > happening inside the crossbow switch within illumos if I > > understand the concept correctly ... > > I'm not an expert on the Crossbow stack, but essentially I think this > is correct, so perhaps we're looking at a VNIC issue with fugu0 and > not anything to do with hardware. that's what I was afraid to ... maybe some 'bad' packets coming in over the network (it is pretty wild setup there) somehow confusing the stack ... > Since you're not using aggregate links, it should be possible to let > the global zone use igb0 directly without disturbing the KVM vnics. I > do this on a number of dev systems. It might be worth a try to move > the address fugu0/v4static to igb0/v4static, though you'll of course > need out-of-band or console access to do that. did that now ... no need for a console btw, if you are cool :-) (and have a console just in case) ipadm delete-addr fugu0/v4static; ipadm create-addr -T static -a 10.10.10.1/30 igb0/v4static cheers tobi > > Eric > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From emunch at utmi.in Wed Oct 30 04:30:49 2013 From: emunch at utmi.in (Sam M) Date: Wed, 30 Oct 2013 10:00:49 +0530 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: References: <20131027163258.GC18552@eschaton.local> Message-ID: Hi Eric, I'm OK with bloody. The problem I'm having seems minor, I only need to know where I can find OmniTI's CA root certificate so that I can install it locally. Sam On 29 October 2013 19:19, Eric Sproul wrote: > On Tue, Oct 29, 2013 at 4:00 AM, Sam M wrote: > > Hello Chris. > > > > Any update on this? Kindly let us know when the process is completed and > I > > can update. > > The unstable (aka bloody) repo is frequently, well, unstable. If this > is inconvenient for you, then the stable release (currently r151006, > soon to be r151008) would be a better choice. > > Eric > -------------- next part -------------- An HTML attachment was scrubbed... URL: From emunch at utmi.in Wed Oct 30 12:46:40 2013 From: emunch at utmi.in (Sam M) Date: Wed, 30 Oct 2013 18:16:40 +0530 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: References: <20131027163258.GC18552@eschaton.local> Message-ID: Hi Eric, The issue I'm having is that I had Bloody up and running and then my HD crashed. While on bloody, I upgraded my 8 TB data zpool. Now, the same zpool is not accessible when I'm running the release version of OmniOS. The issue I mentioned in my original email seems minor but it's causing other issues. I understand bloody is not supposed to be stable, but I can access the data zpool in readonly mode. So I was hoping for a way to fix the pkg issue, or I guess I'll wait for the updates to finish... Thanks. Sam On 29 October 2013 19:19, Eric Sproul wrote: > On Tue, Oct 29, 2013 at 4:00 AM, Sam M wrote: > > Hello Chris. > > > > Any update on this? Kindly let us know when the process is completed and > I > > can update. > > The unstable (aka bloody) repo is frequently, well, unstable. If this > is inconvenient for you, then the stable release (currently r151006, > soon to be r151008) would be a better choice. > > Eric > -------------- next part -------------- An HTML attachment was scrubbed... URL: From svavar at fiton.is Wed Oct 30 15:44:07 2013 From: svavar at fiton.is (=?iso-8859-1?Q?Svavar_=D6rn_Eysteinsson?=) Date: Wed, 30 Oct 2013 15:44:07 +0000 Subject: [OmniOS-discuss] Moving a zfs pool from server to another with less memory. Message-ID: <7AB8797E-EB1E-4D82-94CE-4DD3B246C769@fiton.is> Hi. Are there any special configuration or setup that I need to take consider ? I'm currently moving a 14TB ZFS pool from a out-dated OpenIndiana server with 16GB in RAM. The new server will only provide 8GB of RAM, and will be running OmniOS. The new server has a maximum of 8GB of RAM, so there is no option extending the RAM. I have also in plans to extend the size of the pool to at least 20TB. It only serves as a archive server. not much of client activity, only rsync and archival stuff. Any help and or information much appreciated. Thanks allot. Best regards, Svavar Reykjavik - Iceland From jimklimov at cos.ru Wed Oct 30 15:52:43 2013 From: jimklimov at cos.ru (Jim Klimov) Date: Wed, 30 Oct 2013 16:52:43 +0100 Subject: [OmniOS-discuss] Moving a zfs pool from server to another with less memory. In-Reply-To: <7AB8797E-EB1E-4D82-94CE-4DD3B246C769@fiton.is> References: <7AB8797E-EB1E-4D82-94CE-4DD3B246C769@fiton.is> Message-ID: <52712B4B.3080707@cos.ru> On 2013-10-30 16:44, Svavar ?rn Eysteinsson wrote: > > Hi. > > Are there any special configuration or setup that I need to take consider ? > > I'm currently moving a 14TB ZFS pool from a out-dated OpenIndiana server with 16GB in RAM. > The new server will only provide 8GB of RAM, and will be running OmniOS. > The new server has a maximum of 8GB of RAM, so there is no option extending the RAM. > > I have also in plans to extend the size of the pool to at least 20TB. > It only serves as a archive server. not much of client activity, only rsync and archival stuff. First of all, probably, make sure that your RAM is ECC (my "limited" NAS at home was based on desktop hardware which only used non-ECC memory which could be the cause of some of my problems - with no good way to check). Also, this amount of memory is very small for dedup for example. Otherwise, especially for an archival system with little random IO (sans scrubbing) it might not matter much... Basically, this all revolves around the "working set" (or "hot data") size, so that for the data you mostly use your data or metadata is speedily available in RAM. There are rough estimates like "you need 1GB RAM per TB of storage", but exact numbers depend on the system's usage and data layout (i.e. average number of blocks per TB). HTH, //Jim From cnehren+omnios-discuss at omniti.com Wed Oct 30 16:12:55 2013 From: cnehren+omnios-discuss at omniti.com (Chris Nehren) Date: Wed, 30 Oct 2013 12:12:55 -0400 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: References: <20131027163258.GC18552@eschaton.local> Message-ID: <20131030161255.GD2186@eschaton.local> On Wed, Oct 30, 2013 at 18:16:40 +0530, Sam M wrote: > Hi Eric, > > The issue I'm having is that I had Bloody up and running and then my HD > crashed. While on bloody, I upgraded my 8 TB data zpool. Now, the same > zpool is not accessible when I'm running the release version of OmniOS. The > issue I mentioned in my original email seems minor but it's causing other > issues. > > I understand bloody is not supposed to be stable, but I can access the data > zpool in readonly mode. > > So I was hoping for a way to fix the pkg issue, or I guess I'll wait for > the updates to finish... If you install pkg at 0.5.11,5.11-0.151007:20131027T234759Z (an unsigned version that supports signing), you should be able to use that as an interstitial version from which to do the rest of the upgrade. Let me know if this doesn't work for you. -- Chris Nehren Site Reliability Engineer, OmniTI From Kevin.Swab at colostate.edu Wed Oct 30 17:37:46 2013 From: Kevin.Swab at colostate.edu (Kevin Swab) Date: Wed, 30 Oct 2013 11:37:46 -0600 Subject: [OmniOS-discuss] multipath problem when replacing a failed SAS drive Message-ID: <527143EA.1080307@ColoState.EDU> Hello, I'm running OmniOS r151006p on the following system: - Supermicro X8DT6 board, Xeon E5606 CPU, 48GB ram - Supermicro SC847 chassis, 36 drive bays, SAS expanders, LSI 9211-8i controller - 34 x Toshiba 3T SAS drives MG03SCA300 in one pool w/ 16 mirrored sets + 2 hot spares 'mpathadm list lu' showed all drives as having two paths to the controller. Yesterday, one of the drives failed and was replaced. The new drive is only showing one path in mpathadm, and errors have started showing up periodically in /var/adm/messages: # mpathadm list lu /dev/rdsk/c1t5000039478CA7150d0 mpath-support: libmpscsi_vhci.so /dev/rdsk/c1t5000039478CA7150d0s2 Total Path Count: 1 Operational Path Count: 1 Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31120101 Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x31120101 Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31120101 Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x31120101 Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31120101 Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x31120101 Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, IOCLogInfo=0x31120101 Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x31120101 The error messages refer to target 89, which I can confirm corresponds to the missing path for my replacement drive using "lsiutil": # lsiutil -p 1 16 LSI Logic MPT Configuration Utility, Version 1.63, June 4, 2009 1 MPT Port found Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC 1. mpt_sas0 LSI Logic SAS2008 03 200 0d000100 0 SAS2008's links are 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G B___T SASAddress PhyNum Handle Parent Type [ ... cut ... ] 0 89 5000039478ca7152 17 0059 0032 SAS Target 0 90 5000039478ca7153 17 005a 000a SAS Target [ ... cut ... ] When I ask "lsiutil" to rescan the bus, I see the following error when it gets to target 89: # lsiutil -p 1 8 LSI Logic MPT Configuration Utility, Version 1.63, June 4, 2009 1 MPT Port found Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC 1. mpt_sas0 LSI Logic SAS2008 03 200 0d000100 0 SAS2008's links are 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G B___T___L Type Vendor Product Rev [ ... cut ... ] ScsiIo to Bus 0 Target 89 failed, IOCStatus = 004b (IOC Terminated) 0 90 0 Disk TOSHIBA MG03SCA300 0108 5000039478ca7153 17 [ ... cut ... ] This problem has happened to me once before on a similar system. At that time, I tried reseating the drive, and tried several different replacement drives, all had the same issue. I even tried rebooting the system and that didn't help. Does anyone know how I can clear this issue up? I'd be happy to provide any additional information that might be helpful, TIA, Kevin -- ------------------------------------------------------------------- Kevin Swab UNIX Systems Administrator ACNS Colorado State University Phone: (970)491-6572 Email: Kevin.Swab at ColoState.EDU GPG Fingerprint: 7026 3F66 A970 67BD 6F17 8EB8 8A7D 142F 2392 791C From tobi at oetiker.ch Wed Oct 30 17:56:47 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Wed, 30 Oct 2013 18:56:47 +0100 (CET) Subject: [OmniOS-discuss] hw recomendation for JBOD box Message-ID: We are looking at buying a system consisting of a 1U server and 1 or more 3U JBOD boxes to run and OmniOS ZFS server. Any HW recommendations for the JBOD box, Controller, Disks, what are you using ? cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From johan.kragsterman at capvert.se Wed Oct 30 18:02:41 2013 From: johan.kragsterman at capvert.se (Johan Kragsterman) Date: Wed, 30 Oct 2013 19:02:41 +0100 Subject: [OmniOS-discuss] Ang: multipath problem when replacing a failed SAS drive In-Reply-To: <527143EA.1080307@ColoState.EDU> References: <527143EA.1080307@ColoState.EDU> Message-ID: An HTML attachment was scrubbed... URL: From Kevin.Swab at ColoState.EDU Wed Oct 30 18:13:01 2013 From: Kevin.Swab at ColoState.EDU (Kevin Swab) Date: Wed, 30 Oct 2013 12:13:01 -0600 Subject: [OmniOS-discuss] Ang: multipath problem when replacing a failed SAS drive In-Reply-To: References: <527143EA.1080307@ColoState.EDU> Message-ID: <52714C2D.5040205@ColoState.EDU> The problem drive is currently configured as a hot-spare (it replaced the old hot-spare, which kicked in when the original drive failed), but I'll remove it from the pool and do some testing with it and report back... Thanks! Kevin On 10/30/2013 12:02 PM, Johan Kragsterman wrote: > Hi, Kevin! > > What if you replace the drive with one of the hotspares? I mean, let the > hotspare stay at its place, and configure it for replacing the > problematic drive. Then you will find out wether the backplane has a bad > port or not. Allways start to try to narrow it down. > > Rgrds Johan > > > > -----"OmniOS-discuss" skrev: ----- > Till: omnios-discuss at lists.omniti.com > Fr?n: Kevin Swab > S?nt av: "OmniOS-discuss" > Datum: 2013.10.30 18:38 > ?rende: [OmniOS-discuss] multipath problem when replacing a failed SAS drive > > Hello, > > I'm running OmniOS r151006p on the following system: > > - Supermicro X8DT6 board, Xeon E5606 CPU, 48GB ram > - Supermicro SC847 chassis, 36 drive bays, SAS expanders, LSI 9211-8i > controller > - 34 x Toshiba 3T SAS drives MG03SCA300 in one pool w/ 16 mirrored sets > + 2 hot spares > > 'mpathadm list lu' showed all drives as having two paths to the controller. > > Yesterday, one of the drives failed and was replaced. The new drive is > only showing one path in mpathadm, and errors have started showing up > periodically in /var/adm/messages: > > > > # mpathadm list lu /dev/rdsk/c1t5000039478CA7150d0 > mpath-support: libmpscsi_vhci.so > /dev/rdsk/c1t5000039478CA7150d0s2 > Total Path Count: 1 > Operational Path Count: 1 > > Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, > IOCLogInfo=0x31120101 > Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, > IOCLogInfo=0x31120101 > Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. > Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc > Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, > IOCLogInfo=0x31120101 > Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, > IOCLogInfo=0x31120101 > Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. > Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc > Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, > IOCLogInfo=0x31120101 > Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. > Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc > Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, > IOCLogInfo=0x31120101 > Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, > IOCLogInfo=0x31120101 > Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. > Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc > Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: > /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): > Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, > IOCLogInfo=0x31120101 > > > > The error messages refer to target 89, which I can confirm corresponds > to the missing path for my replacement drive using "lsiutil": > > > > # lsiutil -p 1 16 > > LSI Logic MPT Configuration Utility, Version 1.63, June 4, 2009 > > 1 MPT Port found > > Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC > 1. mpt_sas0 LSI Logic SAS2008 03 200 0d000100 0 > > SAS2008's links are 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G > > B___T SASAddress PhyNum Handle Parent Type > [ ... cut ... ] > 0 89 5000039478ca7152 17 0059 0032 SAS Target > 0 90 5000039478ca7153 17 005a 000a SAS Target > [ ... cut ... ] > > > > When I ask "lsiutil" to rescan the bus, I see the following error when > it gets to target 89: > > > > # lsiutil -p 1 8 > > LSI Logic MPT Configuration Utility, Version 1.63, June 4, 2009 > > 1 MPT Port found > > Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC > 1. mpt_sas0 LSI Logic SAS2008 03 200 0d000100 0 > > SAS2008's links are 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G > > B___T___L Type Vendor Product Rev > [ ... cut ... ] > ScsiIo to Bus 0 Target 89 failed, IOCStatus = 004b (IOC Terminated) > 0 90 0 Disk TOSHIBA MG03SCA300 0108 5000039478ca7153 > 17 > [ ... cut ... ] > > > > This problem has happened to me once before on a similar system. At > that time, I tried reseating the drive, and tried several different > replacement drives, all had the same issue. I even tried rebooting the > system and that didn't help. > > Does anyone know how I can clear this issue up? I'd be happy to provide > any additional information that might be helpful, > > TIA, > Kevin > > > > -- > ------------------------------------------------------------------- > Kevin Swab UNIX Systems Administrator > ACNS Colorado State University > Phone: (970)491-6572 Email: Kevin.Swab at ColoState.EDU > GPG Fingerprint: 7026 3F66 A970 67BD 6F17 8EB8 8A7D 142F 2392 791C > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -- ------------------------------------------------------------------- Kevin Swab UNIX Systems Administrator ACNS Colorado State University Phone: (970)491-6572 Email: Kevin.Swab at ColoState.EDU GPG Fingerprint: 7026 3F66 A970 67BD 6F17 8EB8 8A7D 142F 2392 791C From esproul at omniti.com Wed Oct 30 18:29:06 2013 From: esproul at omniti.com (Eric Sproul) Date: Wed, 30 Oct 2013 14:29:06 -0400 Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: References: Message-ID: Tobi, I'd recommend reviewing the parts lists that Joyent publishes: https://github.com/joyent/manufacturing See the parts_database.ods file. It's mostly Supermicro kit, and what I find very helpful is the lists of BIOS and firmware revisions within those parts. Eric On Wed, Oct 30, 2013 at 1:56 PM, Tobias Oetiker wrote: > We are looking at buying a system consisting of a 1U server and 1 > or more 3U JBOD boxes to run and OmniOS ZFS server. Any HW > recommendations for the JBOD box, Controller, Disks, what are you > using ? > > cheers > tobi > > > -- > Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland > http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From bdha at mirrorshades.net Wed Oct 30 18:39:15 2013 From: bdha at mirrorshades.net (Bryan Horstmann-Allen) Date: Wed, 30 Oct 2013 14:39:15 -0400 Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: References: Message-ID: <20131030183914.GA4167@lab.pobox.com> +------------------------------------------------------------------------------ | On 2013-10-30 14:29:06, Eric Sproul wrote: | | Tobi, | I'd recommend reviewing the parts lists that Joyent publishes: | https://github.com/joyent/manufacturing | | See the parts_database.ods file. It's mostly Supermicro kit, and what | I find very helpful is the lists of BIOS and firmware revisions within | those parts. I've also had very good experience with Fujitsu RX200 and RX300s (using IT-flashed non-Fujitsu non-RAID LSI HBAs) and their JX40 JBODs. (We have ~40 or so of those systems, and half a dozen JX40s.) iRMC Enterprise is actually comparatively nice to use, too. Cheers. -- bdha cyberpunk is dead. long live cyberpunk. From cks at cs.toronto.edu Wed Oct 30 20:25:06 2013 From: cks at cs.toronto.edu (Chris Siebenmann) Date: Wed, 30 Oct 2013 16:25:06 -0400 Subject: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS? Message-ID: <20131030202506.664471A0487@apps0.cs.toronto.edu> This is a long shot and I suspect that the answer is no, but: in OmniOS, is it possible somehow to have disk device names for disks behind LSI SAS controllers that are based on the physical slot ('phy') that the disk is found in instead of the disk's reported WNN or serial number? (I understand that this is only easy if there are no SAS expanders involved, which is the situation that I care about.) I know that I can recover this information from prtconf -v with appropriate mangling, but our contemplated environment would be much more manageable if we could directly use physical slot based device naming. Thanks in advance. I'll post a summary if there are any private replies (for anything besides 'nope, can't do it'). - cks From esproul at omniti.com Wed Oct 30 20:34:16 2013 From: esproul at omniti.com (Eric Sproul) Date: Wed, 30 Oct 2013 16:34:16 -0400 Subject: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS? In-Reply-To: <20131030202506.664471A0487@apps0.cs.toronto.edu> References: <20131030202506.664471A0487@apps0.cs.toronto.edu> Message-ID: On Wed, Oct 30, 2013 at 4:25 PM, Chris Siebenmann wrote: > This is a long shot and I suspect that the answer is no, but: in > OmniOS, is it possible somehow to have disk device names for disks > behind LSI SAS controllers that are based on the physical slot ('phy') > that the disk is found in instead of the disk's reported WNN or serial > number? Chris, I'm not 100% sure, but I think the integration of https://www.illumos.org/issues/4018 will give you what you want. This is currently available in r151007 but will be part of the upcoming r151008 release. Issues 4016-4019 are all related, in fact, and are all in r151007 at this time. Eric From narayan.desai at gmail.com Wed Oct 30 20:53:53 2013 From: narayan.desai at gmail.com (Narayan Desai) Date: Wed, 30 Oct 2013 15:53:53 -0500 Subject: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS? In-Reply-To: <20131030202506.664471A0487@apps0.cs.toronto.edu> References: <20131030202506.664471A0487@apps0.cs.toronto.edu> Message-ID: I hacked up some scripts to deal with our similar setup. There are a few things missing (like identify by name), but the scripts here will collect data and match between all of the different identifiers that are used to refer to a single device: https://github.com/narayandesai/diy-lsi Questions and patches welcome. -nld On Wed, Oct 30, 2013 at 3:25 PM, Chris Siebenmann wrote: > This is a long shot and I suspect that the answer is no, but: in > OmniOS, is it possible somehow to have disk device names for disks > behind LSI SAS controllers that are based on the physical slot ('phy') > that the disk is found in instead of the disk's reported WNN or serial > number? > > (I understand that this is only easy if there are no SAS expanders > involved, which is the situation that I care about.) > > I know that I can recover this information from prtconf -v with > appropriate mangling, but our contemplated environment would be much > more manageable if we could directly use physical slot based device > naming. > > Thanks in advance. I'll post a summary if there are any private > replies (for anything besides 'nope, can't do it'). > > - cks > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.jochum at alcatel-lucent.com Wed Oct 30 21:24:16 2013 From: paul.jochum at alcatel-lucent.com (Paul Jochum) Date: Wed, 30 Oct 2013 16:24:16 -0500 Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: References: Message-ID: <52717900.1000700@alcatel-lucent.com> An HTML attachment was scrubbed... URL: From tobi at oetiker.ch Wed Oct 30 22:05:11 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Wed, 30 Oct 2013 23:05:11 +0100 (CET) Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: References: Message-ID: Hi Eric, Today Eric Sproul wrote: > Tobi, > I'd recommend reviewing the parts lists that Joyent publishes: > https://github.com/joyent/manufacturing so that would be this http://www.supermicro.com/products/system/4u/6047/ssg-6047r-e1r36l.cfm filled with UltraStar 7k3000 and a ZeusRam 8GB as Zil and 256 GB ram nice :-) no jbod though as far as I can see ... so maybe jbod is not such a good idea ... cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From bdha at mirrorshades.net Wed Oct 30 22:15:22 2013 From: bdha at mirrorshades.net (Bryan Horstmann-Allen) Date: Wed, 30 Oct 2013 18:15:22 -0400 Subject: [OmniOS-discuss] hw recomendation for JBOD box Message-ID: JBODs tend to be behind expanders which can cause major headaches. If your model allows for all in-chassis, its definitely a nicer way to go. Depends on your use cases and requirements. Tobias Oetiker wrote: >Hi Eric, > >Today Eric Sproul wrote: > >> Tobi, >> I'd recommend reviewing the parts lists that Joyent publishes: >> https://github.com/joyent/manufacturing > >so that would be this > >http://www.supermicro.com/products/system/4u/6047/ssg-6047r-e1r36l.cfm > >filled with UltraStar 7k3000 and a ZeusRam 8GB as Zil > >and 256 GB ram > >nice :-) no jbod though as far as I can see ... so maybe jbod is >not such a good idea ... > >cheers >tobi > > >-- >Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland >http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 >_______________________________________________ >OmniOS-discuss mailing list >OmniOS-discuss at lists.omniti.com >http://lists.omniti.com/mailman/listinfo/omnios-discuss From cscoman at gmail.com Wed Oct 30 22:27:10 2013 From: cscoman at gmail.com (Jason Cox) Date: Wed, 30 Oct 2013 15:27:10 -0700 Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: <52717900.1000700@alcatel-lucent.com> References: <52717900.1000700@alcatel-lucent.com> Message-ID: I second Paul's recommendation. I use that JBOD in my environment as well and it has been very solid compared to other vendor hardware I have used in the past. I actually got the everything from them, www.areasys.com for server and JBOD. On Wed, Oct 30, 2013 at 2:24 PM, Paul Jochum wrote: > Tobi: > > I have had good luck with equipment from DataOnStorage.com. Not only > reasonably priced and reliable, but they also sell a piece of software > (which does run on OmniOS) called OSM, which allows a command line > interface to identify (i.e. blinking lights) for the enclosure and disks in > the enclosure. Very useful when replacing a failing disk. > > Other recommendations: > > - highly recommend using SAS over SATA disks > - having 2 SAS cables connecting the JBOD to the server > - use 6Gb/s SAS for everything (it has more reliability features than > 3 Gb/2 SAS) > - use LSI JBOD cards (such as the LSI SAS 9207-8e) > > hope this helps, > > Paul > On 10/30/2013 12:56 PM, Tobias Oetiker wrote: > > We are looking at buying a system consisting of a 1U server and 1 > or more 3U JBOD boxes to run and OmniOS ZFS server. Any HW > recommendations for the JBOD box, Controller, Disks, what are you > using ? > > cheers > tobi > > > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > -- Jason Cox -------------- next part -------------- An HTML attachment was scrubbed... URL: From mir at miras.org Wed Oct 30 22:28:08 2013 From: mir at miras.org (Michael Rasmussen) Date: Wed, 30 Oct 2013 23:28:08 +0100 Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: References: Message-ID: <20131030232808.7e723df0@sleipner.datanom.net> On Wed, 30 Oct 2013 23:05:11 +0100 (CET) Tobias Oetiker wrote: > > http://www.supermicro.com/products/system/4u/6047/ssg-6047r-e1r36l.cfm > > filled with UltraStar 7k3000 and a ZeusRam 8GB as Zil > > and 256 GB ram Nice rick;-) > > nice :-) no jbod though as far as I can see ... so maybe jbod is > not such a good idea ... > Point 6: Onboard LSI 2308 IT mode. For LSI HBA IT mode means jbod mode. And no, the only good thing for ZFS is jbod mode! The non-IT mode HBA's where you create a RAID0 for each disk is simply horrible. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- I've got a very bad feeling about this. -- Han Solo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dave-oo at pooserville.com Thu Oct 31 00:13:23 2013 From: dave-oo at pooserville.com (Dave Pooser) Date: Wed, 30 Oct 2013 19:13:23 -0500 Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: Message-ID: On 10/30/13 5:15 PM, "Bryan Horstmann-Allen" wrote: >JBODs tend to be behind expanders which can cause major headaches. If >your model allows for all in-chassis, its definitely a nicer way to go. SAS expanders with SATA disks can be major headaches waiting to happen, but AFAICT SAS expanders with SAS disks are reliable and stable. I'd be interested in hearing from people with different experiences, though. -- Dave Pooser Cat-Herder-in-Chief, Pooserville.com "...Life is not a journey to the grave with the intention of arriving safely in one pretty and well-preserved piece, but to slide across the finish line broadside, thoroughly used up, worn out, leaking oil, and shouting GERONIMO!!!" -- Bill McKenna From johan.kragsterman at capvert.se Thu Oct 31 04:29:05 2013 From: johan.kragsterman at capvert.se (Johan Kragsterman) Date: Thu, 31 Oct 2013 05:29:05 +0100 Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: References: , Message-ID: Tobi! @ the discussion about JBOD and expanders: For me, JBOD is the best solution, at least for spinning disks. Where you would place your cache is another question. But for the JBOD, you would need to ask yourself wether you would like expanders or not. That depends of course of your environmental needs, the prestanda needed, your workload, etc. JBOD, for me, is the best solution because of the flexibility. It's easy to move it to another storage head. There was a discussion on this list a couple of month ago, where someone mentioned expanderless JBOD's, I believe it was Supermicro. I don't recall who it was that mentioned them, perhaps it was Richard Elling? With these you can get all the bandwith you like, so it's like internal disks. I would like someone that has experience of these to comment on this. Otherwise, normally perhaps, you wouldn't need direct links to all of your drives, especially if you got a good cache implementation. I would also consider, if I was in your situation, a 2U storage head server, instead of a 1U, because of two things: 1: The cache. You would like your cache to be able to expand. 2: Expansion even here: You would like to have good expansion possibilities in the chassi and the mo'bo'(slots), for beeing able to connect to more JBOD's. In a 1U chassi your expansion possibilities are very limited. Rgrds Johan -----"OmniOS-discuss" skrev: ----- Till: Eric Sproul Fr?n: Tobias Oetiker S?nt av: "OmniOS-discuss" Datum: 2013.10.30 23:06 Kopia: omnios-discuss ?rende: Re: [OmniOS-discuss] hw recomendation for JBOD box Hi Eric, Today Eric Sproul wrote: > Tobi, > I'd recommend reviewing the parts lists that Joyent publishes: > https://github.com/joyent/manufacturing so that would be this http://www.supermicro.com/products/system/4u/6047/ssg-6047r-e1r36l.cfm filled with UltraStar 7k3000 and a ZeusRam 8GB as Zil and 256 GB ram nice :-) no jbod though as far as I can see ... so maybe jbod is not such a good idea ... cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch?tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss at lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss From tobi at oetiker.ch Thu Oct 31 04:29:44 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Thu, 31 Oct 2013 05:29:44 +0100 (CET) Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: <20131030232808.7e723df0@sleipner.datanom.net> References: <20131030232808.7e723df0@sleipner.datanom.net> Message-ID: Yesterday Michael Rasmussen wrote: > On Wed, 30 Oct 2013 23:05:11 +0100 (CET) > Tobias Oetiker wrote: > > > > > http://www.supermicro.com/products/system/4u/6047/ssg-6047r-e1r36l.cfm > > > > filled with UltraStar 7k3000 and a ZeusRam 8GB as Zil > > > > and 256 GB ram > > Nice rick;-) > > > > > nice :-) no jbod though as far as I can see ... so maybe jbod is > > not such a good idea ... > > > Point 6: Onboard LSI 2308 IT mode. For LSI HBA IT mode means jbod > mode. And no, the only good thing for ZFS is jbod mode! The non-IT mode > HBA's where you create a RAID0 for each disk is simply horrible. sure, jbod mode, I meant having an external jbod box attached cheers tobi > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From emunch at utmi.in Thu Oct 31 07:07:48 2013 From: emunch at utmi.in (Sam M) Date: Thu, 31 Oct 2013 12:37:48 +0530 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: <20131030161255.GD2186@eschaton.local> References: <20131027163258.GC18552@eschaton.local> <20131030161255.GD2186@eschaton.local> Message-ID: Chris, Thanks. I tried your suggestion, it's not working, output below. Frankly, I don't understand what it means. # pkg install pkg at 0.5.11,5.11-0.151007:20131027T234759Z Creating Plan \ pkg install: No matching version of package/pkg can be installed: Reject: pkg://omnios/package/pkg at 0.5.11,5.11-0.151007:20131027T234759Z Reason: All versions matching 'require' dependency pkg:/system/library at 0.5.11,5.11-0.151007 are rejected Reject: pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130514T014236Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130516T041413Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130613T153322Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130621T203201Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130702T200639Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130716T130854Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130827T215423Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130904T140541Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20130930T235448Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20131021T160227Z pkg://omnios/system/library at 0.5.11 ,5.11-0.151007:20131031T015418Z Reason: This version is excluded by installed incorporation pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11 ,5.11-0.151006:20130506T161042Z This version is excluded by installed incorporation pkg://omnios/incorporation/jeos/illumos-gate at 11 ,5.11-0.151006:20130506T183443Z On 30 October 2013 21:42, Chris Nehren wrote: > pkg at 0.5.11,5.11-0.151007:20131027T234759Z > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben at fluffy.co.uk Thu Oct 31 11:54:50 2013 From: ben at fluffy.co.uk (Ben Summers) Date: Thu, 31 Oct 2013 11:54:50 +0000 Subject: [OmniOS-discuss] Boot from mirrored USB? Message-ID: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> Hello, I'm speccing out some new hardware. It seems challenging to get vendor supported configurations which give you lots of discs on a Solarish OS, rather than using horrid RAID cards. The best config I've found so far seems to be a Fujitsu RX200 with 4 internal 15k SAS discs (the internal supported card can only do 8 drives if you use RAID), plus a Fujitsu branded LSI controller connected to an Intel 3.5" JBOD array for bulk storage and maybe an SSD for ZIL. Because I'd like to use all the internal discs for a database as a pair of mirrors in a single JBOD, I was wondering if anyone boots from USB discs? The RX200 has a single internal USB slot for such things, and you can get some very low profile USB drives for an external port: http://www.sandisk.co.uk/products/usb/drives/cruzer-fit/ http://www.kingston.com/datasheets/dtmc_en.pdf Would it be a sensible option to install OmniOS with a mirrored USB rpool? Zone roots would go on the internal discs. Thanks for any advice and/or warnings, Ben -- http://bens.me.uk From cnehren+omnios-discuss at omniti.com Thu Oct 31 13:53:39 2013 From: cnehren+omnios-discuss at omniti.com (Chris Nehren) Date: Thu, 31 Oct 2013 09:53:39 -0400 Subject: [OmniOS-discuss] Boot from mirrored USB? In-Reply-To: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> Message-ID: <20131031135339.GG2186@eschaton.local> On Thu, Oct 31, 2013 at 11:54:50 +0000, Ben Summers wrote: > > Hello, > > I'm speccing out some new hardware. It seems challenging to get vendor supported configurations which give you lots of discs on a Solarish OS, rather than using horrid RAID cards. > > The best config I've found so far seems to be a Fujitsu RX200 with 4 internal 15k SAS discs (the internal supported card can only do 8 drives if you use RAID), plus a Fujitsu branded LSI controller connected to an Intel 3.5" JBOD array for bulk storage and maybe an SSD for ZIL. > > Because I'd like to use all the internal discs for a database as a pair of mirrors in a single JBOD, I was wondering if anyone boots from USB discs? SmartOS is designed to run from USB drives. I don't know if their configuration supports mirroring, though. -- Chris Nehren From cnehren+omnios-discuss at omniti.com Thu Oct 31 13:56:03 2013 From: cnehren+omnios-discuss at omniti.com (Chris Nehren) Date: Thu, 31 Oct 2013 09:56:03 -0400 Subject: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited] In-Reply-To: References: <20131027163258.GC18552@eschaton.local> <20131030161255.GD2186@eschaton.local> Message-ID: <20131031135603.GH2186@eschaton.local> On Thu, Oct 31, 2013 at 12:37:48 +0530, Sam M wrote: > Chris, Thanks. I tried your suggestion, it's not working, output below. > Frankly, I don't understand what it means. > > # pkg install pkg at 0.5.11,5.11-0.151007:20131027T234759Z > Creating Plan \ > [install fail snipped] Sam, I think this is due to some changes in the repo that happened in between the time I made my suggestion and the time you attempted to update your machine. I would suggest holding off updating until the next major stable release (r151008) comes, which should be Real Soon Now. -- Chris Nehren Site Reliability Engineer, OmniTI From jesus at omniti.com Thu Oct 31 14:01:35 2013 From: jesus at omniti.com (Theo Schlossnagle) Date: Thu, 31 Oct 2013 10:01:35 -0400 Subject: [OmniOS-discuss] Boot from mirrored USB? In-Reply-To: <20131031135339.GG2186@eschaton.local> References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> <20131031135339.GG2186@eschaton.local> Message-ID: I believe napp-it based on OmniOS also boots from USB. The mirroring is hard because I don't think it is a native ZFS boot -- works more like a ram disk. On Thu, Oct 31, 2013 at 9:53 AM, Chris Nehren < cnehren+omnios-discuss at omniti.com> wrote: > On Thu, Oct 31, 2013 at 11:54:50 +0000, Ben Summers wrote: > > > > Hello, > > > > I'm speccing out some new hardware. It seems challenging to get vendor > supported configurations which give you lots of discs on a Solarish OS, > rather than using horrid RAID cards. > > > > The best config I've found so far seems to be a Fujitsu RX200 with 4 > internal 15k SAS discs (the internal supported card can only do 8 drives if > you use RAID), plus a Fujitsu branded LSI controller connected to an Intel > 3.5" JBOD array for bulk storage and maybe an SSD for ZIL. > > > > Because I'd like to use all the internal discs for a database as a pair > of mirrors in a single JBOD, I was wondering if anyone boots from USB discs? > > SmartOS is designed to run from USB drives. I don't know if their > configuration supports mirroring, though. > > -- > Chris Nehren > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss 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: From sriram at belenix.org Thu Oct 31 14:07:53 2013 From: sriram at belenix.org (Sriram Narayanan) Date: Thu, 31 Oct 2013 07:07:53 -0700 Subject: [OmniOS-discuss] Boot from mirrored USB? In-Reply-To: References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> <20131031135339.GG2186@eschaton.local> Message-ID: Some of my servers boot opendiana 151 from mirrored USB. I've tested this on each server that we created a set for. Ram On Oct 31, 2013 7:01 AM, "Theo Schlossnagle" wrote: > I believe napp-it based on OmniOS also boots from USB. The mirroring is > hard because I don't think it is a native ZFS boot -- works more like a ram > disk. > > > On Thu, Oct 31, 2013 at 9:53 AM, Chris Nehren < > cnehren+omnios-discuss at omniti.com> wrote: > >> On Thu, Oct 31, 2013 at 11:54:50 +0000, Ben Summers wrote: >> > >> > Hello, >> > >> > I'm speccing out some new hardware. It seems challenging to get vendor >> supported configurations which give you lots of discs on a Solarish OS, >> rather than using horrid RAID cards. >> > >> > The best config I've found so far seems to be a Fujitsu RX200 with 4 >> internal 15k SAS discs (the internal supported card can only do 8 drives if >> you use RAID), plus a Fujitsu branded LSI controller connected to an Intel >> 3.5" JBOD array for bulk storage and maybe an SSD for ZIL. >> > >> > Because I'd like to use all the internal discs for a database as a pair >> of mirrors in a single JBOD, I was wondering if anyone boots from USB discs? >> >> SmartOS is designed to run from USB drives. I don't know if their >> configuration supports mirroring, though. >> >> -- >> Chris Nehren >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> > > > > -- > > Theo Schlossnagle > > http://omniti.com/is/theo-schlossnagle > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cnehren+omnios-discuss at omniti.com Thu Oct 31 14:16:32 2013 From: cnehren+omnios-discuss at omniti.com (Chris Nehren) Date: Thu, 31 Oct 2013 10:16:32 -0400 Subject: [OmniOS-discuss] Boot from mirrored USB? In-Reply-To: References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> <20131031135339.GG2186@eschaton.local> Message-ID: <20131031141632.GI2186@eschaton.local> On Thu, Oct 31, 2013 at 07:07:53 -0700, Sriram Narayanan wrote: > Some of my servers boot opendiana 151 from mirrored USB. I've tested this > on each server that we created a set for. > Very cool. Do you have docs somewhere for setting that up? -- Chris Nehren From Rob at Logan.com Thu Oct 31 14:19:20 2013 From: Rob at Logan.com (Rob Logan) Date: Thu, 31 Oct 2013 10:19:20 -0400 Subject: [OmniOS-discuss] [SPAM] Re: Boot from mirrored USB? In-Reply-To: References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> <20131031135339.GG2186@eschaton.local> Message-ID: <527266E8.7040201@Logan.com> > Some of my servers boot opendiana 151 from mirrored USB. I built a few root mirrored USB systems (three way), but stop because /var was wearing out the cheap USB sticks. http://rob.com/lancair/2013.01/usb.jpg Rob From jim.oltman at gmail.com Thu Oct 31 15:19:09 2013 From: jim.oltman at gmail.com (Jim Oltman) Date: Thu, 31 Oct 2013 09:19:09 -0600 Subject: [OmniOS-discuss] hw recomendation for JBOD box In-Reply-To: References: Message-ID: I agree with Paul above. At my company, I had to convince them that ZFS was the way to go. We ended up going with Nexenta and their HA cluster option. Two headnodes (Inte E5645 with 48GB RAM each) that each connect to 3 JBODs via dual LSI 9207-8e in each headnode. We have 2 DataOn DNS-1600 4U 24 bay JBODs and one 2U LSI 12 Bay JBOD. Each JBOD has 2 redundant cards with 2 inputs and one output on each card. This allows for high availability software to fail over to a different headnode without the need to unplug anything from the back. I really prefer the DataON JBODs to the SuperMicro. The DataON JBODs have 99% field replaceable parts. Dual PSUs, dual SAS controller cards (both removeable without taking down power). If you have to replace a failed expander on the SuperMicro JBOD, you have to take down the whole JBOD and replace the backplane. Can get messy. The DataON JBOD is more expensive, but you really get what you pay for. Don't get me wrong. We have a couple SuperMicro JBODs and they've worked well. I'm just really nervous for the day that the backplane dies and I have to take down storage for X number of days while I get new parts. Good Luck! Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben at fluffy.co.uk Thu Oct 31 15:32:06 2013 From: ben at fluffy.co.uk (Ben Summers) Date: Thu, 31 Oct 2013 15:32:06 +0000 Subject: [OmniOS-discuss] Boot from mirrored USB? In-Reply-To: <527266E8.7040201@Logan.com> References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> <20131031135339.GG2186@eschaton.local> <527266E8.7040201@Logan.com> Message-ID: Thanks for all the feedback! It sounds like it's worth a bit of experimentation, but I should make sure things like /var are not on the USB stick. :-) Ben On 31 Oct 2013, at 14:19, Rob Logan wrote: > > Some of my servers boot opendiana 151 from mirrored USB. > > I built a few root mirrored USB systems (three way), but stop because > /var was wearing out the cheap USB sticks. http://rob.com/lancair/2013.01/usb.jpg > > Rob > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- http://bens.me.uk From mark.homoky at lingidiom.com Thu Oct 31 15:36:22 2013 From: mark.homoky at lingidiom.com (Mark Homoky) Date: Thu, 31 Oct 2013 15:36:22 +0000 Subject: [OmniOS-discuss] Boot from mirrored USB? In-Reply-To: <20131031135339.GG2186@eschaton.local> References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> <20131031135339.GG2186@eschaton.local> Message-ID: <527278F6.9020109@lingidiom.com> On 31/10/2013 13:53, Chris Nehren wrote: > On Thu, Oct 31, 2013 at 11:54:50 +0000, Ben Summers wrote: >> Hello, >> >> I'm speccing out some new hardware. It seems challenging to get vendor supported configurations which give you lots of discs on a Solarish OS, rather than using horrid RAID cards. >> >> The best config I've found so far seems to be a Fujitsu RX200 with 4 internal 15k SAS discs (the internal supported card can only do 8 drives if you use RAID), plus a Fujitsu branded LSI controller connected to an Intel 3.5" JBOD array for bulk storage and maybe an SSD for ZIL. >> >> Because I'd like to use all the internal discs for a database as a pair of mirrors in a single JBOD, I was wondering if anyone boots from USB discs? > SmartOS is designed to run from USB drives. I don't know if their > configuration supports mirroring, though. I guess that depends on how we interpret "mirroring". Mirrored boot disks make sense and are required in a traditional environment such as OmniOS. SmartOS just needs a method of getting the server up and running. SmartOS can be booted from a USB stick; CD ROM; or iPXE boot - effectively two fallback methods in addition to your primary boot method. ZFS has use of all the disks - internal or otherwise - for data storage. Depending on their size I'd recommend 3-way mirrors to ensure redundancy in the event of a disk failure and long resilver times. I'm not against OmniOS - we run it here and love it! The only negative I can see running SmartOS is the lack of IPS packaging - but it's a minor negative at that. -- Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 899 bytes Desc: OpenPGP digital signature URL: From valrhona at gmail.com Thu Oct 31 15:48:17 2013 From: valrhona at gmail.com (Valrhona) Date: Thu, 31 Oct 2013 16:48:17 +0100 Subject: [OmniOS-discuss] Boot from mirrored USB? In-Reply-To: References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> <20131031135339.GG2186@eschaton.local> Message-ID: I have been running OmniOS and Napp-It on my Dell T710 server, booting off of a USB stick running on the internal port for several months, with no issues or problems. I deliberately found and bought an SLC flash-based USB stick for this purpose, on Taobao (China's Ebay) last time I visited, which were dirt-cheap ($20 for 16 GB) and work like a charm. This is the main fileserver I use everyday, and USB booting works fine. I am also running OpenIndiana on my major workstation, with mirrored SLC Intel SSDs, and again no issues or problems; just followed the standard installation guide, and everything works fine. Peter On Thu, Oct 31, 2013 at 3:01 PM, Theo Schlossnagle wrote: > I believe napp-it based on OmniOS also boots from USB. The mirroring is > hard because I don't think it is a native ZFS boot -- works more like a ram > disk. > > > On Thu, Oct 31, 2013 at 9:53 AM, Chris Nehren > wrote: >> >> On Thu, Oct 31, 2013 at 11:54:50 +0000, Ben Summers wrote: >> > >> > Hello, >> > >> > I'm speccing out some new hardware. It seems challenging to get vendor >> > supported configurations which give you lots of discs on a Solarish OS, >> > rather than using horrid RAID cards. >> > >> > The best config I've found so far seems to be a Fujitsu RX200 with 4 >> > internal 15k SAS discs (the internal supported card can only do 8 drives if >> > you use RAID), plus a Fujitsu branded LSI controller connected to an Intel >> > 3.5" JBOD array for bulk storage and maybe an SSD for ZIL. >> > >> > Because I'd like to use all the internal discs for a database as a pair >> > of mirrors in a single JBOD, I was wondering if anyone boots from USB discs? >> >> SmartOS is designed to run from USB drives. I don't know if their >> configuration supports mirroring, though. >> >> -- >> Chris Nehren >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > > -- > > Theo Schlossnagle > > http://omniti.com/is/theo-schlossnagle > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > From Kevin.Swab at colostate.edu Thu Oct 31 17:01:20 2013 From: Kevin.Swab at colostate.edu (Kevin Swab) Date: Thu, 31 Oct 2013 11:01:20 -0600 Subject: [OmniOS-discuss] Ang: multipath problem when replacing a failed SAS drive In-Reply-To: <52714C2D.5040205@ColoState.EDU> References: <527143EA.1080307@ColoState.EDU> <52714C2D.5040205@ColoState.EDU> Message-ID: <52728CE0.3040608@ColoState.EDU> I put the drive that's missing a path in it's own pool and did some reading and writing (filled the drive with 0's using 'dd', then read them back off). Other than a handful of errors in iostat and /var/adm/messages (like the ones I reported before), everything appeared to work fine: # iostat -En c1t5000039478CA7150d0 c1t5000039478CA7150d0 Soft Errors: 0 Hard Errors: 2 Transport Errors: 29 Vendor: TOSHIBA Product: MG03SCA300 Revision: 0108 Serial No: Z2H0A008FTP3 Size: 3000.59GB <3000592982016 bytes> Media Error: 0 Device Not Ready: 0 No Device: 2 Recoverable: 0 Illegal Request: 0 Predictive Failure Analysis: 0 So the port on the backplane appears (at least partially) functional, where do you think I should go from here? Thanks again, Kevin On 10/30/2013 12:13 PM, Kevin Swab wrote: > The problem drive is currently configured as a hot-spare (it replaced > the old hot-spare, which kicked in when the original drive failed), but > I'll remove it from the pool and do some testing with it and report back... > > Thanks! > Kevin > > On 10/30/2013 12:02 PM, Johan Kragsterman wrote: >> Hi, Kevin! >> >> What if you replace the drive with one of the hotspares? I mean, let the >> hotspare stay at its place, and configure it for replacing the >> problematic drive. Then you will find out wether the backplane has a bad >> port or not. Allways start to try to narrow it down. >> >> Rgrds Johan >> >> >> >> -----"OmniOS-discuss" skrev: ----- >> Till: omnios-discuss at lists.omniti.com >> Fr?n: Kevin Swab >> S?nt av: "OmniOS-discuss" >> Datum: 2013.10.30 18:38 >> ?rende: [OmniOS-discuss] multipath problem when replacing a failed SAS drive >> >> Hello, >> >> I'm running OmniOS r151006p on the following system: >> >> - Supermicro X8DT6 board, Xeon E5606 CPU, 48GB ram >> - Supermicro SC847 chassis, 36 drive bays, SAS expanders, LSI 9211-8i >> controller >> - 34 x Toshiba 3T SAS drives MG03SCA300 in one pool w/ 16 mirrored sets >> + 2 hot spares >> >> 'mpathadm list lu' showed all drives as having two paths to the controller. >> >> Yesterday, one of the drives failed and was replaced. The new drive is >> only showing one path in mpathadm, and errors have started showing up >> periodically in /var/adm/messages: >> >> >> >> # mpathadm list lu /dev/rdsk/c1t5000039478CA7150d0 >> mpath-support: libmpscsi_vhci.so >> /dev/rdsk/c1t5000039478CA7150d0s2 >> Total Path Count: 1 >> Operational Path Count: 1 >> >> Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, >> IOCLogInfo=0x31120101 >> Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, >> IOCLogInfo=0x31120101 >> Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. >> Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc >> Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, >> IOCLogInfo=0x31120101 >> Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, >> IOCLogInfo=0x31120101 >> Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. >> Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc >> Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, >> IOCLogInfo=0x31120101 >> Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. >> Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc >> Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, >> IOCLogInfo=0x31120101 >> Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler mptsas_handle_event_sync: IOCStatus=0x8000, >> IOCLogInfo=0x31120101 >> Oct 30 09:30:22 hagler scsi: [ID 365881 kern.info] >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler Log info 0x31120101 received for target 89. >> Oct 30 09:30:22 hagler scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc >> Oct 30 09:30:22 hagler scsi: [ID 243001 kern.warning] WARNING: >> /pci at 0,0/pci8086,3410 at 9/pci1000,3020 at 0 (mpt_sas0): >> Oct 30 09:30:22 hagler mptsas_handle_event: IOCStatus=0x8000, >> IOCLogInfo=0x31120101 >> >> >> >> The error messages refer to target 89, which I can confirm corresponds >> to the missing path for my replacement drive using "lsiutil": >> >> >> >> # lsiutil -p 1 16 >> >> LSI Logic MPT Configuration Utility, Version 1.63, June 4, 2009 >> >> 1 MPT Port found >> >> Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC >> 1. mpt_sas0 LSI Logic SAS2008 03 200 0d000100 0 >> >> SAS2008's links are 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G >> >> B___T SASAddress PhyNum Handle Parent Type >> [ ... cut ... ] >> 0 89 5000039478ca7152 17 0059 0032 SAS Target >> 0 90 5000039478ca7153 17 005a 000a SAS Target >> [ ... cut ... ] >> >> >> >> When I ask "lsiutil" to rescan the bus, I see the following error when >> it gets to target 89: >> >> >> >> # lsiutil -p 1 8 >> >> LSI Logic MPT Configuration Utility, Version 1.63, June 4, 2009 >> >> 1 MPT Port found >> >> Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC >> 1. mpt_sas0 LSI Logic SAS2008 03 200 0d000100 0 >> >> SAS2008's links are 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G, 6.0 G >> >> B___T___L Type Vendor Product Rev >> [ ... cut ... ] >> ScsiIo to Bus 0 Target 89 failed, IOCStatus = 004b (IOC Terminated) >> 0 90 0 Disk TOSHIBA MG03SCA300 0108 5000039478ca7153 >> 17 >> [ ... cut ... ] >> >> >> >> This problem has happened to me once before on a similar system. At >> that time, I tried reseating the drive, and tried several different >> replacement drives, all had the same issue. I even tried rebooting the >> system and that didn't help. >> >> Does anyone know how I can clear this issue up? I'd be happy to provide >> any additional information that might be helpful, >> >> TIA, >> Kevin >> >> >> >> -- >> ------------------------------------------------------------------- >> Kevin Swab UNIX Systems Administrator >> ACNS Colorado State University >> Phone: (970)491-6572 Email: Kevin.Swab at ColoState.EDU >> GPG Fingerprint: 7026 3F66 A970 67BD 6F17 8EB8 8A7D 142F 2392 791C >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> > -- ------------------------------------------------------------------- Kevin Swab UNIX Systems Administrator ACNS Colorado State University Phone: (970)491-6572 Email: Kevin.Swab at ColoState.EDU GPG Fingerprint: 7026 3F66 A970 67BD 6F17 8EB8 8A7D 142F 2392 791C From geoffn at gnaa.net Thu Oct 31 17:20:42 2013 From: geoffn at gnaa.net (Geoff Nordli) Date: Thu, 31 Oct 2013 10:20:42 -0700 Subject: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS? In-Reply-To: References: <20131030202506.664471A0487@apps0.cs.toronto.edu> Message-ID: <5272916A.1060300@gnaa.net> On 13-10-30 01:34 PM, Eric Sproul wrote: > On Wed, Oct 30, 2013 at 4:25 PM, Chris Siebenmann wrote: >> This is a long shot and I suspect that the answer is no, but: in >> OmniOS, is it possible somehow to have disk device names for disks >> behind LSI SAS controllers that are based on the physical slot ('phy') >> that the disk is found in instead of the disk's reported WNN or serial >> number? > Chris, > I'm not 100% sure, but I think the integration of > https://www.illumos.org/issues/4018 will give you what you want. This > is currently available in r151007 but will be part of the upcoming > r151008 release. > > Issues 4016-4019 are all related, in fact, and are all in r151007 at this time. > > Hi Eric. I haven't played with this yet, but will this allow you to light the LED? So you know what disk has failed or needs replacing. thanks, Geoff From alka at hfg-gmuend.de Thu Oct 31 17:28:26 2013 From: alka at hfg-gmuend.de (=?ISO-8859-1?Q?G=FCnther_Alka?=) Date: Thu, 31 Oct 2013 18:28:26 +0100 Subject: [OmniOS-discuss] Boot from mirrored USB? In-Reply-To: References: <4EFE3929-FA6A-4FC7-934E-C9A5DA5DBC21@fluffy.co.uk> <20131031135339.GG2186@eschaton.local> Message-ID: <5272933A.6050501@hfg-gmuend.de> napp-it has a web menu entry to create ZFS mirrored disks or mirrored usb sticks (both bootable) following the blog of Constantin Gonzales: http://constantin.glez.de/blog/2011/03/how-set-zfs-root-pool-mirror-oracle-solaris-11-express With high quality and fast usb sticks especially in a mirrored config and atime disabled, usb boot is a very attractive boot method where you can easily create clones of sticks for backups or OS deployment (I offer a free Windows clone tool and preconfigured OmniOS images for download at napp-it.org). Performance wise usb boot is quite ok. Only problem: currently you can only boot from usb when you plugin the sticks in those ports that were used during setup. It would be perfect it you may boot from any usb port maybe on similar mainboards. But this seems a Grub restriction where the physical bootdevice is hardcoded during setup. On 31.10.2013 15:01, Theo Schlossnagle wrote: > I believe napp-it based on OmniOS also boots from USB. The mirroring > is hard because I don't think it is a native ZFS boot -- works more > like a ram disk. > > > On Thu, Oct 31, 2013 at 9:53 AM, Chris Nehren > > wrote: > > On Thu, Oct 31, 2013 at 11:54:50 +0000, Ben Summers wrote: > > > > Hello, > > > > I'm speccing out some new hardware. It seems challenging to get > vendor supported configurations which give you lots of discs on a > Solarish OS, rather than using horrid RAID cards. > > > > The best config I've found so far seems to be a Fujitsu RX200 > with 4 internal 15k SAS discs (the internal supported card can > only do 8 drives if you use RAID), plus a Fujitsu branded LSI > controller connected to an Intel 3.5" JBOD array for bulk storage > and maybe an SSD for ZIL. > > > > Because I'd like to use all the internal discs for a database as > a pair of mirrors in a single JBOD, I was wondering if anyone > boots from USB discs? > > SmartOS is designed to run from USB drives. I don't know if their > configuration supports mirroring, though. > > -- > Chris Nehren > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > > -- > > Theo Schlossnagle > > http://omniti.com/is/theo-schlossnagle > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- H f G Hochschule f?r Gestaltung university of design Schw?bisch Gm?nd Marie-Curie-Str. 19 73529 Schw?bisch Gm?nd Guenther Alka, Dipl.-Ing. (FH) Leiter des Rechenzentrums head of computer center Tel 07171 602 624 Fax 07171 69259 guenther.alka at hfg-gmuend.de http://rz.hfg-gmuend.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From esproul at omniti.com Thu Oct 31 17:50:54 2013 From: esproul at omniti.com (Eric Sproul) Date: Thu, 31 Oct 2013 13:50:54 -0400 Subject: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS? In-Reply-To: <5272916A.1060300@gnaa.net> References: <20131030202506.664471A0487@apps0.cs.toronto.edu> <5272916A.1060300@gnaa.net> Message-ID: On Thu, Oct 31, 2013 at 1:20 PM, Geoff Nordli wrote: > I haven't played with this yet, but will this allow you to light the LED? > > So you know what disk has failed or needs replacing. I haven't tried it yet either, but assuming you have a SES chip, I believe so. Eric From mayuresh at kathe.in Thu Oct 31 17:54:33 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 31 Oct 2013 13:54:33 -0400 Subject: [OmniOS-discuss] java : feca beba : endian problem? Message-ID: <20131031175433.GA6982@wolfman.devio.us> hello, i've been writing short java programs under omnios, and they work well, no issues with that. just did a "od -x .class" on one of my programs and found the following; 0000000 feca beba 0000 3200 2e00 000a 000b 0915 0000020 1600 1700 0008 0a18 1900 1a00 000a 0016 0000040 0a1b 1c00 1d00 0008 081e 1f00 000a 0019 0000060 0720 2100 0007 0122 0600 693c 696e 3e74 . . . is that reference to "feca beba" due to endian issues? it should actually be "cafe babe". :) ~mayuresh From alka at hfg-gmuend.de Thu Oct 31 18:03:55 2013 From: alka at hfg-gmuend.de (=?ISO-8859-1?Q?G=FCnther_Alka?=) Date: Thu, 31 Oct 2013 19:03:55 +0100 Subject: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS? In-Reply-To: <20131030202506.664471A0487@apps0.cs.toronto.edu> References: <20131030202506.664471A0487@apps0.cs.toronto.edu> Message-ID: <52729B8B.4080104@hfg-gmuend.de> I have added a physical slot detection that displays physical Slot, WWN and serials together with the option to switch on the red alert led on supported backplanes within napp-it with the help of sas2ircu (a LSI tool that displays slot and disk serial). On 30.10.2013 21:25, Chris Siebenmann wrote: > This is a long shot and I suspect that the answer is no, but: in > OmniOS, is it possible somehow to have disk device names for disks > behind LSI SAS controllers that are based on the physical slot ('phy') > that the disk is found in instead of the disk's reported WNN or serial > number? > > (I understand that this is only easy if there are no SAS expanders > involved, which is the situation that I care about.) > > I know that I can recover this information from prtconf -v with > appropriate mangling, but our contemplated environment would be much > more manageable if we could directly use physical slot based device > naming. > > Thanks in advance. I'll post a summary if there are any private > replies (for anything besides 'nope, can't do it'). > > - cks > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From jesus at omniti.com Thu Oct 31 18:10:23 2013 From: jesus at omniti.com (Theo Schlossnagle) Date: Thu, 31 Oct 2013 14:10:23 -0400 Subject: [OmniOS-discuss] java : feca beba : endian problem? In-Reply-To: <20131031175433.GA6982@wolfman.devio.us> References: <20131031175433.GA6982@wolfman.devio.us> Message-ID: Class files are cross endian portable. the header is 0xbabecafe big endian... od -x will print native endian... looks right to me. On Thu, Oct 31, 2013 at 1:54 PM, Mayuresh Kathe wrote: > hello, i've been writing short java programs under > omnios, and they work well, no issues with that. > > just did a "od -x .class" on one of my > programs and found the following; > > 0000000 feca beba 0000 3200 2e00 000a 000b 0915 > 0000020 1600 1700 0008 0a18 1900 1a00 000a 0016 > 0000040 0a1b 1c00 1d00 0008 081e 1f00 000a 0019 > 0000060 0720 2100 0007 0122 0600 693c 696e 3e74 > . > . > . > > is that reference to "feca beba" due to endian > issues? > it should actually be "cafe babe". :) > > ~mayuresh > > _______________________________________________ > 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: From felix.nielsen at gmail.com Thu Oct 31 18:26:45 2013 From: felix.nielsen at gmail.com (Felix Nielsen) Date: Thu, 31 Oct 2013 19:26:45 +0100 Subject: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS? In-Reply-To: <52729B8B.4080104@hfg-gmuend.de> References: <20131030202506.664471A0487@apps0.cs.toronto.edu> <52729B8B.4080104@hfg-gmuend.de> Message-ID: <3C6A3499-FE2C-4E95-9F58-E96A63089212@gmail.com> Hi G?nther, Is that feature included in napp-it? If so where and if not how do I get it :) Thanks Felix Btw. napp-it rocks :) Den 31/10/2013 kl. 19.03 skrev G?nther Alka : > I have added a physical slot detection that displays physical > Slot, WWN and serials together with the option to switch on the red > alert led on supported backplanes within napp-it with the help of > sas2ircu (a LSI tool that displays slot and disk serial). > > > On 30.10.2013 21:25, Chris Siebenmann wrote: >> This is a long shot and I suspect that the answer is no, but: in >> OmniOS, is it possible somehow to have disk device names for disks >> behind LSI SAS controllers that are based on the physical slot ('phy') >> that the disk is found in instead of the disk's reported WNN or serial >> number? >> >> (I understand that this is only easy if there are no SAS expanders >> involved, which is the situation that I care about.) >> >> I know that I can recover this information from prtconf -v with >> appropriate mangling, but our contemplated environment would be much >> more manageable if we could directly use physical slot based device >> naming. >> >> Thanks in advance. I'll post a summary if there are any private >> replies (for anything besides 'nope, can't do it'). >> >> - cks >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From alka at hfg-gmuend.de Thu Oct 31 21:37:12 2013 From: alka at hfg-gmuend.de (alka) Date: Thu, 31 Oct 2013 22:37:12 +0100 Subject: [OmniOS-discuss] Physical slot based disk names for LSI SAS on OmniOS? In-Reply-To: <3C6A3499-FE2C-4E95-9F58-E96A63089212@gmail.com> References: <20131030202506.664471A0487@apps0.cs.toronto.edu> <52729B8B.4080104@hfg-gmuend.de> <3C6A3499-FE2C-4E95-9F58-E96A63089212@gmail.com> Message-ID: hi Felix its part of the monitor extension (free for less than 8 disks) see Menu disks >> SAS2 extension Am 31.10.2013 um 19:26 schrieb Felix Nielsen: > Hi G?nther, > > Is that feature included in napp-it? If so where and if not how do I get it :) > > Thanks > Felix > > Btw. napp-it rocks :) > > Den 31/10/2013 kl. 19.03 skrev G?nther Alka : > >> I have added a physical slot detection that displays physical >> Slot, WWN and serials together with the option to switch on the red >> alert led on supported backplanes within napp-it with the help of >> sas2ircu (a LSI tool that displays slot and disk serial). >> >> >> On 30.10.2013 21:25, Chris Siebenmann wrote: >>> This is a long shot and I suspect that the answer is no, but: in >>> OmniOS, is it possible somehow to have disk device names for disks >>> behind LSI SAS controllers that are based on the physical slot ('phy') >>> that the disk is found in instead of the disk's reported WNN or serial >>> number? >>> >>> (I understand that this is only easy if there are no SAS expanders >>> involved, which is the situation that I care about.) >>> >>> I know that I can recover this information from prtconf -v with >>> appropriate mangling, but our contemplated environment would be much >>> more manageable if we could directly use physical slot based device >>> naming. >>> >>> Thanks in advance. I'll post a summary if there are any private >>> replies (for anything besides 'nope, can't do it'). >>> >>> - cks >>> _______________________________________________ >>> OmniOS-discuss mailing list >>> OmniOS-discuss 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: From mayuresh at kathe.in Thu Oct 31 22:13:25 2013 From: mayuresh at kathe.in (Mayuresh Kathe) Date: Thu, 31 Oct 2013 18:13:25 -0400 Subject: [OmniOS-discuss] java : feca beba : endian problem? In-Reply-To: References: <20131031175433.GA6982@wolfman.devio.us> Message-ID: <20131031221118.GA26743@wolfman.devio.us> i checked on openbsd running on x86-64, the header is still the same, "fecabeba". as per the material i've read on java, it should always be, "cafebabe". am i doing something wrong somewhere? On Thu, Oct 31, 2013 at 02:10:23PM -0400, Theo Schlossnagle wrote: > Class files are cross endian portable. the header is 0xbabecafe big > endian... od -x will print native endian... looks right to me. > > > On Thu, Oct 31, 2013 at 1:54 PM, Mayuresh Kathe wrote: > > > hello, i've been writing short java programs under > > omnios, and they work well, no issues with that. > > > > just did a "od -x .class" on one of my > > programs and found the following; > > > > 0000000 feca beba 0000 3200 2e00 000a 000b 0915 > > 0000020 1600 1700 0008 0a18 1900 1a00 000a 0016 > > 0000040 0a1b 1c00 1d00 0008 081e 1f00 000a 0019 > > 0000060 0720 2100 0007 0122 0600 693c 696e 3e74 > > . > > . > > . > > > > is that reference to "feca beba" due to endian > > issues? > > it should actually be "cafe babe". :) > > > > ~mayuresh > > > > _______________________________________________ > > 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