From: Chris Mason Subject: Re: [PATCH RFC] ext3 data=guarded v3 Date: Thu, 16 Apr 2009 10:56:11 -0400 Message-ID: <1239893771.4346.0.camel@think.oraclecorp.com> References: <1239816159-6868-1-git-send-email-chris.mason@oracle.com> <1239881953.20254.17.camel@marge.simson.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Jan Kara , Linus Torvalds , "Theodore Ts'o" , Linux Kernel Developers List , Ext4 Developers List To: Mike Galbraith Return-path: Received: from acsinet11.oracle.com ([141.146.126.233]:43653 "EHLO acsinet11.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754240AbZDPPeU (ORCPT ); Thu, 16 Apr 2009 11:34:20 -0400 In-Reply-To: <1239881953.20254.17.camel@marge.simson.net> Sender: linux-ext4-owner@vger.kernel.org List-ID: On Thu, 2009-04-16 at 13:39 +0200, Mike Galbraith wrote: > On Wed, 2009-04-15 at 13:22 -0400, Chris Mason wrote: > > Hello everyone, > > Greetings, > > > This passed a longer stress test and generally seems to be working. I > > don't think anyone would recommend it as a default for 2.6.30, but it > > may be a good idea to have a review party and decide if it is safe enough > > to include so people can experiment with it. > > I know you didn't say RFT, but I did some anyway, and found a 100% > repeatable corruption scenario wrt git+umount. > Well, that's a surprise. I can trigger it here too, trying to figure out how this is different from the fsx and fsstress hammering. It looks like git is just going good old fashioned writes, so I must be losing one or two of them. -chris