Re: HEADS UP: major CAM ATA MFC
Alexander Motin wrote: Eugene Grosbein wrote: Alexander Motin wrote: Feedbacks are welcome as always. Today's RELENG_8 build is broken (my /usr/src is symlink to /usr/local/src): Can you try to update your sources again? ahci driver in 8-STABLE and HEAD are identical now and building fine in both, I've checked it yesterday. I've updated again using cvsup.freebsd.org and now the problem has gone, world builds just fine. It seems my local mirror had wrong moment for update last night. Sorry for noise, I really should update again before posting. Thanks! Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0-RC3 USB lock up on mounting two partitions from one USB drive
When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On Tue, 17 Nov 2009 16:29:06 -0800 Freddie Cash fjwc...@gmail.com wrote about Support for SAS/SATA non-RAID adapters: FC Any recommendations on other SAS/SATA controllers to look at (just not FC anything with MegaRAID in the name)? I installed a Supermicro AOC-USASLP-L8i card here some days ago. Should be even cheaper than the ones you mentioned and comes with a LSI chip supported by mpt driver: m...@pci0:6:0:0:class=0x01 card=0xa68015d9 chip=0x00581000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'SAS 3000 series, 8-port with 1068E -StorPort' class = mass storage subclass = SCSI I only installed it last week and cannot comment much on performance and stability up to now. cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Invitation to connect on LinkedIn
LinkedIn Andrei Antoukh requested to add you as a connection on LinkedIn: -- Valeriy, I'd like to add you to my professional network on LinkedIn. - Andrei Accept invitation from Andrei Antoukh http://www.linkedin.com/e/2bA_QBNshSoW6_Mg2FRMfzNsaTwKa_DOn-2pAopq/blk/I34716907_4/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYQnPsMejoNdPgPiiYRdBASjRd5pyYSd3wUe30NdPwLrCBxbOYWrSlI/EML_comm_afe/ View invitation from Andrei Antoukh http://www.linkedin.com/e/2bA_QBNshSoW6_Mg2FRMfzNsaTwKa_DOn-2pAopq/blk/I34716907_4/d5YTc3AScjsQcQALqnpPbOYWrSlI/svi/ -- DID YOU KNOW you can showcase your professional knowledge on LinkedIn to receive job/consulting offers and enhance your professional reputation? Posting replies to questions on LinkedIn Answers puts you in front of the world's professional community. http://www.linkedin.com/e/abq/inv-24/ -- (c) 2009, LinkedIn Corporation ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
better driver for this marvell chip. If someone gets to port it to FreeBSD, the card may be pretty decent choice for those who have PCI-X slot on-board. I have PCI-X and just purchased an unbranded card based on the SiL3124 chipset, as I was only using SATA 1 before. I didn't expect much, but it's actually suprisingly fast. Certainly a lot better than I expected - I've only had it a week, but so far I would recommend it. Mind you, this is my first real forray onto the world of non-SCSI controllers so if I just bought a nightmare chipset with loads of known issues then please tell me :-) -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-stable@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On 18 Nov 2009, at 10:17, Gerrit Kühn wrote: Supermicro AOC-USASLP-L8i card All my childhood traumas magically went away when I bought this card. Recommended! Thomas___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On Wed, Nov 18, 2009 at 11:05:45AM +, Pete French wrote: better driver for this marvell chip. If someone gets to port it to FreeBSD, the card may be pretty decent choice for those who have PCI-X slot on-board. I have PCI-X and just purchased an unbranded card based on the SiL3124 chipset, as I was only using SATA 1 before. I didn't expect much, but it's actually suprisingly fast. Certainly a lot better than I expected - I've only had it a week, but so far I would recommend it. Mind you, this is my first real forray onto the world of non-SCSI controllers so if I just bought a nightmare chipset with loads of known issues then please tell me :-) I tend to avoid Silicon Image as a result of their 3112 snafu. I'm generally not that impressed by their 3114 and 3512 chips either, but the 3112 problem is severe. http://en.wikipedia.org/wiki/Silicon_Image_Inc.#Product_alerts The 3124 and later revisions are supposedly decent, but I've avoided them due to their history (I stick to Intel ICHx controllers + AHCI and don't bother with hardware RAID). Avoiding SIMG is difficult though, since they're used on most consumer and/or residential products, and are even more common when it comes to external hard drive enclosures (USB, Firewire, or otherwise) or similar devices. But it's the 3112 you have to watch out for. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
On Wed, Nov 18, 2009 at 12:13:32PM +0100, Hans Petter Selasky wrote: I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. The OP should be able to use smartmontools to obtain SMART stats from the SATA drive within the USB enclosure. The command will be somewhat funky, given that the drive is ATA but is mapped through CAM on FreeBSD and appears as a daX disk. I believe the following should work, but I have no way to test: smartctl --device=ata -a /dev/da0 You should check your console logs (dmesg) before and after running this command, as there may be sense key errors from CAM which can help determine if SMART is passed through or not. There's mention in the smartctl man page of a device type called sat which is an ATA-SCSI emulation layer, but I believe it's the Linux equivalent of our CAM. Recent (in the past ~24 hours) commits to the RELENG_8 branch might provide native capability for smartctl to work without the --type argument, since mav@ has been improving the CAM layer to work with ATA disks. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Jeremy Chadwick wrote: On Wed, Nov 18, 2009 at 12:13:32PM +0100, Hans Petter Selasky wrote: I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. The OP should be able to use smartmontools to obtain SMART stats from the SATA drive within the USB enclosure. The command will be somewhat funky, given that the drive is ATA but is mapped through CAM on FreeBSD and appears as a daX disk. I believe the following should work, but I have no way to test: smartctl --device=ata -a /dev/da0 You should check your console logs (dmesg) before and after running this command, as there may be sense key errors from CAM which can help determine if SMART is passed through or not. There's mention in the smartctl man page of a device type called sat which is an ATA-SCSI emulation layer, but I believe it's the Linux equivalent of our CAM. Recent (in the past ~24 hours) commits to the RELENG_8 branch might provide native capability for smartctl to work without the --type argument, since mav@ has been improving the CAM layer to work with ATA disks. Does not work for my external Seagate FreeAgent Go 500G USB2.0 drive %smartctl -a /dev/da0 smartctl version 5.38 [i386-portbld-freebsd8.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: Seagate FreeAgent GoVersion: 102D Device type: disk Local Time is: Wed Nov 18 21:22:01 2009 KRAT Device does not support SMART Error Counter logging not supported Device does not support Self Test logging %smartctl --device=ata /dev/da0 smartctl version 5.38 [i386-portbld-freebsd8.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. %smartctl --device=ata -T permissive /dev/da0 smartctl version 5.38 [i386-portbld-freebsd8.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: boot issues
On Wednesday 18 November 2009 2:19:45 am Randy Bush wrote: [ this happened a month ago and i backed off ] i386, 7.2-stable from last summer cvsupped releng_7 made and installed kernel buildworld boot -s installworld mergemaster reboot hung after beastie, just as it did the other month booted -s mount -2 / /etc/rc.d/hostid start /etc/rc.d/zfs start looked around and all seemed ok ^D came up ok and that is how it is running now but why will it boot through -s and not from beastie? Err, so what happens if you break into the boot loader prompt (option 6 IIRC) and then just type 'boot', how far does it get before it hangs? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On Tue, Nov 17, 2009 at 11:43 PM, Rink Springer r...@freebsd.org wrote: On Tue, Nov 17, 2009 at 08:38:21PM -0800, Freddie Cash wrote: I've also found a couple of Areca cards (PCI-X, non-RAID/PCIe RAID), and have heard good things about Areca support in FreeBSD. Any comments on their quality/performance/reliability? I have got an Areca ARC-1110 4x SATA2 PCI-X card in my server, and I'm quite impressed with the performance; these cards do very well in terms I/O operations per second and the driver has been rock solid for me. The only downside is that they are quite expensive (but well worth it, IMO) Compared to a 3Ware 9550SXU controller, these are cheap. The Areca is only $500 (open-box) or $700 (new) on newegg.ca. The 3Ware cards are over $1000, with the PCIe versions being over $1200 (which is what started me on this journey -- hardware budgets are getting smaller and smaller each year). -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Invitation to connect on LinkedIn
On Wed, Nov 18, 2009 at 01:07:46AM -0800, Andrei Antoukh wrote: LinkedIn Andrei Antoukh requested to add you as a connection on LinkedIn: -- Why isn't LinkedIn in FreeBSD.org's spam blocker? -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
2009/11/18 Gerrit Kühn ger...@pmp.uni-hannover.de: On Tue, 17 Nov 2009 16:29:06 -0800 Freddie Cash fjwc...@gmail.com wrote about Support for SAS/SATA non-RAID adapters: FC Any recommendations on other SAS/SATA controllers to look at (just not FC anything with MegaRAID in the name)? I installed a Supermicro AOC-USASLP-L8i card here some days ago. Should be even cheaper than the ones you mentioned and comes with a LSI chip supported by mpt driver: m...@pci0:6:0:0: class=0x01 card=0xa68015d9 chip=0x00581000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'SAS 3000 series, 8-port with 1068E -StorPort' class = mass storage subclass = SCSI I only installed it last week and cannot comment much on performance and stability up to now. These look nice, and are in the $200-300 CDN range. Have the same mini-SAS connectors as the 3Ware cards we use, so wouldn't have to re-cable the chassis. Are you using these as standard disk controllers, or are you using the RAID features (seems it supports RAID0 and RAID1 in hardware, RAID5 in software)? Reading through the manual right now, and it doesn't cover using the card in non-RAID modes. Wondering if the drives would show up as normal da0 da1 da2 etc. All of these (there's a couple variations on the card) appear to be PCIe, though, no PCI-X. We have 24 drive bays, and only 2 PCIe slots. Have 3 PCI-X slots, though, so would need at least 1 PCI-X controller. -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On Wed, 18 Nov 2009 08:56:14 -0800 Freddie Cash fjwc...@gmail.com wrote about Re: Support for SAS/SATA non-RAID adapters: FC I installed a Supermicro AOC-USASLP-L8i card here some days ago. FC Should be even cheaper than the ones you mentioned and comes with a FC LSI chip supported by mpt driver: FC m...@pci0:6:0:0: class=0x01 card=0xa68015d9 FC chip=0x00581000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: FC Symbios Logic, NCR)' device = 'SAS 3000 series, 8-port with FC 1068E -StorPort' class = mass storage FC subclass = SCSI FC I only installed it last week and cannot comment much on performance FC and stability up to now. FC These look nice, and are in the $200-300 CDN range. Have the same FC mini-SAS connectors as the 3Ware cards we use, so wouldn't have to FC re-cable the chassis. Hm, I don't know the recent exchange rate, but are you sure this is the same card? I paid something like 80,-€ (excl. VAT). FC Are you using these as standard disk controllers, or are you using the FC RAID features (seems it supports RAID0 and RAID1 in hardware, RAID5 in FC software)? Reading through the manual right now, and it doesn't cover FC using the card in non-RAID modes. Wondering if the drives would show FC up as normal da0 da1 da2 etc. I think my card does not have the raid features included, maybe that's why it was so cheap. The devices appear as normal scsi disks: dmesg: da0 at mpt0 bus 0 target 0 lun 0 da0: ATA WDC WD5001ABYS-0 1D01 Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) [...] cliff# camcontrol devlist ATA WDC WD5001ABYS-0 1D01at scbus0 target 0 lun 0 (da0,pass0) ATA WDC WD5001ABYS-0 1D01at scbus0 target 1 lun 0 (da1,pass1) ATA WDC WD5001ABYS-0 1D01at scbus0 target 2 lun 0 (da2,pass2) ATA WDC WD5001ABYS-0 1D01at scbus0 target 3 lun 0 (da3,pass3) ATA WDC WD5001ABYS-0 1D01at scbus0 target 4 lun 0 (da4,pass4) ATA WDC WD5001ABYS-0 1D01at scbus0 target 5 lun 0 (da5,pass5) ATA WDC WD5001ABYS-0 1D01at scbus0 target 6 lun 0 (da6,pass6) ATA WDC WD5001ABYS-0 1D01at scbus0 target 7 lun 0 (da7,pass7) FC All of these (there's a couple variations on the card) appear to be FC PCIe, though, no PCI-X. We have 24 drive bays, and only 2 PCIe slots. FC Have 3 PCI-X slots, though, so would need at least 1 PCI-X FC controller. I guess the version of the card I have here was actually intended to be used in some kind of special Supermirco-Extension Slot. However, it fits into a standard PCIe slot and works nicely there as far as I can tell. Do you have the opportunity of using a riser card that would give you one more slot? cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
Freddie Cash wrote: On Tue, Nov 17, 2009 at 11:43 PM, Rink Springer r...@freebsd.org wrote: On Tue, Nov 17, 2009 at 08:38:21PM -0800, Freddie Cash wrote: I've also found a couple of Areca cards (PCI-X, non-RAID/PCIe RAID), and have heard good things about Areca support in FreeBSD. Any comments on their quality/performance/reliability? I have got an Areca ARC-1110 4x SATA2 PCI-X card in my server, and I'm quite impressed with the performance; these cards do very well in terms I/O operations per second and the driver has been rock solid for me. The only downside is that they are quite expensive (but well worth it, IMO) Compared to a 3Ware 9550SXU controller, these are cheap. The Areca is only $500 (open-box) or $700 (new) on newegg.ca. The 3Ware cards are over $1000, with the PCIe versions being over $1200 (which is what started me on this journey -- hardware budgets are getting smaller and smaller each year). We've also tried the Areca cards with FreeBSD - the Areca ARC-1680IX-12-2G PCIe x8 card to be precise. It's a SAS/SATA RAID card. The performance was very impressive. MUCH better than the Dell PERC4/5/6s we were used to. The drivers also seemed to be rock solid (FreeBSD is even listed as a supported OS on the company's website). The feature-set of the card itself is also very rich... The one we tried had its own OOB management via serial port or dedicated 100mbps ethernet jack. It supports endless combinations of RAID arrays, volumes, and SMTP/SNMP alerts. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
2009/11/18 Gerrit Kühn ger...@pmp.uni-hannover.de: On Wed, 18 Nov 2009 08:56:14 -0800 Freddie Cash fjwc...@gmail.com wrote about Re: Support for SAS/SATA non-RAID adapters: FC I installed a Supermicro AOC-USASLP-L8i card here some days ago. FC Should be even cheaper than the ones you mentioned and comes with a FC LSI chip supported by mpt driver: FC m...@pci0:6:0:0: class=0x01 card=0xa68015d9 FC chip=0x00581000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: FC Symbios Logic, NCR)' device = 'SAS 3000 series, 8-port with FC 1068E -StorPort' class = mass storage FC subclass = SCSI FC I only installed it last week and cannot comment much on performance FC and stability up to now. FC These look nice, and are in the $200-300 CDN range. Have the same FC mini-SAS connectors as the 3Ware cards we use, so wouldn't have to FC re-cable the chassis. Hm, I don't know the recent exchange rate, but are you sure this is the same card? I paid something like 80,-€ (excl. VAT). Oops, you're right, was reading the model numbers wrong. The LSI1068-based one is only $129 CDN, the Intel IOP-based ones are $200-300 CDN. Last time I checked the Euro was in the $1.50-2.00 CDN range. FC Are you using these as standard disk controllers, or are you using the FC RAID features (seems it supports RAID0 and RAID1 in hardware, RAID5 in FC software)? Reading through the manual right now, and it doesn't cover FC using the card in non-RAID modes. Wondering if the drives would show FC up as normal da0 da1 da2 etc. I think my card does not have the raid features included, maybe that's why it was so cheap. The devices appear as normal scsi disks: dmesg: da0 at mpt0 bus 0 target 0 lun 0 da0: ATA WDC WD5001ABYS-0 1D01 Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) [...] Nice. Thanks for the output. FC All of these (there's a couple variations on the card) appear to be FC PCIe, though, no PCI-X. We have 24 drive bays, and only 2 PCIe slots. FC Have 3 PCI-X slots, though, so would need at least 1 PCI-X FC controller. I guess the version of the card I have here was actually intended to be used in some kind of special Supermirco-Extension Slot. However, it fits into a standard PCIe slot and works nicely there as far as I can tell. Do you have the opportunity of using a riser card that would give you one more slot? Urgh, I have yet to find a riser card that will plug into a Tyan motherboard and not cause issues. Due to all the issues we've had with riser cards in the past, we have sworn off all riser cards. For our 2U servers, we use low-profile cards to avoid risers. I'll keep looking for a PCI-X card. These look like they'll cover our PCIe needs. -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
Gerrit Kühn wrote: On Wed, 18 Nov 2009 08:56:14 -0800 Freddie Cash fjwc...@gmail.com wrote about Re: Support for SAS/SATA non-RAID adapters: FC I installed a Supermicro AOC-USASLP-L8i card here some days ago. FC Should be even cheaper than the ones you mentioned and comes with a FC LSI chip supported by mpt driver: I guess the version of the card I have here was actually intended to be used in some kind of special Supermirco-Extension Slot. However, it fits into a standard PCIe slot and works nicely there as far as I can tell. Do you have the opportunity of using a riser card that would give you one more slot? Those Supermicro UIO cards look like backwards PCIe cards. Do they come with other brackets for fitting into a PCIe slot, or did you have to go bracketless? The online manual at http://www.supermicro.com/manuals/other/AOC-USASLP-L8i.pdf didn't mention anything about brackets or how it'd work in PCIe slots. Barry ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
Freddie Cash wrote: On Tue, Nov 17, 2009 at 11:43 PM, Rink Springer r...@freebsd.org wrote: On Tue, Nov 17, 2009 at 08:38:21PM -0800, Freddie Cash wrote: I've also found a couple of Areca cards (PCI-X, non-RAID/PCIe RAID), and have heard good things about Areca support in FreeBSD. Any comments on their quality/performance/reliability? I have got an Areca ARC-1110 4x SATA2 PCI-X card in my server, and I'm quite impressed with the performance; these cards do very well in terms I/O operations per second and the driver has been rock solid for me. The only downside is that they are quite expensive (but well worth it, IMO) Compared to a 3Ware 9550SXU controller, these are cheap. The Areca is only $500 (open-box) or $700 (new) on newegg.ca. The 3Ware cards are over $1000, with the PCIe versions being over $1200 (which is what started me on this journey -- hardware budgets are getting smaller and smaller each year). The 3ware cards are not that expensive unless you need a truckload of ports. For the 9650SE on newegg.com; 2 port is 185 4 port is 324 8 port is 525 12 port is 669 Where are you getting the 1200 dollar price from? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On Wed, Nov 18, 2009 at 11:37:03AM -0600, Barry Pederson wrote: Gerrit Kühn wrote: On Wed, 18 Nov 2009 08:56:14 -0800 Freddie Cash fjwc...@gmail.com wrote about Re: Support for SAS/SATA non-RAID adapters: FC I installed a Supermicro AOC-USASLP-L8i card here some days ago. FC Should be even cheaper than the ones you mentioned and comes with a FC LSI chip supported by mpt driver: I guess the version of the card I have here was actually intended to be used in some kind of special Supermirco-Extension Slot. However, it fits into a standard PCIe slot and works nicely there as far as I can tell. Do you have the opportunity of using a riser card that would give you one more slot? Those Supermicro UIO cards look like backwards PCIe cards. Do they come with other brackets for fitting into a PCIe slot, or did you have to go bracketless? The online manual at http://www.supermicro.com/manuals/other/AOC-USASLP-L8i.pdf didn't mention anything about brackets or how it'd work in PCIe slots. Supermicro UIO slots will adapt to whatever adapter you stick in them which are labelled compatible with said motherboard. The UIO slot itself is proprietary, but provides pinout interfaces to support both PCIe 1x, 4x, and 8x, as well as PCI (32-bit and 64-bit), and PCI-X (presumably 100 and 133MHz). But ultimately it depends on what board offers what pinouts through the UIO slot. Rather than document it, here's how it works in the Real World(tm): - We need a PCIe x8 on our X7SBi for a low-profile RAID card - X7SBi motherboard has a UIO slot: http://www.supermicro.com/products/motherboard/Xeon3000/3210/X7SBA.cfm - UIO slot on this board supports one of the following, depending on which riser you buy: - (1) PCIe x8 - (1) PCI-X 133MHz (64-bit). - Scroll down to the bottom of the page and you'll find: - CSE-RR1U-ELi -- 1U PCI-E x8 Riser Card for X7SBi - Visit Supermicro's Accessories page, and select Riser Cards: http://www.supermicro.com/support/resources/Riser/riser.aspx - Search for CSE-RR1U-ELi, and you find: http://www.supermicro.com/a_images/products/Accessories/CSE-RR1U-ELi.jpg - Contact Supermicro distributor (whoever you got the server from, or you can contact Supermicro directly to help find a distributor for you) and get the CSE-RR1U-ELi. Some online retailers do sell these risers too. - Costs about US$11. - Buy it, install it, mount the card in it, enjoy. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On Wed, Nov 18, 2009 at 10:00:27AM -0800, Jeremy Chadwick wrote: On Wed, Nov 18, 2009 at 11:37:03AM -0600, Barry Pederson wrote: Gerrit Kühn wrote: On Wed, 18 Nov 2009 08:56:14 -0800 Freddie Cash fjwc...@gmail.com wrote about Re: Support for SAS/SATA non-RAID adapters: FC I installed a Supermicro AOC-USASLP-L8i card here some days ago. FC Should be even cheaper than the ones you mentioned and comes with a FC LSI chip supported by mpt driver: I guess the version of the card I have here was actually intended to be used in some kind of special Supermirco-Extension Slot. However, it fits into a standard PCIe slot and works nicely there as far as I can tell. Do you have the opportunity of using a riser card that would give you one more slot? Those Supermicro UIO cards look like backwards PCIe cards. Do they come with other brackets for fitting into a PCIe slot, or did you have to go bracketless? The online manual at http://www.supermicro.com/manuals/other/AOC-USASLP-L8i.pdf didn't mention anything about brackets or how it'd work in PCIe slots. Supermicro UIO slots will adapt to whatever adapter you stick in them which are labelled compatible with said motherboard. The UIO slot itself is proprietary, but provides pinout interfaces to support both PCIe 1x, 4x, and 8x, as well as PCI (32-bit and 64-bit), and PCI-X (presumably 100 and 133MHz). But ultimately it depends on what board offers what pinouts through the UIO slot. Rather than document it, here's how it works in the Real World(tm): - We need a PCIe x8 on our X7SBi for a low-profile RAID card - X7SBi motherboard has a UIO slot: http://www.supermicro.com/products/motherboard/Xeon3000/3210/X7SBA.cfm - UIO slot on this board supports one of the following, depending on which riser you buy: - (1) PCIe x8 - (1) PCI-X 133MHz (64-bit). - Scroll down to the bottom of the page and you'll find: - CSE-RR1U-ELi -- 1U PCI-E x8 Riser Card for X7SBi - Visit Supermicro's Accessories page, and select Riser Cards: http://www.supermicro.com/support/resources/Riser/riser.aspx - Search for CSE-RR1U-ELi, and you find: http://www.supermicro.com/a_images/products/Accessories/CSE-RR1U-ELi.jpg - Contact Supermicro distributor (whoever you got the server from, or you can contact Supermicro directly to help find a distributor for you) and get the CSE-RR1U-ELi. Some online retailers do sell these risers too. - Costs about US$11. - Buy it, install it, mount the card in it, enjoy. By the way, I'll add that the AOC-USASLP-L8i is **not** compatible with the UIO riser/adapter for the X7SBi. This should be apparent just from examining the location of the PCIe x8 slot on the RAID card vs. where the CSE-RR1U-ELi PCIe x8 slot is located. You'll find what boards the AOC-USASLP-L8i is compatible with, UIO riser-wise, here: http://www.supermicro.com/products/accessories/addon/AOC-USASLP-L8i.cfm So in general, make sure whatever Supermicro card (RAID, Ethernet, SAS, SCSI, whatever) you're going with is indeed compatible with whatever Supermicro board you stick it in. Best thing to do is contact Supermicro Technical Support and ask. Their TS folks are better than average; I can get full specifications for ICs out of them, while I've never been able to achieve this with Tyan. Rackable (who uses Tyan mainboards) might have better luck. :-) -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
libdispatch on 8-Stable or 9-Current
I've been trying to build the libdispatch port on FreeBSD 8-STABLE but not having much luck. I used the instructions here: http://wiki.freebsd.org/GCD They say to install 8.0-RC3 and then update the sources to FreeBSD 8-STABLE. I set my cvsup tag to: *default release=cvs tag=RELENG_8 and rebuilt the world but kern.osreldate didn't change. Its still 800107 which won't allow the port to build. Is there a different cvs tag I should be using or do I have to go to 9-CURRENT? Thanks, Tom___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Invitation to connect on LinkedIn
On 2009-Nov-18 10:13:17 -0600, David Kelly dke...@hiwaay.net wrote: On Wed, Nov 18, 2009 at 01:07:46AM -0800, Andrei Antoukh wrote: LinkedIn Andrei Antoukh requested to add you as a connection on LinkedIn: -- Why isn't LinkedIn in FreeBSD.org's spam blocker? I have raised this with postmaster@ and he is investigating how to block this spam. -- Peter Jeremy pgpnlACiig4DT.pgp Description: PGP signature
Re: Support for SAS/SATA non-RAID adapters
On Wed, Nov 18, 2009 at 10:10 AM, Jeremy Chadwick free...@jdc.parodius.com wrote: By the way, I'll add that the AOC-USASLP-L8i is **not** compatible with the UIO riser/adapter for the X7SBi. This should be apparent just from examining the location of the PCIe x8 slot on the RAID card vs. where the CSE-RR1U-ELi PCIe x8 slot is located. You'll find what boards the AOC-USASLP-L8i is compatible with, UIO riser-wise, here: http://www.supermicro.com/products/accessories/addon/AOC-USASLP-L8i.cfm So in general, make sure whatever Supermicro card (RAID, Ethernet, SAS, SCSI, whatever) you're going with is indeed compatible with whatever Supermicro board you stick it in. Best thing to do is contact Supermicro Technical Support and ask. Their TS folks are better than average; I can get full specifications for ICs out of them, while I've never been able to achieve this with Tyan. Rackable (who uses Tyan mainboards) might have better luck. :-) Ah, in that case, it's not a solution for us. We use Tyan motherboards for pretty much everything, and have never had any luck with any kind of riser card, whether it be in a standard PCI slot or a PCI-X slot. -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On Wed, Nov 18, 2009 at 9:51 AM, Brian Whalen br...@brianwhalen.net wrote: Freddie Cash wrote: On Tue, Nov 17, 2009 at 11:43 PM, Rink Springer r...@freebsd.org wrote: On Tue, Nov 17, 2009 at 08:38:21PM -0800, Freddie Cash wrote: I've also found a couple of Areca cards (PCI-X, non-RAID/PCIe RAID), and have heard good things about Areca support in FreeBSD. Any comments on their quality/performance/reliability? I have got an Areca ARC-1110 4x SATA2 PCI-X card in my server, and I'm quite impressed with the performance; these cards do very well in terms I/O operations per second and the driver has been rock solid for me. The only downside is that they are quite expensive (but well worth it, IMO) Compared to a 3Ware 9550SXU controller, these are cheap. The Areca is only $500 (open-box) or $700 (new) on newegg.ca. The 3Ware cards are over $1000, with the PCIe versions being over $1200 (which is what started me on this journey -- hardware budgets are getting smaller and smaller each year). The 3ware cards are not that expensive unless you need a truckload of ports. For the 9650SE on newegg.com; 2 port is 185 4 port is 324 8 port is 525 12 port is 669 Where are you getting the 1200 dollar price from? We deal in Canadian dollars. :) Our hardware purchaser spent several hours on the phone and web looking for a replacement 9650SE-12ML (12-port, multi-lane, PCIe). Every place she checked showed them as $1000-1200. We need the -12ML (or -16ML) for one server, as it's actually using the RAID features, and the controller in that server died (scorch marks on the heat sink). As that server was using RAID6, we couldn't replace it with any of the 9550s we have as spares. :( We have three servers using these cards. Only 1 is actually using the RAID features. The other two are ZFS storage servers. Going forward, we will be putting in more ZFS systems than non-ZFS systems, so we don't need as fancy of controller. Just lots of ports (or lots of cards, we have 3 PCI-X and 2 PCIe slots to work with). -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
Jeremy Chadwick wrote: The UIO slot itself is proprietary, but provides pinout interfaces to support both PCIe 1x, 4x, and 8x, as well as PCI (32-bit and 64-bit), and PCI-X (presumably 100 and 133MHz). But ultimately it depends on what board offers what pinouts through the UIO slot. Rather than document it, here's how it works in the Real World(tm): - We need a PCIe x8 on our X7SBi for a low-profile RAID card - X7SBi motherboard has a UIO slot: http://www.supermicro.com/products/motherboard/Xeon3000/3210/X7SBA.cfm - UIO slot on this board supports one of the following, depending on which riser you buy: - (1) PCIe x8 - (1) PCI-X 133MHz (64-bit). - Scroll down to the bottom of the page and you'll find: - CSE-RR1U-ELi -- 1U PCI-E x8 Riser Card for X7SBi - Visit Supermicro's Accessories page, and select Riser Cards: http://www.supermicro.com/support/resources/Riser/riser.aspx - Search for CSE-RR1U-ELi, and you find: http://www.supermicro.com/a_images/products/Accessories/CSE-RR1U-ELi.jpg - Contact Supermicro distributor (whoever you got the server from, or you can contact Supermicro directly to help find a distributor for you) and get the CSE-RR1U-ELi. Some online retailers do sell these risers too. - Costs about US$11. - Buy it, install it, mount the card in it, enjoy. By the way, I'll add that the AOC-USASLP-L8i is **not** compatible with the UIO riser/adapter for the X7SBi. This should be apparent just from examining the location of the PCIe x8 slot on the RAID card vs. where the CSE-RR1U-ELi PCIe x8 slot is located. You'll find what boards the AOC-USASLP-L8i is compatible with, UIO riser-wise, here: http://www.supermicro.com/products/accessories/addon/AOC-USASLP-L8i.cfm So in general, make sure whatever Supermicro card (RAID, Ethernet, SAS, SCSI, whatever) you're going with is indeed compatible with whatever Supermicro board you stick it in. Best thing to do is contact Supermicro Technical Support and ask. Their TS folks are better than average; I can get full specifications for ICs out of them, while I've never been able to achieve this with Tyan. Rackable (who uses Tyan mainboards) might have better luck. :-) Thanks for the info. I have no doubt a Supermicro HBA will work in a Supermicro motherboard and chassis given the correct Supermicro risers or other accessories. What I was questioning was where the OP said: it fits into a standard PCIe slot and works nicely there as far as I can tell - which to me sounds like you could use this HBA in a *NON-Supermicro* motherboard. I was just wondering if that was truly the case, given how in the photos it looks to be arranged physically backwards from a regular PCIe card, and given how you mention The UIO slot itself is proprietary. But some more digging on Google has turned up a few mentions along the lines of: This card plugs into a normal PCIe 8x slot but the metal mounting bracket bolted to the card is made for a UIO slot (which is why it's so cheap). All you have to do is remove the metal bracket and zip-tie the card to your case for mechanical support. Electrically it'll work fine in a PCIe x8 or x16 slot. If someone wanted to make PCIe compatible brackets for this affordable card, they'd probably sell a fair number to small shops or home users. Barry ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for SAS/SATA non-RAID adapters
On 11/17/2009 7:29 PM, Freddie Cash wrote: LSI SAS 3081E-R8-port SAS/SATA PCIe I've had excellent luck with LSI cards in a moderate usage home environment. I've had the 3041 and 3081 and never had any issues with either card. I've never really stress tested them for performance with anything other than doing a zpool scrub on them but they've handled everything I've tried to do just fine. Hot swap also works correctly. Jonathan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
It looks like a system issue since it also happens to the SATA drive. The USB drive seems having more difficulty. I will back up rest partitions, Then redo the slice and partition to see if problem goes away. If so, then 8.0-R has a backward compatibility issue on the partition table or format to older FreeBSD release. -Original Message- From: Hans Petter Selasky [mailto:hsela...@c2i.net] Sent: Wednesday, November 18, 2009 3:14 AM To: freebsd-...@freebsd.org Cc: Guojun Jin; freebsd-stable@freebsd.org; questi...@freebsd.org Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: Did newfs on those partition and made things worsen -- restore completely fails: (I had experienced another similar problem on an IDE, which works well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. Is something new in 8.0 making disk partition schema changed? g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 fopen: Device not configured cannot create save file ./restoresymtable for symbol table abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0xa, scs i status == 0x0 (da0:umass-sim0:0:0:0): removing device entry ugen1.2: DMI at usbus1 umass0: DMI Ultra HDD, class 0/0, rev 2.00/1.19, addr 2 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: DMI Ultra HDD 1.19 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) Device da0s3d went missing before all of the data could be written to it; expect data loss. 99 23:19 sysinstall 100 23:20 newfs /dev/da0s3d 101 23:20 newfs /dev/da0s3e 102 23:21 mount /dev/da0s3d /mnt 103 23:21 cd /mnt 104 23:21 dump -0f - /home | restore -rf - 105 23:27 history 15 -Original Message- From: Guojun Jin Sent: Tue 11/17/2009 11:05 PM To: freebsd-stable@freebsd.org Cc: questi...@freebsd.org; freebsd-...@freebsd.org Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing rm -rf * without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
bug with some em nics on RELENG_7
On two Intel chipset Supermicro boards (X8STi and X8STE-0) using the onboard em nics (dmesg info below), I seem to have run into an issue where if I boot the box up with the cables unplugged, I cannot get the NICS to properly work post boot up. This is quite repeatable for me. So at boot time, I have # ifconfig em5 em5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:d6:ef:13 inet 3.3.3.3 netmask 0xff00 broadcast 3.3.3.255 media: Ethernet autoselect status: no carrier I then ping something that would be across the wire while the nic is down. e.g. ping 3.3.3.1 I then plug in the cable so that the other side has 3.3.3.1 ifconfig shows all looks good # ifconfig em5 em5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:d6:ef:13 inet 3.3.3.3 netmask 0xff00 broadcast 3.3.3.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active I try and ping 3.3.3.1 which is on xover (via a switch shows the same behaviour), and no response to the pings BUT, I do see the MAC addr show up # ping -c 2 -S 3.3.3.3 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from 3.3.3.3: 56 data bytes --- 3.3.3.1 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss # arp -na ? (3.3.3.1) at 00:30:48:94:88:20 on em5 [ethernet] ? (3.3.3.3) at 00:30:48:d6:ef:13 on em5 permanent [ethernet] I can see its mac addr ?!? Furthermore, if I do # ifconfig em5 3.3.3.55/32 alias On the other side, I see 0(ich10)# tcpdump -nei igb0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on igb0, link-type EN10MB (Ethernet), capture size 96 bytes 16:16:03.380886 00:30:48:d6:ef:13 ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 3.3.3.55 tell 3.3.3.55, length 46 and I can ping if I specify the alias as the source IP # ping -S 3.3.3.55 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from 3.3.3.55: 56 data bytes 64 bytes from 3.3.3.1: icmp_seq=0 ttl=64 time=0.184 ms 64 bytes from 3.3.3.1: icmp_seq=1 ttl=64 time=0.051 ms 64 bytes from 3.3.3.1: icmp_seq=2 ttl=64 time=0.055 ms 16:17:01.603345 00:30:48:d6:ef:13 00:30:48:94:88:20, ethertype ARP (0x0806), length 60: Reply 3.3.3.55 is-at 00:30:48:d6:ef:13, length 46 16:17:01.603349 00:30:48:94:88:20 00:30:48:d6:ef:13, ethertype IPv4 (0x0800), length 98: 3.3.3.1 3.3.3.55: ICMP echo reply, id 7946, seq 0, length 64 16:17:02.603497 00:30:48:d6:ef:13 00:30:48:94:88:20, ethertype IPv4 (0x0800), length 98: 3.3.3.55 3.3.3.1: ICMP echo request, id 7946, seq 1, length 64 16:17:02.603502 00:30:48:94:88:20 00:30:48:d6:ef:13, ethertype IPv4 (0x0800), length 98: 3.3.3.1 3.3.3.55: ICMP echo reply, id 7946, seq 1, length 64 16:17:03.604510 00:30:48:d6:ef:13 00:30:48:94:88:20, ethertype IPv4 (0x0800), length 98: 3.3.3.55 3.3.3.1: ICMP echo request, id 7946, seq 2, length 64 16:17:03.604516 00:30:48:94:88:20 00:30:48:d6:ef:13, ethertype IPv4 (0x0800), length 98: 3.3.3.1 3.3.3.55: ICMP echo reply, id 7946, seq 2, length 64 but not using the initial IP addr 0[iolite3A]# ping -S 3.3.3.3 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from 3.3.3.3: 56 data bytes ^C --- 3.3.3.1 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss # Yet, # ping -S 3.3.3.3 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from 3.3.3.3: 56 data bytes ^C --- 3.3.3.1 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss # ping -S 3.3.3.4 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from 3.3.3.4: 56 data bytes 64 bytes from 3.3.3.1: icmp_seq=0 ttl=64 time=0.176 ms 64 bytes from 3.3.3.1: icmp_seq=1 ttl=64 time=0.050 ms ^C --- 3.3.3.1 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.050/0.113/0.176/0.063 ms Strange, eh ? e...@pci0:6:0:0: class=0x02 card=0x10d315d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled e...@pci0:7:0:0: class=0x02 card=0x10d315d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled em4: Intel(R) PRO/1000 Network Connection 6.9.6 port 0xdc00-0xdc1f mem 0xfaee-0xfaef,0xfaedc000-0xfaed irq 16 at device 0.0 on pci6 em4: Using MSIX
Re: Re: [solved] Re: Re: Re: diskless - NFS root mount problem
On 11/16/09, Mario Pavlov free...@abv.bg wrote: indeed you get bonus points if you firewall yourself :) and of course this is not the first time I do that so my score is pretty good however my favourite is to forget about net.inet.ip.forwarding when I upgrade routers with many clients :) Tim, thanks for your hints...but I don't understand this one: 2nd, you buildworld and installworld into the diskless root, but never use it. You're using disk space you can reclaim. how so I never use it and can reclaim diskspace ? The Monday's email you sent at 11:22 (by datestamp on gmail), you wrote: mkdir /storage0/diskless cd /usr/src export DESTDIR=/storage0/diskless make buildworld buildkernel installworld distribution installkernel --- You clearly 'make buildworld installworld' but your later exports have /storage0/diskless and /usr being exported. shouldn't it be either /storage0/diskless (as a root filesystem and everything underneath it) or if you want to unecessarily break it up, exporting /storage0/diskless/usr ? Understand? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: whats best pracfive for ZFS on a whole disc these days ?
On Sun, 15 Nov 2009, Daniel O'Connor wrote: There's no need to detach anything. I'll try it when I get home and see how it goes. How can I show what partition has what UUID? gpart list and gpart show do not say.. I suspect if I booted verbose glabel would say but that is a bit annoying :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: whats best pracfive for ZFS on a whole disc these days ?
On Wed, Nov 18, 2009 at 23:15, Daniel O'Connor docon...@gsoft.com.au wrote: On Sun, 15 Nov 2009, Daniel O'Connor wrote: There's no need to detach anything. I'll try it when I get home and see how it goes. How can I show what partition has what UUID? gpart list and gpart show do not say.. I suspect if I booted verbose glabel would say but that is a bit annoying :) % sysctl -b kern.geom.confdot | dot -Tpng foo.png % pkg_which /usr/local/bin/dot graphviz-2.24.0_1 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: libdispatch on 8-Stable or 9-Current
According to Tom Pusateri: and rebuilt the world but kern.osreldate didn't change. Its still 800107 which won't allow the port to build. Change the = into a in libdispatch/Makefile and it will happily build the port. All tests pass. I'm using a fairly recent clang snapshot for the blocks support. llvm-devel-2.7.r89141 (made with make BOOTSTRAP=yes makesum update) libdispatch-147 compiler-rt-0.r83568 FreeBSD ng.keltia.net 8.0-PRERELEASE FreeBSD #6 r199493M: Wed Nov 18 22:33:04 CET 2009 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: HEADS UP: major CAM ATA MFC
According to Alexander Motin:
Feedbacks are welcome as always.
Working fine from here, on a recent Dell T3500 with ICH8/ICH10 controllers
(ATA/AHCI).
Thanks a lot!
Disks were renamed from ad{4,6,8} into ada{0,1,2}. I'm using a full-GPT-ZFS
setup here. ZFS mounted all pools w/o any issue and seems to be using the
gptids instead of the /dev/adNp3 partitions. Swap is not on ZFS but I
added GPT labels with gpart and glabel added the /dev/gpt entries so swap
is fine too.
See below:
ahci0: Intel ICH10 AHCI SATA controller port
0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfedf mem
0xff97-0xff9707ff irq 20 at device 31.2 on pci0
ahci0: [ITHREAD]
ahci0: AHCI v1.20 with 6 3Gbps ports, Port Multiplier not supported
ahcich0: AHCI channel at channel 0 on ahci0
ahcich0: [ITHREAD]
ahcich1: AHCI channel at channel 1 on ahci0
ahcich1: [ITHREAD]
ahcich2: AHCI channel at channel 2 on ahci0
ahcich2: [ITHREAD]
ahcich3: AHCI channel at channel 3 on ahci0
ahcich3: [ITHREAD]
ahcich4: AHCI channel at channel 4 on ahci0
ahcich4: [ITHREAD]
ahcich5: AHCI channel at channel 5 on ahci0
ahcich5: [ITHREAD]
...
(aprobe0:ahcich0:0:0:0): SIGNATURE:
(aprobe1:ahcich1:0:0:0): SIGNATURE:
(aprobe2:ahcich2:0:0:0): SIGNATURE:
(aprobe3:ahcich3:0:0:0): SIGNATURE: eb14
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: ST3320418AS CC44 ATA/ATAPI-8 SATA 2.x device
ada0: 300.000MB/s transfers
ada0: Command Queueing enabled
ada0: 305245MB (625142448 512 byte sectors: 16H 63S/T 16383C)
cd0 at ahcich3 bus 0 scbus3 target 0 lun 0
cd0: PLDS DVD-ROM DH-16D5S VD15 Removable CD-ROM SCSI-0 device
cd0: 150.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present -
tray closed
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: ST3320418AS CC44 ATA/ATAPI-8 SATA 2.x device
ada1: 300.000MB/s transfers
ada1: Command Queueing enabled
ada1: 305245MB (625142448 512 byte sectors: 16H 63S/T 16383C)
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: ST3320418AS CC44 ATA/ATAPI-8 SATA 2.x device
ada2: 300.000MB/s transfers
ada2: Command Queueing enabled
ada2: 305245MB (625142448 512 byte sectors: 16H 63S/T 16383C)
411 [0:31] robe...@ng:~ swapinfo
Device 1K-blocks UsedAvail Capacity
/dev/gpt/swap041943040 4194304 0%
/dev/gpt/swap141943040 4194304 0%
/dev/gpt/swap241943040 4194304 0%
Total125829120 12582912 0%
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: HEADS UP: major CAM ATA MFC
According to Jeremy Chadwick: I didn't have this problem. System has AHCI in use, and the kernel is built to make use of modular atacore. Specifically: # Modular ATA device atacore # Core ATA functionality device ataisa # ISA bus support device atapci # PCI bus support; only generic chipset support device ataahci # AHCI SATA device ataintel# Intel Interesting. My own kernel config file has the following and ahci.ko is loaded by loader.conf. Do I need to change my config to match your own? ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bug with some em nics on RELENG_7
Hey Mike, Can you check if you see the same behavior on RELENG 8? There is a systemic problem having to do with when to enable interrupts that might be behind this. The em driver does not enable them until em_init_locked(), this is because until then its not ready to deal with a TX or RX interrupt. However, this means that a Link interrupt also will not be seen, BUT, and here is where it gets a bit funny, an call to check link happens in attach, it will be either true or false, AND, even if you remove or add a cable after that point, until interrupts are enabled the state will not change. In the days before MSIX one interrupt was for everything so it was impossible to change this without a radical rework to the driver design, but I suppose it would be possible with MSIX to selectively enable the link one earlier, I seem to recall discussions with our Linux crew that made me decide not to pursue that (its of limited value really). Not sure why this happens on Hartwell (82574) and not on 82571, that's an interesting bit, the 82574 is the ONLY interface in the em driver that has MSIX support, unfortunately its kinda hacked in, but it did not really fit into the igb driver either for various technical reasons. What if you boot up, then do NOT ping or anything until the interface is assigned an address (and so init is run), and the cable is plugged in. If that happens first does it work? Do let me know if you can check on 8, if not I can have my validation engineer try this. Best regards, Jack On Wed, Nov 18, 2009 at 1:30 PM, Mike Tancsa m...@sentex.net wrote: On two Intel chipset Supermicro boards (X8STi and X8STE-0) using the onboard em nics (dmesg info below), I seem to have run into an issue where if I boot the box up with the cables unplugged, I cannot get the NICS to properly work post boot up. This is quite repeatable for me. So at boot time, I have # ifconfig em5 em5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:d6:ef:13 inet 3.3.3.3 netmask 0xff00 broadcast 3.3.3.255 media: Ethernet autoselect status: no carrier I then ping something that would be across the wire while the nic is down. e.g. ping 3.3.3.1 I then plug in the cable so that the other side has 3.3.3.1 ifconfig shows all looks good # ifconfig em5 em5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:d6:ef:13 inet 3.3.3.3 netmask 0xff00 broadcast 3.3.3.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active I try and ping 3.3.3.1 which is on xover (via a switch shows the same behaviour), and no response to the pings BUT, I do see the MAC addr show up # ping -c 2 -S 3.3.3.3 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from 3.3.3.3: 56 data bytes --- 3.3.3.1 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss # arp -na ? (3.3.3.1) at 00:30:48:94:88:20 on em5 [ethernet] ? (3.3.3.3) at 00:30:48:d6:ef:13 on em5 permanent [ethernet] I can see its mac addr ?!? Furthermore, if I do # ifconfig em5 3.3.3.55/32 alias On the other side, I see 0(ich10)# tcpdump -nei igb0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on igb0, link-type EN10MB (Ethernet), capture size 96 bytes 16:16:03.380886 00:30:48:d6:ef:13 ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 3.3.3.55 tell 3.3.3.55, length 46 and I can ping if I specify the alias as the source IP # ping -S 3.3.3.55 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from 3.3.3.55: 56 data bytes 64 bytes from 3.3.3.1: icmp_seq=0 ttl=64 time=0.184 ms 64 bytes from 3.3.3.1: icmp_seq=1 ttl=64 time=0.051 ms 64 bytes from 3.3.3.1: icmp_seq=2 ttl=64 time=0.055 ms 16:17:01.603345 00:30:48:d6:ef:13 00:30:48:94:88:20, ethertype ARP (0x0806), length 60: Reply 3.3.3.55 is-at 00:30:48:d6:ef:13, length 46 16:17:01.603349 00:30:48:94:88:20 00:30:48:d6:ef:13, ethertype IPv4 (0x0800), length 98: 3.3.3.1 3.3.3.55: ICMP echo reply, id 7946, seq 0, length 64 16:17:02.603497 00:30:48:d6:ef:13 00:30:48:94:88:20, ethertype IPv4 (0x0800), length 98: 3.3.3.55 3.3.3.1: ICMP echo request, id 7946, seq 1, length 64 16:17:02.603502 00:30:48:94:88:20 00:30:48:d6:ef:13, ethertype IPv4 (0x0800), length 98: 3.3.3.1 3.3.3.55: ICMP echo reply, id 7946, seq 1, length 64 16:17:03.604510 00:30:48:d6:ef:13 00:30:48:94:88:20, ethertype IPv4 (0x0800), length 98: 3.3.3.55 3.3.3.1: ICMP echo request, id 7946, seq 2, length 64 16:17:03.604516 00:30:48:94:88:20 00:30:48:d6:ef:13, ethertype IPv4 (0x0800), length 98: 3.3.3.1 3.3.3.55: ICMP echo reply, id 7946, seq 2, length 64 but not using the initial IP addr 0[iolite3A]# ping -S 3.3.3.3 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from 3.3.3.3: 56 data
Re: whats best pracfive for ZFS on a whole disc these days ?
On Thu, 19 Nov 2009, Marius Nünnerich wrote: On Wed, Nov 18, 2009 at 23:15, Daniel O'Connor docon...@gsoft.com.au wrote: On Sun, 15 Nov 2009, Daniel O'Connor wrote: There's no need to detach anything. I'll try it when I get home and see how it goes. How can I show what partition has what UUID? gpart list and gpart show do not say.. I suspect if I booted verbose glabel would say but that is a bit annoying :) % sysctl -b kern.geom.confdot | dot -Tpng foo.png % pkg_which /usr/local/bin/dot graphviz-2.24.0_1 Ahah, of course, thanks. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: whats best pracfive for ZFS on a whole disc these days ?
On Sun, 15 Nov 2009, Daniel O'Connor wrote: There's no need to detach anything. I'll try it when I get home and see how it goes. Unfortunately I get.. [midget 11:20] ~ sudo zpool replace tank ad4p2 gptid/6866d8b0-a8ac-11de-8e07-00241dd192cc cannot use '/dev/gptid/6866d8b0-a8ac-11de-8e07-00241dd192cc': must be a GEOM provider or regular file [midget 11:20] ~ ll /dev/gptid/6866d8b0-a8ac-11de-8e07-00241dd192cc crw-r- 1 root operator0, 164 Oct 21 15:34 /dev/gptid/6866d8b0-a8ac-11de-8e07-00241dd192cc -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: bug with some em nics on RELENG_7
At 07:29 PM 11/18/2009, Jack Vogel wrote: Hey Mike, Can you check if you see the same behavior on RELENG 8? Hi Jack, Yes, I will reboot the hardware with a RELENG_8 image tomorrow to test Not sure why this happens on Hartwell (82574) and not on 82571, that's an interesting bit, the 82574 is the ONLY interface in the em driver that has MSIX support, unfortunately its kinda hacked in, but it did not really fit into the igb driver either for various technical reasons. Is this the FILTER vs ITHREAD ? Is there a way to force this chipset to use the same logic as 82571s ? # dmesg |grep ^em em0: Intel(R) PRO/1000 Network Connection 6.9.6 port 0xbc00-0xbc1f mem 0xface-0xfacf,0xfacc-0xfacd irq 16 at device 0.0 on pci1 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:78:e6:e0 em1: Intel(R) PRO/1000 Network Connection 6.9.6 port 0xb880-0xb89f mem 0xfac8-0xfac9,0xfac6-0xfac7 irq 17 at device 0.1 on pci1 em1: Using MSI interrupt em1: [FILTER] em1: Ethernet address: 00:15:17:78:e6:e1 em2: Intel(R) PRO/1000 Network Connection 6.9.6 port 0xcc00-0xcc1f mem 0xfade-0xfadf,0xfadc-0xfadd irq 16 at device 0.0 on pci3 em2: Using MSI interrupt em2: [FILTER] em2: Ethernet address: 00:15:17:cf:26:de em3: Intel(R) PRO/1000 Network Connection 6.9.6 port 0xc880-0xc89f mem 0xfad8-0xfad9,0xfad6-0xfad7 irq 17 at device 0.1 on pci3 em3: Using MSI interrupt em3: [FILTER] em3: Ethernet address: 00:15:17:cf:26:df em4: Intel(R) PRO/1000 Network Connection 6.9.6 port 0xdc00-0xdc1f mem 0xfaee-0xfaef,0xfaedc000-0xfaed irq 16 at device 0.0 on pci6 em4: Using MSIX interrupts em4: [ITHREAD] em4: [ITHREAD] em4: [ITHREAD] em4: Ethernet address: 00:30:48:d6:ef:12 em5: Intel(R) PRO/1000 Network Connection 6.9.6 port 0xec00-0xec1f mem 0xfafe-0xfaff,0xfafdc000-0xfafd irq 17 at device 0.0 on pci7 em5: Using MSIX interrupts em5: [ITHREAD] em5: [ITHREAD] em5: [ITHREAD] em5: Ethernet address: 00:30:48:d6:ef:13 What if you boot up, then do NOT ping or anything until the interface is assigned an address (and so init is run), and the cable is plugged in. If that happens first does it work? yes. If I have the cables plugged in and reboot the box, its ok. I am pretty sure all is ok if I boot it up, with no address assigned, plug the cables in, and then assign addr. I havent tested it out yet, but not sure how things play out when the ports are connected to a switch that is not in portfast mode, so the carrier does not always come up right away. The other thing I saw was that the NIC was getting stuck with the carrier showing up, even though cable was unplugged. However, I was not able to find the exact conditions this happened. Do let me know if you can check on 8, if not I can have my validation engineer try this. I will report back tomorrow. ---Mike Best regards, Jack On Wed, Nov 18, 2009 at 1:30 PM, Mike Tancsa mailto:m...@sentex.netm...@sentex.net wrote: On two Intel chipset Supermicro boards (X8STi and X8STE-0) using the onboard em nics (dmesg info below), I seem to have run into an issue where if I boot the box up with the cables unplugged, I cannot get the NICS to properly work post boot up. This is quite repeatable for me. So at boot time, I have # ifconfig em5 em5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:d6:ef:13 inet 3.3.3.3 netmask 0xff00 broadcast 3.3.3.255 media: Ethernet autoselect status: no carrier I then ping something that would be across the wire while the nic is down. e.g. ping 3.3.3.1 I then plug in the cable so that the other side has 3.3.3.1 ifconfig shows all looks good # ifconfig em5 em5: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:d6:ef:13 inet 3.3.3.3 netmask 0xff00 broadcast 3.3.3.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active I try and ping 3.3.3.1 which is on xover (via a switch shows the same behaviour), and no response to the pings BUT, I do see the MAC addr show up # ping -c 2 -S 3.3.3.3 3.3.3.1 PING 3.3.3.1 (3.3.3.1) from http://3.3.3.33.3.3.3: 56 data bytes --- 3.3.3.1 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss # arp -na ? (3.3.3.1) at 00:30:48:94:88:20 on em5 [ethernet] ? (3.3.3.3) at 00:30:48:d6:ef:13 on em5 permanent [ethernet] I can see its mac addr ?!? Furthermore, if I do # ifconfig em5 http://3.3.3.55/323.3.3.55/32 alias On the other side, I see 0(ich10)# tcpdump -nei igb0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on igb0, link-type EN10MB (Ethernet), capture size 96 bytes 16:16:03.380886 00:30:48:d6:ef:13
Re: HEADS UP: major CAM ATA MFC
Jeremy Chadwick wrote: I didn't have this problem. System has AHCI in use, and the kernel is built to make use of modular atacore. Specifically: # Modular ATA device atacore # Core ATA functionality device ataisa # ISA bus support device atapci # PCI bus support; only generic chipset support device ataahci # AHCI SATA device ataintel# Intel How should STABLE user (not tracking freebsd-current@) learn about CAM ATA configuration? There is ahci(4) manual page in 8.0-PRERELEASE but no ada(4) that is linked here. I've just tried Modular ATA configuration of Intel ICH7-based system plus device ahci minus all traditional ata(4) kernel configuration, the kernel builds fine but boot messages do not show any attempt to detect my SATA HDD, so root mount just fails (I use GEOM UFS labels in my /etc/fstab). Typing ? at mounroot prompt I see only daX devices standing for my USB cardreader and no device for HDD. It seems I miss ada(4) device and I cannot find it in 8.0 - not ada.ko nor device ada. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Re: Re: [solved] Re: Re: Re: diskless - NFS root mount problem
oh yes, I got what you meant now true, I used /usr from the server because I wanted to have all my ports available to the client. Is there a nice way to install ports only in the diskless distribution ? thank you. Regards Mario On 11/16/09, Mario Pavlov wrote: indeed you get bonus points if you firewall yourself :) and of course this is not the first time I do that so my score is pretty good however my favourite is to forget about net.inet.ip.forwarding when I upgrade routers with many clients :) Tim, thanks for your hints...but I don't understand this one: 2nd, you buildworld and installworld into the diskless root, but never use it. You're using disk space you can reclaim. how so I never use it and can reclaim diskspace ? The Monday's email you sent at 11:22 (by datestamp on gmail), you wrote: mkdir /storage0/diskless cd /usr/src export DESTDIR=/storage0/diskless make buildworld buildkernel installworld distribution installkernel --- You clearly 'make buildworld installworld' but your later exports have /storage0/diskless and /usr being exported. shouldn't it be either /storage0/diskless (as a root filesystem and everything underneath it) or if you want to unecessarily break it up, exporting /storage0/diskless/usr ? Understand? - Вижте водещите новини от Vesti.bg! http://www.vesti.bg ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: HEADS UP: major CAM ATA MFC
On Thu, Nov 19, 2009 at 10:18:32AM +0700, Eugene Grosbein wrote: Jeremy Chadwick wrote: I didn't have this problem. System has AHCI in use, and the kernel is built to make use of modular atacore. Specifically: # Modular ATA device atacore # Core ATA functionality device ataisa # ISA bus support device atapci # PCI bus support; only generic chipset support device ataahci # AHCI SATA device ataintel# Intel How should STABLE user (not tracking freebsd-current@) learn about CAM ATA configuration? There is ahci(4) manual page in 8.0-PRERELEASE but no ada(4) that is linked here. I don't know. I'm waiting for someone to actually write documentation on this. I keep seeing commits talking about ATA disks via CAM (e.g. SCSI emulation for ATA disks), but the only thing I'm aware of that exists is SCSI emulation for ATAPI devices. I've just tried Modular ATA configuration of Intel ICH7-based system plus device ahci minus all traditional ata(4) kernel configuration, the kernel builds fine but boot messages do not show any attempt to detect my SATA HDD, so root mount just fails (I use GEOM UFS labels in my /etc/fstab). Typing ? at mounroot prompt I see only daX devices standing for my USB cardreader and no device for HDD. This sounds like a different problem. You may want to talk to mav@ about this. It seems I miss ada(4) device and I cannot find it in 8.0 - not ada.ko nor device ada. Same. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: HEADS UP: major CAM ATA MFC
I don't know. I'm waiting for someone to actually write documentation on this. I keep seeing commits talking about ATA disks via CAM (e.g. SCSI emulation for ATA disks), but the only thing I'm aware of that exists is SCSI emulation for ATAPI devices. I've just tried Modular ATA configuration of Intel ICH7-based system plus device ahci minus all traditional ata(4) kernel configuration, the kernel builds fine but boot messages do not show any attempt to detect my SATA HDD, so root mount just fails (I use GEOM UFS labels in my /etc/fstab). Typing ? at mounroot prompt I see only daX devices standing for my USB cardreader and no device for HDD. This sounds like a different problem. You may want to talk to mav@ about this. It seems I miss ada(4) device and I cannot find it in 8.0 - not ada.ko nor device ada. Same. To enable ahci, put ahci_load=YES into loader.conf. Upon reboot, drives will be detected as adaX eg galacticdominator% dmesg |grep ada GEOM_STRIPE: Disk ada3 attached to stripe0. GEOM_STRIPE: Disk ada4 attached to stripe0. a...@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC amd64 ada0 at ahcich0 bus 0 target 0 lun 0 ada0: ST31000528AS CC37 ATA/ATAPI-8 SATA 2.x device ada0: 300.000MB/s transfers ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada0: Native Command Queueing enabled ada1 at ahcich1 bus 0 target 0 lun 0 ada1: ST3750330AS SD15 ATA/ATAPI-8 SATA 2.x device ada1: 300.000MB/s transfers ada1: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C) ada1: Native Command Queueing enabled ada2 at ahcich3 bus 0 target 0 lun 0 ada2: ST3500320AS AD14 ATA/ATAPI-8 SATA 2.x device ada2: 300.000MB/s transfers ada2: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada2: Native Command Queueing enabled ada3 at ahcich4 bus 0 target 0 lun 0 ada3: ST3500320AS AD14 ATA/ATAPI-8 SATA 2.x device ada3: 300.000MB/s transfers ada3: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada3: Native Command Queueing enabled ada4 at ahcich5 bus 0 target 0 lun 0 ada4: ST3750330AS SD15 ATA/ATAPI-8 SATA 2.x device ada4: 300.000MB/s transfers ada4: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C) ada4: Native Command Queueing enabled BIOS must be set to ahci controller mode, and obviously both disk and controller must support it. This works fine off a GENERIC. -- Adam Vande More ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: HEADS UP: major CAM ATA MFC
To enable ahci, put ahci_load=YES into loader.conf. Upon reboot, drives will be detected as adaX eg galacticdominator% dmesg |grep ada GEOM_STRIPE: Disk ada3 attached to stripe0. GEOM_STRIPE: Disk ada4 attached to stripe0. a...@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC amd64 ada0 at ahcich0 bus 0 target 0 lun 0 ada0: ST31000528AS CC37 ATA/ATAPI-8 SATA 2.x device ada0: 300.000MB/s transfers ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada0: Native Command Queueing enabled ada1 at ahcich1 bus 0 target 0 lun 0 ada1: ST3750330AS SD15 ATA/ATAPI-8 SATA 2.x device ada1: 300.000MB/s transfers ada1: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C) ada1: Native Command Queueing enabled ada2 at ahcich3 bus 0 target 0 lun 0 ada2: ST3500320AS AD14 ATA/ATAPI-8 SATA 2.x device ada2: 300.000MB/s transfers ada2: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada2: Native Command Queueing enabled ada3 at ahcich4 bus 0 target 0 lun 0 ada3: ST3500320AS AD14 ATA/ATAPI-8 SATA 2.x device ada3: 300.000MB/s transfers ada3: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada3: Native Command Queueing enabled ada4 at ahcich5 bus 0 target 0 lun 0 ada4: ST3750330AS SD15 ATA/ATAPI-8 SATA 2.x device ada4: 300.000MB/s transfers ada4: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C) ada4: Native Command Queueing enabled BIOS must be set to ahci controller mode, and obviously both disk and controller must support it. This works fine off a GENERIC. Also note this can change loader mappings, so be sure to edit fstab if necessary. -- Adam Vande More ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: HEADS UP: major CAM ATA MFC
On Thu, Nov 19, 2009 at 12:11:26AM -0600, Adam Vande More wrote: I don't know. I'm waiting for someone to actually write documentation on this. I keep seeing commits talking about ATA disks via CAM (e.g. SCSI emulation for ATA disks), but the only thing I'm aware of that exists is SCSI emulation for ATAPI devices. I've just tried Modular ATA configuration of Intel ICH7-based system plus device ahci minus all traditional ata(4) kernel configuration, the kernel builds fine but boot messages do not show any attempt to detect my SATA HDD, so root mount just fails (I use GEOM UFS labels in my /etc/fstab). Typing ? at mounroot prompt I see only daX devices standing for my USB cardreader and no device for HDD. This sounds like a different problem. You may want to talk to mav@ about this. It seems I miss ada(4) device and I cannot find it in 8.0 - not ada.ko nor device ada. Same. To enable ahci, put ahci_load=YES into loader.conf. Upon reboot, drives will be detected as adaX eg galacticdominator% dmesg |grep ada GEOM_STRIPE: Disk ada3 attached to stripe0. GEOM_STRIPE: Disk ada4 attached to stripe0. a...@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC amd64 ada0 at ahcich0 bus 0 target 0 lun 0 ada0: ST31000528AS CC37 ATA/ATAPI-8 SATA 2.x device ada0: 300.000MB/s transfers ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada0: Native Command Queueing enabled ada1 at ahcich1 bus 0 target 0 lun 0 ada1: ST3750330AS SD15 ATA/ATAPI-8 SATA 2.x device ada1: 300.000MB/s transfers ada1: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C) ada1: Native Command Queueing enabled ada2 at ahcich3 bus 0 target 0 lun 0 ada2: ST3500320AS AD14 ATA/ATAPI-8 SATA 2.x device ada2: 300.000MB/s transfers ada2: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada2: Native Command Queueing enabled ada3 at ahcich4 bus 0 target 0 lun 0 ada3: ST3500320AS AD14 ATA/ATAPI-8 SATA 2.x device ada3: 300.000MB/s transfers ada3: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada3: Native Command Queueing enabled ada4 at ahcich5 bus 0 target 0 lun 0 ada4: ST3750330AS SD15 ATA/ATAPI-8 SATA 2.x device ada4: 300.000MB/s transfers ada4: 715404MB (1465149168 512 byte sectors: 16H 63S/T 16383C) ada4: Native Command Queueing enabled BIOS must be set to ahci controller mode, and obviously both disk and controller must support it. This works fine off a GENERIC. AHCI in the BIOS is enabled, AHCI in FreeBSD is in use. Kernel configuration is below my .sig, ditto with dmesg. World sources are from ~45 minutes prior to kernel build date (2009/11/17 20:07 PST). FreeBSD icarus.home.lan 8.0-PRERELEASE FreeBSD 8.0-PRERELEASE #0: Tue Nov 17 20:07:21 PST 2009 r...@icarus.home.lan:/usr/obj/usr/src/sys/X7SBA_RELENG_8_amd64 amd64 Like I said, this whole thing needs to get documented. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | # # Kernel configuration for the following system: # # OS: RELENG_8 # MB: Supermicro X7SBA # arch: amd64 # cpu HAMMER ident GENERIC makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFSLOCKD# Network Lock Manager options NFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat (sgtty) options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK
