From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 18:59:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2F2816A420; Mon, 29 Aug 2005 18:59:39 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51F4443D46; Mon, 29 Aug 2005 18:59:39 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id F23B635876; Mon, 29 Aug 2005 21:02:26 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7TIxZxn002888; Mon, 29 Aug 2005 20:59:35 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7TIxYE5002887; Mon, 29 Aug 2005 20:59:34 +0200 (CEST) (envelope-from mkb) Date: Mon, 29 Aug 2005 20:59:33 +0200 From: Matthias Buelow To: Don Lewis Message-ID: <20050829185933.GB1462@drjekyll.mkbuelow.net> References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508291836.j7TIaVEk013147@gw.catspoiler.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, dinom@balstonresearch.com, markir@paradise.net.nz Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 18:59:39 -0000 Don Lewis wrote: >> I'd like to stress the "probably". I've already seen unrepairable >> filesystem corruption with softupdates enabled in the past with >> "good" scsi disks at power loss. > >Did you remember to disable write caching by setting the WCE mode page >bit to zero? At least with SCSI, it doesn't seem to affect performance >under most workloads. No.. I thought that with SCSI it is "ok" to leave the cache enabled because SCSI supports some sort of request queueing which doesn't break the order established by softupdates? >I've seen this when doing compile, run, panic experiments. The >executable that I just compiled would end up with a size of zero after >the reboot because it was still cached in RAM and executing from RAM >when the machine paniced. The executable was scheduled to be written to >disk about 30 seconds after it was compiled and linked, but the machine >paniced before the 30 seconds was up. Yes, that would account for the 0-size files but not for ones that got deleted by background fsck, with it logging "UNREF FILE" messages (and that were files that have definitely NOT had directory entries removed since amongst those were dot-files in my homedir, which I had to restore from backup then, and some others where I have not yet found out which they were..) >Softupdates only tries to guarantee that the on-disk file system is in a >consistent state at all times, with the possible exception that not all >space may be accounted for. It doesn't try very hard, though, nor is it very successful. mkb.