From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 22:01:01 2005 Return-Path: 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 3CD4C16A4CE for ; Sun, 24 Apr 2005 22:01:01 +0000 (GMT) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id A298443D1D for ; Sun, 24 Apr 2005 22:01:00 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (pD9542A59.dip.t-dialin.net [217.84.42.89]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 27FF934255; Mon, 25 Apr 2005 00:00:54 +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 j3OM0kx7028324; Mon, 25 Apr 2005 00:01:23 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Message-Id: <200504242201.j3OM0kx7028324@drjekyll.mkbuelow.net> From: Matthias Buelow To: Scott Long In-Reply-To: Message from Scott Long of "Sun, 24 Apr 2005 15:19:46 MDT." <426C0D72.9090707@samsco.org> X-Mailer: MH-E 7.82; nmh 1.0.4; GNU Emacs 21.3.1 Date: Mon, 25 Apr 2005 00:00:46 +0200 Sender: mkb@mkbuelow.net cc: stable@freebsd.org cc: Matthias Buelow cc: Palle Girgensohn Subject: Re: background_fsck=no does not work? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2005 22:01:01 -0000 Scott Long writes: >Whether or not its algoritms are correct or the VM and VFS layers >properly support it, modern IDE write caches pretty much make write >orderings a crapshoot. Well.. that can be countered somewhat by using a UPS for servers, or in areas where power is flakey. I'm more concerned about the software being correct, since the handful or so of filesystems I've lost over the years have always been due to software failure (usually some major f*ckup following a kernel panic that fsck couldn't repair...) mkb.