From owner-freebsd-stable@FreeBSD.ORG Sat Jul 16 17:26:20 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 7B49016A420 for ; Sat, 16 Jul 2005 17:26:20 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id E81DD43D48 for ; Sat, 16 Jul 2005 17:26:19 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (p54AA8609.dip0.t-ipconnect.de [84.170.134.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id F1AE2323E4; Sat, 16 Jul 2005 19:29:10 +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 j6GHQWYw001806; Sat, 16 Jul 2005 19:26:32 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j6GHQWOF001805; Sat, 16 Jul 2005 19:26:32 +0200 (CEST) (envelope-from mkb) Date: Sat, 16 Jul 2005 19:26:32 +0200 From: Matthias Buelow To: Lowell Gilbert Message-ID: <20050716172632.GG752@drjekyll.mkbuelow.net> References: <20050715224650.GA48516@outcold.yadt.co.uk> <200507152342.j6FNg5Tx015427@drjekyll.mkbuelow.net> <20050716133710.GA71580@outcold.yadt.co.uk> <20050716141630.GB752@drjekyll.mkbuelow.net> <1121530912.17757.32.camel@zappa.Chelsea-Ct.Org> <44k6jqof72.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44k6jqof72.fsf@be-well.ilk.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process 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: Sat, 16 Jul 2005 17:26:20 -0000 Lowell Gilbert wrote: >Well, break it down a little bit. If an ATA drive properly implements >the cache flush command, then none of the ongoing discussion is Are you sure this is the case? Are there sequence points in softupdates where it issues a flush request and by this guarantees fs integrity? I've read thru McKusick's paper in search for an answer but haven't found any. All I've read so far on mailing lists and from googling was that softupdates doesn't work if the wb-cache is enabled. mkb.