Date: Thu, 26 Sep 2002 14:54:00 -0400 From: Scott Dodson <sdodson@eagle4.cc.gasou.edu> To: Alexander@Leidinger.net Cc: freebsd-current@freebsd.org Subject: Re: Journaled filesystem in CURRENT Message-ID: <200209261854.g8QIscaF007938@eagle4.cc.gasou.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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<Alexander@Leidinger.net> 09/26/02 12:23PM >>> On Thu, 26 Sep 2002 10:52:18 -0500 Dan Nelson <dnelson@allantgroup.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209261854.g8QIscaF007938>