From owner-freebsd-current Thu Sep 26 11:54:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7213737B401 for ; Thu, 26 Sep 2002 11:54:21 -0700 (PDT) Received: from eagle4.cc.gasou.edu (eagle4.cc.GaSoU.edu [141.165.4.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id D06CA43E3B for ; Thu, 26 Sep 2002 11:54:20 -0700 (PDT) (envelope-from sdodson@eagle4.cc.gasou.edu) Received: from rbarrantes (cats-web.cst.GaSoU.edu [141.165.51.113]) by eagle4.cc.gasou.edu (8.12.2/8.12.2) with SMTP id g8QIscaF007938; Thu, 26 Sep 2002 14:54:39 -0400 (EDT) Message-Id: <200209261854.g8QIscaF007938@eagle4.cc.gasou.edu> Mime-Version: 1.0 Date: Thu, 26 Sep 2002 14:54:00 -0400 References: <200209251319.g8PDJYoD047918@ib.com.ua> <20020925111232.B3686@Odin.AC.HMC.Edu> <20020926111949.5c0da160.Alexander@Leidinger.net> <20020926155218.GA67579@dan.emsphone.com> <20020926182319.68907194.Alexander@Leidinger.net> X-Mailer: Groupwise 5.5.3.1 From: Scott Dodson Cc: freebsd-current@freebsd.org Subject: Re: Journaled filesystem in CURRENT To: Alexander@Leidinger.net Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been having loads of problems with the bg-fsck. After recovering from a crash/power failure my machine will boot and start the check. If = there's moderate activity during the time its checking it will panic and reboot, = getting stuck in a loop most of the time. I've not seen anyone mention this on = the list, but I was wondering if anyone's experienced this? This has been = ongoing across many cvsups and buildworlds. Thanks, Scott >>> Alexander Leidinger 09/26/02 12:23PM >>> On Thu, 26 Sep 2002 10:52:18 -0500 Dan Nelson wrote: > > We have something better than those. SoftUpdates. Much faster than > > jfs in metadata intensive operations. >=20 > If you can stand the 20 minutes of severly degraded performance while > the background fsck runs after a crash, and the loss of any files Sometimes it's better to have 20 minutes (or how long it takes to do the bg-fsck on your FS) degraded performance, than no performance at all (you can have this too, just configure the system to make an fg-fsck instead of a bg-fsck)... (how long does it take to check the journal and to do some appropriate actions depending on the journal?) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message