From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261903AbVGEQKJ (ORCPT ); Tue, 5 Jul 2005 12:10:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261928AbVGEQFn (ORCPT ); Tue, 5 Jul 2005 12:05:43 -0400 Received: from 66-23-228-155.clients.speedfactory.net ([66.23.228.155]:57498 "EHLO kevlar.burdell.org") by vger.kernel.org with ESMTP id S261903AbVGEPv3 (ORCPT ); Tue, 5 Jul 2005 11:51:29 -0400 Date: Tue, 5 Jul 2005 11:49:19 -0400 From: Sonny Rao To: Al Boldi Cc: "'Jens Axboe'" , "'David Masover'" , "'Chris Wedgwood'" , "'Nathan Scott'" , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, reiserfs-list@namesys.com Subject: Re: XFS corruption during power-blackout Message-ID: <20050705154919.GA13262@kevlar.burdell.org> Mail-Followup-To: Sonny Rao , Al Boldi , 'Jens Axboe' , 'David Masover' , 'Chris Wedgwood' , 'Nathan Scott' , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, reiserfs-list@namesys.com References: <20050701092412.GD2243@suse.de> <200507011405.RAA27425@raad.intranet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200507011405.RAA27425@raad.intranet> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 01, 2005 at 05:05:11PM +0300, Al Boldi wrote: > Jens Axboe wrote: { > On Fri, Jul 01 2005, David Masover wrote: > > Chris Wedgwood wrote: > > >On Wed, Jun 29, 2005 at 07:53:09AM +0300, Al Boldi wrote: > > > > > > > > >>What I found were 4 things in the dest dir: > > >>1. Missing Dirs,Files. That's OK. > > >>2. Files of size 0. That's acceptable. > > >>3. Corrupted Files. That's unacceptable. > > >>4. Corrupted Files with original fingerprint. That's ABSOLUTELY > > >>unacceptable. > > > > > > > > >disk usually default to caching these days and can lose data as a > > >result, disable that > > > > Not always possible. Some disks lie and leave caching on anyway. > > And the same (and others) disks will not honor a flush anyways. > Moral of that story - avoid bad hardware. > } > > 1. Sync is not the issue. The issue is whether a journaled FS can detect > corrupted files and flag them after a power-blackout! Journaling implies filesystem consistency, not data integrity, AFAIK. > 2. Moral of the story is: What's ext3 doing the others aren't? Ext3 has stronger guaranties than basic filesystem consistency. I.e. in ordered mode, file data is always written before metadata, so the worst that could happen is a growing file's new data is written but the metadata isn't updated before a power failure... so the new writes wouldn't be seen afterwards. You should try the same test w/ ext3 in "writeback" mode and see if it fares better or worse in terms of file corruption. Sonny