Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758044AbZDPRPQ (ORCPT ); Thu, 16 Apr 2009 13:15:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755463AbZDPRPA (ORCPT ); Thu, 16 Apr 2009 13:15:00 -0400 Received: from rcsinet13.oracle.com ([148.87.113.125]:30870 "EHLO rgminet13.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754737AbZDPRO7 (ORCPT ); Thu, 16 Apr 2009 13:14:59 -0400 Subject: Re: [PATCH RFC] ext3 data=guarded v3 From: Chris Mason To: Mike Galbraith Cc: Jan Kara , Linus Torvalds , "Theodore Ts'o" , Linux Kernel Developers List , Ext4 Developers List In-Reply-To: <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> <1239893771.4346.0.camel@think.oraclecorp.com> Content-Type: text/plain Date: Thu, 16 Apr 2009 13:12:56 -0400 Message-Id: <1239901977.4346.3.camel@think.oraclecorp.com> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1 Content-Transfer-Encoding: 7bit X-Source-IP: acsmt703.oracle.com [141.146.40.81] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A010207.49E76750.00BF:SCFMA4539814,ss=1,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1489 Lines: 40 On Thu, 2009-04-16 at 10:56 -0400, Chris Mason wrote: > 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. Ah ok, it is just a missed i_size update. Basically because file_write doesn't wait for page writeback to finish, someone can be updating i_size at the same time the end_io handler for the last page is running. Git triggers this when it does the sha1flush just before closing the file. I'm testing the fixes here, will resend in a little bit. Thanks! -chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/