Subject: Re: 2.6.19 file content corruption on ext3
From: Mike Galbraith <efault@gmx.de>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20061208164206.GA1125@torres.l21.ma.zugschlus.de>
References: <20061207155740.GC1434@torres.l21.ma.zugschlus.de>
	 <4578465D.7030104@cfl.rr.com>
	 <1165541892.1063.0.camel@sebastian.intellilink.co.jp>
	 <20061208164206.GA1125@torres.l21.ma.zugschlus.de>
Content-Type: text/plain; charset=ISO-8859-1
Date: Sun, 10 Dec 2006 00:46:01 +0100
Message-Id: <1165707961.4926.21.camel@Homer.simpson.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 963
Lines: 27

On Fri, 2006-12-08 at 17:42 +0100, Marc Haber wrote:
> On Fri, Dec 08, 2006 at 10:38:12AM +0900, Fernando Luis V?zquez Cao wrote:
> > Does the patch below help?
> > 
> > http://marc.theaimsgroup.com/?l=linux-ext4&m=116483980823714&w=4
> 
> No, pkgcache.bin still getting corrupted within two hours of using
> 2.6.19.
> 
> Greetings
> Marc, back to 2.6.18.3 for the time being

Hi,

I've missed most of this thread, but have cause to be interested.  Do
you have a generic recipe for reproducing file corruption?  I seem to be
(read pretty darn sure, modulus hw (wish) vs sw testing methods...)
experiencing memory corruption problems with 2.6.19, and am interested
in anything that might be related (trigger!).

	-Mike

-
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/