From owner-freebsd-questions@FreeBSD.ORG Tue Dec 1 08:54:40 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 657EA106568D for ; Tue, 1 Dec 2009 08:54:40 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (tunnel490.ipv6.xs4all.nl [IPv6:2001:888:10:1ea::2]) by mx1.freebsd.org (Postfix) with ESMTP id EEC198FC19 for ; Tue, 1 Dec 2009 08:54:39 +0000 (UTC) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.14.2/8.14.2) with ESMTP id nB18rITg091680; Tue, 1 Dec 2009 09:53:18 +0100 (CET) (envelope-from mail25@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.14.2/8.14.2/Submit) id nB18rIMg091679; Tue, 1 Dec 2009 09:53:18 +0100 (CET) (envelope-from mail25@bzerk.org) Date: Tue, 1 Dec 2009 09:53:18 +0100 From: Ruben de Groot To: James Phillips Message-ID: <20091201085318.GA88608@ei.bzerk.org> Mail-Followup-To: Ruben de Groot , James Phillips , Bruce Cran , freebsd-questions@freebsd.org References: <20091130215126.0000563c@unknown> <651489.2831.qm@web65515.mail.ac4.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <651489.2831.qm@web65515.mail.ac4.yahoo.com> User-Agent: Mutt/1.4.2.3i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (ei.bzerk.org [127.0.0.1]); Tue, 01 Dec 2009 09:53:21 +0100 (CET) Cc: Bruce Cran , freebsd-questions@freebsd.org Subject: Re: Phoronix Benchmarks: Waht's wrong with FreeBSD 8.0? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2009 08:54:40 -0000 On Mon, Nov 30, 2009 at 11:34:06PM -0800, James Phillips typed: > > > --- On Mon, 11/30/09, Bruce Cran wrote: > > > > > This is actually the way UFS/FFS works too: when my system > > was crashing > > fairly regularly I was a bit surprised to find empty files > > after > > editing them. > > > > Also, I just verified that saving a file, rebooting, > > editing it again > > (with ee(1)) and powering off the system does still result > > in a zero > > length file being on disk. > > > > Ok, good to know. > > I saw UFS corruption once with frequent restarts, but assumed that was because the "delayed filesystem checking" never had a chance to run. > > Since I don't have a UPS I guess backups are doubly important. Note that finding an empty file you had just been editing before a crash is NOT UFS corruption. It's data loss, probably caused by softupdates, which guarantees filesystem consistency in the case of a crash, but it can sometimes be up to a minute behind in actually writing the data blocks to the disk. Ruben