From owner-freebsd-stable Fri Sep 21 12:38:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 2BB4237B41E for ; Fri, 21 Sep 2001 12:38:28 -0700 (PDT) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15kW4J-0006Du-00; Sat, 22 Sep 2001 07:34:35 +1200 Date: Sat, 22 Sep 2001 07:34:34 +1200 (NZST) From: Juha Saarinen To: j mckitrick Cc: Matt Dillon , Mike Meyer , Daniel O'Connor , Kevin Oberman , "stable@freebsd.org" Subject: Re: RE: hw.ata.wc && hw.ata.tags && softupdates short question In-Reply-To: <20010921185411.C81649@dogma.freebsd-uk.eu.org> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Sep 2001, j mckitrick wrote: > We've been told write caching turned OFF causes a huge performance > hit, but ON can cause data loss. Yes, it's a big performance hit, and no, it's not write caching by itself that causes data loss. Data loss happens during system failures that prevent the drive from writing out the contents of the cache to disk. Microsoft had this problem with newer IDE drives (which have 2MB+ caches), and I think Windows 9x, during shutdown (the OS didn't wait long enough before "flipping the switch" so to speak). Think the patch issued forced a cache writeout before shutdown... It's worth querying the manufacturer of your drive to find out what (if any) mechanisms have been implemented to ensure that the cache is written out if power is suddenly removed. Some drives (IBM I believe) use large capacitors to store enough energy to write out the cache to disk. -- Regards, Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message