From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 1 21:25:43 2007 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 A713016A419 for ; Mon, 1 Oct 2007 21:25:43 +0000 (UTC) (envelope-from smcafee@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 76CD013C448 for ; Mon, 1 Oct 2007 21:25:43 +0000 (UTC) (envelope-from smcafee@collaborativefusion.com) Received: from [192.168.2.72] (icepick.pitbpa0.priv.collaborativefusion.com [192.168.2.72]) (AUTH: LOGIN smcafee, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Mon, 01 Oct 2007 17:25:42 -0400 id 00056454.470165D6.00017953 Message-ID: <47016605.1000003@collaborativefusion.com> Date: Mon, 01 Oct 2007 17:26:29 -0400 From: Sean McAfee User-Agent: Thunderbird 2.0.0.6 (X11/20070810) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <46FD6E94.2080608@collaborativefusion.com> <200710011655.40514.jhb@freebsd.org> In-Reply-To: <200710011655.40514.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes 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, 01 Oct 2007 21:25:43 -0000 John Baldwin wrote: > On Saturday 29 September 2007 09:18:17 pm Benjie Chen wrote: > > Hmm, I haven't tried with megacli, but an internal tool at work is able to > start manual patrol reads w/o causing a crash, and I've also seen production > boxes running automatic patrol reads w/o causing crashes. Do you have to > have a certain load before it will crash? The crashes that we've seen in production have occurred while patrol reads kick off under moderate-high load, but in testing, an automatic read will complete fine. Even with maxed-out I/O*, we haven't been able to come up with reliable testing scenario to trigger crashes on automatic patrol reads. (*My base testing scenario involved running a pretty heavy stress [as in the program available in ports], while repeatedly copying ports & src from an NFS mount to another local mountpoint and SCPing a large file in a loop from another machine.) Sean McAfee Collaborative Fusion, Inc. smcafee@collaborativefusion.com 412-422-3463 x 4025 1710 Murray Avenue, Suite 320 Pittsburgh, PA 15217 **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ****************************************************************