xfs
[Top] [All Lists]

Re: Corruption of in-memory data detected.

To: Steve Lord <lord@xxxxxxx>
Subject: Re: Corruption of in-memory data detected.
From: Utz Lehmann <ulehmann@xxxxxxxxxxxxxx>
Date: Thu, 25 Oct 2001 15:36:27 +0200
Cc: Marc Schmitt <schmitt@xxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx, florin@xxxxxxx
In-reply-to: <200110251212.f9PCC5e08949@xxxxxxxxxxxxxxxxxxxx>; from lord@xxxxxxx on Thu, Oct 25, 2001 at 07:12:05AM -0500
References: <200110242032.f9OKWPk32359@xxxxxxxxxxxxxxxxxxxx> <3BD800FC.6020005@xxxxxxxxxxx> <200110251212.f9PCC5e08949@xxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.3.12i
Hi Steve

Steve Lord [lord@xxxxxxx] wrote:
> 
> OK, so the next possibility is the fact that xfs is setting the block
> size of the device to 512 bytes and that pushes some calculations over.
> I am experimenting with some new code in 2.4.13 which removes this
> chunk of code, the next thing to try may be this, I am running md
> tests on it this morning and so far it looks good, but I do not
> have access to enough disk to test for the size overflow.

Maybe you can use a 1.2TB hole loop mounted.


dd if=/dev/null of=loopfile bs=1024 seek=1288490188
mkfs.xfs loopfile 
mount -o loop loopfile /xxx/


I made this, and copy the kernel sources into /xxx/ and got the same errors
like Marc:

Oct 25 14:54:18 donner kernel: xfs_force_shutdown(loop(7,0),0x8) called from 
line 1020 of file xfs_trans.c.  Return address = 0xc01b4d15
Oct 25 14:54:18 donner kernel: Corruption of in-memory data detected.  Shutting 
down filesystem: loop(7,0)


With 0.98TB no errors occured except one time my machine run out of memory.

Kernel is 2.4.13-pre6-xfs-20011023 + preempt patch.


utz


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