From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261945AbVGER2P (ORCPT ); Tue, 5 Jul 2005 13:28:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261941AbVGER2E (ORCPT ); Tue, 5 Jul 2005 13:28:04 -0400 Received: from [212.76.86.91] ([212.76.86.91]:1028 "EHLO raad.intranet") by vger.kernel.org with ESMTP id S261933AbVGER1r (ORCPT ); Tue, 5 Jul 2005 13:27:47 -0400 Message-Id: <200507051725.UAA07417@raad.intranet> From: "Al Boldi" To: "'Sonny Rao'" Cc: "'Jens Axboe'" , "'David Masover'" , "'Chris Wedgwood'" , "'Nathan Scott'" , , , , Subject: RE: XFS corruption during power-blackout Date: Tue, 5 Jul 2005 20:25:11 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <20050705154919.GA13262@kevlar.burdell.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Thread-Index: AcWBeOboEysnS0HNSRenkfASCK84rQADFsog Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Sonny Rao 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. > > > > 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. } Sonny, Thanks for you input! Is there an option in XFS,ReiserFS,JFS to enable ordered mode?