From owner-freebsd-mobile@FreeBSD.ORG Tue May 27 14:50:15 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF56137B404 for ; Tue, 27 May 2003 14:50:15 -0700 (PDT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D82443F75 for ; Tue, 27 May 2003 14:50:14 -0700 (PDT) (envelope-from metrol@metrol.net) Received: from metlap (adsl-67-121-60-9.dsl.anhm01.pacbell.net [67.121.60.9]) h4RLo93T137146; Tue, 27 May 2003 17:50:09 -0400 From: Michael Collette To: "Kevin Oberman" Date: Tue, 27 May 2003 14:49:21 -0700 User-Agent: KMail/1.5.2 References: <20030527211912.751165D04@ptavv.es.net> In-Reply-To: <20030527211912.751165D04@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305271449.21525.metrol@metrol.net> cc: FreeBSD Mailing Lists Subject: Re: When do files syncronize? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 21:50:16 -0000 On Tuesday 27 May 2003 02:19 pm, Kevin Oberman wrote: > You now know exactly why there is a strong recommendation that write > cache be disabled on boxes that are subject to power failure. Files are > synced just fine, but that only gets updates to the write cache. There > is no way of being sure just when the data will actually get written to > the disk and, if the system loses power, the answer is never. This also > screws up write ordering needed by soft updates to make sure that the > metadata stays consistent. > > You case is a "worst case" in that you had probably just updated this > file and the metadata for it was still queued up. You sent it off to > sleep, which spin down the disk. Since the metadata was never updated, > the file ceased to exist (even though all of the data had probably made > it to the disk). I just had me a REAL hard lesson in that. I now have a nice clean KMail configuration though! :) Nothing like a total wipeout to provide some set aside time for a little clean up. > The cost of turning off write cache is high. I have demonstrated a factor > of 8 slow-down for dd with write cache disabled. So far, it's just barely noticeable that anything has changed. It's just a wee bit sluggish is all. What I have yet to do is compile or install anything since I made this change. Ack! That's that, I'm never going to upgrade KDE again! :( > A possible alternative is to make sure that you wait a minute after > terminating use of the system before suspending, Not exactly a reassuring method. > Another is to do a > hibernate instead of a suspend. This will write all of you memory to > disk before turning off. (This also cuts battery use as the system is > REALLY off when you hibernate.) You will need to create a hibernation > slice on your hard disk to do this. A utility to create it is available > from the IBM web site. http://www.pc.ibm.com/qtechinfo/MIGR-4PESMK.html Many thanks to you and Dave Tweten for that link. Sounds like a full system reinstall to get that slice in play. I'm assuming that it won't just go about adjusting partitions already in play. Good or bad assumption? Ah well, worse case scenario is I wait for 5 to hit stable and run through a clean install. Might even be fun to load Windows on here again in the interim to ease getting all the bios updates on there. That, and for the sheer joy of removing Windows :) Later on, -- "Always listen to experts. They'll tell you what can't be done, and why. Then do it." - Robert A. Heinlein