xfs
[Top] [All Lists]

Re: Corruption of in-memory data detected.

To: Jan Derfinak <ja@xxxxxxxxxxxx>
Subject: Re: Corruption of in-memory data detected.
From: evilninja <evilninja@xxxxxxx>
Date: Fri, 09 Sep 2005 20:01:01 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.0509082156530.9425@xxxxxxxxxxxxxxxxxx>
References: <Pine.LNX.4.58.0509082156530.9425@xxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720)
Jan Derfinak schrieb:
> Helo.
> 
> I switched from older SGI CVS kernel (2.6.12) to current SGI CVS kernel on
> two systems (i386 and x86_64). But after some time ( <12 hours) on both
> systems appeared "Corruption of in-memory data detected." error. I attached
> /var/log/messages log from i386 system. In both cases I was unable to umount 
> FS
> nor did clear shutdown. Both systems are workstation with very little load.
> 
> Sep  7 00:08:26 alien kernel: Filesystem "hda10": xfs_iflush: Bad inode 
> 34351857 magic number 0x2f6c, ptr 0xcc580100
> Sep  7 00:08:26 alien kernel: xfs_force_shutdown(hda10,0x8) called from line 
> 3294 of file fs/xfs/xfs_inode.c.  Return address = 0xc02350fc
> Sep  7 00:08:26 alien kernel: Filesystem "hda10": Corruption of in-memory 
> data detected.  Shutting down filesystem: hda10

...and when you switch back to 2.6.12 it does not happen again? did you
run memtest86+ overnight? i don't know about the xfs cvs repos of the
kernel, but perhaps you can narrow it down a little bit (if xfs' cvs tree
is in heavy flux, then this could be difficult, especially when the error
occurs after 12h...)

-- 
BOFH excuse #210:

We didn't pay the Internet bill and it's been cut off.


<Prev in Thread] Current Thread [Next in Thread>