From owner-freebsd-stable@FreeBSD.ORG Tue May 4 00:33:45 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 190B116A4CE; Tue, 4 May 2004 00:33:45 -0700 (PDT) Received: from ops.tamu.edu (ops.tamu.edu [165.91.250.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD18043D39; Tue, 4 May 2004 00:33:44 -0700 (PDT) (envelope-from nipsy@ops.tamu.edu) Received: from nipsy by ops.tamu.edu with local (Exim 4.30; FreeBSD) id 1BKuQV-0007b8-Jn; Tue, 04 May 2004 02:33:15 -0500 Date: Tue, 4 May 2004 02:33:15 -0500 From: Mark Nipper To: Scott Long Message-ID: <20040504073315.GC27843@ops.tamu.edu> References: <40965292.2040608@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40965292.2040608@freebsd.org> User-Agent: Mutt/1.5.5.1i Sender: Mark Nipper cc: Paul Saab cc: Vinod Kashyap cc: freebsd-stable@freebsd.org Subject: Re: [PATCH] Fix for 3ware driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2004 07:33:45 -0000 On 03 May 2004, Scott Long wrote: > Release testing has shown several recent problems with the 3ware (twe) > driver. Attached is a patch that appears to fix these problems. I > would appreciate as much testing as possible before I commit so that I > can be sure that all of the problems are caught and fixed correctly. > The patch applies to both RELENG_4_10 and RELENG_4 branches. Symptoms > of the problems included i/o hangs under heavy load and filesystem > corruption. Out of curiosity, do you think this might be happening in CURRENT as of at least 5.2.1-RELEASE-p5 too? The reason I ask is because I've seen some hard system freezes (not even crashing, just locking up hard) under 5 with a 2TB twe array. And I can almost reproduce it without fail by hitting my Debian archive on that disk array from three Debian Linux clients simultaneously doing updates through dselect. With Apache grabbing at the same files for those three connections, my 5 server just stops dead. It doesn't happen every single time I do this, but a good percentage of the time (I'd say at least half the time), it will trigger whatever bug I'm seeing. Just to be clear, this box is an SMP box. I'm still running the older BSD scheduler instead of ULE. And it has an em network interface running at 100Mbps/full. The file system on the RAID array is UFS2. I just recently added all the debugging stuff back into the kenerl to see if I could get a good crash dump, but I've been unwilling to trigger the bug again since the server is pseudo-production (I know, I know...) at this point and fsck'ing that much drive space is SLOW (I've had bad luck with the whole background fsck'ing idea; it tends to just lock the machine up again). Anyway. Ignore all of this if you think that this problem shouldn't exist in CURRENT. -- Mark Nipper e-contacts: Computing and Information Services nipsy@tamu.edu Texas A&M University http://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ: 66971617 (979)575-3193 MSN: nipsy@tamu.edu -----BEGIN GEEK CODE BLOCK----- GG/IT d- s++:+ a- C++$ UBL+++$ P--->+++ L+++$ E--- W++ N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP++(+) t 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**) ------END GEEK CODE BLOCK------ ---begin random quote of the moment--- In theory there is no difference between theory and practice. In practice there is. ----end random quote of the moment----