From owner-freebsd-stable Mon Apr 3 13:31: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 7085437B7CE for ; Mon, 3 Apr 2000 13:29:30 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id NAA05289; Mon, 3 Apr 2000 13:28:29 -0700 (PDT) Date: Mon, 3 Apr 2000 13:28:28 -0700 From: Brooks Davis To: Brennan W Stehling Cc: stable@FreeBSD.org Subject: Re: journaling fs Message-ID: <20000403132828.A28633@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from brennan@offwhite.net on Mon, Apr 03, 2000 at 02:53:45PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 02:53:45PM -0500, Brennan W Stehling wrote: > Are there any efforts to build a journaling filesystem for FreeBSD? I > have read of several for Linux, but none for FreeBSD. > > The ufs has been great. I actually think it is more stable than what > linux uses, but I would like to avoid the problems that I have with ufs. > > fsck is just so slow, especially when my drives tend to get so much larger > than before. I have a new 30 gigger and running and fsck on that will > take a long time. If it ever falls hard it will take forever to reboot. The long answer to this question is to read the archives, specificaly -hackers and -fs are good choices. The short answer, is that Kirk is working on back ground fsck for UFS. Journaling is only one solution to this problem. Most of the features you will typicaly see attributed to a JFS have nothing to do with journaling. What most people seem to want from a JFS is buzzword compliance. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message