Date: Wed, 14 Nov 2007 00:30:33 -0500 From: "Simon" <simon@optinet.com> To: "Benjie Chen" <benjie@addgene.org> Cc: Sean McAfee <smcafee@collaborativefusion.com>, "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org> Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes Message-ID: <20071114052840.8BF9D13C459@mx1.freebsd.org> In-Reply-To: <20071113234334.920B213C442@mx1.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On that note, I tried to start Consistency Check using megacli and it resulted in the same problem you reported while starting Patrol Read Other megacli commands also create problems both soft and hard. Is anything being done to correct this? PS: how do other people perform CC? Thank you, Simon On Tue, 13 Nov 2007 18:45:28 -0500, Simon wrote: >So everyone that uses Dell servers with Perc5 and 6.x disables automatic PR? >-Simon >--Original Message Text--- >From: Benjie Chen >Date: Tue, 13 Nov 2007 17:50:41 -0500 >If you disable PR, the problem will go away. Below are some useful commands. Sean mentioned that you could disable it, then set it to do an automatic PR 1 hour after you restart the automatic PR. automatic PR does not crash the system >definitively, but manual PR does. So during your downtime, you could try to do an automatic PR... ># Disables patrol reads on all adapters >megacli -AdpPR -Dsbl -aALL ># Enables automatic patrol reads >megacli -AdpPR -EnblAuto -aALL ># Sets the interval for automatic reads to 1 hour - it only ># accepts whole numbers so that's the lowest you can go >megacli -AdpPR -SetDelay 1 -aALL >Some other useful ones: ># Patrol read settings and information >megacli -AdpPR -Info -aALL ># Extended information >megacli -AdpAllInfo -aALL ># Export controller's event log to file >megacli -AdpEventLog -IncludeDeleted -f <fileName> -aALL ># More logging >megacli -FwTermLog -Dsply -aALL >On 11/13/07, Simon <simon@optinet.com> wrote: 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" >_______________________________________________ >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" >-- >Benjie Chen, Ph.D. >Addgene, a better way to share plasmids >www.addgene.org >_______________________________________________ >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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071114052840.8BF9D13C459>