Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753446AbYFTIKY (ORCPT ); Fri, 20 Jun 2008 04:10:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751702AbYFTIKF (ORCPT ); Fri, 20 Jun 2008 04:10:05 -0400 Received: from dwdmx4.dwd.de ([141.38.3.230]:60548 "EHLO dwdmx4.dwd.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751548AbYFTIKB (ORCPT ); Fri, 20 Jun 2008 04:10:01 -0400 Date: Fri, 20 Jun 2008 08:09:59 +0000 (GMT) From: Holger Kiehl X-X-Sender: kiehl@diagnostix.dwd.de To: Theodore Tso Cc: "Aneesh Kumar K.V" , Jan Kara , Solofo.Ramangalahy@bull.net, Nick Dokos , linux-ext4@vger.kernel.org, linux-kernel Subject: Re: Performance of ext4 In-Reply-To: <20080619155645.GA8582@mit.edu> Message-ID: References: <18513.345.553912.449710@frecb006361.adech.frec.bull.fr> <20080612131928.GB18229@mit.edu> <20080612180605.GD22481@skywalker> <20080616175408.GF3279@atrey.karlin.mff.cuni.cz> <20080616181353.GA20686@skywalker> <20080619155645.GA8582@mit.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1351 Lines: 35 On Thu, 19 Jun 2008, Theodore Tso wrote: > On Tue, Jun 17, 2008 at 11:42:36AM +0000, Holger Kiehl wrote: >> Note how the size of file results.24033.helena.dwd.de changes from >> 9230 before the test to 8208 bytes after the test. Also note the >> date both have the same timestamp "2008-06-17 04:35". I have made a >> copy of results.24033.helena.dwd.de before the test and compared it >> with that after the test. The file is just truncated by 1022 bytes >> and there is no garbage. > > So the corruption is always a truncation, correct? > Correct. > Did you notice the problem with ext4 w/o the patch queue? > No, without patch queue it I did not not notice the problem. > I have a > suspicion that the problem may have been introduced by the delayed > allocation code, but I don't have hard evidence. When you rerun your > benchmark (which seems to be the closest thing we have to a > reproduction case), it would be interesting to know if the problem > goes away with -o nodelalloc (again, it would localize where we need > to look). > Ok I will do thats soon as I have a system available. Holger -- 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/