From owner-freebsd-stable Sat Jun 9 9: 2:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 042C937B401 for ; Sat, 9 Jun 2001 09:02:49 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.10.0/8.10.0) id f59G2ZZ72577 for stable@freebsd.org; Sat, 9 Jun 2001 09:02:35 -0700 (PDT) Date: Sat, 9 Jun 2001 09:02:35 -0700 (PDT) From: David Wolfskill Message-Id: <200106091602.f59G2ZZ72577@bunrab.catwhisker.org> To: stable@freebsd.org Subject: Re: Improvements for FreeBSD v4.3.1-Release? In-Reply-To: <20010609154753.32846.qmail@web14707.mail.yahoo.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Sat, 9 Jun 2001 08:47:53 -0700 (PDT) >From: Donn Miller >I think it's all a matter of tradeoffs. Journaling probably isn't as >fast as softupdates, but otoh, really huge filesystems don't have to >have the long fsck that softupdates requires. BUT, if background fsck >ever gets implemented, it should help immensely even the score in that >area. FWIW, the "background fsck" is (at least partially) implemented in -CURRENT. And there have been a few times that I've experienced a panic in -CURRENT, and the background fsck kicked in; seemed to work as expected for me in those cases -- no surprises; no known data loss or damage. And though I'm somewhat "playing with fire" here, I was also able to mount the filesystems in question OK under -STABLE. (I boot either -STABLE or -CURRENT on my laptop.) Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message