Messages in this thread | | | Subject | Re: filesystem corruption (ReiserFS, 2.6.6): regions replaced by \000 bytes | From | Chris Mason <> | Date | Fri, 28 May 2004 12:54:55 -0400 |
| |
On Fri, 2004-05-28 at 12:42, Pat wrote: > 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 <mason@suse.com> 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. > This is different. The reiserfs bug can only trigger data corruptions in reiserfs, and won't trigger metadata problems.
-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/
| |