From owner-freebsd-fs@FreeBSD.ORG Tue Aug 28 14:25:54 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 6C37F16A419 for ; Tue, 28 Aug 2007 14:25:53 +0000 (UTC) (envelope-from juri_mian@yahoo.com) Received: from web45615.mail.sp1.yahoo.com (web45615.mail.sp1.yahoo.com [68.180.197.180]) by mx1.freebsd.org (Postfix) with SMTP id 1264D13C46E for ; Tue, 28 Aug 2007 14:25:53 +0000 (UTC) (envelope-from juri_mian@yahoo.com) Received: (qmail 42072 invoked by uid 60001); 28 Aug 2007 14:25:49 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=EVXTdUsSeUFKX/bJan8LJfdZSrXEVYrPaA3nWQMflY4x0y5TRLOk0i/Of27mNLjPznjKH5qGwmStQRXAPfHnSiLwP5hO7z2aEoXFiQ8WQC79y5we0K0gol4oRCUaoTbGJY/18CZIZq6OF6/bsUoKFOoyr/4SO8iV93LC7Hzgduk=; X-YMail-OSG: uUjI0KYVM1lnufH5n0g06k9oF6QniX8DdfG7jRkW3tX0PdY_5SXdTMO_LD8OOrQWBPF21SlGVi6ESv2fRKpgnDkYUKSd9.0y7R10 Received: from [71.63.232.32] by web45615.mail.sp1.yahoo.com via HTTP; Tue, 28 Aug 2007 07:25:48 PDT Date: Tue, 28 Aug 2007 07:25:48 -0700 (PDT) From: Juri Mianovich To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <60619.41746.qm@web45615.mail.sp1.yahoo.com> X-Mailman-Approved-At: Tue, 28 Aug 2007 14:58:27 +0000 Cc: Subject: Re: minfree 1 -> 0 -> 1 == death ... PLEASE HELP 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: Tue, 28 Aug 2007 14:25:54 -0000 > > All I want to know is, how do I get back the old > > minfree of 1 I had 24 hours ago instead of the "new > > and improved" minfree of 1 that I have now ? > > Can you try doing: > > > tunefs -o time /dev/aacd0s1e > > and then mounting it? Yes, that was my first instinct, in fact. I can do that, but I am given a warning that filesystems with less than 8% minfree should be optimized for space. After using the filesystem for 10-20 minutes the kernel reverts optimization back to space, even if I explicitly optimize the filesystem for time. So it appears that you cannot force the filesystem to remain optimized for time. Do you know of a way to keep a filesystem optimized for time ? I would like to try running that way. I am currently running with this filesystem mounted, but mounted read-only, and the system is stable that way. Two things I want to try are: - forcing a perm. time optimization, if someone knows how to do that - freeing up enough space to get back to 5 or 8% minfree and seeing if it behaves better with that. But what I would like to know is, is it _known_ that it is more complicated (or perhaps impossible ?) to climb back out of a minfree hole ? Should it be considered a one way move ? Or should I expect to increase and decrease minfree, trading space for performance in whichever direction I am currently moving ? My results seem to suggest it is a one way move, and that you can't expect to regain performance by going back in a positive direction. Comments ? ____________________________________________________________________________________ Got a little couch potato? Check out fun summer activities for kids. http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz