From owner-freebsd-fs@FreeBSD.ORG Mon Aug 27 10:41:16 2007 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04AA916A417 for ; Mon, 27 Aug 2007 10:41:16 +0000 (UTC) (envelope-from juri_mian@yahoo.com) Received: from web45612.mail.sp1.yahoo.com (web45612.mail.sp1.yahoo.com [68.180.197.153]) by mx1.freebsd.org (Postfix) with SMTP id E343113C45E for ; Mon, 27 Aug 2007 10:41:15 +0000 (UTC) (envelope-from juri_mian@yahoo.com) Received: (qmail 68561 invoked by uid 60001); 27 Aug 2007 10:14:02 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=rFMW1wYW1NYqH4VSmlNh4hsnJLZs/+HEHjew8sKApPqFaOqYRmhWBEUXX+hZh4CUZTfydpFbjxphLCXhAtFzyav/+fv1oxDJ46NGx38qFUomnrDRE3cx1aOjHSMmpC4DgYrgdIfTc7u9l3c4SrcFWMJvlUur4c5FTf5zJx8h/dY=; X-YMail-OSG: _bYEjTAVM1n17.OwSjm6cQyIAFVp52.ni0JmgpasExKzo9wWJCVh3i_9GdnCY0sQ0rTifno74wuDPJ8jWzQ0zJf6YAcoPBgDnaot Received: from [71.63.232.32] by web45612.mail.sp1.yahoo.com via HTTP; Mon, 27 Aug 2007 03:14:01 PDT Date: Mon, 27 Aug 2007 03:14:01 -0700 (PDT) From: Juri Mianovich To: freebsd-fs@freebsd.org MIME-Version: 1.0 Message-ID: <72418.68169.qm@web45612.mail.sp1.yahoo.com> X-Mailman-Approved-At: Mon, 27 Aug 2007 11:31:50 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: How do I get back my previous minfree level of performance ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Aug 2007 10:41:16 -0000 I know of a way to beat up (stress) an aac controller that will cause it to crash. I have put safeguards in place to make sure that this never happens. It is well known that going to a minfree level of ZERO on a disk that is near-full is very stressful on the system. Last night, I took a 1.8 TB filesystem with only 10 GB of free space and changed it from: minfree=1 to: minfree=0 and suddenly the aac0 controller starts dying on me. OOPS. Ok, no problem, I did not use any of the space I gained yet, so I will just go right back to a minfree of "1". So basically, I changed my minfree: 1 -> 0 -> 1 But the problem is, the crashes that going to zero caused _persist_ after going back to one. So my question is, what did I leave behind ? And how do I get back to a "real" minfree of 1, and not this broken minfree of 1 that I currently have ? The environment has been carefully controlled - this is the only change that has occurred and this aac0 controller halting has not happened in 300+ days of continuous operation ... it is definitely the move to a minfree of zero that stressed out the aac driver... Comments ? --------------------------------- Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.