Re: [OmniOS-discuss] Intel X550 testers wanted
> On Jun 16, 2016, at 6:08 PM, Bob Friesenhahn > wrote: > > It is expected that after sufficient successful testing that OmniOS will put > the updated drivers in its various existing supported branches, or will we > have to wait until 'bloody' finally becomes the next stable? Once ixgbe passes review and testing, it will be made available on 014 (LTS) and 018 (Stable) This goes for the new i40e driver (for X/XL710 40Gb cards) as well. /dale signature.asc Description: Message signed with OpenPGP using GPGMail ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Intel X550 testers wanted
It is expected that after sufficient successful testing that OmniOS will put the updated drivers in its various existing supported branches, or will we have to wait until 'bloody' finally becomes the next stable? Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] New bloody update
Hello folks! As Dale hinted, there's a new update on the bloody pkg server: http://pkg.omniti.com/omnios/bloody/ with new bloody bits. "uname -v" will say "omnios-master-7397b49". Highlights with this update: - Intel i40e support, from Joyent. - Intel X550 support from OmniTI's own Dale Ghent. - pvscsi support from Nexenta. - Several small & medium size ZFS fixes from upstream/OpenZFS No release media have been cut for this update yet. But I wanted to get these new bits out, so I'm announcing now. Thanks, Dan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] OmniOS & Softlayer
Gea, Thanks for the FYI, I know all too well I should have LSI SAS HBAs but I’m trying to stay within the limits of what Softlayer has on the self. My current boxes at Softlayer I bought and shipped them the correct controllers. Anyways I’m going to try out the JBOD mode of the 9361 to start with. I’ve noticed Oracle uses 9361 with some of their storage units so there might be hope. Currently I’m waiting on Softlayer’s build team to get approval to rip out the SAS expander based backplane and put in a standard SAS one so I can have a dual controller setup. If the 9361 fails I’ll see about the motherboard SATA ports in AHCI mode, hopefully that’s not too strange of a cabling request for them. Any comments if I end with the SATA ports how well Intel S3700’s work on them? The drives they use are the good news in the setup. -Paul On Thu, 16 Jun 2016 08:34:56 +0200 Guenther Alka wrote: >The LSI megaRAID 9361 is a hardware raid controller - the wrong type for >ZFS. >You want a HBA controller best with a raidless IT firmware with an LSI >2008 or 3008 chipset >like the LSI 9207 or 9003 or Sata in AHCI mode. > >Your options: >- replace the 9361 with an HBA > >or >- use it as a bootdevice for ESXi and the local datastore >- pass-through Sata in AHCI mode (enable hotplug for Sata) > >or >- add an HBA > >Gea > > >Am 15.06.2016 um 19:44 schrieb Paul Bucher: >> I?m working on bringing up some new mission critical servers at hosting >> provider Softlayer and wondering if anyone out there also hosts at Softlayer >> using OmniOS and what they?ve used for disk HBA?s at Softlayer with >> OmniOS(just to make it more complicated I use napp-it all in one virtual >> machine setups). My understanding is the current Xeon v3 servers Softlayer >> is using LSI megaRAID 9361 cards in them and I?ve been unable to find much >> about running ZFS on the newer megaraid cards and I really don?t want to do >> some RAID 0 type of setup that I?ve used in the past. Softlayer is using >> Supermicro X10DRU-i+ MBs that have a bunch of SATA ports on them hung off >> the C612 chipset, I?m temped to tell them to use those ports, but I?d like >> to hear someone else?s experience with these since I now OmniOS doesn?t >> always play well with more modern kit. >> >> So far I?ve had great success with all in one setups in the past on >> Softlayers older generation of servers, but I?ve had to ship to Softlayer >> and convenience them to install the standard LSI HBA SAS controllers for me >> which has the downside that if a box goes down they can?t just spin me up a >> newer server in an hour or so since it requires me to buy and ship them a >> new disk controller. >> >> -Paul >> ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Intel X550 testers wanted
All; below is a mail I sent today to the developers@illumos list, submitting my ixgbe patch for review. It adds Intel X550 support. While the coding parts may not be of interest, please skip down to the "What's needed to help" section and, if you can afford some resources and time, follow the instructions on installing a new ixgbe driver to test with. I'm interested in those with ANY model of card supported by ixgbe, especially if you have one of those old 82598 cards, as it was the one part I could not get ahold of to test with (it's the original ixgbe card and fairly dated now) I'll welcome feedback either in this thread or directly to myself. /dale == The following webrev serves to introduce Intel X550 (including X552 and X557) support to ixgbe(7D) http://elemental.org/webrevs/x550-final/ One may find it in git patch format here: http://elemental.org/webrevs/0001-6064-ixgbe-needs-X550-support.patch New adapters supported (and tested) with this patch: * X550-T2 - PCIe add-on card supporting speeds of 10Gb, 1Gb, 100Mb baseT, as well as 2.5Gb and 5.0Gb NBASE-T (Intel’s pre-802.3bz feature) * X550EM - Xeon-D SoC embedded X550 MAC, utilizing one of two models of external PHYs: X552 (for SFP+) and X557 (10Gb, 1Gb baseT) Existing adapters tested with this patch: * X540-T1 * 82599 SFP (aka X520) Patch Description == At a high level, there were two intertwined goals with this patch: 1) To introduce support for the Intel X550 family of adapters. 2) To bring the illumos version of the Intel Common Code (ICC) up to date after ~4 years of deltas accumulating between it and FreeBSD (our source for the ICC) As worked progressed, it became clear that simply adding case statements for the new hardware and a few changes to accommodate adjustments in ICC APIs were not going to be sufficient, and several specific areas required heavy re-working to not only support X550, but also maintain expected behavior with existing adapters. Among these areas of heavy focus are: * Rewrite of autonegotiation management and its interfacing with GLD * RSS (Receive-Side Scaling) overhaul to account for differences between new and legacy adapters * Basic adapter initialization This patch also piggy-backs on Robert’s recent commit which relocated the ixgbe ICC files to their own directory, allowing us to cleanly exempt them from the prying eyes of lint(1). The updated ICC source files are very lint-noisy now, to such an extent that it would be beyond reasonable effort to add and maintain local corrections. I would like the thank and acknowledge Robert Mustacchi and Dan McDonald for their patient guidance and encouragement throughout this project. What’s needed to help test Since this patch is fairly wide-reaching, touching all previously supported adapters as well as the new ones, my hope is that enough interested parties here can assist in vetting it. These adapters include: 82598 - Important, as this is the one part I do not have 82599 (X520) X540 X550 (and X550EM on Xeon-D SoC systems) To encourage testing, I am providing updated ixgbe packages for OmniOS r151014, r15108, and Bloody. Robert Mustacchi has kindly assembled SmartOS images containing this new ixgbe driver code as well. OmniOS users: OmniOS Bloody users need only to utter 'pkg update' to upgrade their Bloody systems to the latest bits, which include this new ixgbe driver code. For users of OmniOS r151014 or r151018, package archive download and installation instructions may be found here: http://omnios.omniti.com/media/x550/INSTALL.txt SmartOS users: - SmartOS users can download the following images: SmartOS ISO: https://us-east.manta.joyent.com/rmustacc/public/preview/x550/platform-20160616T055400Z.iso SmartOS USB: https://us-east.manta.joyent.com/rmustacc/public/preview/x550/platform-20160616T055400Z.usb.bz2 SmartOS Raw Platform: https://us-east.manta.joyent.com/rmustacc/public/preview/x550/platform-20160616T055400Z.tgz But wait! There’s more (work)! === During the course of this work, it became apparent that a few additional areas deserve some attention, but are areas which are more suitable as follow-ups to this initial support patch. Among these areas are: * Interrupt handler task queue overhaul to convert them to taskq_dispatch_ent * SFP setup and interrupt handling, with further refinements to autonegotiation logic to accommodate multispeed fiber correctly * Additional interrupt handlers for currently unclaimed types - 82599 (and newer) thermal sensor alarms and uncorrectable ECC events I will be filing bugs for these follow-ups once they can be fully (and properly) characterized. signature.asc Description: Message signed with OpenPGP using GPGMail ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omn
[OmniOS-discuss] Scrub leaves pool in wiered state with all devices in "repairing" ?
Howdy! I started a scrub on a zfs pool and it appears to be stuck in some wierd state. Details below... Ideas on the problem or how to proceed??? Thanx - steve Server is a DELL R710 OmniOS v11 r151014 SAS controller is a LSI 9201. Here is output from lsiutils Main menu, select an option: [1-99 or e/p/w or 0 to quit] 69 Seg/Bus/Dev/FunBoard Name Board Assembly Board Tracer 0 5 0 0 SAS9201-16e H3-25379-01D SV04414910 ** Here is a zpool status ** pool: dfs1_data31 state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: scrub in progress since Thu Jun 16 10:25:17 2016 81.3G scanned out of 16.9T at 5.65M/s, (scan is slow, no estimated time) 3.33G repaired, 0.47% done config: NAME STATE READ WRITE CKSUM dfs1_data31 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 c0t5000C5008D634F3Bd0s0 ONLINE 9 0 0 (repairing) c0t5000C5008D632173d0s0 ONLINE 18 0 0 (repairing) c0t5000C5008D64A043d0s0 ONLINE 8 0 0 (repairing) c0t5000C5008D6450FFd0s0 ONLINE 10 0 0 (repairing) c0t5000C5008D62EEFBd0s0 ONLINE 18 0 0 (repairing) spares c7t5000CCA03B699D71d0s0AVAIL errors: No known data errors * Here are log entries... *** kern.warning<4>: Jun 16 14:40:30 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:30 dfs102 #011mptsas_handle_event_sync: event 0xf, IOCStatus=0x8000, IOCLogInfc kern.warning<4>: Jun 16 14:40:30 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:30 dfs102 #011mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x3112010c kern.info<6>: Jun 16 14:40:30 dfs102 genunix: [ID 365881 kern.info] /pci@0,0/pci8086,3410@9/pci1000,30d0@0 (: kern.info<6>: Jun 16 14:40:30 dfs102 #011Log info 0x3112010c received for target 154 w5000c5008d62eef9. kern.info<6>: Jun 16 14:40:30 dfs102 #011scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event_sync: event 0xf, IOCStatus=0x8000, IOCLogInfc kern.info<6>: Jun 16 14:40:31 dfs102 genunix: [ID 365881 kern.info] /pci@0,0/pci8086,3410@9/pci1000,30d0@0 (: kern.info<6>: Jun 16 14:40:31 dfs102 #011Log info 0x3112010c received for target 156 w5000c5008d64a041. kern.info<6>: Jun 16 14:40:31 dfs102 #011scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x3112010c kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event_sync: event 0xf, IOCStatus=0x8000, IOCLogInfc kern.info<6>: Jun 16 14:40:31 dfs102 genunix: [ID 365881 kern.info] /pci@0,0/pci8086,3410@9/pci1000,30d0@0 (: kern.info<6>: Jun 16 14:40:31 dfs102 #011Log info 0x3112010c received for target 153 w5000c5008d634f39. kern.info<6>: Jun 16 14:40:31 dfs102 #011scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x3112010c kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event_sync: event 0xf, IOCStatus=0x8000, IOCLogInfc kern.info<6>: Jun 16 14:40:37 dfs102 genunix: [ID 365881 kern.info] /pci@0,0/pci8086,3410@9/pci1000,30d0@0 (: kern.info<6>: Jun 16 14:40:37 dfs102 #011Log info 0x3112010c received for target 154 w5000c5008d62eef9. kern.info<6>: Jun 16 14:40:37 dfs102 #011scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event: IOCStatus=0x8000, IOCLogInfo=0x3112010c kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/p: kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event_sync: event 0xf, IOCStatus=0x8000, IOCLogInfc kern.w
Re: [OmniOS-discuss] Can't get omnios installer to boot under Xen4.4
Am 16.06.16 um 16:41 schrieb Dan McDonald: Our AWS images have something called PVgrub, and you may need that. I don't construct our AWS images, so I don't have immediate answers for you. Our EC2 AMI wiki may be instructive: https://omnios.omniti.com/wiki.php/Ec2Ami Dan Ahh… that looks interesting… thanks for pointing me to that. I'm sure that this will help. Thanks, Stephan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Can't get omnios installer to boot under Xen4.4
Our AWS images have something called PVgrub, and you may need that. I don't construct our AWS images, so I don't have immediate answers for you. Our EC2 AMI wiki may be instructive: https://omnios.omniti.com/wiki.php/Ec2Ami Dan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Can't get omnios installer to boot under Xen4.4
Hi all, I am trying to get OmniOS to run as a guest under Xen4.4. The issue I have, is that the installer kernel seems to boot, but then it just sits there doing actually nothing. I have tried a couple of releases r016 to bloody, but none will advance more than that stage. I have also tried HVM and HVMPV, but that didn't make a change as well. Anyone there, who has successfully done that? Is there some magic I can add to the vm.cfg file to get the installer running? I can successfully run Solaris11 as a guest, but not OmniOS… and I do want OmniOS, that's for sure. ;) Any hints, suggestions are much appreciated. Thanks, Stephan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
