[Top] [All Lists]

Re: Corruption of in-memory data

To: Matteo Centonza <matteo@xxxxxx>
Subject: Re: Corruption of in-memory data
From: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 5 Nov 2002 11:37:59 +0100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.44.0211050946080.15770-100000@quasar.sif.it>; from matteo@sif.it on Tue, Nov 05, 2002 at 11:09:20 +0100
References: <Pine.LNX.4.44.0211050946080.15770-100000@quasar.sif.it>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On 05 Nov 2002 11:09:20 Matteo Centonza wrote:

i get this message and subsequent filesystem shutdown using
CVS from 20021031-09:47 (CET):

Nov 4 15:07:00 embeh kernel: xfs_force_shutdown(lvm(58,3),0x8) called from
line 1042 of file xfs_trans.c.  Return address = 0xc01e2c17
Nov 4 15:07:00 embeh kernel: Filesystem "lvm(58,3)": Corruption of
in-memory data detected.  Shutting down filesystem: lvm(58,3)

The problem with the two stacked layer (LVM+RAID5) seems to have gone
away (see bug 182). I tend to exclude a memory problem here given that the
machine ran fine (with XFS 1.1) before trying the new kernel.

After the fs shutdown, the machine was rebooted and the bare recovery made
the trick. The subsequent xfs_check showed no problems (so the xfs_repair
-n). The same problem happened  5 hours later to the same filesystem (out
of 10 this machine exports).


assuming this machine acts as nfsserver?
Then it might be related to BUG #186...



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