From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932377AbWLSANS (ORCPT ); Mon, 18 Dec 2006 19:13:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932465AbWLSANS (ORCPT ); Mon, 18 Dec 2006 19:13:18 -0500 Received: from [85.204.20.254] ([85.204.20.254]:41970 "EHLO megainternet.ro" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S932377AbWLSANR (ORCPT ); Mon, 18 Dec 2006 19:13:17 -0500 Subject: Re: 2.6.19 file content corruption on ext3 From: Andrei Popa Reply-To: andrei.popa@i-neo.ro To: Linus Torvalds Cc: Alessandro Suardi , Peter Zijlstra , Andrew Morton , Linux Kernel Mailing List , Hugh Dickins , Florian Weimer , Marc Haber , Martin Michlmayr In-Reply-To: References: <1166314399.7018.6.camel@localhost> <1166466272.10372.96.camel@twins> <1166468651.6983.6.camel@localhost> <1166471069.6940.4.camel@localhost> <1166476297.6862.1.camel@localhost> <5a4c581d0612181400t347fc9efx69e55efb3ef40c45@mail.gmail.com> Content-Type: text/plain Organization: I-NEO Date: Tue, 19 Dec 2006 02:13:11 +0200 Message-Id: <1166487191.6869.1.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2006-12-18 at 14:45 -0800, Linus Torvalds wrote: > > On Mon, 18 Dec 2006, Alessandro Suardi wrote: > > > > No idea whether this can be a data point or not, but > > here it goes... my P2P box is about to turn 5 days old > > while running nonstop one or both of aMule 2.1.3 and > > BitTorrent 4.4.0 on ext3 mounted w/default options > > on both IDE and USB disks. Zero corruption. > > > > AMD K7-800, 512MB RAM, PREEMPT/UP kernel, > > 2.6.19-git20 on top of up-to-date FC6. > > It _looks_ like PREEMPT/SMP is one common configuration. > > It might also be that the blocksize of the filesystem matters. 4kB > filesystems are fundamentally simpler than 1kB filesystems, for example. > You can tell at least with "/sbin/dumpe2fs -h /dev/..." or something. > > Andrei - one thing that might be interesting to see: when corruption > occurs, can you get the corrupted file somehow? And compare it with a > known-good copy to see what the corruption looks like? the corrupted file has a chink full with zeros http://193.226.119.62/corruption0.jpg http://193.226.119.62/corruption1.jpg