From owner-freebsd-current@FreeBSD.ORG Tue Sep 30 23:39:53 2003 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 4FA3516A4BF for ; Tue, 30 Sep 2003 23:39:53 -0700 (PDT) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9141C43FDF for ; Tue, 30 Sep 2003 23:39:51 -0700 (PDT) (envelope-from rehsack@liwing.de) Received: (qmail 35962 invoked from network); 1 Oct 2003 06:39:47 -0000 Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164]) (envelope-sender ) by mail.liwing.de (qmail-ldap-1.03) with SMTP for ; 1 Oct 2003 06:39:47 -0000 Message-ID: <3F7A76B3.6080508@liwing.de> Date: Wed, 01 Oct 2003 06:39:47 +0000 From: Jens Rehsack User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030928 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20030930221148.54E7E5D07@ptavv.es.net> In-Reply-To: <20030930221148.54E7E5D07@ptavv.es.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Improvements to fsck performance in -current ...? 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: Wed, 01 Oct 2003 06:39:53 -0000 Kevin Oberman wrote: [...] > Current has two major changes re speeding up fsck. > > The most significant is the background operation of fsck on file > system with soft updates enabled. Because of the way softupdates > works, you are assured of metadata consistency on reboot, so the file > systems can be mounted and used immediately with fsck started up in > the background about a minute after the system comes up. Be careful what you promise :-) Most new disks have an own disk cache and some of them have a write cache enabled. In case of a hardware failure (or power failure) this data may get lost and the disk's metadata isn't consistent. It's only when no write cache below the system is active. Jens