From owner-freebsd-questions@FreeBSD.ORG Tue Aug 8 16:52:59 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B78116A4DE for ; Tue, 8 Aug 2006 16:52:59 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA94843D45 for ; Tue, 8 Aug 2006 16:52:58 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.6/8.13.6) id k78GqvhX059693; Tue, 8 Aug 2006 11:52:57 -0500 (CDT) (envelope-from dan) Date: Tue, 8 Aug 2006 11:52:57 -0500 From: Dan Nelson To: Atom Powers Message-ID: <20060808165256.GB69605@dan.emsphone.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 6.1-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.12-2006-07-14 Cc: Freminlins , freebsd-questions@freebsd.org Subject: Re: Large File System? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2006 16:52:59 -0000 In the last episode (Aug 08), Atom Powers said: > On 8/8/06, Freminlins wrote: > >On 08/08/06, Atom Powers wrote: > >> > >> Thanks. I found my problem. (Sysinstall, aka fdisk, won't do more > >> that 1.2TB.) BTW, anybody have any good advice on how to manage a > >> large file system? > ... > >The single most important thing missing for me in FreeBSD is a > >journalling file system as I would use it on every box. > > What exactly does a journaling file system give you? As I understand > it, it doesn't prevent corruption and it doesn't help you fix the > corruption when it occurs. Journalling lets you roll back/forward a partially-commited filesystem change, so a full filesytem check isn't required to mark it clean after an unintended system reset. -- Dan Nelson dnelson@allantgroup.com