From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 22:44:02 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 3DC1E16A468 for ; Tue, 13 Nov 2007 22:44:02 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id E202213C448 for ; Tue, 13 Nov 2007 22:44:01 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 86383 invoked by uid 110); 13 Nov 2007 21:43:46 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 13 Nov 2007 21:43:46 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" , "Sean McAfee" Date: Tue, 13 Nov 2007 16:45:38 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: <47016605.1000003@collaborativefusion.com> MIME-Version: 1.0 Message-Id: <20071113224401.E202213C448@mx1.freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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: Tue, 13 Nov 2007 22:44:02 -0000 Hello, I'm just wondering, was this ever resolved? I was about to start using new 2950 with Perc5 in it, but now I'm afraid to as I cannot afford downtime. Why this is still a linux hack is beyond me. The way Dell is doing, they ought to have a port specifically for FreeBSD If I disable PR altogether (not sure if this is possible, yet), although I don't see why it wouldn't be, would the mentioned problem go away? Thank you, Simon On Mon, 01 Oct 2007 17:26:29 -0400, Sean McAfee wrote: >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. >**************************************************************** >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org"