From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263692AbUE1Qm7 (ORCPT ); Fri, 28 May 2004 12:42:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263697AbUE1Qm7 (ORCPT ); Fri, 28 May 2004 12:42:59 -0400 Received: from ned.cc.purdue.edu ([128.210.189.24]:19621 "EHLO ned.cc.purdue.edu") by vger.kernel.org with ESMTP id S263692AbUE1Qm5 (ORCPT ); Fri, 28 May 2004 12:42:57 -0400 From: Pat To: Chris Mason Subject: Re: filesystem corruption (ReiserFS, 2.6.6): regions replaced by \000 bytes Date: Fri, 28 May 2004 11:42:54 -0500 User-Agent: KMail/1.5.4 References: <20040528122854.GA23491@clipper.ens.fr> <20040528162450.GE422@louise.pinerecords.com> <1085761753.22636.3329.camel@watt.suse.com> In-Reply-To: <1085761753.22636.3329.camel@watt.suse.com> Cc: linux-kernel@vger.kernel.org, David Madore MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200405281142.54299.finnegpt@purdue.edu> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Friday 28 May 2004 11:29, Chris Mason wrote: > On Fri, 2004-05-28 at 12:24, Tomas Szepe wrote: > > On May-28 2004, Fri, 08:46 -0400 > > > > Chris Mason wrote: > > > > The bottom line: I've experienced file corruption, of the > > > > following nature: consecutive regions (all, it seems, aligned > > > > on 256-byte boundaries, and typically around 1kb or 2kb in > > > > length) of seemingly random files are replaced by null bytes. > > > > > > The good news is that we tracked this one down recently. > > > 2.6.7-rc1 shouldn't do this anymore. > > > > So did this only affect SMP machines? > > No, if you slept in the right spot you could hit it on UP. I saw this once when using 2.6.6, it was messing up the filesystem structures as well (ext2 & ext3), replacing mostly with nulls, some with random letters and numbers, for 4-6 character lengths, and not on any nice boundaries. Since I stopped trying to use the ATI framebuffer driver (this is on a 21164A alpha, 164LX motherboard, ATI Mach64 CT video), it seems to have stopped. Also, I noticed that the framebuffer driver didn't work so well. 2.6.7-rc1 seems to have a compile error for alpha as well, I'll post that in a separate email. Pat -- PLUG Vice President -- http://plug.purdue.org The Computer Refuge -- http://computer-refuge.org Purdue University Research Computing -- http://www.itap.purdue.edu/rcs