From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 26 07:14:57 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DCE11065671 for ; Sun, 26 Oct 2008 07:14:57 +0000 (UTC) (envelope-from spork@bway.net) Received: from xena.bway.net (xena.bway.net [216.220.96.26]) by mx1.freebsd.org (Postfix) with ESMTP id BFAE78FC14 for ; Sun, 26 Oct 2008 07:14:56 +0000 (UTC) (envelope-from spork@bway.net) Received: (qmail 84710 invoked by uid 0); 26 Oct 2008 06:48:16 -0000 Received: from unknown (HELO toasty.nat.fasttrackmonkey.com) (spork@96.57.102.250) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 26 Oct 2008 06:48:16 -0000 Date: Sun, 26 Oct 2008 02:48:16 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@toasty.nat.fasttrackmonkey.com To: freebsd-hardware@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 07:14:57 -0000 Hello all, I have two questions regarding hardware support for two servers. One is an older Supermicro with a X5DPR-iG2+ mainboard, the other is a suggestion for a brand new box that is well-supported... Both boxes will be in a co-lo, so stuff needs to not be "quirky". First the old box. I need an SATA controller, non-RAID. I'll be using gmirror. I have PCI-X slots, so I'd like to go with a PCI-X controller. There seem to be very few out there, and this one keeps popping up everywhere: http://www.newegg.com/Product/Product.aspx?Item=N82E16816124014 The comments there mention the chip is a Silicon Image 3124, but I don't know if I can trust a random NewEgg user. Can anyone confirm that controller as working and free of quirks? Are there other cards I should be looking at? Next, I'm looking for a basic 1U server for light webhosting. Reliability and compatibility are the two main concerns. I'm very happy with 3Ware RAID cards, so I will likely add that in myself. The server would optimally already have a hot swap SATA backplane and 4 drive bays. I'm open to the semi-barebones route like the Supermicro servers as well as major vendors like Dell and HP. Having some type of IP-KVM-like functionality as an option would also be nice, but I'll settle for a serial console. I'd like to keep this under $2K. Both servers will be running FreeBSD 7.1 (if it's out in time). Thanks, Charles From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 26 12:50:18 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E56111065684 for ; Sun, 26 Oct 2008 12:50:18 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id C8FE88FC13 for ; Sun, 26 Oct 2008 12:50:18 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by QMTA03.emeryville.ca.mail.comcast.net with comcast id XPrx1a00L0vp7WLA3QqJXW; Sun, 26 Oct 2008 12:50:18 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA05.emeryville.ca.mail.comcast.net with comcast id XQqH1a0022P6wsM8RQqHck; Sun, 26 Oct 2008 12:50:18 +0000 X-Authority-Analysis: v=1.0 c=1 a=Ou8-nDE8AAAA:8 a=WQALGF90AAAA:8 a=NMgbMNkgAAAA:8 a=RzwWTIVYAAAA:8 a=nxlI2F2nAAAA:8 a=HqhU5Q3nAAAA:8 a=QycZ5dHgAAAA:8 a=3l0DIMQr0BUNupLDAOYA:9 a=Ml7-OakL__uDJ_86OmgA:7 a=ghofpDRZaHQiCBLuGfoe19IlMNUA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 276B1C9419; Sun, 26 Oct 2008 05:50:17 -0700 (PDT) Date: Sun, 26 Oct 2008 05:50:17 -0700 From: Jeremy Chadwick To: Charles Sprickman Message-ID: <20081026125017.GA88016@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 12:50:19 -0000 On Sun, Oct 26, 2008 at 02:48:16AM -0400, Charles Sprickman wrote: > Hello all, > > I have two questions regarding hardware support for two servers. One is > an older Supermicro with a X5DPR-iG2+ mainboard, the other is a > suggestion for a brand new box that is well-supported... Both boxes will > be in a co-lo, so stuff needs to not be "quirky". > > First the old box. I need an SATA controller, non-RAID. I'll be using > gmirror. I have PCI-X slots, so I'd like to go with a PCI-X controller. > There seem to be very few out there, and this one keeps popping up > everywhere: > > http://www.newegg.com/Product/Product.aspx?Item=N82E16816124014 > > The comments there mention the chip is a Silicon Image 3124, but I don't > know if I can trust a random NewEgg user. That card does in fact use a Silicon Image chip -- I've confirmed by looking at the PCB itself (you can see the Silicon Image logo printed on it), and by looking at the Windows drivers: http://www.adeltek.com/Product%20Manual/PCI%20IO%20CONTROLLER/SD-PCXSA2-2E2R.jpg http://www.adeltek.com/Product%20Driver/PCI-X%20controller/sd-pcxsa2-2e2r.zip Stay away from this card. > Can anyone confirm that controller as working and free of quirks? > Are there other cards I should be looking at? I was hoping the X5DPR-iG2+ would have a UIO slot, but it doesn't. Too old I guess. PCI-X is also slowly getting phased out too, so it's becoming harder to find native PCI-X cards. These are cards I can recommend for your situation. Yes, they do RAID, they all support JBOD; just plug the disks in and go. http://www.highpoint-tech.com/USA/series_2000.htm HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) http://www.areca.com.tw/products/pcix.htm Areca ARC-1110 (arcmsr(4) driver) Areca ARC-1120 (arcmsr(4) driver) Areca ARC-1130 (arcmsr(4) driver) Areca ARC-1160 (arcmsr(4) driver) Areca ARC-1130ML (arcmsr(4) driver) Areca ARC-1160ML (arcmsr(4) driver) The FreeBSD community members who have Areca cards have been thrilled with them, and *do* use the native RAID features reliably. Other cards which might work, but there's no confirmation of it, so I have to assume they aren't supported (in the case of the SX4300, I even see a mail dated January 2007 from someone asking for support for the card): Promise FastTrak SX4300 Promise FastTrak SX8300 Promise SuperTrak EX8300 I'm glad you have good experiences with 3Ware, but as for me, I'm too wary of their stuff based on a history of firmware bugs/issues. It's purely a personal decision of mine, so I don't "slam" 3Ware at all. > Next, I'm looking for a basic 1U server for light webhosting. > Reliability and compatibility are the two main concerns. I'm very happy > with 3Ware RAID cards, so I will likely add that in myself. The server > would optimally already have a hot swap SATA backplane and 4 drive bays. > I'm open to the semi-barebones route like the Supermicro servers as well > as major vendors like Dell and HP. Having some type of IP-KVM-like > functionality as an option would also be nice, but I'll settle for a > serial console. I'd like to keep this under $2K. There's a bunch of Supermicro systems which meet your needs. The first four are very new, and use the Intel X48 chipset. I don't know of any FreeBSD people using the X7SBU board, but I'm sure there are some. http://www.supermicro.com/products/system/1U/ Supermicro SuperServer 5015B-URB (~US$975) Supermicro SuperServer 5015B-NTRB (~US$975) Supermicro SuperServer 5015B-UB (~US$785) Supermicro SuperServer 5015B-NTB (~US$785) Supermicro SuperServer 5015B-MTB (~US$655) bsdhwmon(8) supports the 5015B-MTB (X7SBi), but doesn't support the others (X7SBU). If someone out there has an X7SBU, please get in touch with me so I can add support for it! Specifically with regards to the 5015B-MTB: note no floppy drive. Supermicro replaced it with a front-panel USB/COM port thingus, which can be removed and replaced with a floppy drive (purchased from a distributor). I believe the front is COM2, while the rear is COM1. "Why do I care about floppy drives?" I don't usually... except some Supermicro boards have compatibility problems with certain brand/model/revisions of USB flash drives. You can read about my experience (and my interaction with engineering) on my blog: http://koitsu.wordpress.com/2008/04/05/supermicro-pdsmi-bios-bugs/ http://koitsu.wordpress.com/2008/04/26/supermicro-pdsmi-bios-bugs-part-2/ http://koitsu.wordpress.com/2008/07/10/supermicro-pdsmi-bios-bugs-finale/ Regarding KVM-over-IP: the Supermicro boards support an IPMI card add-on which does this, but I **highly** recommend avoiding it. I know guys over at Yahoo who complain constantly about these cards being flaky (mostly card firmware bugs), people on the mailing lists have stated this, and folks on #bsdports as well. Go with serial if possible. But if you do have to get the IPMI card, buy one which has a dedicated NIC; DO NOT buy one which "piggybacks" on top of an on-board NIC, it will only cause you problems. If you really want a KVM-over-IP solution, consider a KVM-over-IP device like ones from Aten; they'll work with anything. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 26 19:30:13 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D15B81065671 for ; Sun, 26 Oct 2008 19:30:13 +0000 (UTC) (envelope-from spork@bway.net) Received: from xena.bway.net (xena.bway.net [216.220.96.26]) by mx1.freebsd.org (Postfix) with ESMTP id 736AA8FC12 for ; Sun, 26 Oct 2008 19:30:13 +0000 (UTC) (envelope-from spork@bway.net) Received: (qmail 92603 invoked by uid 0); 26 Oct 2008 19:30:12 -0000 Received: from unknown (HELO toasty.nat.fasttrackmonkey.com) (spork@96.57.102.250) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 26 Oct 2008 19:30:12 -0000 Date: Sun, 26 Oct 2008 15:30:11 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@toasty.nat.fasttrackmonkey.com To: Jeremy Chadwick In-Reply-To: <20081026125017.GA88016@icarus.home.lan> Message-ID: References: <20081026125017.GA88016@icarus.home.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 19:30:13 -0000 On Sun, 26 Oct 2008, Jeremy Chadwick wrote: > On Sun, Oct 26, 2008 at 02:48:16AM -0400, Charles Sprickman wrote: >> Hello all, >> >> I have two questions regarding hardware support for two servers. One is >> an older Supermicro with a X5DPR-iG2+ mainboard, the other is a >> suggestion for a brand new box that is well-supported... Both boxes will >> be in a co-lo, so stuff needs to not be "quirky". >> >> First the old box. I need an SATA controller, non-RAID. I'll be using >> gmirror. I have PCI-X slots, so I'd like to go with a PCI-X controller. >> There seem to be very few out there, and this one keeps popping up >> everywhere: >> >> http://www.newegg.com/Product/Product.aspx?Item=N82E16816124014 >> >> The comments there mention the chip is a Silicon Image 3124, but I don't >> know if I can trust a random NewEgg user. > > That card does in fact use a Silicon Image chip -- I've confirmed by > looking at the PCB itself (you can see the Silicon Image logo printed on > it), and by looking at the Windows drivers: > > http://www.adeltek.com/Product%20Manual/PCI%20IO%20CONTROLLER/SD-PCXSA2-2E2R.jpg > http://www.adeltek.com/Product%20Driver/PCI-X%20controller/sd-pcxsa2-2e2r.zip > > Stay away from this card. Will do. Google was very unhelpful with finding info on Silicon Image and FreeBSD, so I thank you for that. >> Can anyone confirm that controller as working and free of quirks? >> Are there other cards I should be looking at? > > I was hoping the X5DPR-iG2+ would have a UIO slot, but it doesn't. Too > old I guess. PCI-X is also slowly getting phased out too, so it's > becoming harder to find native PCI-X cards. > > These are cards I can recommend for your situation. Yes, they do RAID, > they all support JBOD; just plug the disks in and go. > > http://www.highpoint-tech.com/USA/series_2000.htm > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) Ouch. I was thinking more along the lines of a dead-simple SATA card in the under $50 range. I'm not up at all on PCI-X stuff, but I assume I can go with a normal PCI card, right? Or 64-bit PCI (or is that PCI-X)? What kind of performance hit would I have going from a PCI-X card to something else, and if I remove the PCI-X restriction, is there another recommended card? > http://www.areca.com.tw/products/pcix.htm > Areca ARC-1110 (arcmsr(4) driver) > Areca ARC-1120 (arcmsr(4) driver) > Areca ARC-1130 (arcmsr(4) driver) > Areca ARC-1160 (arcmsr(4) driver) > Areca ARC-1130ML (arcmsr(4) driver) > Areca ARC-1160ML (arcmsr(4) driver) > > The FreeBSD community members who have Areca cards have been thrilled > with them, and *do* use the native RAID features reliably. I looked at those last time I was shopping. The only thing that really bugged me about them was the fan on the card. I know that sounds silly, but when you're spending 4 figures and a $3 fan is what's keeping the card from frying, and you can't monitor that fan... I just didn't like that. I really like the 9550SX. I abused the hell out of it while I had the server at home. Unclean shutdowns during drive rebuilds, shutdowns while growing an array, all sorts of "OMG! Don't do that!" scenarios and I could not break it. My expectations were low though, as my previous experience was with Adaptec SCSI RAID controllers. >> Next, I'm looking for a basic 1U server for light webhosting. >> Reliability and compatibility are the two main concerns. I'm very happy >> with 3Ware RAID cards, so I will likely add that in myself. The server >> would optimally already have a hot swap SATA backplane and 4 drive bays. >> I'm open to the semi-barebones route like the Supermicro servers as well >> as major vendors like Dell and HP. Having some type of IP-KVM-like >> functionality as an option would also be nice, but I'll settle for a >> serial console. I'd like to keep this under $2K. > > There's a bunch of Supermicro systems which meet your needs. The first > four are very new, and use the Intel X48 chipset. I don't know of any > FreeBSD people using the X7SBU board, but I'm sure there are some. > > http://www.supermicro.com/products/system/1U/ > Supermicro SuperServer 5015B-URB (~US$975) > Supermicro SuperServer 5015B-NTRB (~US$975) > Supermicro SuperServer 5015B-UB (~US$785) > Supermicro SuperServer 5015B-NTB (~US$785) > Supermicro SuperServer 5015B-MTB (~US$655) Thanks for the lineup, I'll check those out. > Regarding KVM-over-IP: the Supermicro boards support an IPMI card add-on > which does this, but I **highly** recommend avoiding it. I know guys > over at Yahoo who complain constantly about these cards being flaky > (mostly card firmware bugs), people on the mailing lists have stated > this, and folks on #bsdports as well. Go with serial if possible. But > if you do have to get the IPMI card, buy one which has a dedicated NIC; > DO NOT buy one which "piggybacks" on top of an on-board NIC, it will > only cause you problems. We have one Supermicro at a client site with the IPMI card. A total waste of money. It was/is flakey as hell and not something we rely on at all. I'd never even look at IPMI again. > If you really want a KVM-over-IP solution, consider a KVM-over-IP device > like ones from Aten; they'll work with anything. I'm a bit intrigued by the Dell and HP add-in cards that are NOT IPMI, but do offer a full remote console. The cost appears to be about the same as an IPMI card. I've never bought either brand before though, and I have no idea how well supported these things are under FreeBSD (especially their own branded RAID controllers). Dell PowerEdge R200 (upgrade CPU to C2D or Xeon, add RAID, add DRAC card) - around $1500 http://configure.us.dell.com/dellstore/config.aspx?oc=becwuk1&c=us&l=en&s=bsd&cs=04&kc=category~rack_optimized The DRAC card, which has it's own ethernet port and supports booting from an ISO, etc.: http://accessories.us.dell.com/sna/products/Networking_Communication/productdetail.aspx?c=us&l=en&s=bsd&cs=04&sku=313-2822 On the HP side, the DL160 looks interesting as well. Like the Dell, info on the RAID controllers is pretty slim. Here's their "lights out" management option: http://h30094.www3.hp.com/product.asp?sku=3778577 Apparently it's already on the server, and you license advanced features. Probably a shared NIC situation... Any opinions on this mess are welcome... Thanks, Charles > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 26 20:49:37 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FD3F1065671 for ; Sun, 26 Oct 2008 20:49:37 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by mx1.freebsd.org (Postfix) with ESMTP id 0BAF18FC28 for ; Sun, 26 Oct 2008 20:49:36 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by QMTA02.emeryville.ca.mail.comcast.net with comcast id XYh71a0010b6N64A2Ypciy; Sun, 26 Oct 2008 20:49:36 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA03.emeryville.ca.mail.comcast.net with comcast id XYpb1a0042P6wsM8PYpbu9; Sun, 26 Oct 2008 20:49:35 +0000 X-Authority-Analysis: v=1.0 c=1 a=NMgbMNkgAAAA:8 a=RzwWTIVYAAAA:8 a=iLNU1ar6AAAA:8 a=cH6R9-kdAAAA:8 a=QycZ5dHgAAAA:8 a=v6c4UUzHkwm2t02kLHIA:9 a=F_66DtAPzBqvvrx_jYYA:7 a=02yFB6DFJ25-kolLTtUXxAN7lFMA:4 a=pgSDvz2WSYwA:10 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 05F42C941E; Sun, 26 Oct 2008 13:49:35 -0700 (PDT) Date: Sun, 26 Oct 2008 13:49:35 -0700 From: Jeremy Chadwick To: Charles Sprickman Message-ID: <20081026204935.GA2429@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 20:49:37 -0000 On Sun, Oct 26, 2008 at 03:30:11PM -0400, Charles Sprickman wrote: > On Sun, 26 Oct 2008, Jeremy Chadwick wrote: >> I was hoping the X5DPR-iG2+ would have a UIO slot, but it doesn't. Too >> old I guess. PCI-X is also slowly getting phased out too, so it's >> becoming harder to find native PCI-X cards. >> >> These are cards I can recommend for your situation. Yes, they do RAID, >> they all support JBOD; just plug the disks in and go. >> >> http://www.highpoint-tech.com/USA/series_2000.htm >> HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) >> HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) >> HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) >> HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) > > Ouch. I was thinking more along the lines of a dead-simple SATA card in > the under $50 range. I'm not up at all on PCI-X stuff, but I assume I > can go with a normal PCI card, right? Or 64-bit PCI (or is that PCI-X)? > What kind of performance hit would I have going from a PCI-X card to > something else, and if I remove the PCI-X restriction, is there another > recommended card? Any PCI 2.x or 3.x revision card should work fine in a PCI-X slot. Of course, the card will only run at 33MHz 32-bit (vs. 133MHz 64-bit, which is what native PCI-X is), but it'll still work. Most PCI cards are 32-bit 33MHz, but a 64-bit 33MHz PCI card should also work. The only PCI 1.x cards will probably fry your motherboard; they use a 5V bus, not a 3.3V bus. :-) This doesn't apply to your situation, but it's good knowledge for others who are reading: You can also use a PCI-X card in a PCI slot -- some of the connector pins will "hang off" the end of the slot without worry -- but ONLY IF the PCI-X card specifically states it works in 32-bit 33MHz mode. The specsheet/manual will state something like this; it if doesn't, don't risk it. >> http://www.areca.com.tw/products/pcix.htm >> Areca ARC-1110 (arcmsr(4) driver) >> Areca ARC-1120 (arcmsr(4) driver) >> Areca ARC-1130 (arcmsr(4) driver) >> Areca ARC-1160 (arcmsr(4) driver) >> Areca ARC-1130ML (arcmsr(4) driver) >> Areca ARC-1160ML (arcmsr(4) driver) >> >> The FreeBSD community members who have Areca cards have been thrilled >> with them, and *do* use the native RAID features reliably. > > I looked at those last time I was shopping. The only thing that really > bugged me about them was the fan on the card. I know that sounds silly, > but when you're spending 4 figures and a $3 fan is what's keeping the > card from frying, and you can't monitor that fan... I just didn't like > that. Regarding the fan -- the card has RPM monitoring of the on-board fan, and it's reported inside of the card BIOS, as well as the CLI utilities. Also, the user manual states the following: ========= Included in the product box is a field replaceable passive heatsink to be used only if there is enough airflow to adequately cool the passive heatsink. The "Controller Fan Detection" function is available in the version 1.36 date: 2005-05-19 and later for preventing the Buzzer warning. When using the passive heatsink, disable the "Controller Fan Detection" function through this McBIOS RAID manager setting. The following screen shot shows how to change the McBIOS RAID manager setting to disable the beeper function. (This function is not available in the web browser setting.) ========= I believe this means, assuming you set up monitoring of the card properly, you can monitor fan RPMs, and also get an alert if the fan dies (presumably RPM == 0, or possibly RPM < 250). There's an audible buzzer (see above) which also gets emit if the fan dies. Finally, tihe Areca CLI utilities are FreeBSD-native and do not require Linux emulation. I refuse to buy any card or software which requires such -- absolutely preposterous in this day and age. (I'm looking at you, Brother (printer manufacturer)) > We have one Supermicro at a client site with the IPMI card. A total > waste of money. It was/is flakey as hell and not something we rely on at > all. I'd never even look at IPMI again. IPMI -- great in concept, *horribly* implemented because there's really no "standard" to how all these vendors do it. >> If you really want a KVM-over-IP solution, consider a KVM-over-IP device >> like ones from Aten; they'll work with anything. In reply to my own comment, there's something I should mention about KVM-over-IP switches: "virtual media" support. They all require a USB connection between the KVM-over-IP switch and the host system. That made me pretty much ignore "virtual media" with such switches, but all the rest of the features are useful. Also, there's a huge problem with KVM-over-IP that isn't immediately thought of until one is actually in the situation (and I've witnessed this twice in private mails when helping other FreeBSD users): KVM-over-IP switches remove your ability to copy/paste data from the VGA console into, say, an Email. If you're needing to debug something in a bootloader or in the kernel and it requires more than a page of output, you're kinda screwed (what're you going to do, take 50 photos with a digital camera as fast as the screen scrolls?). Just something to keep in mind for those who might be considering this route. > I'm a bit intrigued by the Dell and HP add-in cards that are NOT IPMI, > but do offer a full remote console. The cost appears to be about the > same as an IPMI card. I've never bought either brand before though, and > I have no idea how well supported these things are under FreeBSD > (especially their own branded RAID controllers). > > Dell PowerEdge R200 (upgrade CPU to C2D or Xeon, add RAID, add DRAC card) > - around $1500 > http://configure.us.dell.com/dellstore/config.aspx?oc=becwuk1&c=us&l=en&s=bsd&cs=04&kc=category~rack_optimized > > The DRAC card, which has it's own ethernet port and supports booting from > an ISO, etc.: > > http://accessories.us.dell.com/sna/products/Networking_Communication/productdetail.aspx?c=us&l=en&s=bsd&cs=04&sku=313-2822 > > On the HP side, the DL160 looks interesting as well. Like the Dell, info > on the RAID controllers is pretty slim. Here's their "lights out" > management option: > > http://h30094.www3.hp.com/product.asp?sku=3778577 > > Apparently it's already on the server, and you license advanced features. > Probably a shared NIC situation... iLO/iLO2 = Integrated Lights-Out (v2), which means the remote management chip is on-board, rather than requiring purchase of an add-in card. LOM/LOM2 are terms for the older systems which require the actual external card. The best remote management I've ever seen has been on HP/Compaq Proliant systems with iLO/LOM/LOM2. Downright one of the most useful features I've ever seen. It was a total trip seeing an ex-roommate of mine sit in our living room with his Windows laptop, installing Red Hat onto a server in Australia, using the Red Hat CD in his laptop, while having pure control over the system even before it boots. That is *absolutely* how it should be done. Of course, the "virtual media" feature of the iLO often requires a license of some kind, which costs $$$. Regarding shared NIC on iLO: absolutely not. HP/Compaq knows better than this. All the iLO stuff has a pure dedicated NIC. See "Rear panel components" in the service guide manual, note item #11: http://Fbizsupport.austin.hp.com/bc/docs/support/SupportManual/c01555951%2Fc01555951.pdf On the other hand, IMHO, HP/Compaq hardware is *incredibly* overpriced for no justified reason. And if I remember right, you're forced to buy all of your H/W from them (hard disks, cards, RAM, whatever). The iLO is one thing which is truly remarkable about their hardware. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 26 20:52:29 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 309E41065670 for ; Sun, 26 Oct 2008 20:52:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by mx1.freebsd.org (Postfix) with ESMTP id 12F2F8FC08 for ; Sun, 26 Oct 2008 20:52:28 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by QMTA04.emeryville.ca.mail.comcast.net with comcast id XQkU1a00217UAYkA4YsUdo; Sun, 26 Oct 2008 20:52:28 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA13.emeryville.ca.mail.comcast.net with comcast id XYsR1a00C2P6wsM8ZYsRn8; Sun, 26 Oct 2008 20:52:26 +0000 X-Authority-Analysis: v=1.0 c=1 a=cH6R9-kdAAAA:8 a=QycZ5dHgAAAA:8 a=1JZGt49aCsuxapgoLuoA:9 a=gqjdjplGUUvqs9ygUjaxH2-Wh7gA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 7852AC9419; Sun, 26 Oct 2008 13:52:25 -0700 (PDT) Date: Sun, 26 Oct 2008 13:52:25 -0700 From: Jeremy Chadwick To: Charles Sprickman Message-ID: <20081026205225.GA3719@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <20081026204935.GA2429@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081026204935.GA2429@icarus.home.lan> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 20:52:29 -0000 On Sun, Oct 26, 2008 at 01:49:35PM -0700, Jeremy Chadwick wrote: > http://Fbizsupport.austin.hp.com/bc/docs/support/SupportManual/c01555951%2Fc01555951.pdf I typo'd this while removing the URL entity encoding variables. God I hate it when people write CGIs which blindly rewrite all characters rather than just the ones covered by the RFC... http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01555951/c01555951.pdf -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 26 22:22:23 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2DDA106566C; Sun, 26 Oct 2008 22:22:23 +0000 (UTC) (envelope-from louie@transsys.com) Received: from ringworld.transsys.com (ringworld.transsys.com [144.202.0.15]) by mx1.freebsd.org (Postfix) with ESMTP id 975F98FC17; Sun, 26 Oct 2008 22:22:23 +0000 (UTC) (envelope-from louie@transsys.com) Received: from PM-G5.transsys.com (c-69-141-158-166.hsd1.nj.comcast.net [69.141.158.166]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: louie) by ringworld.transsys.com (Postfix) with ESMTP id 5A5775C55; Sun, 26 Oct 2008 17:58:08 -0400 (EDT) Message-Id: <53B2E924-A690-4DAE-B937-076B1DA89F8E@transsys.com> From: Louis Mamakos To: Jeremy Chadwick In-Reply-To: <20081026204935.GA2429@icarus.home.lan> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Sun, 26 Oct 2008 17:58:07 -0400 References: <20081026125017.GA88016@icarus.home.lan> <20081026204935.GA2429@icarus.home.lan> X-Mailer: Apple Mail (2.929.2) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 22:22:23 -0000 On Oct 26, 2008, at 4:49 PM, Jeremy Chadwick wrote: > On Sun, Oct 26, 2008 at 03:30:11PM -0400, Charles Sprickman wrote: >> On Sun, 26 Oct 2008, Jeremy Chadwick wrote: >> >> Ouch. I was thinking more along the lines of a dead-simple SATA >> card in >> the under $50 range. I'm not up at all on PCI-X stuff, but I >> assume I >> can go with a normal PCI card, right? Or 64-bit PCI (or is that >> PCI-X)? >> What kind of performance hit would I have going from a PCI-X card to >> something else, and if I remove the PCI-X restriction, is there >> another >> recommended card? > > Any PCI 2.x or 3.x revision card should work fine in a PCI-X slot. Of > course, the card will only run at 33MHz 32-bit (vs. 133MHz 64-bit, > which is > what native PCI-X is), but it'll still work. Most PCI cards are 32- > bit > 33MHz, but a 64-bit 33MHz PCI card should also work. > > The only PCI 1.x cards will probably fry your motherboard; they use > a 5V > bus, not a 3.3V bus. :-) This has been a concern of mine. I just bought a Dell Poweredge 2650 off of eBay, and was going to outfit it with a USB2/Firewire PCI card so I can attach some cheap bulk storage to it for backup purposes. The Dell has PCI-X slots; backwards compatible with PCI, right? Try to find a USB PCI board that doesn't require a 5V capable PCI slot.. I haven't been able to; of course it's pretty obvious in that the USB host is supposed to supply 5V power to the peripherals.. D'oh! Oh well. You'll have to try extra hard to fry your machine with the wrong flavor card as the PC card connectors are keyed differently, and unless you try Really Hard or try to plug it in backwards, it just won't fit. louie From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 26 22:43:03 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65C611065683 for ; Sun, 26 Oct 2008 22:43:03 +0000 (UTC) (envelope-from groot@kde.org) Received: from poster.science.ru.nl (poster.science.ru.nl [131.174.30.28]) by mx1.freebsd.org (Postfix) with ESMTP id E86BD8FC0A for ; Sun, 26 Oct 2008 22:43:02 +0000 (UTC) (envelope-from groot@kde.org) Received: from smeltpunt.science.ru.nl (smeltpunt.science.ru.nl [131.174.16.145]) by poster.science.ru.nl (8.13.7/5.28) with ESMTP id m9QMQUE4014309 for ; Sun, 26 Oct 2008 23:26:30 +0100 (MET) Received: from bacon.localnet ([81.69.166.221]) (authen=adridg) by smeltpunt.science.ru.nl (8.13.7/5.28) with ESMTP id m9QMQP4C008185 for ; Sun, 26 Oct 2008 23:26:26 +0100 (MET) From: Adriaan de Groot Organization: KDE e.V. To: freebsd-hardware@freebsd.org Date: Sun, 26 Oct 2008 23:25:45 +0100 User-Agent: KMail/1.10.0 (KDE/4.1.0; ; ) References: <20081026204935.GA2429@icarus.home.lan> In-Reply-To: <20081026204935.GA2429@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200810262325.45865.groot@kde.org> X-Spam-Score: -0.362 () AWL,BAYES_50,RDNS_NONE X-Scanned-By: MIMEDefang 2.63 on 131.174.16.145 Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 22:43:03 -0000 On Sunday 26 October 2008 21:49:35 Jeremy Chadwick wrote: > > Ouch. =A0I was thinking more along the lines of a dead-simple SATA card= in > > =A0 the under $50 range. =A0I'm not up at all on PCI-X stuff, but I ass= ume I > > can go with a normal PCI card, right? =A0Or 64-bit PCI (or is that PCI-= X)? > > What kind of performance hit would I have going from a PCI-X card to > > something else, and if I remove the PCI-X restriction, is there another > > recommended card? In the "cheap and it seems functional in my 4-drive GEOM mirror setup" --=20 software raid, so easy to migrate, there's SiI3124-based cards. Addonics ma= kes=20 a 4-port PCI-X card which I ran in a 32-bit PCI slot for a while. Note that= =20 these don't do any kind of HW raid, so it might not be applicable at all (I= =20 haven't read this entire thread). There's also a 2-port 3132 based PCIe x1 card and a 4-port PCIe x4 card (I= =20 suppose that's 3124 again, but don't know). It's all the same architectural= ly,=20 and supported by ata(4). [ade] From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 26 23:31:22 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 414C3106566C for ; Sun, 26 Oct 2008 23:31:22 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by mx1.freebsd.org (Postfix) with ESMTP id 20D008FC19 for ; Sun, 26 Oct 2008 23:31:21 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by QMTA04.emeryville.ca.mail.comcast.net with comcast id XYN21a0011HpZEsA4bXMNk; Sun, 26 Oct 2008 23:31:21 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA14.emeryville.ca.mail.comcast.net with comcast id XbXL1a00L2P6wsM8abXMWK; Sun, 26 Oct 2008 23:31:21 +0000 X-Authority-Analysis: v=1.0 c=1 a=8pif782wAAAA:8 a=iLNU1ar6AAAA:8 a=pjdaNNIBAAAA:8 a=QycZ5dHgAAAA:8 a=x_0BXkGkrDjYVzsEahgA:9 a=oSNBRW9n5CipFkna_p0A:7 a=BET1rdtd09ktS785hhx09FetYoAA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 8296EC9419; Sun, 26 Oct 2008 16:31:20 -0700 (PDT) Date: Sun, 26 Oct 2008 16:31:20 -0700 From: Jeremy Chadwick To: Louis Mamakos Message-ID: <20081026233120.GA5517@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <20081026204935.GA2429@icarus.home.lan> <53B2E924-A690-4DAE-B937-076B1DA89F8E@transsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53B2E924-A690-4DAE-B937-076B1DA89F8E@transsys.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 23:31:22 -0000 On Sun, Oct 26, 2008 at 05:58:07PM -0400, Louis Mamakos wrote: > On Oct 26, 2008, at 4:49 PM, Jeremy Chadwick wrote: > >> On Sun, Oct 26, 2008 at 03:30:11PM -0400, Charles Sprickman wrote: >>> On Sun, 26 Oct 2008, Jeremy Chadwick wrote: >>> >>> Ouch. I was thinking more along the lines of a dead-simple SATA >>> card in >>> the under $50 range. I'm not up at all on PCI-X stuff, but I assume >>> I >>> can go with a normal PCI card, right? Or 64-bit PCI (or is that >>> PCI-X)? >>> What kind of performance hit would I have going from a PCI-X card to >>> something else, and if I remove the PCI-X restriction, is there >>> another >>> recommended card? >> >> Any PCI 2.x or 3.x revision card should work fine in a PCI-X slot. Of >> course, the card will only run at 33MHz 32-bit (vs. 133MHz 64-bit, >> which is >> what native PCI-X is), but it'll still work. Most PCI cards are 32- >> bit >> 33MHz, but a 64-bit 33MHz PCI card should also work. >> >> The only PCI 1.x cards will probably fry your motherboard; they use a >> 5V >> bus, not a 3.3V bus. :-) > > > This has been a concern of mine. I just bought a Dell Poweredge 2650 > off of eBay, and was going to outfit it with a USB2/Firewire PCI card > so I can attach some cheap bulk storage to it for backup purposes. The > Dell has PCI-X slots; backwards compatible with PCI, right? Try to > find a USB PCI board that doesn't require a 5V capable PCI slot.. > > I haven't been able to; of course it's pretty obvious in that the USB > host is supposed to supply 5V power to the peripherals.. D'oh! Oh well. Why do you think think the voltage provided on the USB bus is directly proportional to the voltage provided across the PCI bus? A PCI 3.3V expansion card (for USB ports) card *most definitely* provides 5V to the USB bus. The voltage increase is done with a very small amount of circuitry on the card itself. (I've confirmed this with two separate EE folks I know; I showed them your message, and they're equally as confused why you think that.) Maybe what you're trying to say is that your PowerEdge 2650 box only has the old 5V PCI slots, thus you need a USB PCI card that works in such scenarios? If so, I'm baffled as to why you're having such difficulty. Many PCI cards (including PCI USB cards -- I've Googled and found many!) are "Universal PCI" cards (keyed to work on both 3.3V and 5V PCI slots), and those will work fine. How to determine what's what: http://en.wikipedia.org/wiki/Image:PCI_Keying.png The Dell PowerEdge 2650 Systems Installation and Troubleshooting Guide indicates that the mainboard uses a riser board to provide three (3) PCI-X slots: http://support.dell.com/support/edocs/systems/pe2650/en/it/5g375aa0.htm#1046001 Googling around for a few minutes turns up some photos of the 6H580 riser board, which confirm the slots are 64-bit PCI-X 3.3V: http://cgi.ebay.com/Dell-6H580-PowerEdge-2650-PCI-Riser-Board-Card-TESTED_W0QQitemZ200218132010QQcmdZViewItem But what revision of PCI-X? Well, the speeds (MHz) available for each slot change depending upon what's installed where. Here's that reference: http://support.dell.com/support/edocs/systems/pe2650/en/it/5g375c60.htm#1059976 Which says the maximum rate is 133MHz, confirming these are PCI-X 1.0 slots. Have fun. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 27 01:27:14 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 538E8106567C; Mon, 27 Oct 2008 01:27:14 +0000 (UTC) (envelope-from louie@transsys.com) Received: from ringworld.transsys.com (ringworld.transsys.com [144.202.0.15]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF0E8FC0A; Mon, 27 Oct 2008 01:27:13 +0000 (UTC) (envelope-from louie@transsys.com) Received: from PM-G5.TransSys.COM (c-69-141-158-166.hsd1.nj.comcast.net [69.141.158.166]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: louie) by ringworld.transsys.com (Postfix) with ESMTP id 5570B5C04; Sun, 26 Oct 2008 21:27:12 -0400 (EDT) Message-Id: <2F0DB513-B639-46CB-8D8F-E6D9410FE401@transsys.com> From: Louis Mamakos To: Jeremy Chadwick In-Reply-To: <20081026233120.GA5517@icarus.home.lan> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Sun, 26 Oct 2008 21:27:10 -0400 References: <20081026125017.GA88016@icarus.home.lan> <20081026204935.GA2429@icarus.home.lan> <53B2E924-A690-4DAE-B937-076B1DA89F8E@transsys.com> <20081026233120.GA5517@icarus.home.lan> X-Mailer: Apple Mail (2.929.2) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 01:27:14 -0000 On Oct 26, 2008, at 7:31 PM, Jeremy Chadwick wrote: >> >> This has been a concern of mine. I just bought a Dell Poweredge 2650 >> off of eBay, and was going to outfit it with a USB2/Firewire PCI card >> so I can attach some cheap bulk storage to it for backup purposes. >> The >> Dell has PCI-X slots; backwards compatible with PCI, right? Try to >> find a USB PCI board that doesn't require a 5V capable PCI slot.. >> >> I haven't been able to; of course it's pretty obvious in that the USB >> host is supposed to supply 5V power to the peripherals.. D'oh! Oh >> well. > > Why do you think think the voltage provided on the USB bus is directly > proportional to the voltage provided across the PCI bus? A PCI 3.3V > expansion card (for USB ports) card *most definitely* provides 5V to > the > USB bus. The voltage increase is done with a very small amount of > circuitry on the card itself. (I've confirmed this with two > separate EE > folks I know; I showed them your message, and they're equally as > confused why you think that.) I'm well aware of the existence of switching power supply regulators; however the selection of USB/Firewire boards I was able to find didn't appear to be universal cards -- at least based on the photos provided of the actual products. The last board I bought for another system didn't have any on-board power source -- other than PTC fuses, the power just came off the PCI backplane connector. It's the easy and obvious solution. Perhaps not quite as obvious these days with 3.3V only buses. > > Maybe what you're trying to say is that your PowerEdge 2650 box only > has > the old 5V PCI slots, thus you need a USB PCI card that works in such > scenarios? If so, I'm baffled as to why you're having such > difficulty. > Many PCI cards (including PCI USB cards -- I've Googled and found > many!) > are "Universal PCI" cards (keyed to work on both 3.3V and 5V PCI > slots), > and those will work fine. How to determine what's what: > > http://en.wikipedia.org/wiki/Image:PCI_Keying.png The 2650 only has 3.3V slots. This determined by the physical keying of the connectors on the riser. I looked a bunch of boards on Amazon, and they didn't appear to be universal PCI cards. And if you look at the photos, there's nothing there that would appear to be a small switcher to generate the +5V for the USB interface. > > > The Dell PowerEdge 2650 Systems Installation and Troubleshooting Guide > indicates that the mainboard uses a riser board to provide three (3) > PCI-X slots: > > http://support.dell.com/support/edocs/systems/pe2650/en/it/5g375aa0.htm#1046001 > > Googling around for a few minutes turns up some photos of the 6H580 > riser board, which confirm the slots are 64-bit PCI-X 3.3V: > > http://cgi.ebay.com/Dell-6H580-PowerEdge-2650-PCI-Riser-Board-Card-TESTED_W0QQitemZ200218132010QQcmdZViewItem > > But what revision of PCI-X? Well, the speeds (MHz) available for each > slot change depending upon what's installed where. Here's that > reference: > > http://support.dell.com/support/edocs/systems/pe2650/en/it/5g375c60.htm#1059976 > > Which says the maximum rate is 133MHz, confirming these are PCI-X 1.0 > slots. My bandwidth needs are modest, just to run the USB/Firewire interfaces. The 2650 is pretty cost effective on ebay these days, though you're constrained to using SCA SCSI drives which are somewhat more expensive than your generic SATA drives these days. I've got 5 bays populated with 73GB drives which is sufficient for the usual email/www server, I'd like to drop some larger, less performant drives for over-the-net backup use. The search continues.. louie > > > Have fun. :-) > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 27 05:20:05 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58D56106566B for ; Mon, 27 Oct 2008 05:20:05 +0000 (UTC) (envelope-from lbaron@freedomtc.com) Received: from mx1.freebsdsystems.com (ns.freebsdsystems.com [69.90.68.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0F0878FC16 for ; Mon, 27 Oct 2008 05:20:04 +0000 (UTC) (envelope-from lbaron@freedomtc.com) Received: (qmail 15655 invoked by uid 89); 27 Oct 2008 04:53:23 -0000 Received: from unknown (HELO panda.freebsdsystems.com) (lbaron@freedomtc.com@99.237.236.194) by mail.freedomtc.com with ESMTPA; 27 Oct 2008 04:53:23 -0000 Message-ID: <49054942.4000802@freedomtc.com> Date: Mon, 27 Oct 2008 00:53:22 -0400 From: Lanny Baron Organization: Freedom Technologies Corp. FreeBSD Systems User-Agent: Thunderbird 2.0.0.12 (X11/20080303) MIME-Version: 1.0 To: Charles Sprickman References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 05:20:05 -0000 Have a look at http://www.freedomtc.com/featured_1u_server.php Regards, +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Lanny Baron Freedom Technologies Corporation High Performance Servers and RAID Systems Toll Free: 1.877.963.1900 http://www.freedomtc.com +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Charles Sprickman wrote: > Hello all, > > I have two questions regarding hardware support for two servers. One is > an older Supermicro with a X5DPR-iG2+ mainboard, the other is a > suggestion for a brand new box that is well-supported... Both boxes > will be in a co-lo, so stuff needs to not be "quirky". > > First the old box. I need an SATA controller, non-RAID. I'll be using > gmirror. I have PCI-X slots, so I'd like to go with a PCI-X controller. > There seem to be very few out there, and this one keeps popping up > everywhere: > > http://www.newegg.com/Product/Product.aspx?Item=N82E16816124014 > > The comments there mention the chip is a Silicon Image 3124, but I don't > know if I can trust a random NewEgg user. > > Can anyone confirm that controller as working and free of quirks? > Are there other cards I should be looking at? > > Next, I'm looking for a basic 1U server for light webhosting. > Reliability and compatibility are the two main concerns. I'm very happy > with 3Ware RAID cards, so I will likely add that in myself. The server > would optimally already have a hot swap SATA backplane and 4 drive > bays. I'm open to the semi-barebones route like the Supermicro servers > as well as major vendors like Dell and HP. Having some type of > IP-KVM-like functionality as an option would also be nice, but I'll > settle for a serial console. I'd like to keep this under $2K. > > Both servers will be running FreeBSD 7.1 (if it's out in time). > > Thanks, > > Charles > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 27 13:32:13 2008 Return-Path: Delivered-To: hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D79B106566C for ; Mon, 27 Oct 2008 13:32:13 +0000 (UTC) (envelope-from spamd@stu.cn.ua) Received: from stu.cn.ua (stalker.stu.cn.ua [195.69.76.130]) by mx1.freebsd.org (Postfix) with ESMTP id 3373A8FC08 for ; Mon, 27 Oct 2008 13:32:11 +0000 (UTC) (envelope-from spamd@stu.cn.ua) Received: from stu.cn.ua (localhost [127.0.0.1]) by stu.cn.ua (Postfix) with ESMTP id 2281A247477; Sun, 26 Oct 2008 00:49:25 +0300 (EEST) Received: by stu.cn.ua (Postfix, from userid 58) id 084ED247429; Sun, 26 Oct 2008 00:49:25 +0300 (EEST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on stalker.stu.cn.ua X-Spam-Level: X-Spam-Status: No, score=-106.6 required=4.5 tests=BAYES_00, RCVD_IN_DNSWL_MED, SPF_PASS,USER_IN_WHITELIST autolearn=ham version=3.2.5 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by stu.cn.ua (Postfix) with ESMTP id 1A03F247382 for ; Sun, 26 Oct 2008 00:49:19 +0300 (EEST) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A5567157A43; Sat, 25 Oct 2008 21:48:20 +0000 (UTC) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 784B6106576E; Sat, 25 Oct 2008 21:48:17 +0000 (UTC) (envelope-from owner-freebsd-current@freebsd.org) Delivered-To: current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB66F106569C; Sat, 25 Oct 2008 21:48:01 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id 703A98FC17; Sat, 25 Oct 2008 21:48:01 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id B01D371F463; Sat, 25 Oct 2008 17:29:36 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OgoeYrlfpFne; Sat, 25 Oct 2008 17:29:36 -0400 (EDT) Received: from localhost (daemon.egr.msu.edu [35.9.44.65]) by mx.egr.msu.edu (Postfix) with ESMTP id 396E471F45E; Sat, 25 Oct 2008 17:29:36 -0400 (EDT) Received: by localhost (Postfix, from userid 21281) id 23D4057F; Sat, 25 Oct 2008 17:29:36 -0400 (EDT) Date: Sat, 25 Oct 2008 17:29:36 -0400 From: Adam McDougall To: Nick Hibma Message-ID: <20081025212935.GV61867@egr.msu.edu> References: <200810092344.10388.nick@van-laarhoven.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200810092344.10388.nick@van-laarhoven.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-Virus-Scanned: ClamAV using ClamSMTP on stalker.stu.cn.ua Cc: FreeBSD Hardware Mailing list , FreeBSD CURRENT Mailing List , Andrea Guzzo Subject: Re: Request for testers: Option 3G cards, also Sierra, Huawei and Novatel X-BeenThere: freebsd-hardware@freebsd.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2008 13:32:13 -0000 Seems to work fine with my Novatel V740 (EVDO from Verizon) Expresscard. I'm using the latest version with the bufsize patch and I'm glad I no longer have to hack in a patch to get relatively fast speeds through it (just got 140kB/sec in a test which is just over 1Mbit/sec). On Thu, Oct 09, 2008 at 11:44:09PM +0200, Nick Hibma wrote: Just now I have committed a driver for Option and Huawei cards previously supported by the ubsa driver. More information is in the commit message. I am looking for people who would be able to provide more information after testing with the 3G cards branded by: OEM: Merlin Huawei Option Sierra Novatel Qualcomm Rebranded: Dell Vodafone Note: The driver can be copied across to FreeBSD 7-STABLE if you copy the sys/modules/u3g directory and sys/dev/usb/u3g.c and sys/dev/usb/usbdevs files from HEAD and _move_ the ID from ubsa to u3g. More information can be found on http://people.freebsd.org/~n_hibma/u3g.html Thanks, Nick ---------- Forwarded Message ---------- Subject: svn commit: r183735 - in head: share/man/man4 sys/conf sys/dev/usb sys/i386/conf sys/modules sys/modules/u3g Date: Thu October 9 2008 From: Nick Hibma To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Author: n_hibma Date: Thu Oct 9 21:25:01 2008 New Revision: 183735 URL: http://svn.freebsd.org/changeset/base/183735 Log: Say hello to the u3g driver, implementing support for 3G modems. This was located in the ubsa driver, but should be moved into a separate driver: - 3G modems provide multiple serial ports to allow AT commands while the PPP connection is up. - 3G modems do not provide baud rate or other serial port settings. - Huawei cards need specific initialisation. - ubsa is for Belkin adapters, an Linuxy choice for another device like 3G. Speeds achieved here with a weak signal at best is ~40kb/s (UMTS). No spooky STALLED messages as well. Next: Move over all entries for Sierra and Novatel cards once I have found testers, and implemented serial port enumeration for Sierra (or rather have Andrea Guzzo do it). They list all endpoints in 1 iface instead of 4 ifaces. Submitted by: aguzzo@anywi.com MFC after: 3 weeks Added: head/share/man/man4/u3g.4 (contents, props changed) head/sys/dev/usb/u3g.c (contents, props changed) head/sys/modules/u3g/ head/sys/modules/u3g/Makefile (contents, props changed) Modified: head/share/man/man4/Makefile head/sys/conf/NOTES head/sys/conf/files head/sys/dev/usb/ubsa.c head/sys/dev/usb/usbdevs head/sys/i386/conf/GENERIC head/sys/modules/Makefile Modified: head/share/man/man4/Makefile ============================================================================== --- head/share/man/man4/Makefile Thu Oct 9 20:51:25 2008 (r183734) +++ head/share/man/man4/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -384,6 +384,7 @@ MAN= aac.4 \ twe.4 \ tx.4 \ txp.4 \ + u3g.4 \ uark.4 \ uart.4 \ ubsa.4 \ Added: head/share/man/man4/u3g.4 ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/man/man4/u3g.4 Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,100 @@ +.\" +.\" Copyright (c) 2008 AnyWi Technologies +.\" All rights reserved. +.\" +.\" This code is derived from uark.c +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted, provided that the above +.\" copyright notice and this permission notice appear in all copies. +.\" +.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\" +.\" $FreeBSD$ +.\" +.Dd October 7, 2008 +.Dt U3G 4 +.Os +.Sh NAME +.Nm u3g +.Nd USB support for 3G datacards +.Sh SYNOPSIS +To compile this driver into the kernel, +place the following lines in your +kernel configuration file: +.Bd -ragged -offset indent +.Cd "device u3g" +.Cd "device ucom" +.Ed +.Pp +Alternatively, to load the driver as a +module at boot time, place the following line in +.Xr loader.conf 5 : +.Bd -literal -offset indent +u3g_load="YES" +.Ed +.Sh DESCRIPTION +The +.Nm +driver provides support for the multiple USB-to-serial interfaces exposed by +many 3G usb/pccard modems. +.Pp +The device is accessed through the +.Xr ucom 4 +driver which makes it behave like a +.Xr tty 4 . +.Sh HARDWARE +The +.Nm +driver supports the following adapters: +.Pp +.Bl -bullet -compact +.It +Option Globetrotter 3G Fusion (only 3G part, not WLAN) +.It +Option Globetrotter 3G Fusion Quad (only 3G part, not WLAN) +.It +Option Globetrotter 3G Quad +.It +Option Globetrotter 3G +.It +Vodafone Mobile Connect Card 3G +.It +Huawei E220 (E270?) +.It +Huawei Mobile +.El +.Pp +The supported 3G cards provide the necessary modem port for ppp, +pppd, or mpd connections as well as extra ports (depending on the specific +device) to provide other functions (diagnostic port, SIM toolkit port) +.Sh SEE ALSO +.Xr tty 4 , +.Xr ucom 4 , +.Xr usb 4 , +.Xr ubsa 4 +.Sh HISTORY +The +.Nm +driver +appeared in +.Fx 7.0 . +The +.Xr ubsa 4 +manual page was modified for +.Nm +by +.An Andrea Guzzo Aq aguzzo@anywi.com +in September 2008. +.Sh AUTHORS +The +.Nm +driver was written by +.An Andrea Guzzo Aq aguzzo@anywi.com . +Hardware for testing provided by AnyWi Technologies, Leiden, NL. Modified: head/sys/conf/NOTES ============================================================================== --- head/sys/conf/NOTES Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/conf/NOTES Thu Oct 9 21:25:01 2008 (r183735) @@ -2416,6 +2416,8 @@ device uscanner # # USB serial support device ucom +# USB support for 3G modem cards by Option, Huawei and Sierra +device u3g # USB support for Technologies ARK3116 based serial adapters device uark # USB support for Belkin F5U103 and compatible serial adapters @@ -2441,7 +2443,6 @@ device aue # ASIX Electronics AX88172 USB 2.0 ethernet driver. Used in the # LinkSys USB200M and various other adapters. - device axe # Modified: head/sys/conf/files ============================================================================== --- head/sys/conf/files Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/conf/files Thu Oct 9 21:25:01 2008 (r183735) @@ -1327,6 +1327,7 @@ dev/usb/ohci_pci.c optional ohci pci dev/usb/sl811hs.c optional slhci dev/usb/slhci_pccard.c optional slhci pccard dev/usb/uark.c optional uark +dev/usb/u3g.c optional u3g dev/usb/ubsa.c optional ubsa dev/usb/ubser.c optional ubser dev/usb/ucom.c optional ucom Added: head/sys/dev/usb/u3g.c ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/dev/usb/u3g.c Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,330 @@ +/* + * Copyright (c) 2008 AnyWi Technologies + * Author: Andrea Guzzo + * * based on uark.c 1.1 2006/08/14 08:30:22 jsg * + * * parts from ubsa.c 183348 2008-09-25 12:00:56Z phk * + * + * Permission to use, copy, modify, and distribute this software for any + * purpose with or without fee is hereby granted, provided that the above + * copyright notice and this permission notice appear in all copies. + * + * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES + * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF + * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR + * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN + * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF + * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + * + * $FreeBSD$ + */ + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +#include + +#include "usbdevs.h" + +#ifdef U3G_DEBUG +#define DPRINTFN(n, x) do { if (u3gdebug > (n)) printf x; } while (0) +int u3gtebug = 0; +#else +#define DPRINTFN(n, x) +#endif +#define DPRINTF(x) DPRINTFN(0, x) + +#define U3GBUFSZ 1024 +#define U3G_MAXPORTS 4 + +struct u3g_softc { + struct ucom_softc sc_ucom[U3G_MAXPORTS];; + device_t sc_dev; + usbd_device_handle sc_udev; + u_char sc_msr; + u_char sc_lsr; + u_char numports; + + usbd_interface_handle sc_intr_iface; /* interrupt interface */ +#ifdef U3G_DEBUG + int sc_intr_number; /* interrupt number */ + usbd_pipe_handle sc_intr_pipe; /* interrupt pipe */ + u_char *sc_intr_buf; /* interrupt buffer */ +#endif + int sc_isize; +}; + +struct ucom_callback u3g_callback = { + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, + NULL, +}; + +static const struct usb_devno u3g_devs[] = { + /* OEM: Option */ + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, + { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, + /* OEM: Huawei */ + { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, + { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 }, + + { 0, 0 } +}; + +#ifdef U3G_DEBUG +static void +u3g_intr(usbd_xfer_handle xfer, usbd_private_handle priv, usbd_status status) +{ + struct u3g_softc *sc = (struct u3g_softc *)priv; + device_printf(sc->sc_dev, "INTERRUPT CALLBACK\n"); +} +#endif + +static int +u3g_huawei_reinit(usbd_device_handle dev) +{ + /* The Huawei device presents itself as a umass device with Windows + * drivers on it. After installation of the driver, it reinits into a + * 3G serial device. + */ + usb_device_request_t req; + usb_config_descriptor_t *cdesc; + + /* Get the config descriptor */ + cdesc = usbd_get_config_descriptor(dev); + if (cdesc == NULL) + return (UMATCH_NONE); + + /* One iface means umass mode, more than 1 (4 usually) means 3G mode */ + if (cdesc->bNumInterface > 1) + return (UMATCH_VENDOR_PRODUCT); + + req.bmRequestType = UT_WRITE_DEVICE; + req.bRequest = UR_SET_FEATURE; + USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); + USETW(req.wIndex, UHF_PORT_SUSPEND); + USETW(req.wLength, 0); + + (void) usbd_do_request(dev, &req, 0); + + return UMATCH_NONE; /* mismatch; it will be gone and reappear */ +} + +static int +u3g_match(device_t self) +{ + struct usb_attach_arg *uaa = device_get_ivars(self); + + if (uaa->iface != NULL) + return (UMATCH_NONE); + + if (uaa->vendor == USB_VENDOR_HUAWEI) + return u3g_huawei_reinit(uaa->device); + + if (usb_lookup(u3g_devs, uaa->vendor, uaa->product)) + return UMATCH_VENDOR_PRODUCT; + + return UMATCH_NONE; +} + +static int +u3g_attach(device_t self) +{ + struct u3g_softc *sc = device_get_softc(self); + struct usb_attach_arg *uaa = device_get_ivars(self); + usbd_device_handle dev = uaa->device; + usbd_interface_handle iface; + usb_interface_descriptor_t *id; + usb_endpoint_descriptor_t *ed; + usbd_status error; + int i, n; + usb_config_descriptor_t *cdesc; + struct ucom_softc *ucom = NULL; + char devnamefmt[32]; + + sc->sc_dev = self; +#ifdef DEBUG + sc->sc_intr_number = -1; + sc->sc_intr_pipe = NULL; +#endif + /* Move the device into the configured state. */ + error = usbd_set_config_index(dev, 1, 1); + if (error) { + device_printf(self, "failed to set configuration: %s\n", + usbd_errstr(error)); + goto bad; + } + + /* get the config descriptor */ + cdesc = usbd_get_config_descriptor(dev); + + if (cdesc == NULL) { + device_printf(self, "failed to get configuration descriptor\n"); + goto bad; + } + + sc->sc_udev = dev; + sc->numports = (cdesc->bNumInterface <= U3G_MAXPORTS)?cdesc->bNumInterface:U3G_MAXPORTS; + for ( i = 0; i < sc->numports; i++ ) { + ucom = &sc->sc_ucom[i]; + + ucom->sc_dev = self; + ucom->sc_udev = dev; + error = usbd_device2interface_handle(dev, i, &iface); + if (error) { + device_printf(ucom->sc_dev, + "failed to get interface, err=%s\n", + usbd_errstr(error)); + ucom->sc_dying = 1; + goto bad; + } + id = usbd_get_interface_descriptor(iface); + ucom->sc_iface = iface; + + ucom->sc_bulkin_no = ucom->sc_bulkout_no = -1; + for (n = 0; n < id->bNumEndpoints; n++) { + ed = usbd_interface2endpoint_descriptor(iface, n); + if (ed == NULL) { + device_printf(ucom->sc_dev, + "could not read endpoint descriptor\n"); + goto bad; + } + if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_IN && + UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) + ucom->sc_bulkin_no = ed->bEndpointAddress; + else if (UE_GET_DIR(ed->bEndpointAddress) == UE_DIR_OUT && + UE_GET_XFERTYPE(ed->bmAttributes) == UE_BULK) + ucom->sc_bulkout_no = ed->bEndpointAddress; + } + if (ucom->sc_bulkin_no == -1 || ucom->sc_bulkout_no == -1) { + device_printf(ucom->sc_dev, "missing endpoint\n"); + goto bad; + } + ucom->sc_parent = sc; + ucom->sc_ibufsize = U3GBUFSZ; + ucom->sc_obufsize = U3GBUFSZ; + ucom->sc_ibufsizepad = U3GBUFSZ; + ucom->sc_opkthdrlen = 0; + + ucom->sc_callback = &u3g_callback; + + sprintf(devnamefmt,"U%d.%%d", device_get_unit(self)); + DPRINTF(("u3g: in=0x%x out=0x%x, devname=%s\n", + ucom->sc_bulkin_no, ucom->sc_bulkout_no, devnamefmt)); +#if __FreeBSD_version < 800000 + ucom_attach_tty(ucom, TS_CALLOUT, devnamefmt, i); +#else + ucom_attach_tty(ucom, devnamefmt, i); +#endif + } +#ifdef U3G_DEBUG + if (sc->sc_intr_number != -1 && sc->sc_intr_pipe == NULL) { + sc->sc_intr_buf = malloc(sc->sc_isize, M_USBDEV, M_WAITOK); + error = usbd_open_pipe_intr(sc->sc_intr_iface, + sc->sc_intr_number, + USBD_SHORT_XFER_OK, + &sc->sc_intr_pipe, + sc, + sc->sc_intr_buf, + sc->sc_isize, + u3g_intr, + 100); + if (error) { + device_printf(self, + "cannot open interrupt pipe (addr %d)\n", + sc->sc_intr_number); + goto bad; + } + } +#endif + device_printf(self, "configured %d serial ports (/dev/cuaU%d.X)", + sc->numports, device_get_unit(self)); + + return 0; + +bad: + DPRINTF(("u3g_attach: ATTACH ERROR\n")); + ucom->sc_dying = 1; + return ENXIO; +} + +static int +u3g_detach(device_t self) +{ + struct u3g_softc *sc = device_get_softc(self); + int rv = 0; + int i; + + DPRINTF(("u3g_detach: sc=%p\n", sc)); + + for (i = 0; i < sc->numports; i++) { + if(sc->sc_ucom[i].sc_udev) { + sc->sc_ucom[i].sc_dying = 1; + rv = ucom_detach(&sc->sc_ucom[i]); + if(rv != 0) { + device_printf(self, "Can't deallocat port %d", i); + return rv; + } + } + } + +#ifdef U3G_DEBUG + if (sc->sc_intr_pipe != NULL) { + int err = usbd_abort_pipe(sc->sc_intr_pipe); + if (err) + device_printf(self, + "abort interrupt pipe failed: %s\n", + usbd_errstr(err)); + err = usbd_close_pipe(sc->sc_intr_pipe); + if (err) + device_printf(self, + "close interrupt pipe failed: %s\n", + usbd_errstr(err)); + free(sc->sc_intr_buf, M_USBDEV); + sc->sc_intr_pipe = NULL; + } +#endif + + return 0; +} + +static device_method_t u3g_methods[] = { + /* Device interface */ + DEVMETHOD(device_probe, u3g_match), + DEVMETHOD(device_attach, u3g_attach), + DEVMETHOD(device_detach, u3g_detach), + + { 0, 0 } +}; + +static driver_t u3g_driver = { + "ucom", + u3g_methods, + sizeof (struct u3g_softc) +}; + +DRIVER_MODULE(u3g, uhub, u3g_driver, ucom_devclass, usbd_driver_load, 0); +MODULE_DEPEND(u3g, usb, 1, 1, 1); +MODULE_DEPEND(u3g, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); Modified: head/sys/dev/usb/ubsa.c ============================================================================== --- head/sys/dev/usb/ubsa.c Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/dev/usb/ubsa.c Thu Oct 9 21:25:01 2008 (r183735) @@ -161,8 +161,6 @@ SYSCTL_INT(_hw_usb_ubsa, OID_AUTO, debug struct ubsa_softc { struct ucom_softc sc_ucom; - int sc_huawei; - int sc_iface_number; /* interface number */ usbd_interface_handle sc_intr_iface; /* interrupt interface */ @@ -228,24 +226,11 @@ static const struct ubsa_product { { USB_VENDOR_GOHUBS, USB_PRODUCT_GOHUBS_GOCOM232 }, /* Peracom */ { USB_VENDOR_PERACOM, USB_PRODUCT_PERACOM_SERIAL1 }, - /* Dell version of the Novatel 740 */ - { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, - /* Option Vodafone MC3G */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G }, - /* Option GlobeTrotter 3G */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3G }, - /* Option GlobeTrotter 3G QUAD */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GQUAD }, - /* Option GlobeTrotter 3G+ */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS }, - /* Option GlobeTrotter Max 3.6 */ - { USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36 }, - /* Huawei Mobile */ - { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE }, - { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E270 }, + /* Merlin */ { USB_VENDOR_MERLIN, USB_PRODUCT_MERLIN_V620 }, /* Qualcomm, Inc. ZTE CDMA */ { USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_CDMA_MSM }, + /* Novatel */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM }, /* Novatel Wireless Merlin ES620 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620 }, @@ -256,6 +241,8 @@ static const struct ubsa_product { /* Novatel Wireless Merlin U740 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740 }, { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740_2 }, + /* Dell version of the Novatel 740 */ + { USB_VENDOR_DELL, USB_PRODUCT_DELL_U740 }, /* Novatel Wireless Merlin U950D */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U950D }, /* Novatel Wireless Merlin V620 */ @@ -341,52 +328,6 @@ MODULE_DEPEND(ubsa, usb, 1, 1, 1); MODULE_DEPEND(ubsa, ucom, UCOM_MINVER, UCOM_PREFVER, UCOM_MAXVER); MODULE_VERSION(ubsa, UBSA_MODVER); -/* - * Huawei Exxx radio devices have a built in flash disk which is their - * default power up configuration. This allows the device to carry its - * own installation software. - * - * Instead of following the USB spec, and create multiple configuration - * descriptors for this, the devices expects the driver to send - * UF_DEVICE_REMOTE_WAKEUP to endpoint 2 to reset the device, so it - * reprobes, now with the radio exposed. - */ - -static usbd_status -ubsa_huawei(device_t self, struct usb_attach_arg *uaa) { - usb_device_request_t req; usbd_device_handle dev; - usb_config_descriptor_t *cdesc; - - if (self == NULL) - return (UMATCH_NONE); - if (uaa == NULL) - return (UMATCH_NONE); - dev = uaa->device; - if (dev == NULL) - return (UMATCH_NONE); - /* get the config descriptor */ - cdesc = usbd_get_config_descriptor(dev); - if (cdesc == NULL) - return (UMATCH_NONE); - - if (cdesc->bNumInterface > 1) - return (0); - - /* Bend it like Beckham */ - device_printf(self, "Kicking Huawei device into radio mode\n"); - memset(&req, 0, sizeof req); - req.bmRequestType = UT_WRITE_DEVICE; - req.bRequest = UR_SET_FEATURE; - USETW(req.wValue, UF_DEVICE_REMOTE_WAKEUP); - USETW(req.wIndex, 2); - USETW(req.wLength, 0); - - /* We get error return, but it works */ - (void)usbd_do_request(dev, &req, 0); - return (UMATCH_NONE); -} - - static int ubsa_match(device_t self) { @@ -399,9 +340,6 @@ ubsa_match(device_t self) for (i = 0; ubsa_products[i].vendor != 0; i++) { if (ubsa_products[i].vendor == uaa->vendor && ubsa_products[i].product == uaa->product) { - if (uaa->vendor == USB_VENDOR_HUAWEI && - ubsa_huawei(self, uaa)) - break; return (UMATCH_VENDOR_PRODUCT); } } @@ -424,9 +362,6 @@ ubsa_attach(device_t self) dev = uaa->device; ucom = &sc->sc_ucom; - if (uaa->vendor == USB_VENDOR_HUAWEI) - sc->sc_huawei = 1; - /* * initialize rts, dtr variables to something * different from boolean 0, 1 @@ -575,8 +510,6 @@ ubsa_request(struct ubsa_softc *sc, u_in usbd_status err; /* The huawei Exxx devices support none of these tricks */ - if (sc->sc_huawei) - return (0); req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = request; USETW(req.wValue, value); Modified: head/sys/dev/usb/usbdevs ============================================================================== --- head/sys/dev/usb/usbdevs Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/dev/usb/usbdevs Thu Oct 9 21:25:01 2008 (r183735) @@ -1434,7 +1434,7 @@ product HTC SMARTPHONE 0x0a51 SmartPhon /* HUAWEI products */ product HUAWEI MOBILE 0x1001 Huawei Mobile -product HUAWEI E270 0x1003 Huawei HSPA modem +product HUAWEI E220 0x1003 Huawei HSDPA modem /* HUAWEI 3com products */ product HUAWEI3COM WUB320G 0x0009 Aolynk WUB320g Modified: head/sys/i386/conf/GENERIC ============================================================================== --- head/sys/i386/conf/GENERIC Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/i386/conf/GENERIC Thu Oct 9 21:25:01 2008 (r183735) @@ -304,6 +304,7 @@ device urio # Diamond Rio 500 MP3 play device uscanner # Scanners # USB Serial devices device ucom # Generic com ttys +device u3g # USB-based 3G modems (Option, Huawei, Sierra) device uark # Technologies ARK3116 based serial adapters device ubsa # Belkin F5U103 and compatible serial adapters device uftdi # For FTDI usb serial adapters Modified: head/sys/modules/Makefile ============================================================================== --- head/sys/modules/Makefile Thu Oct 9 20:51:25 2008 (r183734) +++ head/sys/modules/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -269,6 +269,7 @@ SUBDIR= ${_3dfx} \ twe \ tx \ txp \ + u3g \ uark \ uart \ ubsa \ Added: head/sys/modules/u3g/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/sys/modules/u3g/Makefile Thu Oct 9 21:25:01 2008 (r183735) @@ -0,0 +1,8 @@ +# $FreeBSD$ + +.PATH: ${.CURDIR}/../../dev/usb + +KMOD= u3g +SRCS= u3g.c ucomvar.h opt_usb.h device_if.h bus_if.h usbdevs.h + +.include _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" ------------------------------------------------------- _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 11:18:20 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 228D11065671; Tue, 28 Oct 2008 11:18:20 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id CE3818FC18; Tue, 28 Oct 2008 11:18:19 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KumKd-000KHE-Hp; Tue, 28 Oct 2008 21:01:53 +1000 Message-ID: <4906F123.30908@dannysplace.net> Date: Tue, 28 Oct 2008 21:01:55 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <20081026125017.GA88016@icarus.home.lan> In-Reply-To: <20081026125017.GA88016@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-28 21:01:51 X-Connected-IP: 203.206.171.212:3740 X-Message-Linecount: 45 X-Body-Linecount: 31 X-Message-Size: 1934 X-Body-Size: 1289 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, spork@bway.net, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 11:18:20 -0000 Jeremy Chadwick wrote: > These are cards I can recommend for your situation. Yes, they do RAID, > they all support JBOD; just plug the disks in and go. > > http://www.highpoint-tech.com/USA/series_2000.htm > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) > > http://www.areca.com.tw/products/pcix.htm > Areca ARC-1110 (arcmsr(4) driver) > Areca ARC-1120 (arcmsr(4) driver) > Areca ARC-1130 (arcmsr(4) driver) > Areca ARC-1160 (arcmsr(4) driver) > Areca ARC-1130ML (arcmsr(4) driver) > Areca ARC-1160ML (arcmsr(4) driver) One other thing that those in the know might be able to answer for me. When thinking about ZFS or Geom (or even vinum!) and a decent SATA card in JBOD mode: What happens with the write caching? Do the caches only work when you build an array? If they also work in JBOD mode, then I guess it is important to disable all write caching (can you even do that with these cards?) unless you also buy the BBU? I'd be interested to know for sure so I know if I must shell out for a BBU as well as the card itself.... -D From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 11:18:22 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E6E3106567D; Tue, 28 Oct 2008 11:18:22 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id D28EF8FC1F; Tue, 28 Oct 2008 11:18:20 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KumE0-000KEA-EA; Tue, 28 Oct 2008 20:55:15 +1000 Message-ID: <4906EF86.7050702@dannysplace.net> Date: Tue, 28 Oct 2008 20:55:02 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <20081026125017.GA88016@icarus.home.lan> In-Reply-To: <20081026125017.GA88016@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-28 20:55:00 X-Connected-IP: 203.206.171.212:3733 X-Message-Linecount: 76 X-Body-Linecount: 62 X-Message-Size: 3116 X-Body-Size: 2469 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, spork@bway.net, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 11:18:22 -0000 Jeremy Chadwick wrote: > http://www.highpoint-tech.com/USA/series_2000.htm > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) Can you (or someone else) please tell me a little more about this? Do the drives (in JBOD mode) present themselves as part of the ATA bus or SCSI bus? Do you know if NCQ and SATA-II support is in there? Can you do Smart queries to the drives? > http://www.areca.com.tw/products/pcix.htm > Areca ARC-1110 (arcmsr(4) driver) > Areca ARC-1120 (arcmsr(4) driver) > Areca ARC-1130 (arcmsr(4) driver) > Areca ARC-1160 (arcmsr(4) driver) > Areca ARC-1130ML (arcmsr(4) driver) > Areca ARC-1160ML (arcmsr(4) driver) > > The FreeBSD community members who have Areca cards have been thrilled > with them, and *do* use the native RAID features reliably. Personally I am torn right now between an Adapted 31205, a 3ware 9650SE-12ML and an Areca 1230. I'm going for ZFS so I really want a fast SATA card with lots of ports (8-12) and no raid functionality. There is not much out there and it's all expensive. > There's a bunch of Supermicro systems which meet your needs. The first > four are very new, and use the Intel X48 chipset. I don't know of any > FreeBSD people using the X7SBU board, but I'm sure there are some. > > http://www.supermicro.com/products/system/1U/ > Supermicro SuperServer 5015B-URB (~US$975) > Supermicro SuperServer 5015B-NTRB (~US$975) > Supermicro SuperServer 5015B-UB (~US$785) > Supermicro SuperServer 5015B-NTB (~US$785) > Supermicro SuperServer 5015B-MTB (~US$655) > > bsdhwmon(8) supports the 5015B-MTB (X7SBi), but doesn't support the > others (X7SBU). If someone out there has an X7SBU, please get in > touch with me so I can add support for it! I have an X7SBE, so I'm, keen to try out bsdhwmon. Installing right now... Out of curiosity (and way OT)I get a lot of ACPI messages on my supermicro board: Oct 22 11:50:29 nas kernel: ACPI Error (psargs-0459): [\_SB_.PCI0.PSMS] Namespace lookup failure, AE_NOT_FOUND Oct 22 11:50:29 nas kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.LPC0.SIO_.MSE0._STA] (Node 0xffffff00013a6260), AE_NOT_FOUND If you use supermicro boards a lot then perhaps you have seen these? -D From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 12:14:26 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB7C8106566B for ; Tue, 28 Oct 2008 12:14:26 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id AE7ED8FC1E for ; Tue, 28 Oct 2008 12:14:26 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by QMTA03.emeryville.ca.mail.comcast.net with comcast id YBXy1a00E0mlR8UA3CESG9; Tue, 28 Oct 2008 12:14:26 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA11.emeryville.ca.mail.comcast.net with comcast id YCER1a0082P6wsM8XCER1a; Tue, 28 Oct 2008 12:14:26 +0000 X-Authority-Analysis: v=1.0 c=1 a=9rRZX3FN1PoA:10 a=NMgbMNkgAAAA:8 a=RzwWTIVYAAAA:8 a=nxlI2F2nAAAA:8 a=QycZ5dHgAAAA:8 a=ibCGu94otFclfIRUHDkA:9 a=z-XsTRvUS4t9ZREPB1UA:7 a=vtn4wnYbf-6D-fbdY5CLMKdBeVEA:4 a=_1I0gKQXIP8A:10 a=ElxRAO5CFNMA:10 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 1F719C9419; Tue, 28 Oct 2008 05:14:25 -0700 (PDT) Date: Tue, 28 Oct 2008 05:14:25 -0700 From: Jeremy Chadwick To: Danny Carroll Message-ID: <20081028121425.GA48941@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <4906EF86.7050702@dannysplace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4906EF86.7050702@dannysplace.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 12:14:27 -0000 On Tue, Oct 28, 2008 at 08:55:02PM +1000, Danny Carroll wrote: > Jeremy Chadwick wrote: > > http://www.highpoint-tech.com/USA/series_2000.htm > > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) > > Can you (or someone else) please tell me a little more about this? Do > the drives (in JBOD mode) present themselves as part of the ATA bus or > SCSI bus? The hptrr(4) driver relies on SCSI CAM/da(4), and does not use the ata(4) driver in any way. > Do you know if NCQ and SATA-II support is in there? Re: SATAII: if the product data sheet or the user manual states the card supports SATA300, then yes. Re: NCQ: the user manual probably answers this question, or a FAQ/KB article. I hope you're not planning on disabling write caching on your disks (as people often ask if controllers or drives supports command queueing so they can do this. NCQ does not provide the amount of performance increase like SCSI command queuing does. On the other hand, TCQ (often found on SAS drives) does.) > Can you do Smart queries to the drives? I have no idea. I suppose it would have to support pass(4), or provide the functionality itself (Areca controllers do the latter). > > http://www.areca.com.tw/products/pcix.htm > > Areca ARC-1110 (arcmsr(4) driver) > > Areca ARC-1120 (arcmsr(4) driver) > > Areca ARC-1130 (arcmsr(4) driver) > > Areca ARC-1160 (arcmsr(4) driver) > > Areca ARC-1130ML (arcmsr(4) driver) > > Areca ARC-1160ML (arcmsr(4) driver) > > > > The FreeBSD community members who have Areca cards have been thrilled > > with them, and *do* use the native RAID features reliably. > > Personally I am torn right now between an Adapted 31205, a 3ware > 9650SE-12ML and an Areca 1230. I'm going for ZFS so I really want a > fast SATA card with lots of ports (8-12) and no raid functionality. I recommend avoiding Adaptec. I will repeat that: avoid Adaptec. You are not going to find a SATA card that has non-RAID capability with that amount of ports. Besides, it shouldn't matter to you if the card has RAID capability, because nothing forces you to use it. All that should matter to you is the following: * Is the card version/model supported under FreeBSD? * Does the card supports disks in a JBOD fashion (not part of an array)? * Can I get SMART stats from the drive (or via CLI; see below)? * Is there a native FreeBSD CLI binary for controlling features of the controller if I need it? > There is not much out there and it's all expensive. But neither of these are FreeBSD problems. The same would apply if you were using any operating system. > > There's a bunch of Supermicro systems which meet your needs. The first > > four are very new, and use the Intel X48 chipset. I don't know of any > > FreeBSD people using the X7SBU board, but I'm sure there are some. > > > > http://www.supermicro.com/products/system/1U/ > > Supermicro SuperServer 5015B-URB (~US$975) > > Supermicro SuperServer 5015B-NTRB (~US$975) > > Supermicro SuperServer 5015B-UB (~US$785) > > Supermicro SuperServer 5015B-NTB (~US$785) > > Supermicro SuperServer 5015B-MTB (~US$655) > > > > bsdhwmon(8) supports the 5015B-MTB (X7SBi), but doesn't support the > > others (X7SBU). If someone out there has an X7SBU, please get in > > touch with me so I can add support for it! > > I have an X7SBE, so I'm, keen to try out bsdhwmon. Installing right now... > > Out of curiosity (and way OT)I get a lot of ACPI messages on my > supermicro board: > > Oct 22 11:50:29 nas kernel: ACPI Error (psargs-0459): [\_SB_.PCI0.PSMS] > Namespace lookup failure, AE_NOT_FOUND > Oct 22 11:50:29 nas kernel: ACPI Error (psparse-0626): Method > parse/execution failed [\_SB_.PCI0.LPC0.SIO_.MSE0._STA] (Node > 0xffffff00013a6260), AE_NOT_FOUND > > If you use supermicro boards a lot then perhaps you have seen these? I have not seen these on any of our systems. Chances are they're ACPI or AML errors which can be fixed by the vendor with a BIOS upgrade. I would recommend asking about this on freebsd-acpi instead. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 12:19:16 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83457106569C for ; Tue, 28 Oct 2008 12:19:16 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 3A4C18FC0A for ; Tue, 28 Oct 2008 12:19:15 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by QMTA06.emeryville.ca.mail.comcast.net with comcast id YAJe1a0030x6nqcA6CKFXL; Tue, 28 Oct 2008 12:19:15 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA12.emeryville.ca.mail.comcast.net with comcast id YCKE1a00S2P6wsM8YCKFW4; Tue, 28 Oct 2008 12:19:15 +0000 X-Authority-Analysis: v=1.0 c=1 a=9rRZX3FN1PoA:10 a=NMgbMNkgAAAA:8 a=RzwWTIVYAAAA:8 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=3wyRMPjvTEpyA1IrkpMA:9 a=3-h81Hb9_kVYgxIAKxVNhHcbZBcA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id D5E2CC9419; Tue, 28 Oct 2008 05:19:14 -0700 (PDT) Date: Tue, 28 Oct 2008 05:19:14 -0700 From: Jeremy Chadwick To: Danny Carroll Message-ID: <20081028121914.GB48941@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <4906F123.30908@dannysplace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4906F123.30908@dannysplace.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 12:19:16 -0000 On Tue, Oct 28, 2008 at 09:01:55PM +1000, Danny Carroll wrote: > Jeremy Chadwick wrote: > > These are cards I can recommend for your situation. Yes, they do RAID, > > they all support JBOD; just plug the disks in and go. > > > > http://www.highpoint-tech.com/USA/series_2000.htm > > HighPoint RocketRAID 2210 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2220 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2224 (hptrr(4) driver; be sure to read NOTES) > > HighPoint RocketRAID 2240 (hptrr(4) driver; be sure to read NOTES) > > > > http://www.areca.com.tw/products/pcix.htm > > Areca ARC-1110 (arcmsr(4) driver) > > Areca ARC-1120 (arcmsr(4) driver) > > Areca ARC-1130 (arcmsr(4) driver) > > Areca ARC-1160 (arcmsr(4) driver) > > Areca ARC-1130ML (arcmsr(4) driver) > > Areca ARC-1160ML (arcmsr(4) driver) > > One other thing that those in the know might be able to answer for me. > When thinking about ZFS or Geom (or even vinum!) and a decent SATA card > in JBOD mode: > > What happens with the write caching? Do the caches only work when you > build an array? If they also work in JBOD mode, then I guess it is > important to disable all write caching (can you even do that with these > cards?) unless you also buy the BBU? This has been discussed recently on -hardware. I will stand firm on my statement: don't disable write caching on disks. http://lists.freebsd.org/pipermail/freebsd-hardware/2008-October/005450.html -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 12:19:30 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38CC51065670 for ; Tue, 28 Oct 2008 12:19:30 +0000 (UTC) (envelope-from groot@kde.org) Received: from smeltpunt.science.ru.nl (smeltpunt.science.ru.nl [131.174.16.145]) by mx1.freebsd.org (Postfix) with ESMTP id C40DA8FC24 for ; Tue, 28 Oct 2008 12:19:29 +0000 (UTC) (envelope-from groot@kde.org) Received: from [10.0.0.5] ([81.69.166.221]) (authen=adridg) by smeltpunt.science.ru.nl (8.13.7/5.28) with ESMTP id m9SCJOZU004509; Tue, 28 Oct 2008 13:19:25 +0100 (MET) From: Adriaan de Groot To: freebsd-hardware@freebsd.org Date: Tue, 28 Oct 2008 15:17:36 +0100 User-Agent: KMail/1.9.7 References: <20081026125017.GA88016@icarus.home.lan> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200810281517.37226.groot@kde.org> Cc: Charles Sprickman Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 12:19:30 -0000 [ re-visiting this thread ] On Sunday 26 October 2008, Charles Sprickman wrote: > > Stay away from this card. Jeremy, any specific reasons for that? Yes, it's a low-end piece of crap=20 consumer electronics, but as a straightforward 4-port SATA card it seems to= =20 do well enough. It's just part of ata(4) and one of the ones I've got has=20 been up for 395 days driving striped mirrored GEOMs under reasonable (but=20 certainly not high) load. > Will do. =A0Google was very unhelpful with finding info on Silicon Image = and > FreeBSD, so I thank you for that. Strange. They're supported out of the box in ata(4) now. The right search string would have been "sii 3124 driver freebsd" which tur= ns=20 up some of my older work on it, or=20 http://www.freebsd.org/cgi/man.cgi?query=3Data&apropos=3D0&sektion=3D4&manp= ath=3DFreeBSD+7.0-RELEASE&format=3Dhtml which will get you the ata(4) manpage which now lists 3124 and 3132. Again, this is a low end cheap-ass SATA card. Unlike the RTL 8139 it=20 doesn't "redefine the notion of low-end", but it seems to get the job done. =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 12:22:57 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F6661065684; Tue, 28 Oct 2008 12:22:57 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 061268FC26; Tue, 28 Oct 2008 12:22:56 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Kunb0-000Kjp-Pr; Tue, 28 Oct 2008 22:22:55 +1000 Message-ID: <4907041E.4050705@dannysplace.net> Date: Tue, 28 Oct 2008 22:22:54 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <20081026125017.GA88016@icarus.home.lan> <4906EF86.7050702@dannysplace.net> <20081028121425.GA48941@icarus.home.lan> In-Reply-To: <20081028121425.GA48941@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-28 22:22:51 X-Connected-IP: 203.206.171.212:3814 X-Message-Linecount: 68 X-Body-Linecount: 54 X-Message-Size: 2690 X-Body-Size: 1971 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, spork@bway.net, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 12:22:57 -0000 Jeremy Chadwick wrote: > Re: SATAII: if the product data sheet or the user manual states the card > supports SATA300, then yes. > > Re: NCQ: the user manual probably answers this question, or a FAQ/KB > article. I hope you're not planning on disabling write caching on your > disks (as people often ask if controllers or drives supports command > queueing so they can do this. NCQ does not provide the amount of > performance increase like SCSI command queuing does. On the other > hand, TCQ (often found on SAS drives) does.) That's a good point about the cache, I forgot about the one on the drives. > I have no idea. I suppose it would have to support pass(4), or provide > the functionality itself (Areca controllers do the latter). 3ware as well I am told. > I recommend avoiding Adaptec. I will repeat that: avoid Adaptec. I appreciate the comment, can you tell me why or is it a personal preference? > You are not going to find a SATA card that has non-RAID capability with > that amount of ports. Besides, it shouldn't matter to you if the card > has RAID capability, because nothing forces you to use it. All that > should matter to you is the following: > > * Is the card version/model supported under FreeBSD? > * Does the card supports disks in a JBOD fashion (not part of an array)? > * Can I get SMART stats from the drive (or via CLI; see below)? > * Is there a native FreeBSD CLI binary for controlling features of the > controller if I need it? Yup. > >> There is not much out there and it's all expensive. > > But neither of these are FreeBSD problems. The same would apply if you > were using any operating system. No, I agree it is not a Freebsd problem. It's everything to do with demand at the moment. > I have not seen these on any of our systems. Chances are they're ACPI > or AML errors which can be fixed by the vendor with a BIOS upgrade. > I would recommend asking about this on freebsd-acpi instead. Thanks! -D From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 12:24:40 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C4E7106567D; Tue, 28 Oct 2008 12:24:40 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 0301B8FC23; Tue, 28 Oct 2008 12:24:39 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Kunci-000KkJ-KG; Tue, 28 Oct 2008 22:24:39 +1000 Message-ID: <4907048D.6080800@dannysplace.net> Date: Tue, 28 Oct 2008 22:24:45 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <20081026125017.GA88016@icarus.home.lan> <4906F123.30908@dannysplace.net> <20081028121914.GB48941@icarus.home.lan> In-Reply-To: <20081028121914.GB48941@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-28 22:24:37 X-Connected-IP: 203.206.171.212:3816 X-Message-Linecount: 25 X-Body-Linecount: 11 X-Message-Size: 1074 X-Body-Size: 357 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, spork@bway.net, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,AWL,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 12:24:40 -0000 Jeremy Chadwick wrote: > This has been discussed recently on -hardware. I will stand firm on my > statement: don't disable write caching on disks. Ok, but what about the write caching on the array controller. Is it for writes in JBOD mode or simply when configured as an array? Just trying to figure out if I should be budgeting for a BBU as well. -D From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 12:30:38 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7DFD1065670 for ; Tue, 28 Oct 2008 12:30:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by mx1.freebsd.org (Postfix) with ESMTP id BC5FD8FC16 for ; Tue, 28 Oct 2008 12:30:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by QMTA09.emeryville.ca.mail.comcast.net with comcast id YA8U1a00117UAYkA9CWeAU; Tue, 28 Oct 2008 12:30:38 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA13.emeryville.ca.mail.comcast.net with comcast id YCWd1a00F2P6wsM8ZCWd6j; Tue, 28 Oct 2008 12:30:38 +0000 X-Authority-Analysis: v=1.0 c=1 a=8pif782wAAAA:8 a=QycZ5dHgAAAA:8 a=Z2wRAiUwHsblTQCHHzYA:9 a=H5nHDbAWbaP7aQKuv2L-k9ODvDQA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 69BE5C9419; Tue, 28 Oct 2008 05:30:37 -0700 (PDT) Date: Tue, 28 Oct 2008 05:30:37 -0700 From: Jeremy Chadwick To: Adriaan de Groot Message-ID: <20081028123037.GA49386@icarus.home.lan> References: <20081026125017.GA88016@icarus.home.lan> <200810281517.37226.groot@kde.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200810281517.37226.groot@kde.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Charles Sprickman , freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 12:30:38 -0000 On Tue, Oct 28, 2008 at 03:17:36PM +0100, Adriaan de Groot wrote: > [ re-visiting this thread ] > > On Sunday 26 October 2008, Charles Sprickman wrote: > > > Stay away from this card. > > Jeremy, any specific reasons for that? Yes, it's a low-end piece of crap > consumer electronics, but as a straightforward 4-port SATA card it seems to > do well enough. It's just part of ata(4) and one of the ones I've got has > been up for 395 days driving striped mirrored GEOMs under reasonable (but > certainly not high) load. A large number of problems people report to the FreeBSD lists involve Silicon Image controllers. There are confirmed problems within certain models of their SATA controllers which cause silent data corruption and other issues, affecting Linux, FreeBSD, and Windows. See "Product Alerts" below, then try Googling "silicon image corruption". I'm not talking out of my ass. http://en.wikipedia.org/wiki/Silicon_Image If you have one that works, "good for you". :-) But based on the above, I **will NOT** recommend these controllers. I'm not even willing to trust later revisions like the 3124; not catching data corruption during QA/testing is simply unacceptable regardless of what "class" of product it is. I would be very surprised to hear someone advocate use of Silicon Image controllers after reading the above. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 19:00:27 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7E9C1065680 for ; Tue, 28 Oct 2008 19:00:27 +0000 (UTC) (envelope-from michel.belanger@mediom.qc.ca) Received: from mailsrv01.mediom.qc.ca (mailsrv01.mediom.qc.ca [69.4.216.9]) by mx1.freebsd.org (Postfix) with ESMTP id 8A9838FC08 for ; Tue, 28 Oct 2008 19:00:27 +0000 (UTC) (envelope-from michel.belanger@mediom.qc.ca) Received: from localhost (localhost [127.0.0.1]) by mailsrv01.mediom.qc.ca (Postfix) with ESMTP id A19DF686FB for ; Tue, 28 Oct 2008 14:27:40 -0400 (EDT) X-Virus-Scanned: amavisd-new at mailsrv01.mediom.qc.ca Received: from mailsrv01.mediom.qc.ca ([127.0.0.1]) by localhost (mailsrv01.mediom.qc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2N8VNKuFu2eg for ; Tue, 28 Oct 2008 14:27:40 -0400 (EDT) Received: from [69.4.208.2] (69-4-208-2.mediom.qc.ca [69.4.208.2]) by mailsrv01.mediom.qc.ca (Postfix) with ESMTP id EEB8C684EC for ; Tue, 28 Oct 2008 14:27:39 -0400 (EDT) Message-ID: <490759B3.4030705@mediom.qc.ca> Date: Tue, 28 Oct 2008 14:28:03 -0400 From: =?ISO-8859-1?Q?Michel_B=E9langer?= Organization: =?ISO-8859-1?Q?M=C9DIOM_INTERNET?= User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: My 3 Questions X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: michb@mediom.qc.ca List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 19:00:27 -0000 I want buying a server for running FreeBSD 7.0 but i have three questions. 1- Freebsd can support Dual Quad Xeon CPU (QUAD CORE XEON E5405 2.0G 12M 1333 XD VT) ? 2- FreeBSD can support this network card (DUAL INTEL 82563EB GIGABIT ETHERNET 10/100/1000) ? 3- What is the best FreeBSD version (i386, amd64) ? If a install amd64, the 32 bits application works well ? I have searching on google but i did'nt find answer. Thanks a lot. MICHEL BÉLANGER From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 17:43:57 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C90F9106567E for ; Tue, 28 Oct 2008 17:43:57 +0000 (UTC) (envelope-from note@note2email.com) Received: from judo.dreamhost.com (judo.dreamhost.com [66.33.216.100]) by mx1.freebsd.org (Postfix) with ESMTP id AE77C8FC13 for ; Tue, 28 Oct 2008 17:43:57 +0000 (UTC) (envelope-from note@note2email.com) Received: from crusty.g.dreamhost.com (crusty.g.dreamhost.com [67.205.8.12]) by judo.dreamhost.com (Postfix) with ESMTP id 52E7317B1CC for ; Tue, 28 Oct 2008 10:24:36 -0700 (PDT) Received: from mountaindew.dreamhost.com (mountaindew.dreamhost.com [208.97.171.25]) by crusty.g.dreamhost.com (Postfix) with ESMTP id DFE1111ED63 for ; Tue, 28 Oct 2008 10:24:35 -0700 (PDT) Received: by mountaindew.dreamhost.com (Postfix, from userid 1349231) id DF3DF7C552; Tue, 28 Oct 2008 10:24:30 -0700 (PDT) To: freebsd-hardware@freebsd.org User-Agent: note2email Date: Tue, 28 Oct 2008 10:24:30 -0700 Session-ID: 2870b2637347d14b1a7e14eef1416313 IP-Address: 208.100.241.202 From: "note@note2email.com" X-Sender: note@note2email.com X-Mailer: note2email X-Priority: 3 (Normal) Message-ID: <49074acebedc1@note2email.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 28 Oct 2008 20:44:34 +0000 Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "note@note2email.com" List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 17:43:57 -0000 > A large number of problems people report to the FreeBSD lists involve > Silicon Image controllers. There are confirmed problems within certain > models of their SATA controllers which cause silent data corruption and > other issues, affecting Linux, FreeBSD, and Windows. See "Product > Alerts" below, then try Googling "silicon image corruption". I'm not > talking out of my ass. > > http://en.wikipedia.org/wiki/Silicon_Image Which points to http://osdir.com/ml/ide/2005-03/msg00126.html which says: "It's basically because of faulty SATA implementation of the affected seagate hard drives combined with standard-compliant but peculiar behavior of silicon image controllers." So you blame Silicon Image for Seagate's bug. Nice. I have been using the 3512 with Seagate drives and NetBSD for several years with zero data corruption. If FreeBSD has problems with Silicon Image controllers it isn't Silicon Image's fault. Word is that the 3124 and 3132 are much better and faster than the 1st generation controllers such as my 3512. They are documented, datasheets are available on the web, unlike some SATA controllers. I would consider them. > This has been discussed recently on -hardware. I will stand firm on my > statement: don't disable write caching on disks. > > http://lists.freebsd.org/pipermail/freebsd-hardware/2008-October/005450.html Write caching on disks enabled: data loss, fast writes Write caching on disks disabled, no NCQ: no data loss, slow writes Write caching on disks disabled, NCQ: no data loss, fast writes Sorry, but data loss is simply not acceptable. When can we expect NCQ support for FreeBSD? The ability to turn the disk's write cache on and off is essential. I haven't found a USB-to-SATA bridge that allows this, limiting their usefulness to testing new disks, mounting read-only or for data which is expendable. > Besides, it shouldn't matter to you if the card > has RAID capability, because nothing forces you to use it. The problem is that cards with real RAID are far more expensive. ____________________________________________________________________ Do not reply to this message. If this e-mail is unsolicited and you would like to report it please visit the following link: http://www.note2email.com/flag/id/2870b2637347d14b1a7e14eef1416313 This note was sent to : freebsd-hardware@freebsd.org from the following IP address: 208.100.241.202 (c) 2008 note2email.com. All rights reserved. From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 23:14:17 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DE3E106564A for ; Tue, 28 Oct 2008 23:14:17 +0000 (UTC) (envelope-from alive@dienub.org) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id 07A0C8FC1A for ; Tue, 28 Oct 2008 23:14:16 +0000 (UTC) (envelope-from alive@dienub.org) Received: by yx-out-2324.google.com with SMTP id 8so704597yxb.13 for ; Tue, 28 Oct 2008 16:14:16 -0700 (PDT) Received: by 10.150.121.3 with SMTP id t3mr5916677ybc.220.1225233818996; Tue, 28 Oct 2008 15:43:38 -0700 (PDT) Received: by 10.150.143.17 with HTTP; Tue, 28 Oct 2008 15:43:39 -0700 (PDT) Message-ID: Date: Tue, 28 Oct 2008 23:43:39 +0100 From: "Rada alive" To: michb@mediom.qc.ca In-Reply-To: <490759B3.4030705@mediom.qc.ca> MIME-Version: 1.0 References: <490759B3.4030705@mediom.qc.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: My 3 Questions X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 23:14:17 -0000 On Tue, Oct 28, 2008 at 7:28 PM, Michel B=E9langer < michel.belanger@mediom.qc.ca> wrote: > I want buying a server for running FreeBSD 7.0 but i have three questions= . > > 1- Freebsd can support Dual Quad Xeon CPU (QUAD CORE XEON E5405 2.0G 12M > 1333 XD VT) ? > 2- FreeBSD can support this network card (DUAL INTEL 82563EB GIGABIT > ETHERNET 10/100/1000) ? > 3- What is the best FreeBSD version (i386, amd64) ? If a install amd64, > the 32 bits application works well ? > > I have searching on google but i did'nt find answer. > > Thanks a lot. > > MICHEL B=C9LANGER > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.or= g > " > 1. Yes 2. Yes 3. Use amd64, install libs32. If you can, compile your applications from ports. If proprietary, check ports or ask software vendor if they have 64bi= t binaries. From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 28 23:42:35 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDE7A1065678 for ; Tue, 28 Oct 2008 23:42:35 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 9CFAA8FC28 for ; Tue, 28 Oct 2008 23:42:35 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by QMTA06.emeryville.ca.mail.comcast.net with comcast id YPel1a00217UAYkA6PiaEo; Tue, 28 Oct 2008 23:42:34 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA13.emeryville.ca.mail.comcast.net with comcast id YPVp1a0022P6wsM8ZPVpzl; Tue, 28 Oct 2008 23:29:49 +0000 X-Authority-Analysis: v=1.0 c=1 a=8pif782wAAAA:8 a=o1rluHeAAAAA:8 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=iZiw9mRv_1Gc0UQGWA0A:9 a=J4Z0rnjlD3v0R8fyMhQA:7 a=VL-6PV1gnHlsfw9xhnifyYQV0scA:4 a=EoioJ0NPDVgA:10 a=ZTWHGil2_3sA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id DE668C9419; Tue, 28 Oct 2008 16:29:48 -0700 (PDT) Date: Tue, 28 Oct 2008 16:29:48 -0700 From: Jeremy Chadwick To: "note@note2email.com" Message-ID: <20081028232948.GA61480@icarus.home.lan> References: <49074acebedc1@note2email.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49074acebedc1@note2email.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2008 23:42:35 -0000 On Tue, Oct 28, 2008 at 10:24:30AM -0700, note@note2email.com wrote: > > A large number of problems people report to the FreeBSD lists involve > > Silicon Image controllers. There are confirmed problems within certain > > models of their SATA controllers which cause silent data corruption and > > other issues, affecting Linux, FreeBSD, and Windows. See "Product > > Alerts" below, then try Googling "silicon image corruption". I'm not > > talking out of my ass. > > > > http://en.wikipedia.org/wiki/Silicon_Image > > Which points to > > http://osdir.com/ml/ide/2005-03/msg00126.html > > which says: > > "It's basically because of faulty SATA implementation of the > affected seagate hard drives combined with standard-compliant > but peculiar behavior of silicon image controllers." > > So you blame Silicon Image for Seagate's bug. Nice. Wow, thanks, I see you really did your research before posting this. Let's ignore the hundreds of posts between users on forums talking about data corruption on SiI controllers with NON-SEAGATE disks, as well as an equally large number of posts on Linux mailing lists with the same facts. I will not let you hold me responsible for Wikipedia's reference material being sparse. I'll also point you to similar 'misleading' information about nForce controllers and Maxtor disks. There are known incompatibilities with some versions of nVidia MCPs and Maxtor disks. The problem has to do with NCQ support, but absolutely no one is certain if the problem is with nVidia's chip or Maxtor's firmware. nVidia has done absolutely nothing about the problem, while Maxtor has documented the problem and offers -- assuming you ask for it -- a disk firmware that works around the problem by changing the NCQ implementation. But the same disks work fine on Intel, VIA, SiS, Promise, and even SiI controllers. So who's to blame? :-) I really, *really* hope you get my point. Let's not turn this thread a "usual BSD thread", where a bunch of administrators sit around and do burn-outs in parking lots, getting absolutely nothing accomplished other than gnashing of teeth. > I have been using the 3512 with Seagate drives and NetBSD for > several years with zero data corruption. If FreeBSD has problems > with Silicon Image controllers it isn't Silicon Image's fault. I've provided enough evidence that the problem has NOTHING to do with FreeBSD. The problem is OS-independent. Since you're explicitly ignoring this fact, I have to classify this as trolling. > Word is that the 3124 and 3132 are much better and faster than the > 1st generation controllers such as my 3512. They are documented, > datasheets are available on the web, unlike some SATA controllers. > I would consider them. > > > This has been discussed recently on -hardware. I will stand firm on my > > statement: don't disable write caching on disks. > > > > http://lists.freebsd.org/pipermail/freebsd-hardware/2008-October/005450.html > > Write caching on disks enabled: data loss, fast writes > Write caching on disks disabled, no NCQ: no data loss, slow writes > Write caching on disks disabled, NCQ: no data loss, fast writes > > Sorry, but data loss is simply not acceptable. When can we expect NCQ > support for FreeBSD? Matt Dillon and some others have explained why disabling write caching is simply unreasonable, and why it gives people a false sense of security ("if I disable write caching, my data will ALWAYS be written to the disk!" is simply untrue). It doesn't even matter if you have a controller that has a BBU. > The ability to turn the disk's write cache on and off is essential. See kern/127717. Despite not being an advocate of disabling write caching, I've no problem extending tools/drivers to provide features. > I haven't found a USB-to-SATA bridge that allows this, limiting > their usefulness to testing new disks, mounting read-only or > for data which is expendable. > > > Besides, it shouldn't matter to you if the card > > has RAID capability, because nothing forces you to use it. > > The problem is that cards with real RAID are far more expensive. The OP has specific requirements for SATA controllers. The specifics greatly limit what choices he has. The fact of the matter is, there are only two companies which make ""affordable"" consumer SATA controllers: Promise and HighPoint. I'm specifically excluding SiI from the list for what at this point should be obvious. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 29 14:08:07 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91CA2106564A for ; Wed, 29 Oct 2008 14:08:07 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from fallbackmx06.syd.optusnet.com.au (fallbackmx06.syd.optusnet.com.au [211.29.132.8]) by mx1.freebsd.org (Postfix) with ESMTP id 7931E8FC18 for ; Wed, 29 Oct 2008 14:08:06 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by fallbackmx06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m9T6GB2D026403 for ; Wed, 29 Oct 2008 17:16:11 +1100 Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail16.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m9T6G7fj021574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Oct 2008 17:16:08 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id m9T6G7j4027951; Wed, 29 Oct 2008 17:16:07 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id m9T6G6aZ027950; Wed, 29 Oct 2008 17:16:06 +1100 (EST) (envelope-from peter) Date: Wed, 29 Oct 2008 17:16:06 +1100 From: Peter Jeremy To: "note@note2email.com" Message-ID: <20081029061606.GN1137@server.vk2pj.dyndns.org> References: <49074acebedc1@note2email.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrvsYIebpInmECXG" Content-Disposition: inline In-Reply-To: <49074acebedc1@note2email.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hardware@freebsd.org Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2008 14:08:07 -0000 --lrvsYIebpInmECXG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Oct-28 10:24:30 -0700, "note@note2email.com" = wrote: >Sorry, but data loss is simply not acceptable. So, you're happy to use SATA controllers with known data corruption problems but the use of write caching (which may result in data loss if there's a power loss) is "not acceptable". > When can we expect NCQ support for FreeBSD? When someone implements it. If it's a serious issue for you, either implement it or offer to pay someone to implement it for you. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --lrvsYIebpInmECXG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkH/6YACgkQ/opHv/APuIeKfgCeIrgXAY/OJxZfWFQiTpg5E03n vNsAoKS5R8rgYte5XE5zudzpxd9C0iwW =Uxr+ -----END PGP SIGNATURE----- --lrvsYIebpInmECXG-- From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 29 15:24:18 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EE051065686 for ; Wed, 29 Oct 2008 15:24:18 +0000 (UTC) (envelope-from groot@kde.org) Received: from smeltpunt.science.ru.nl (smeltpunt.science.ru.nl [131.174.16.145]) by mx1.freebsd.org (Postfix) with ESMTP id 060768FC1B for ; Wed, 29 Oct 2008 15:24:17 +0000 (UTC) (envelope-from groot@kde.org) Received: from n142207.science.ru.nl (n142207.science.ru.nl [131.174.142.207]) by smeltpunt.science.ru.nl (8.13.7/5.28) with ESMTP id m9TFOFSF006512 for ; Wed, 29 Oct 2008 16:24:16 +0100 (MET) From: Adriaan de Groot Organization: KDE e.V. To: freebsd-hardware@freebsd.org Date: Wed, 29 Oct 2008 16:32:06 +0100 User-Agent: KMail/1.9.7 References: <49074acebedc1@note2email.com> <20081029061606.GN1137@server.vk2pj.dyndns.org> In-Reply-To: <20081029061606.GN1137@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200810291632.06845.groot@kde.org> X-Spam-Score: -2.405 () ALL_TRUSTED,BAYES_20 X-Scanned-By: MIMEDefang 2.63 on 131.174.16.145 Subject: Re: PCI-X SATA Card + Server Recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2008 15:24:18 -0000 On Wednesday 29 October 2008 07:16:06 am Peter Jeremy wrote: > > =A0When can we expect NCQ support for FreeBSD? > > When someone implements it. =A0If it's a serious issue for you, either > implement it or offer to pay someone to implement it for you. If I remember correctly -- this is from nearly a year ago -- Soren was goin= g=20 to do so for at least AHCI (Intel) things. It's a pretty big change in the= =20 way ata(4) works, because of the pervasive assumption that one ATA command= =20 results in one corresponding response. That assumption made doing FIS-based= =20 things (for SiI3124 support, oh irony in this thread) complicated as well. I really don't know what the status of this work on Soren's side is. Nor do= I=20 remember anything of my attempts to work NCQ into the SiI driver parts of=20 ata(4). I think I ran quite quickly into issues of simply remembering which= =20 slots were in use; it was going to be a horrific hack on my part in any cas= e. Note that drivers like the Areca one do do NCQ, but they hook in to the SCS= I=20 subsystem where that fits better with the design as a whole. [ade] =2D-=20 Adriaan de Groot From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 29 18:12:12 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E73761065678 for ; Wed, 29 Oct 2008 18:12:11 +0000 (UTC) (envelope-from steve@kcilink.com) Received: from yertle.kcilink.com (myrtle.kcilink.com [66.250.193.116]) by mx1.freebsd.org (Postfix) with ESMTP id 77CBF8FC08 for ; Wed, 29 Oct 2008 18:12:11 +0000 (UTC) (envelope-from steve@kcilink.com) Received: from steve.int.kcilink.com (steve.int.kcilink.com [192.168.7.99]) by yertle.kcilink.com (Postfix) with ESMTP id 86A528A009 for ; Wed, 29 Oct 2008 13:54:26 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kcilink.com; s=kci0709; t=1225302866; bh=Yoo3YjrFHuuc2Wad3wc81w7S6L60vSWuQu2usVk c0wo=; h=Message-Id:From:To:Content-Type:Mime-Version:Subject:Date; b=LLzo+eegQgk8/pOMzK8rk4x2a91yx0ASRJCeZZKLesXHVxRzfZoP8CAt32WlWRa4R 54vvVcBmqkVAyKkfvChAWeCv+kLgNexvt8MRceBj5xqH7u0PMOjEeQUW6IKb3wR8lub aLUSuJs6qjlGgm+Xrm5NheNKjzasK31HU/gfhFQ= Message-Id: From: Steve Scally To: freebsd-hardware@freebsd.org Mime-Version: 1.0 (Apple Message framework v929.2) Date: Wed, 29 Oct 2008 13:54:26 -0400 X-Mailer: Apple Mail (2.929.2) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Dell PE1900 DAT72 drive failing FreeBSD 7 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2008 18:12:12 -0000 All, I have a Dell PE1900 with an internal DAT72 drive. The drive appears to fail midway through a dump after detecting the end of tape and prompting for a new one. There is no specific sequence in which it fails. Sometimes it could be after the first tape or after the second tape. Dumps will complete for weeks at a time with no issue then suddenly fail. There are no logs with errors except for the dmesg.boot file after a reboot, which fixes the issue. Before the dump there are these two lines: "ahd0: SCSI Cell parity error SSTAT3 == 0x2 ahd0: Missing case in ahd_handle_scsiint. status = 0" I did a search and found this posting http://lists.freebsd.org/pipermail/freebsd-scsi/2007-February/002869.html which suggests to upgrade the BIOS and any other firmware. I tried this suggestion and updated the Dell BIOS from v2.0.1 to v2.3.1 and the Base Management Controller firmware from v1.69 to v2.09 however, the issue still occurs. Durning this time all other services such as mail, samba, and nfs remain functional. The only service affected is SSH. When you try to login after the failure occurs you receive "PTY allocation request failed on channel 0." Thank you in advance for the help. If you need anymore information let me know. Steve Uname -a FreeBSD 7.0-PRERELEASE #1: Wed Jan 23 22:52:15 EST 2008 amd64 pciconf -l | grep ahd ahd0@pci0:8:1:0: class=0x010000 card=0x00409005 chip=0x80169005 rev=0x10 hdr=0x00 ahd1@pci0:8:1:1: class=0x010000 card=0x00409005 chip=0x80169005 rev=0x10 hdr=0x00 ahd0: port 0xec00-0xecff, 0xe800-0xe8ff mem 0xfcb7e000-0xfcb7ffff irq 32 at device 1.0 on pci8 ahd0: [ITHREAD] >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahd0: Dumping Card State at program address 0x1c Mode 0x33 Card was paused INTSTAT[0x8] SELOID[0x9] SELID[0x0] HS_MAILBOX[0x0] INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33] SCSISIGI[0x18] SCSIPHASE[0x0] SCSIBUS[0x80] LASTPHASE[0x1] SCSISEQ0[0x40] SCSISEQ1[0x12] SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0xc0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x0] KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x10] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] SCB Count = 512 CMDS_PENDING = 8 LASTSCB 0xffff CURRSCB 0x1f7 NEXTSCB 0x0 qinstart = 16 qinfifonext = 16 QINFIFO: WAITING_TID_QUEUES: 9 ( 0x1f7 ) 10 ( 0x1f6 ) 11 ( 0x1f5 ) 12 ( 0x1f4 ) 13 ( 0x1f3 ) 14 ( 0x1f2 ) 15 ( 0x1f1 ) 6 ( 0x1f9 ) Pending list: 505 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x67] 497 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xf7] 498 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xe7] 499 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xd7] 500 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xc7] 501 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xb7] 502 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xa7] 503 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x97] Total 8 Kernel Free SCB lists: Any Device: 504 506 507 508 509 510 511 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x0 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0x1f9 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] LQIN: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc] CCSCBCTL[0x4] ahd0: REG0 == 0x1f9, SINDEX = 0x10e, DINDEX = 0x10e ahd0: SCBPTR == 0x1f7, SCB_NEXT == 0xffc0, SCB_NEXT2 == 0x1f6 CDB 12 0 0 0 24 0 STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> sa0: Removable Sequential Access SCSI-3 device sa0: 80.000MB/s transfers (40.000MHz, offset 32, 16bit) From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 30 13:36:23 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D71DC106567A; Thu, 30 Oct 2008 13:36:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2BB198FC12; Thu, 30 Oct 2008 13:36:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id m9UDaGYk048207; Thu, 30 Oct 2008 09:36:16 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Steve Scally Date: Thu, 30 Oct 2008 09:28:17 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810300928.18621.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Thu, 30 Oct 2008 09:36:16 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8541/Wed Oct 29 22:54:28 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Dell PE1900 DAT72 drive failing FreeBSD 7 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2008 13:36:24 -0000 On Wednesday 29 October 2008 01:54:26 pm Steve Scally wrote: > All, > > I have a Dell PE1900 with an internal DAT72 drive. The drive appears > to fail midway through a dump after detecting the end of tape and > prompting for a new one. There is no specific sequence in which it > fails. Sometimes it could be after the first tape or after the second > tape. Dumps will complete for weeks at a time with no issue then > suddenly fail. There are no logs with errors except for the > dmesg.boot file after a reboot, which fixes the issue. Before the > dump there are these two lines: > "ahd0: SCSI Cell parity error SSTAT3 == 0x2 > ahd0: Missing case in ahd_handle_scsiint. status = 0" You will probably have better lucking sending this to freebsd-scsi@FreeBSD.org as I know several SCSI folks are on that list, but I'm not sure they are on this one. > I did a search and found this posting http://lists.freebsd.org/pipermail/freebsd-scsi/2007-February/002869.html > which suggests to upgrade the BIOS and any other firmware. I tried > this suggestion and updated the Dell BIOS from v2.0.1 to v2.3.1 and > the Base Management Controller firmware from v1.69 to v2.09 however, > the issue still occurs. Durning this time all other services such as > mail, samba, and nfs remain functional. The only service affected is > SSH. When you try to login after the failure occurs you receive "PTY > allocation request failed on channel 0." Thank you in advance for the > help. If you need anymore information let me know. > > Steve > > Uname -a > FreeBSD 7.0-PRERELEASE #1: Wed Jan 23 22:52:15 EST 2008 amd64 > > pciconf -l | grep ahd > > ahd0@pci0:8:1:0: class=0x010000 card=0x00409005 chip=0x80169005 > rev=0x10 hdr=0x00 > ahd1@pci0:8:1:1: class=0x010000 card=0x00409005 chip=0x80169005 > rev=0x10 hdr=0x00 > > ahd0: port 0xec00-0xecff, > 0xe800-0xe8ff mem 0xfcb7e000-0xfcb7ffff irq 32 at device 1.0 on pci8 > ahd0: [ITHREAD] > > >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< > ahd0: Dumping Card State at program address 0x1c Mode 0x33 > Card was paused > INTSTAT[0x8] SELOID[0x9] SELID[0x0] HS_MAILBOX[0x0] > INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33] > SCSISIGI[0x18] SCSIPHASE[0x0] SCSIBUS[0x80] LASTPHASE[0x1] > SCSISEQ0[0x40] SCSISEQ1[0x12] SEQCTL0[0x0] SEQINTCTL[0x0] > SEQ_FLAGS[0xc0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x0] > KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] > SSTAT0[0x10] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] > SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] > LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] > > SCB Count = 512 CMDS_PENDING = 8 LASTSCB 0xffff CURRSCB 0x1f7 NEXTSCB > 0x0 > qinstart = 16 qinfifonext = 16 > QINFIFO: > WAITING_TID_QUEUES: > 9 ( 0x1f7 ) > 10 ( 0x1f6 ) > 11 ( 0x1f5 ) > 12 ( 0x1f4 ) > 13 ( 0x1f3 ) > 14 ( 0x1f2 ) > 15 ( 0x1f1 ) > 6 ( 0x1f9 ) > Pending list: > 505 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x67] > 497 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xf7] > 498 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xe7] > 499 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xd7] > 500 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xc7] > 501 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xb7] > 502 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0xa7] > 503 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x97] > Total 8 > Kernel Free SCB lists: > Any Device: 504 506 507 508 509 510 511 496 495 494 493 492 491 490 > 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 > 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 > 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 > 438 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 > 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 406 405 > 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 > 387 386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 > 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356 355 354 > 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 > 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 > 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 > 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 > 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 > 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 > 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 > 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 > 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 > 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 > 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 > 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 > 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 > 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 > 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 > 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 > 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 > 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 > 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 > 2 1 0 > Sequencer Complete DMA-inprog list: > Sequencer Complete list: > Sequencer DMA-Up and Complete list: > Sequencer On QFreeze and Complete list: > > ahd0: FIFO0 Free, LONGJMP == 0x80ff, SCB 0x0 > SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] > SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] > SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] > > ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0x1f9 > SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] > SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] > SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 > HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] > LQIN: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 > 0x0 0x0 0x0 0x0 > ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 > ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0 > ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 > SIMODE0[0xc] > CCSCBCTL[0x4] > ahd0: REG0 == 0x1f9, SINDEX = 0x10e, DINDEX = 0x10e > ahd0: SCBPTR == 0x1f7, SCB_NEXT == 0xffc0, SCB_NEXT2 == 0x1f6 > CDB 12 0 0 0 24 0 > STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 > <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> > > sa0: Removable Sequential Access > SCSI-3 device sa0: 80.000MB/s transfers (40.000MHz, offset 32, 16bit) > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 03:14:55 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41FE01065672 for ; Fri, 31 Oct 2008 03:14:55 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id F1E8F8FC12 for ; Fri, 31 Oct 2008 03:14:54 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KvkTM-000J1l-3P for freebsd-hardware@freebsd.org; Fri, 31 Oct 2008 13:14:54 +1000 Message-ID: <490A782F.9060406@dannysplace.net> Date: Fri, 31 Oct 2008 13:14:55 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-31 13:14:52 X-Connected-IP: 203.206.171.212:1550 X-Message-Linecount: 60 X-Body-Linecount: 49 X-Message-Size: 2439 X-Body-Size: 2055 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Subject: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 03:14:55 -0000 Hello all, I've just become the proud new owner of an Areca 1231-ML which I plan to use to set up an office server. I'm very curious as to how ZFS compares to a hardware solution so I plan to run some tests before I put this thing to work. The purpose of this email is to find out if anyone would like to see specific things tested as well as perhaps get some advice on how to get the most information out of the tests. My setup: Supermicro X7SBE board with 2Gb ram and an E6550 Core 2 Duo. FreeBSD 7.0-Stable compiled with amd64 sources from mid August. 1 x ST9120822AS 120gb disk (for the OS) For the array(s) 9 x ST31000340AS 1tb disks 1 x ST31000333AS 1tb disk (trying to swap this for a ST31000340AS) My thoughts are to do the following tests with bonnie++: 1 5 disk Areca Raid5 2 5 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) 3 5 Disk ZFS RaidZ1 (Connected to ICH9 On board SATA controller) 4 5 disk Areca Raid6 5 5 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) 6 5 Disk ZFS RaidZ2 (Connected to ICH9 On board SATA controller) 7 10 disk Areca Raid5 8 10 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) 9 10 disk Areca Raid6 10 10 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) My aim is to see what sort of performance gain you get by buying an Areca card for use in JBOD as well as seeing how ZFS compares to the hardware solution which offers write caching etc. I'm really only interested in testing ZFS's volume management performance, so for that reason I will also put ZFS on the Areca Raid drives. Not sure if it's a good idea to create 2 Raid drives and stripe them or simply use 1 large disk and give it to ZFS. Any thoughts on this setup as well as advice on what options to give to bonnie++ (or suggestions on another disk testing package) are very welcome. I do have some concern about the size of the eventual array and ZFS' use of system memory. Are there guidelines available that give advice on how much memory a box should have with large ZFS arrays? Can an AMD64 kernel make use of memory above 2g? -D From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 03:32:10 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C21C61065680 for ; Fri, 31 Oct 2008 03:32:10 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 6DDD38FC1E for ; Fri, 31 Oct 2008 03:32:10 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA10.westchester.pa.mail.comcast.net with comcast id Z63h1a03z0mv7h05AFY7Co; Fri, 31 Oct 2008 03:32:07 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA11.westchester.pa.mail.comcast.net with comcast id ZFY81a00C2P6wsM3XFY8H6; Fri, 31 Oct 2008 03:32:09 +0000 X-Authority-Analysis: v=1.0 c=1 a=aQgbMQmz5TEA:10 a=qMCG-Xc8eBMA:10 a=QycZ5dHgAAAA:8 a=1NznHZZxJBy8A4U4o0sA:9 a=VjeOX3E2aCwusk-sF1gA:7 a=VNbSGEzM3tjgmtdmVJVFkesu6k8A:4 a=EoioJ0NPDVgA:10 a=l5bgqdDrG-gA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 3DE29C9419; Thu, 30 Oct 2008 20:32:08 -0700 (PDT) Date: Thu, 30 Oct 2008 20:32:08 -0700 From: Jeremy Chadwick To: Danny Carroll Message-ID: <20081031033208.GA21220@icarus.home.lan> References: <490A782F.9060406@dannysplace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <490A782F.9060406@dannysplace.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 03:32:10 -0000 Cross-posting this to freebsd-fs, as I'm sure people there will have other recommendations. (This is one of those rare cross-posting situations.....) On Fri, Oct 31, 2008 at 01:14:55PM +1000, Danny Carroll wrote: > I've just become the proud new owner of an Areca 1231-ML which I plan to > use to set up an office server. > > I'm very curious as to how ZFS compares to a hardware solution so I plan > to run some tests before I put this thing to work. > > The purpose of this email is to find out if anyone would like to see > specific things tested as well as perhaps get some advice on how to get > the most information out of the tests. > > My setup: > Supermicro X7SBE board with 2Gb ram and an E6550 Core 2 Duo. > FreeBSD 7.0-Stable compiled with amd64 sources from mid August. > 1 x ST9120822AS 120gb disk (for the OS) > For the array(s) > 9 x ST31000340AS 1tb disks > 1 x ST31000333AS 1tb disk (trying to swap this for a ST31000340AS) > > My thoughts are to do the following tests with bonnie++: > 1 5 disk Areca Raid5 > 2 5 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) > 3 5 Disk ZFS RaidZ1 (Connected to ICH9 On board SATA controller) > 4 5 disk Areca Raid6 > 5 5 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) > 6 5 Disk ZFS RaidZ2 (Connected to ICH9 On board SATA controller) > 7 10 disk Areca Raid5 > 8 10 Disk ZFS RaidZ1 (Connected to Areca in JBOD mode) > 9 10 disk Areca Raid6 > 10 10 Disk ZFS RaidZ2 (Connected to Areca in JBOD mode) > > My aim is to see what sort of performance gain you get by buying an > Areca card for use in JBOD as well as seeing how ZFS compares to the > hardware solution which offers write caching etc. I'm really only > interested in testing ZFS's volume management performance, so for that > reason I will also put ZFS on the Areca Raid drives. Not sure if it's a > good idea to create 2 Raid drives and stripe them or simply use 1 large > disk and give it to ZFS. > > Any thoughts on this setup as well as advice on what options to give to > bonnie++ (or suggestions on another disk testing package) are very welcome. I think these sets of tests are good. There are some others I'd like to see, but they'd only be applicable if the 1231-ML has hardware cache. I can mention what those are if the card does have hardware caching. > I do have some concern about the size of the eventual array and ZFS' use > of system memory. Are there guidelines available that give advice on > how much memory a box should have with large ZFS arrays? The general concept is: "the more RAM the better". However, if you're using RELENG_7, then there's not much point (speaking solely about ZFS) to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap maximum. Regarding size of the array vs. memory usage: as long as you tune kmem and ZFS ARC, you shouldn't have much trouble. There have been some key people reporting lately that they run very large ZFS arrays without issue, with proper tuning. Also, just a reminder: do not pick a value of 2048M for kmem_size or kmem_size_max; the machine won't boot/work. You shouldn't go above something like 1536M, although some have tuned slightly above that with success. (You need to remember that there is more to kernel memory allocation than just this, so you don't want to exhaust it all assigning it to kmap. Hope that makes sense...) > Can an AMD64 kernel make use of memory above 2g? Only on CURRENT; 7.x cannot, and AFAIK, will never be able to, as the engineering efforts required to fix it are too great. I look forward to seeing your numbers. Someone here might be able to compile them into some graphs and other whatnots to make things easier for future readers. Thanks for doing all of this! -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 04:08:01 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2F72106567A; Fri, 31 Oct 2008 04:08:01 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 826F68FC14; Fri, 31 Oct 2008 04:08:01 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KvlIb-000JJS-BH; Fri, 31 Oct 2008 14:08:00 +1000 Message-ID: <490A849C.7030009@dannysplace.net> Date: Fri, 31 Oct 2008 14:07:56 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> In-Reply-To: <20081031033208.GA21220@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-31 14:07:50 X-Connected-IP: 203.206.171.212:1636 X-Message-Linecount: 84 X-Body-Linecount: 70 X-Message-Size: 3160 X-Body-Size: 2565 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 04:08:01 -0000 Jeremy Chadwick wrote: > I think these sets of tests are good. There are some others I'd like to > see, but they'd only be applicable if the 1231-ML has hardware cache. I > can mention what those are if the card does have hardware caching. The card comes standard with 256Mb of cache. >> I do have some concern about the size of the eventual array and ZFS' use >> of system memory. Are there guidelines available that give advice on >> how much memory a box should have with large ZFS arrays? > > The general concept is: "the more RAM the better". However, if you're > using RELENG_7, then there's not much point (speaking solely about ZFS) > to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap > maximum. > > Regarding size of the array vs. memory usage: as long as you tune kmem > and ZFS ARC, you shouldn't have much trouble. There have been some > key people reporting lately that they run very large ZFS arrays without > issue, with proper tuning. I followed the recommendations here: http://wiki.freebsd.org/ZFSTuningGuide vm.kmem_size="1024M" vm.kmem_size_max="1024M" vfs.zfs.debug=1 And : kern.maxvnodes=400000 I have not added the following because they were listed in the i386 section. (These values were quoted for a machine with 768Mb of ram) vfs.zfs.arc_max="40M" vfs.zfs.vdev.cache.size="5M" Am I right in assuming these do not apply to amd64? The article was not specific. > > Also, just a reminder: do not pick a value of 2048M for kmem_size or > kmem_size_max; the machine won't boot/work. You shouldn't go above > something like 1536M, although some have tuned slightly above that > with success. (You need to remember that there is more to kernel > memory allocation than just this, so you don't want to exhaust it all > assigning it to kmap. Hope that makes sense...) It makes sense. I'm using 1024 at the moment, but I've never really looked into what memory is actually being used. Tuning advice here would be well received :-) >> Can an AMD64 kernel make use of memory above 2g? > > Only on CURRENT; 7.x cannot, and AFAIK, will never be able to, as the > engineering efforts required to fix it are too great. > > I look forward to seeing your numbers. Someone here might be able to > compile them into some graphs and other whatnots to make things easier > for future readers. Ahhh, well, that will eventually decide my upgrade path when RELENG_8 is released and stable. > Thanks for doing all of this! No worries, hopefully it will be useful information to future google searches :-P -D From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 04:34:14 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BB57106564A for ; Fri, 31 Oct 2008 04:34:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by mx1.freebsd.org (Postfix) with ESMTP id 61F108FC1D for ; Fri, 31 Oct 2008 04:34:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by QMTA09.emeryville.ca.mail.comcast.net with comcast id ZDQy1a02m0vp7WLA9GaDzR; Fri, 31 Oct 2008 04:34:13 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA05.emeryville.ca.mail.comcast.net with comcast id ZGaC1a0072P6wsM8RGaCL5; Fri, 31 Oct 2008 04:34:13 +0000 X-Authority-Analysis: v=1.0 c=1 a=aQgbMQmz5TEA:10 a=qMCG-Xc8eBMA:10 a=6I5d2MoRAAAA:8 a=QycZ5dHgAAAA:8 a=r2IpIlXKJzo0qGbSTxYA:9 a=HyDW3Yd7XQi1SnKOiQQA:7 a=gJmddOa55550gD97BL6kJ_vfTOwA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 3EDB8C9419; Thu, 30 Oct 2008 21:34:12 -0700 (PDT) Date: Thu, 30 Oct 2008 21:34:12 -0700 From: Jeremy Chadwick To: Danny Carroll Message-ID: <20081031043412.GA22289@icarus.home.lan> References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <490A849C.7030009@dannysplace.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 04:34:14 -0000 On Fri, Oct 31, 2008 at 02:07:56PM +1000, Danny Carroll wrote: > Jeremy Chadwick wrote: > > I think these sets of tests are good. There are some others I'd like to > > see, but they'd only be applicable if the 1231-ML has hardware cache. I > > can mention what those are if the card does have hardware caching. > > The card comes standard with 256Mb of cache. I'd like to see the performance difference between these scenarios: - Memory cache enabled on Areca, write caching enabled on disks - Memory cache enabled on Areca, write caching disabled on disks - Memory cache disabled on Areca, write caching enabled on disks - Memory cache disabled on Areca, write caching disabled on disks I don't know if the controller will let you disable use of memory cache, but I'm hoping it does. I'm pretty sure it lets you disable disk write caching in its BIOS or via the CLI utility. > >> I do have some concern about the size of the eventual array and ZFS' use > >> of system memory. Are there guidelines available that give advice on > >> how much memory a box should have with large ZFS arrays? > > > > The general concept is: "the more RAM the better". However, if you're > > using RELENG_7, then there's not much point (speaking solely about ZFS) > > to getting more than maybe 3 or 4GB; you're still limited to a 2GB kmap > > maximum. > > > > Regarding size of the array vs. memory usage: as long as you tune kmem > > and ZFS ARC, you shouldn't have much trouble. There have been some > > key people reporting lately that they run very large ZFS arrays without > > issue, with proper tuning. > > I followed the recommendations here: > http://wiki.freebsd.org/ZFSTuningGuide > > vm.kmem_size="1024M" > vm.kmem_size_max="1024M" > vfs.zfs.debug=1 > > And : kern.maxvnodes=400000 > > I have not added the following because they were listed in the i386 > section. (These values were quoted for a machine with 768Mb of ram) > vfs.zfs.arc_max="40M" > vfs.zfs.vdev.cache.size="5M" > > Am I right in assuming these do not apply to amd64? The article was not > specific. All of the tuning variables apply to i386 and amd64. You do not need the vfs.zfs.debug variable; I'm not sure why you enabled that. I imagine it will have some impact on performance. I do not know anything about kern.maxvnodes, or vfs.zfs.vdev.cache.size. The tuning variables I advocate for a system with 2GB of RAM or more, on RELENG_7, are: vm.kmem_size="1536M" vm.kmem_size_max="1536M" vfs.zfs.arc_min="16M" vfs.zfs.arc_max="64M" vfs.zfs.prefetch_disable="1" You can gradually increase arc_min and arc_max by ~16MB increments as you see fit; you should see general performance improvements as they get larger (more data being kept in the ARC), but don't get too crazy. I've tuned arc_max up to 128MB before with success, but I don't want to try anything larger without decreasing kmem_size_*. > > Also, just a reminder: do not pick a value of 2048M for kmem_size or > > kmem_size_max; the machine won't boot/work. You shouldn't go above > > something like 1536M, although some have tuned slightly above that > > with success. (You need to remember that there is more to kernel > > memory allocation than just this, so you don't want to exhaust it all > > assigning it to kmap. Hope that makes sense...) > > It makes sense. I'm using 1024 at the moment, but I've never really > looked into what memory is actually being used. > > Tuning advice here would be well received :-) The only reason you need to adjust kmem_size and kmem_size_max is to increase the amount of available kmap memory which ZFS relies heavily on. If the values are too low, under heavy I/O, the kernel will panic with kmem exhaustion messages (see the ZFS Wiki for what some look like, or my Wiki). I would recommend you stick with a consistent set of loader.conf tuning variables, and focus entirely on comparing the performance of ZFS on the Areca controller vs. the ICH controller. You can perform a "ZFS tuning comparison" later. One step at a time; don't over-exert yourself quite yet. :-) You can add raidz2 to this comparison list too if you feel it's worthwhile, but I think most people will be using raidz1. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 04:47:49 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78385106564A; Fri, 31 Oct 2008 04:47:49 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 282558FC0C; Fri, 31 Oct 2008 04:47:49 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KvlvG-000JWi-9A; Fri, 31 Oct 2008 14:47:48 +1000 Message-ID: <490A8DFB.8030405@dannysplace.net> Date: Fri, 31 Oct 2008 14:47:55 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> In-Reply-To: <20081031043412.GA22289@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-31 14:47:46 X-Connected-IP: 203.206.171.212:1692 X-Message-Linecount: 97 X-Body-Linecount: 83 X-Message-Size: 3915 X-Body-Size: 3244 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 04:47:49 -0000 Jeremy Chadwick wrote: > On Fri, Oct 31, 2008 at 02:07:56PM +1000, Danny Carroll wrote: > - Memory cache enabled on Areca, write caching enabled on disks > - Memory cache enabled on Areca, write caching disabled on disks > - Memory cache disabled on Areca, write caching enabled on disks > - Memory cache disabled on Areca, write caching disabled on disks Does it matter what type of disk we are talking about? What I mean is, do you want to see this with both Raid5 and Raid6 arrays? Also, I'm pretty sure that in JBod mode the cache (on the card) will do nothing. But I am not certain, so I'll do the tests there as well. What about stripe sizes? I mainly use big files so I was going to stripe accordingly. But the bonnie++ tests might give strange results in that case. > I don't know if the controller will let you disable use of memory cache, > but I'm hoping it does. I'm pretty sure it lets you disable disk > write caching in its BIOS or via the CLI utility. > It's been a while since I've had a hardware raid card. I'll see what is available. > All of the tuning variables apply to i386 and amd64. > > You do not need the vfs.zfs.debug variable; I'm not sure why you enabled > that. I imagine it will have some impact on performance. Consider it gone. > I do not know anything about kern.maxvnodes, or vfs.zfs.vdev.cache.size. > At the moment I am not hitting anywhere near the max vnodes setting. So I think it is irrelevant. > The tuning variables I advocate for a system with 2GB of RAM or more, > on RELENG_7, are: > > vm.kmem_size="1536M" > vm.kmem_size_max="1536M" > vfs.zfs.arc_min="16M" > vfs.zfs.arc_max="64M" > vfs.zfs.prefetch_disable="1" > > You can gradually increase arc_min and arc_max by ~16MB increments as > you see fit; you should see general performance improvements as they > get larger (more data being kept in the ARC), but don't get too crazy. > I've tuned arc_max up to 128MB before with success, but I don't want > to try anything larger without decreasing kmem_size_*. What is the arc? Is it the ZFS file cache? > The only reason you need to adjust kmem_size and kmem_size_max is to > increase the amount of available kmap memory which ZFS relies heavily > on. If the values are too low, under heavy I/O, the kernel will panic > with kmem exhaustion messages (see the ZFS Wiki for what some look > like, or my Wiki). > > I would recommend you stick with a consistent set of loader.conf > tuning variables, and focus entirely on comparing the performance of > ZFS on the Areca controller vs. the ICH controller. Once I am settled on a 'starting point' I won't be altering it for the tests. > You can perform a "ZFS tuning comparison" later. One step at a time; > don't over-exert yourself quite yet. :-) Yeah, this is weekend stuff for me at the moment, it will take me some time to get things done. Firstly I need to figure out how I am going to hook up 10 drives to my system. I don't have the drive-bay space and I am not shelling out for a new case so I am hunting around for an ancient external disk cabinet. > You can add raidz2 to this comparison list too if you feel it's > worthwhile, but I think most people will be using raidz1. I might as well do both. -D From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 04:55:02 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F36B1065670; Fri, 31 Oct 2008 04:55:02 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id C56ED8FC1D; Fri, 31 Oct 2008 04:55:01 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Kvm2F-000JZ2-9I; Fri, 31 Oct 2008 14:55:01 +1000 Message-ID: <490A8FAD.8060009@dannysplace.net> Date: Fri, 31 Oct 2008 14:55:09 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Jeremy Chadwick References: <490A782F.9060406@dannysplace.net> <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> In-Reply-To: <20081031043412.GA22289@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2008-10-31 14:54:59 X-Connected-IP: 203.206.171.212:1696 X-Message-Linecount: 31 X-Body-Linecount: 17 X-Message-Size: 1347 X-Body-Size: 676 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: koitsu@FreeBSD.org, freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=8.0 tests=ALL_TRUSTED,TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 04:55:02 -0000 Jeremy Chadwick wrote: > > I'd like to see the performance difference between these scenarios: > > - Memory cache enabled on Areca, write caching enabled on disks > - Memory cache enabled on Areca, write caching disabled on disks > - Memory cache disabled on Areca, write caching enabled on disks > - Memory cache disabled on Areca, write caching disabled on disks > > I don't know if the controller will let you disable use of memory cache, > but I'm hoping it does. I'm pretty sure it lets you disable disk > write caching in its BIOS or via the CLI utility. The manual suggests that the write cache can be disabled. Perhaps there is no read cache for this card. -D From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 09:35:27 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13D65106567D for ; Fri, 31 Oct 2008 09:35:27 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by mx1.freebsd.org (Postfix) with ESMTP id B47178FC31 for ; Fri, 31 Oct 2008 09:35:26 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA09.westchester.pa.mail.comcast.net ([76.96.62.20]) by QMTA06.westchester.pa.mail.comcast.net with comcast id ZMDE1a0010SCNGk56Mavlc; Fri, 31 Oct 2008 09:34:55 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA09.westchester.pa.mail.comcast.net with comcast id ZMbQ1a00H2P6wsM3VMbRYm; Fri, 31 Oct 2008 09:35:25 +0000 X-Authority-Analysis: v=1.0 c=1 a=aQgbMQmz5TEA:10 a=qMCG-Xc8eBMA:10 a=QycZ5dHgAAAA:8 a=BuEIq7yJM_gBHHhUonMA:9 a=BCseai8xRAVsDhux3Lq9B5VicFgA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 6B836C9419; Fri, 31 Oct 2008 02:35:24 -0700 (PDT) Date: Fri, 31 Oct 2008 02:35:24 -0700 From: Jeremy Chadwick To: Simun Mikecin Message-ID: <20081031093524.GA27933@icarus.home.lan> References: <580369.72525.qm@web36607.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <580369.72525.qm@web36607.mail.mud.yahoo.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Danny Carroll , reebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 09:35:27 -0000 On Fri, Oct 31, 2008 at 01:44:25AM -0700, Simun Mikecin wrote: > Jeremy Chadwick wrote: > > The tuning variables I advocate for a system with 2GB of RAM or more, > > on RELENG_7, are: > > vm.kmem_size="1536M" > > vm.kmem_size_max="1536M" > > There is no point in setting vm.kmem_size_max. Setting vm.kmem_size is > enough. vm.kmem_size_max is used for auto-tuning of kmem size which is > in this case actually overriden by manually setting vm.kmem_size. This information hasn't been mentioned by anyone before, so it's news to me. > > vfs.zfs.arc_min="16M" > > vfs.zfs.arc_max="64M" > > vfs.zfs.prefetch_disable="1" > > You can gradually increase arc_min and arc_max by ~16MB increments as > > you see fit; you should see general performance improvements as they > > get larger (more data being kept in the ARC), but don't get too crazy. > > I've tuned arc_max up to 128MB before with success, but I don't want > > to try anything larger without decreasing kmem_size_*. > > Can you explain why would you have to decrease kmem_size to use larger > ARC? AFAIK it should be contrary to what you are saying: when you use > larger kmem_size you can also use larger arc_max. Well, my understanding (which is probably wrong) is that the memory used for the ARC is somehow separate from that of the kmap. I was under the impression the kmap was used by ZFS for other things, and did not include ARC. If I'm incorrect, please state so -- it's cool, I just need to know. :-) > My suggestion if you are using kmem_size of 1536M would be to not tune > arc_min and arc_max if your system isn't panicing. If it does you > should try decreasing arc_max (from it's default value) until it > doesn't. People have advocated increasing arc_min and arc_max in the past, citing large performance gains as arc_max gets larger; you might see people mentioning that they see great performance increases when increasing arc_max from 64M to 128M. My understanding is that increasing the ARC provides more actual cached data that ZFS can reference (vs. pulling it off disk). Again, if I'm incorrect, please state so. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 09:11:07 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 066271065686 for ; Fri, 31 Oct 2008 09:11:07 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: from web36607.mail.mud.yahoo.com (web36607.mail.mud.yahoo.com [209.191.85.24]) by mx1.freebsd.org (Postfix) with SMTP id A57A58FC28 for ; Fri, 31 Oct 2008 09:11:06 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: (qmail 73161 invoked by uid 60001); 31 Oct 2008 08:44:25 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=ZWXbW9ZIC3mWOaV4MWsfDFKPAsc/LAp8Uq0GmN8veYBj/1FIspiNW1d+m22XKeFgl0so0oguTnJxgKJvwD0DrfGU618d9pN4FyuntcDlJLPgyJsOJ9n2n8BJCX/NkJd6p7Z93MxcrqaaVjvQR5mTLHD+htA7dARtZDDGgNiY2Wg=; X-YMail-OSG: bm_9wYwVM1mhYQn4Mm3qK.xkJubVu_xhfEAjZuexXYGOTy6Z_nnvYq.bcRIAxGvxdwOPwz164XyEKGx7uFd98wO04Eicwi9Fvqi66xSAhxNlLRWXIcmON6mQUfoA09NF5BpYvfOBiQnbbbr3j1Ebasb0Kz1VlHR47yjaLRmE Received: from [213.147.110.159] by web36607.mail.mud.yahoo.com via HTTP; Fri, 31 Oct 2008 01:44:25 PDT X-Mailer: YahooMailWebService/0.7.260.1 Date: Fri, 31 Oct 2008 01:44:25 -0700 (PDT) From: Simun Mikecin To: Jeremy Chadwick MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <580369.72525.qm@web36607.mail.mud.yahoo.com> X-Mailman-Approved-At: Fri, 31 Oct 2008 11:24:49 +0000 Cc: Danny Carroll , reebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: numisemis@yahoo.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 09:11:07 -0000 Jeremy Chadwick wrote: > The tuning variables I advocate for a system with 2GB of RAM or more, > on RELENG_7, are: > vm.kmem_size="1536M" > vm.kmem_size_max="1536M" There is no point in setting vm.kmem_size_max. Setting vm.kmem_size is enough. vm.kmem_size_max is used for auto-tuning of kmem size which is in this case actually overriden by manually setting vm.kmem_size. > vfs.zfs.arc_min="16M" > vfs.zfs.arc_max="64M" > vfs.zfs.prefetch_disable="1" > You can gradually increase arc_min and arc_max by ~16MB increments as > you see fit; you should see general performance improvements as they > get larger (more data being kept in the ARC), but don't get too crazy. > I've tuned arc_max up to 128MB before with success, but I don't want > to try anything larger without decreasing kmem_size_*. Can you explain why would you have to decrease kmem_size to use larger ARC? AFAIK it should be contrary to what you are saying: when you use larger kmem_size you can also use larger arc_max. My suggestion if you are using kmem_size of 1536M would be to not tune arc_min and arc_max if your system isn't panicing. If it does you should try decreasing arc_max (from it's default value) until it doesn't. From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 11:57:19 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FB341065690 for ; Fri, 31 Oct 2008 11:57:19 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: from web36607.mail.mud.yahoo.com (web36607.mail.mud.yahoo.com [209.191.85.24]) by mx1.freebsd.org (Postfix) with SMTP id C10798FC14 for ; Fri, 31 Oct 2008 11:57:18 +0000 (UTC) (envelope-from numisemis@yahoo.com) Received: (qmail 95792 invoked by uid 60001); 31 Oct 2008 11:57:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=Xx5P1H9N7KfCFmOVYMmufYtn1vsNP97B0b0jqM0p5M7X0X6JquHiFx7tLCBXubf0h6Q/We0DICYH3YuidGI49yCl7jLMEbQAzzSLBnmavqo7HHSPR+dFAiqUXmpxVkaOqMJUPFRndPlHMSryBp+dKxFhTd0DQtsSvwttHIGmwpk=; X-YMail-OSG: pGRKbMgVM1nnwL_FxOOUxkTIpyITRbpGf3fq_BkMuHx3YZbgjlGAwbXLMJZ8h_zlaw-- Received: from [213.147.110.159] by web36607.mail.mud.yahoo.com via HTTP; Fri, 31 Oct 2008 04:57:18 PDT X-Mailer: YahooMailWebService/0.7.260.1 Date: Fri, 31 Oct 2008 04:57:18 -0700 (PDT) From: Simun Mikecin To: Jeremy Chadwick MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <174490.95560.qm@web36607.mail.mud.yahoo.com> X-Mailman-Approved-At: Fri, 31 Oct 2008 12:04:34 +0000 Cc: freebsd-fs@freebsd.org, Danny Carroll , freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: numisemis@yahoo.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 11:57:19 -0000 Jeremy Chadwick wrote: > Well, my understanding (which is probably wrong) is that the memory > used for the ARC is somehow separate from that of the kmap. I was > under the impression the kmap was used by ZFS for other things, and > did not include ARC. kmem is used by ARC. You can check your total kmem usage by ZFS using 'vmstat -m' under the line that says 'solaris'. > People have advocated increasing arc_min and arc_max in the past, citing > large performance gains as arc_max gets larger; you might see people > mentioning that they see great performance increases when increasing > arc_max from 64M to 128M. My understanding is that increasing the ARC > provides more actual cached data that ZFS can reference (vs. pulling it > off disk). Again, if I'm incorrect, please state so. You are correct about the benefits of increasing arc_max. I don't know of any benefits of tuning arc_min. Maybe someone else can answer this. By default on 7-STABLE arc_max will be 3/4 of kmem_size. So if you are using 1536M for kmem_size, arc_max will be 1152M by default. But some people will maybe need to lower it to avoid panic during heavy I/O since in those scenarios ARC cache size could for short periods of time be larger than arc_max and reach kmem limit. From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 13:08:15 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2900310656DA for ; Fri, 31 Oct 2008 13:08:15 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id CF48F8FC19 for ; Fri, 31 Oct 2008 13:08:14 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KvspN-0004T4-Eg for freebsd-hardware@freebsd.org; Fri, 31 Oct 2008 12:10:09 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 31 Oct 2008 12:10:09 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 31 Oct 2008 12:10:09 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Fri, 31 Oct 2008 13:10:52 +0100 Lines: 43 Message-ID: References: <490A782F.9060406@dannysplace.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig995BDAC16D611178C224C6FB" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.17 (X11/20080925) In-Reply-To: <490A782F.9060406@dannysplace.net> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 13:08:15 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig995BDAC16D611178C224C6FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Danny Carroll wrote: > Any thoughts on this setup as well as advice on what options to give to= > bonnie++ (or suggestions on another disk testing package) are very welc= ome. I'd suggest two more tests, because bonnie++ won't tell you the performance of random IO and file system overhead: 1) randomIO: http://arctic.org/~dean/randomio/ 2) blogbench: http://www.pureftpd.org/project/blogbench Be sure to select appropriate parameters for both (and the same parameters in every test so they can be compared) and study how they are used so you don't, for example, benchmark your system drive instead of the array :) ! (try not to put the system on the array - use the array only for benchmarks). For example, use blogbench "-c 30 -i 20 -r 40 -W 5 -w 5" to simulate a read-mostly environment. --------------enig995BDAC16D611178C224C6FB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJCvXMldnAQVacBcgRAmP0AJ4scofueN5iTmVihIr6KQMubM/a4ACg1Bwt RBZs7V1uhtdsAxDrQNcFC2s= =NGkA -----END PGP SIGNATURE----- --------------enig995BDAC16D611178C224C6FB-- From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 16:53:52 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB6FB1065672 for ; Fri, 31 Oct 2008 16:53:52 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id DBCBC8FC26 for ; Fri, 31 Oct 2008 16:53:34 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so1230993ugs.39 for ; Fri, 31 Oct 2008 09:53:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=ZVLQALGrYWtgGvXN43iw7cDmCQRhyEB+2OLmUkm65us=; b=vkKCdJ0PriaGoxAeoDfJ6/Y77wTcG2Nr7V75Fb//s76Ix/1Lk8HED4Lej9I5N+wWOw WOS1vjVLU9pkmtVyH9L27DeRnwVGhUCm1ZoIelZfGB3HUweq6CUTx0tz3QOrSbnyzMW1 hu+LtdqbhFjqyrnbAnqsaVTRlPKvj4unR86gw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=XJ/ZVyh/O5S2M06LSkJTIhDtcYw1tmqZSCvSuWu0RrLdCxg9iib1DIgALnvs8LrBUX BTPclBjaWQirzawD74gtsMr6WtTmEjMQ4EPSyuqRsVlJOwBpdW0THGZ62rDod5JGYIhC 8Cw4RdFZ0ENuK0s2lUE+CWspH1U0ibtTSN/k4= Received: by 10.210.28.6 with SMTP id b6mr5253337ebb.68.1225471579250; Fri, 31 Oct 2008 09:46:19 -0700 (PDT) Received: by 10.210.20.8 with HTTP; Fri, 31 Oct 2008 09:46:19 -0700 (PDT) Message-ID: Date: Fri, 31 Oct 2008 12:46:19 -0400 From: grarpamp To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: PCI-X SATA Card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 16:53:52 -0000 http://www.supermicro.com/products/accessories/addon/AoC-SAT2-MV8.cfm supermicro aoc-sat2-mv8 marvell 88sx6081, 8port, jbod, 64bit/133mhz, $95 Search the recent FreeBSD lists for it, seems to work. Hope to have a few soon. From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 16:59:20 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74A131065686 for ; Fri, 31 Oct 2008 16:59:20 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.181]) by mx1.freebsd.org (Postfix) with ESMTP id 536E18FC12 for ; Fri, 31 Oct 2008 16:59:09 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so1029135ika.3 for ; Fri, 31 Oct 2008 09:59:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=rllLim9zqKC1498ccSObyqpDzyWu7r4VnZqGrhqSP7U=; b=u3z7LXUcJDu2hZEc7QAQsebsAbyMB4UNkSBPie2HsqGMe6wDHYm+bPdbxtO6ZidsTg GXMJJngjmudIE2B6ps1aMjYjKL9iCt2uK4tABaFxMtOj70sk0NBRIVTzYjyGPsI7XPwU Nzwiv6NuJhTWzGDtzK91O70BogBWEmV4HRV30= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=DkAVcZT4a8v612CPfDxvXyz4jXh6hoXF7b65LmWJQqhg6vLRIV9zQ27iES4kCUU9S3 b6Ja+Ej5IfLhWE0e/9yQ8YLsYjspYm3m6UPin4ODVhV6tSMsrI0jUbzPvR721VwoMdgr BSR1Yf8FI6F9xyxAkpDkrbxUVBzD9a7+Ws8F0= Received: by 10.210.80.17 with SMTP id d17mr13622577ebb.36.1225470725187; Fri, 31 Oct 2008 09:32:05 -0700 (PDT) Received: by 10.210.20.8 with HTTP; Fri, 31 Oct 2008 09:32:05 -0700 (PDT) Message-ID: Date: Fri, 31 Oct 2008 12:32:05 -0400 From: grarpamp To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Benchmark tools: was Areca vs ZFS X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 16:59:20 -0000 Don't randomio, blogbench [and bonnie] pretty much do a subset of what iozone does? iozone.org: Read, write, re-read, re-write, read backwards, read strided, fread, fwrite, random read/write, pread/pwrite variants From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 31 17:13:54 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 659051065698 for ; Fri, 31 Oct 2008 17:13:54 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id E68F78FC17 for ; Fri, 31 Oct 2008 17:13:53 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so1237821ugs.39 for ; Fri, 31 Oct 2008 10:13:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=ZVLQALGrYWtgGvXN43iw7cDmCQRhyEB+2OLmUkm65us=; b=vkKCdJ0PriaGoxAeoDfJ6/Y77wTcG2Nr7V75Fb//s76Ix/1Lk8HED4Lej9I5N+wWOw WOS1vjVLU9pkmtVyH9L27DeRnwVGhUCm1ZoIelZfGB3HUweq6CUTx0tz3QOrSbnyzMW1 hu+LtdqbhFjqyrnbAnqsaVTRlPKvj4unR86gw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=XJ/ZVyh/O5S2M06LSkJTIhDtcYw1tmqZSCvSuWu0RrLdCxg9iib1DIgALnvs8LrBUX BTPclBjaWQirzawD74gtsMr6WtTmEjMQ4EPSyuqRsVlJOwBpdW0THGZ62rDod5JGYIhC 8Cw4RdFZ0ENuK0s2lUE+CWspH1U0ibtTSN/k4= Received: by 10.210.28.6 with SMTP id b6mr5253337ebb.68.1225471579250; Fri, 31 Oct 2008 09:46:19 -0700 (PDT) Received: by 10.210.20.8 with HTTP; Fri, 31 Oct 2008 09:46:19 -0700 (PDT) Message-ID: Date: Fri, 31 Oct 2008 12:46:19 -0400 From: grarpamp To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: PCI-X SATA Card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 17:13:54 -0000 http://www.supermicro.com/products/accessories/addon/AoC-SAT2-MV8.cfm supermicro aoc-sat2-mv8 marvell 88sx6081, 8port, jbod, 64bit/133mhz, $95 Search the recent FreeBSD lists for it, seems to work. Hope to have a few soon.