xfs
[Top] [All Lists]

Re: Corruption of in-memory data detected.

To: Marc Schmitt <schmitt@xxxxxxxxxxx>
Subject: Re: Corruption of in-memory data detected.
From: Steve Lord <lord@xxxxxxx>
Date: Tue, 23 Oct 2001 17:26:55 -0500
Cc: Steve Lord <lord@xxxxxxx>, Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx, florin@xxxxxxx
In-reply-to: Message from Marc Schmitt <schmitt@inf.ethz.ch> of "Wed, 24 Oct 2001 00:22:40 +0200." <3BD5EDB0.1A238C02@inf.ethz.ch>
Sender: owner-linux-xfs@xxxxxxxxxxx
> Hi Steve,
> 
> Steve Lord wrote:
> > 
> > Hmm, can you run xfs_repair -n on the filesystem (when unmounted) I
> > suspect there is something corrupted in there. You are shutting down
> > because xfs is cancelling a transaction which has already modified
> > metadata - this does not happen during normal operation.
> 
> Just to remind, mongo.pl always recreates the file system on /dev/md0
> (with 'mkfs.xfs -l size=32768b -f /dev/md0') before it starts creating
> files.
> Here is the output of 'xfs_repair -n /dev/md0':
> 

OK, that looked pretty toasty - I see this is a pretty big device too,
how big ? Can you also send the version of mkfs you are using, and
the raid configuration file. I was not aware you were using md until
now. Also, how many mongo threads are you running in parallel?

The reason I ask this is that you need a recent mkfs command if you are
using an fs bigger than 1 Tbyte, the xfs inode can overflow 32 bits if
you do not bump the inode size, a recent mkfs will do this automatically.

Steve





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