Date: Wed, 22 Aug 2001 23:28:27 -0400 From: "Robert J. Adams" <radams@siscom.net> To: <freebsd-hardware@FreeBSD.ORG> Subject: Re: 3ware stuff not ready for heavy duty useage-followup Message-ID: <00bd01c12b84$be0a2d60$7215fbd1@jason> References: <200108221652.JAA03752@mina.soco.agilent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Just to add my two pennies here.. and to say "It has been done..." and works flawlessly. We currently have 3 servers running the following config: Tyan S2567U3AN mobo 2x Intel 1G Chip 2gig ram escalade 7800, 8 channel *16* WD 80gig drives and two servers running: Tyan S2567U3AN mobo 2x Intel 1G Chip 2gig ram escalade 6800, 8 channel *16* Maxtor 80gig drives All RAID5 All are in cases from rackmountpro.com that have a 450W mini redundant power supply. These servers are slammed pretty hard.. each taking in a full newsfeed etc. No problems at all.. We've lost 3 drives in 4 months, no problems w/ rebuilds. I couldn't be happier w/ the 3ware stuff.. Thanks, Jason ----- Original Message ----- From: "Darryl Okahata" <darrylo@soco.agilent.com> To: "Hodge Podge" <nicole@unixgirl.com> Cc: "Marc Rassbach" <marc@milestonerdl.com>; <freebsd-hardware@FreeBSD.ORG>; "Michael VanLoon" <MichaelV@EDIFECS.COM> Sent: Wednesday, August 22, 2001 12:52 PM Subject: Re: 3ware stuff not ready for heavy duty useage-followup > Hodge Podge <nicole@unixgirl.com> wrote: > > > Yes however I will bet even money that if I put a seperate power supply on > > every friggen drive and still have the same problem someones gonna say.. I b > > et > > one of Those supplys was bad.. Can folks try, just try to imagine that they > > "could" be wrong and come up with some other reason? Do I honestly have to > > Prove it wrong in some scientific way before you are willing to imagine some > > other possibility? Jeeze. Some time I or someone else will have a chance to > > test the theory, but for now that is all it is. One thoery. > > OK, let's look at the other possibilities: > > 1. Non-3ware hardware problem (bad motherboard, RAM, etc.). > > Very unlikely, as this problem happens on "multiple systems". > > 2. Bad batch of 3ware boards. > > Unlikely, but a very small sliver of a possibility. > > 3. 3ware hardware bug. > > If so, you're screwed. There's probably nothing you can do about it. > > 4. 3ware firmware problem. > > If so, you're probably screwed. At the very least, you'll probably > have to wait some unknown, probably long, period of time for a > firmware update. > > 5. FreeBSD problem. > > Not very likely, but a possibility. Other people seem to be having > success with 3ware and high loads. I have not seen anyone mention > using an 8-drive setup, though (I get to do this in a few weeks, > although the system won't generally be under high load). > > Unless you're conversant with FreeBSD disk driver debugging, you're > at the mercy of the FreeBSD driver developer (yes, I know who it is), > whom you may have unintentionally pissed off beyond redemption. At > the very least, in order to fix any problems, he'd have to reproduce > your problems. > > [ Note: as another person has mentioned, you're coming across as a > real hard case (even before your recent messages). I'm sure it's > unintentional, but you've got to be aware of this. If you want > help, you don't want to (unintentionally) piss off the people who > might be able to help you. Please note that many of the people > here are anal-retentive analytics who need data, data, and more > DATA (yes, I'll raise my hand ;-). You haven't given much details, > and, for much of the details which you have given, you've given as > part of "snippy"/"unintentionally insulting" responses or > maddeningly dribbled them out across many postings. ] > > 6. Large noise sources near your systems. > > Unlikely, as you haven't mentioned any special situations (like > having an arc welder, large motor, or transmitter near your systems). > > 7. Bad line power. > > Unlikely (well, unknown, as you haven't given any details), but, as > Borja mentioned, a bad UPS can really screw you over. > > 8. Power supply problem. > > Unknown. Seems pretty likely, but you're also seeing this problem > across multiple systems, which can imply that it's not a power supply > problem -- however, you haven't said that any of the other systems > have large, beefy power supplies. > > This is one of the few things that you can test and control. > > Well, the above are the possibilities as I see them. It's your choice. > What do you want to do? > > -- > Darryl Okahata > darrylo@soco.agilent.com > > DISCLAIMER: this message is the author's personal opinion and does not > constitute the support, opinion, or policy of Agilent Technologies, or > of the little green men that have been following him all day. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00bd01c12b84$be0a2d60$7215fbd1>