From owner-freebsd-questions Sat Jun 22 12:04:30 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01707 for questions-outgoing; Sat, 22 Jun 1996 12:04:30 -0700 (PDT) Received: from hod.tera.com (hod.tera.com [206.215.142.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01701 for ; Sat, 22 Jun 1996 12:04:28 -0700 (PDT) Received: from athena.tera.com (athena.tera.com [206.215.142.62]) by hod.tera.com (8.7.5/8.7.3) with ESMTP id MAA18453; Sat, 22 Jun 1996 12:03:02 -0700 (PDT) From: Gary Kline Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id MAA16245; Sat, 22 Jun 1996 12:03:02 -0700 (PDT) Message-Id: <199606221903.MAA16245@athena.tera.com> Subject: Re: LFS anyone? To: jmb@freefall.freebsd.org (Jonathan M. Bresler) Date: Sat, 22 Jun 1996 12:03:01 -0700 (PDT) Cc: anneb@svl.tec.army.mil, kline@tera.com, black@mr.net, questions@freebsd.org In-Reply-To: <199606212004.NAA22850@freefall.freebsd.org> from "Jonathan M. Bresler" at "Jun 21, 96 01:04:42 pm" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Jonathan M. Bresler: > Anne Brink wrote: > > > > > According to Ben Black: > > > Seems like the LFS would make fsck's obsolete. Yes? No? > > > > > > Yes, LFS does some rollbacks after a crash, BUT, the file system is not > > checked. It's just assumed to be fine. Fsck actually does verify that you > > LFS works forward from a 'checkpoint' to reconstruct the filesystem > in the event of a crash. at the time the checkpoint was written > the filesystem was stable and consistent. there are two checkpoint > regions on disk, the active checkpoint toggles back and forth between > the two. the last item written to disk is the toggle. > > > like syslogs and mail logs and things like that. If you have lots of random > > file accesses, especially over NFS which caches things in blocks, not whole > > files, you may lose a /lot/ of the LFS functionality, and possibly get worse > > performance than with FFS. The LFS model isn't consistent with the concept > > of cylinder groups, but uses the theory of locality which helps its efficiency. > > As for a regular user file system? Well, I'd want to run some benchmarks. (-; > > memory, memory, memory. for LFS to be effective on general purpose > uses, you must have enough memory to satisfy a very large percentage > of reads from the (now unified vm and ) file cache. > > at least this is my understanding of LFS, i may be wrong > i imagine that i will find out ;) > Interesting stuff. For my own system, or for any system, data integrity is the critical issue. Memory is cheap (or at least reasonable); getting more so. gary (dreaming of those 4GB SIMM's :-) >