From owner-freebsd-stable@FreeBSD.ORG Tue Sep 5 10:06:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 D313D16A4DD for ; Tue, 5 Sep 2006 10:06:03 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id B16A143D4C for ; Tue, 5 Sep 2006 10:06:02 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate1.punkt.de with ESMTP id k85A61JY007020 for ; Tue, 5 Sep 2006 12:06:01 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k85A61a9001546; Tue, 5 Sep 2006 12:06:01 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k85A608w001544; Tue, 5 Sep 2006 12:06:00 +0200 (CEST) (envelope-from ry93) Date: Tue, 5 Sep 2006 12:06:00 +0200 From: "Patrick M. Hausen" To: "Patrick M. Hausen" Message-ID: <20060905100600.GB896@hugo10.ka.punkt.de> References: <20060901164238.GA66726@hugo10.ka.punkt.de> <44F86AB9.9000002@samsco.org> <20060905073017.GA95687@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060905073017.GA95687@hugo10.ka.punkt.de> User-Agent: Mutt/1.5.10i Cc: freebsd-stable@freebsd.org Subject: Re: LSI/amr driver controller cache problem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Sep 2006 10:06:03 -0000 Hi, all! > > Also, check the cache > > setting on the drives itself. Maybe the drives are loosing power or > > getting reset while data is in their cache. > > I'm starting to suspect something like this. The controller's setting > for the individual drives' caches is "OFF". But these (Seagate ST3500841NS) > would not be the first ATA/SATA drives to "lie" about their cache for > "performance". Seems like for i in 0 1 2 3 4 5 do megarc -pSetCache -WCE0 -SaveCacheSetting -ch0 -id$i -a0 done did the trick. This is supposed to disable the physical drives' write cache and save this setting in the drives' NVRAM, if supported. I don't know why simply setting the WC to "off" in the controller's BIOS setup tool didn't have the same effect. I'm keeping my fingers crossed ;-) Time to re-enable softupdates and do some more stress testing. Up to now the system survived two times "make installworld && reboot" after I changed the settings. Thanks to the guys keeping the amr driver up-to-date. The Linux "megamgr" utility works just fine. If I find the time, I'll make a port. Regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de