From owner-freebsd-mobile Tue Mar 13 1: 7:34 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id F195037B718; Tue, 13 Mar 2001 01:07:27 -0800 (PST) (envelope-from Helge.Oldach@de.origin-it.com) Received: from mail.de.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id KAA26098; Tue, 13 Mar 2001 10:07:15 +0100 (MET) (envelope-from Helge.Oldach@de.origin-it.com) Received: from smtprelay-de1.origin-it.com(172.16.188.53) by gw-nl1.origin-it.com via mwrap (4.0a) id xma026082; Tue, 13 Mar 01 10:07:19 +0100 Received: from mailhub.de.origin-it.com (mailhub.de.origin-it.com [172.16.189.20]) by mail.de.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id KAA01308; Tue, 13 Mar 2001 10:07:12 +0100 (MET) Received: from galaxy.de.cp.philips.com (galaxy.de.cp.philips.com [130.143.166.29]) by mailhub.de.origin-it.com (8.11.2/8.11.2/hmo23oct00) with ESMTP id f2D975G94966; Tue, 13 Mar 2001 10:07:06 +0100 (CET) (envelope-from Helge.Oldach@de.origin-it.com) Received: (from hmo@localhost) by galaxy.de.cp.philips.com (8.9.3/8.9.3/hmo14aug98) id KAA08943; Tue, 13 Mar 2001 10:07:04 +0100 (MET) Message-Id: <200103130907.KAA08943@galaxy.de.cp.philips.com> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <20010313005811.J29888@fw.wintelcom.net> from Alfred Perlstein at "Mar 13, 2001 0:58:11 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 13 Mar 2001 10:07:03 +0100 (MET) Cc: oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG From: Helge Oldach X-Address: Atos Origin GmbH, Billstrasse 80, D-20539 Hamburg, Germany X-Phone: +49 40 7886 464, Fax: +49 40 7886 235, Mobile: +49 160 4782517 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alfred Perlstein: >* Helge Oldach [010313 00:48] wrote: >> Alfred Perlstein: >> >If basically running with blind write caching turned on is akin to >> >running your filesystem in async mode. This is because write >> >caching gives the drive license to lie about completing a write, >> >the various ordering of writes are effectively bypassed. If you >> >crash without these dependancies actually written to the disk, when >> >you come back up you have a good chance of losing large portions >> >of your filesystem. >> >> I'd say this is a bit too pessimistic. There is a fundamental difference >> between softupdates and ATA write-cacheing: Softupdates holds the async >> data in main RAM while ATA write-cacheing already has it in the (cache >> memory of the) disk device. >> >> Obviously a power outage would affect both situations in a similar way. >> But during just an operating system crash (assuming power stays up), >> one should be better off with ATA write-cacheing, as the disk should be >> able to dump the data from the cache chips to the physical medium. With >> softupdates async data is just lost. >> >> Generally I'd say it's not a bad idea to have write caching on the disk >> enabled - assuming that it is decently implemented. BTW, don't SCSI >> disks use write cacheing as well? :-) > >I'm pretty sure you're wrong. I think you misunderstood my argument. Agreed, there is practically no difference in the damage done to softupdates versus write-cacheing during a power outage. But there should be a difference when the OS dies away while power stays up. The OS dying away means that the disk has lots of time to spill out the cached data to the physical medium as it's no longer banged at high data rates by the host. So at least in theory we should be better off in this situation. >I'm not 100% certain, but many people working with embedded systems >have explained to me that it's no longer safe to assume that write >cached data will be sync'd to the disk's media at crash time. That may be correct. But then this breaks my naive understanding of "write caching"... And again: Isn't write-cacheing turned on on SCSI disks? :-) Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message