From owner-freebsd-stable Wed Mar 14 16:35: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 9B9E737B718 for ; Wed, 14 Mar 2001 16:35:03 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2F0TTF04572; Wed, 14 Mar 2001 16:29:30 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103150029.f2F0TTF04572@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: rand@meridian-enviro.com Cc: freebsd-stable@freebsd.org, bryanh@meridian-enviro.com Subject: Re: 3ware problems In-reply-to: Your message of "Wed, 14 Mar 2001 18:18:23 CST." <87g0gfopf4.wl@delta.meridian-enviro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Mar 2001 16:29:29 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We are having an interesting problem with a new 3ware (Escalade 6400) > controller. We have 4 75GB IBM DTLA disks configured in a RAID 1+0 > array. > > Our problem is with MySQL: It will eventually just stop with a state > of 'getblk'. The entire /var/db/mysql filesystem becomes > stuck, any attempts of doing any operations to the /var/db/mysql > filesystem simply hang. > > The rest of the system works perfectly, even after mysqld becomes > stuck. A reboot will always complain that it can't flush a buffer, but > the system comes back up and things work fine for a while, until it > happens again. > > We have a handfull of fairly large (10 to 30 million rows) tables and > can reliably reproduce the problem by inserting 30 million rows into a > table. It does not always hang at the same time, and it usually takes > a few hours of operation to get stuck. > > Does anybody have any ideas for us? Not until you tell us which version of FreeBSD you're running. 8) Seriously; there is a driver/firmware interaction that can cause this, and if you're running something older than FreeBSD 4.2, you should upgrade. You'll want to make sure you have the most recent firmware on the cards, too. If you've done this and you're still having problems, build the driver with TWE_DEBUG enabled, and boot a kernel with DDB enabled. Then, when mysql sticks, break to DDB and say db> call twe_report and send me the output. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message