From owner-freebsd-stable Wed Mar 14 8:38:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A659937B718; Wed, 14 Mar 2001 08:38:31 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA47422; Wed, 14 Mar 2001 08:36:47 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200103141636.IAA47422@gndrsh.dnsmgr.net> Subject: Re: Disk I/O problem in 4.3-BETA In-Reply-To: <200103141405.f2EE5Ks71827@aslan.scsiguy.com> from "Justin T. Gibbs" at "Mar 14, 2001 07:05:20 am" To: gibbs@scsiguy.com (Justin T. Gibbs) Date: Wed, 14 Mar 2001 08:36:47 -0800 (PST) Cc: bright@wintelcom.net (Alfred Perlstein), Helge.Oldach@de.origin-it.com (Helge Oldach), oberman@es.net, sos@freebsd.dk, mobile@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >First off, some disk caches are getting > 10megs, that's a lot > >of potnetial seeking after loosing power depending on the cache > >contents... > > I've heard that most modern drives reserve a contiguous area of the > disk the size of the cache near where the heads park to dump any > cache contents on power outage. This avoids most if not all seeking. > When the disk powers up again, the reserve track is read and the > transactions are written to the correct locations. Any disk that does > this should be safe to use with write caching enabled. As some one who has spent some time working with disk drive manufactures in the far past all sorts of work is done to make sure that the write cache is not a failure mechanism for lost data. Some of the designs include things like using the spindle motor as a generator and the inertia of the platters to drive it to insure the drive has adaquate power for a long enough period to flush any cached data. Other things done are in non-segmented write caches is to only cache write data for the current track (this is actually where the write cache does most of its good) and always flush it before doing any seek. Only broken WC designs loose data in a power out sitation. There are many broken designs out there. There are also many that work perfectly. The general tell tell on this is what state the WCE bit is in when the drive comes from the factory. Those manufactures who have good designs tend to ship with WCE on, those that tend to loose data always ship with WCE off. With the wonderful breakthroughs in supercapacitors it should now be possible to have some very large caches. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message