xfs
[Top] [All Lists]

Re: Corruption of in-memory data

To: Gorazd Golob <gorazd.golob@xxxxxxxxxxxx>
Subject: Re: Corruption of in-memory data
From: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 29 May 2006 08:22:34 +1000
Cc: xfs@xxxxxxxxxxx
In-reply-to: <1148832223.17036.34.camel@xxxxxxxxxxxxxxxxxx>; from gorazd.golob@xxxxxxxxxxxx on Sun, May 28, 2006 at 06:03:43PM +0200
References: <1148758234.16365.12.camel@xxxxxxxxxxxxxxxxxx> <1148832223.17036.34.camel@xxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
Hi,

On Sun, May 28, 2006 at 06:03:43PM +0200, Gorazd Golob wrote:
> hi!
> 
> I forgot to paste one line before that kernel msg;
> Whole message is:
> 
> [446868.954403] xfs_force_shutdown(sdb1,0x8) called from line 1031 of
> file fs/xfs/xfs_trans.c.  Return address = 0xffffffff802e7d5d
> [446868.995464] Filesystem "sdb1": Corruption of in-memory data
> detected.  Shutting down filesystem: sdb1
> [446869.000960] Please umount the filesystem, and rectify the problem(s)
> 
> On Sat, 2006-05-27 at 21:30 +0200, Gorazd Golob wrote:
> > Hi!
> > 
> > Anyone have idea what does that mean?
> > 
> > [376278.129936] Filesystem "sdb1": Corruption of in-memory data
> > detected.  Shutting down filesystem: sdb1
> > [376278.135533] Please umount the filesystem, and rectify the problem(s)

This is unfortuately a very generic "something went wrong"
sort of message - something, somewhere (could be in/outside
XFS) caused an error that caused a dirty transaction to have
to be cancelled, and thats fatal.

To answer your off-list mail, you might be able to remount
read-only and run repair with -d.

cheers.

-- 
Nathan


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