From owner-freebsd-current@FreeBSD.ORG Mon Jul 26 17:43:14 2004 Return-Path: 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 B2DC116A4CE; Mon, 26 Jul 2004 17:43:14 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53E2F43D2D; Mon, 26 Jul 2004 17:43:14 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from pooker.samsco.org (scottl@localhost [127.0.0.1]) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6QHntIA082865; Mon, 26 Jul 2004 11:49:55 -0600 (MDT) (envelope-from scottl@freebsd.org) Received: from localhost (scottl@localhost)i6QHntrc082862; Mon, 26 Jul 2004 11:49:55 -0600 (MDT) (envelope-from scottl@freebsd.org) X-Authentication-Warning: pooker.samsco.org: scottl owned process doing -bs Date: Mon, 26 Jul 2004 11:49:55 -0600 (MDT) From: Scott Long Sender: scottl@pooker.samsco.org To: Brian Fundakowski Feldman In-Reply-To: <20040726152151.GC1473@green.homeunix.org> Message-ID: <20040726114142.E32601@pooker.samsco.org> References: <1090718450.2020.4.camel@illusion.com> <200407251112.46183.doconnor@gsoft.com.au> <20040726152151.GC1473@green.homeunix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org cc: bugghy Subject: Re: magic sysrq keys functionality X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 17:43:14 -0000 On Mon, 26 Jul 2004, Brian Fundakowski Feldman wrote: B> On Sun, Jul 25, 2004 at 09:23:36PM +0000, bugghy wrote: > > Yeah but it sometimes "freezes" (no reboot) ... and I'd rather umount my > > filesystems before rebooting. > > SoftUpdates guarantess that your file systems will not get corrupt. > This isn't entirely correct. Softupdates guarantees that you won't get corruption due to metadata pointing to invalid or stale data blocks. That's not the same as guaranteeing that there won't be any corruption. Write caching on the drive combined with an in-opportune power loss or other failure can easily leave you with corrupt or incomplete metadata and/or data blocks. A panic while metadata is being committed to disk can also leave the metadata highly inconsistent and prone to corruption. This isn't to say the SU is bad or that other strategies are necessarily better, just that there are definite risks. Scott