From owner-freebsd-stable@FreeBSD.ORG Tue Nov 28 21:41:23 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ADC6416A551 for ; Tue, 28 Nov 2006 21:41:23 +0000 (UTC) (envelope-from chris@vindaloo.com) Received: from corellia.vindaloo.com (corellia.vindaloo.com [64.51.148.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 179C343CAB for ; Tue, 28 Nov 2006 21:41:18 +0000 (GMT) (envelope-from chris@vindaloo.com) Received: from yavin.vindaloo.com (yavin.vindaloo.com [172.24.144.34]) by corellia.vindaloo.com (Postfix) with ESMTP id 08DE45C4C; Tue, 28 Nov 2006 16:41:22 -0500 (EST) Received: from dagobah.vindaloo.com (dagobah.vindaloo.com [172.24.145.68]) by yavin.vindaloo.com (Postfix) with ESMTP id 8A548253A4; Tue, 28 Nov 2006 16:41:21 -0500 (EST) Received: from localhost.vindaloo.com (localhost.vindaloo.com [IPv6:::1]) by dagobah.vindaloo.com (8.13.8/8.13.8) with ESMTP id kASLfCI9001301; Tue, 28 Nov 2006 16:41:12 -0500 (EST) (envelope-from chris@vindaloo.com) From: Christopher Sean Hilton To: Kevin Oberman In-Reply-To: <20061128195138.6B09C45096@ptavv.es.net> References: <20061128195138.6B09C45096@ptavv.es.net> Content-Type: text/plain Date: Tue, 28 Nov 2006 16:41:11 -0500 Message-Id: <1164750071.1074.39.camel@dagobah.vindaloo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Problems unmounting/fssyncking extern UFS filesystem 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: Tue, 28 Nov 2006 21:41:23 -0000 On Tue, 2006-11-28 at 11:51 -0800, Kevin Oberman wrote: [ ... ] > The magic phrase is "buffer cache has been flushed". In the real world > of discs with cache there is no way to be certain when the data is > REALLY on the disc. That is why things get clobbered if the power is > cycled to the disc too soon after syncing and why a sleep (or typing > sync three times) is still a good idea and probably always will be. > Please understand that this is an honest question but isn't that true only of IDE heritage drives. E.g. If a SCSI drive with Tagged Queuing says that the the bits have been written doesn't it mean that the bits have really been written? -- Chris