Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 May 2004 02:33:15 -0500
From:      Mark Nipper <nipsy@tamu.edu>
To:        Scott Long <scottl@freebsd.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: [PATCH] Fix for 3ware driver
Message-ID:  <20040504073315.GC27843@ops.tamu.edu>
In-Reply-To: <40965292.2040608@freebsd.org>
References:  <40965292.2040608@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040504073315.GC27843>